1. Controller and scope
Desarrollo de Aplicaciones Móviles Franco Alexander Ayala Palma E.I.R.L., operating as FayalApps ("we"), is responsible for the processing described in this policy. Contact us at fayalapps@gmail.com.
This policy covers the launch version of RiderSense: accounts, lessons, visual training, learning progress, My Garage, reminders and subscriptions. We will update it if the service or its providers change materially.
2. Information we process
Depending on the features you use, we may process:
- Account and identity: your name or profile identifier, email address, technical user ID and sign-in provider, including Apple or Google.
- Preferences and learning: onboarding answers, language and units, completed lessons, training sessions, results, scores, levels, achievements and educational progress.
- My Garage: motorcycle make, model, year, mileage, maintenance history and notes you enter. Profile and motorcycle photos are optional and are selected or captured by you.
- Device and usage: notification tokens when you allow notifications, app and operating system versions, limited interaction events, crash reports, performance information and technical diagnostics used for security, stability and service improvement.
- Subscriptions: access status, purchased products and purchase or restoration events. App Store or Google Play processes payments; RiderSense does not receive or store your complete payment card number.
3. How we use information
We use information to create and protect your account, synchronize progress across devices, provide the content and tools you select, operate My Garage, manage Premium access, answer support requests, deliver authorized reminders and detect failures or abuse.
We do not sell your personal information or use it for behavioral advertising. Your learning and Garage information is not published as public content in RiderSense.
4. Permissions and notifications
Camera or photo access is requested only when you choose to add a photo. Notification permission is requested for reminders; you can disable notifications in RiderSense or your device settings. The app features described here do not use GPS location. Google Analytics may derive approximate location from a masked IP address for usage statistics; this does not use device location services.
5. Providers and international processing
RiderSense uses Google Firebase for authentication, synchronization, private storage, notifications, analytics and diagnostics; Apple and Google for sign-in; RevenueCat for subscription access; and App Store or Google Play for payments. These providers process information under their own terms and may host or process it outside Chile.
We share information with providers needed to deliver the relevant feature, with authorities when legally required, or with your authorization. We do not authorize providers to use your information for their own purposes incompatible with providing the service.
6. Retention and security
We retain information while your account is active or as needed to provide the service, resolve issues, prevent fraud, meet legal obligations or handle disputes. Deleted photos and records are removed according to applicable technical deletion and backup cycles.
We use account-based access controls, security rules, encryption in transit and reasonable organizational safeguards. No system is infallible. Protect your device and do not share Apple or Google credentials.
7. Your rights and account deletion
You may request information, access, correction, updates, objection or deletion where applicable by emailing fayalapps@gmail.com with the subject "RiderSense Privacy". We may request reasonable information to verify your identity.
You can request deletion of your account and associated data through the official account deletion page linked below. Deleting an account does not automatically cancel a subscription: manage cancellation through the store where you subscribed.
8. Changes to this policy
We may update this policy to reflect legal, technical or feature changes. We publish the current version at this URL with its update date. Where new authorization is required, we will request it before applying the change.