Privacy Policy for Angle

Effective Date: October 19, 2026

1. Introduction

Welcome to Angle (the "App"), provided by alovola ("we," "us," or "our"). We are committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our mobile application, particularly acknowledging our use of Google's Firebase platform.

Please read this privacy policy carefully. If you do not agree with the terms of this privacy policy, please do not access the application.

This App is designed to record your motorcycle rides using your mobile device's sensors and GPS, allowing you to analyze various parameters of your ride afterwards, such as total distance, average speed, top speed, acceleration, braking events, and estimated lean angles.

2. Information We Collect

We may collect information about you in a variety of ways. The information we may collect via the App includes:

• Account Information (Social Login or Anonymous Usage):

  You can use certain features of the App anonymously. If you choose to create an account to save and sync your rides across devices, we rely on third-party identity providers (e.g., Google Sign-In, Apple Sign-In) facilitated through Firebase Authentication.

  When you log in using a social provider, we receive a unique User ID and your email address from that provider via Firebase Authentication, and the name on that account if the provider shares it. We do not request or store other personal details like your address or phone number. The User ID and email are used solely for technical purposes: authenticating you, associating your ride data with your account, ensuring data synchronization, and essential technical communication (e.g., security notices); your email is never shown to other riders.

  Your name in the App: when you sign in, we store the name you choose in the App. It is prefilled with the name from your Google or Apple account, and you can change it at any time. This name is public: it is shown on your profile to other riders whether your profile is public or private, it is how other riders find you in rider search, and it appears next to your follows, follow requests, kudos and shared routes (see section 5). Guest (anonymous) accounts have no name. Names are moderated like other public content (see Content Moderation in section 5).

• Ride Data (Collected Automatically During Recording):
  • Precise Geolocation Data (GPS): We collect real-time location data during your recorded rides to track your route, calculate distance, and determine speed. Collection stops when you stop recording.
  • Product Improvement and Route Discovery: We analyze aggregated, de-identified Ride Data — including location and motion sensor data — across our user base to improve our routing suggestions, refine our lean angle algorithms, and identify roads and curves that may be of interest to riders. This analysis relies on aggregated data and is not used to profile or individually track a specific user.
  • Motion Sensor Data: We collect data from your device's accelerometer and gyroscope during recorded rides to estimate acceleration, braking intensity, and lean angles. Collection stops when you stop recording.
  • Derived Ride Metrics: Based on the collected location and motion data, we calculate and store metrics such as start/end times, duration, total distance, route map, average speed, maximum speed, acceleration/braking events, and estimated lean angles associated with each recorded ride. This data is linked to your User ID if you are logged in.
• Location for Weather Updates, Nearby Updates and Route Creation:
  • Weather Updates: When you grant location permission, the App uses your device's location to show weather conditions and forecasts for your area. We store your last known location (updated only when you move a significant distance) and the latest forecast in your profile, and we send these coordinates to our weather data provider to retrieve the forecast.
  • Route Creation: When you plan or create a route, the App uses your current location (for example, as the starting point) together with the destinations and waypoints you choose. This information is sent to our servers and to mapping and routing providers to calculate the route.
  • Nearby Updates: We use the same stored location to tell you about new routes and twisty roads in your area. Only a coarse area (about 40 × 20 km) derived from it is used for this, and it is not shared with anyone.
  • This location use happens outside of ride recording and only to provide these features. You can disable location permission at any time in your device settings; weather updates and location-based route creation may then be unavailable.
• Device and Usage Information (Potentially via Firebase):
  • Device Information: We may collect device information such as your mobile device ID (resettable identifiers like Firebase Installation ID or Advertising ID), model, manufacturer, operating system, version information, IP address, and mobile network information. We do not collect persistent hardware identifiers like IMEI or Serial Numbers. Firebase services (like Analytics, Crashlytics) may collect this automatically.
  • Device Identifier for Abuse Prevention: each time you sign in, the App sends us an identifier the operating system gives the App for your device (Android ID on Android, the identifier for vendor on iOS) together with your User ID. We use it only to enforce suspensions of riders who seriously or repeatedly break our Terms of Service, so that a suspended rider cannot simply create a new account on the same device. It is visible only to our administrators, never shown to other riders and never used for advertising or analytics. The legal basis is our legitimate interest in keeping the community safe (Art. 6(1)(f) GDPR). It is kept while your account exists, or for as long as a suspension tied to that device applies.
  • Usage Data: We may collect information about how you interact with the App, such as features used, session duration, screen views, and crashes. Services like Firebase Analytics and Firebase Crashlytics help us collect and analyze this data to understand usage patterns and improve the App.
• Push Notifications:
  • Notification Token: A device notification token (Firebase Cloud Messaging) stored in your profile so we can send you notifications.
  • Notification Preference: Whether you want the weekly roundup of nearby updates (nearbyPushFrequency: weekly or off).
  • Nearby Area Channel: While the weekly roundup is on, your device subscribes to a channel for a coarse area (about 40 × 20 km) and your language, so the roundup can be delivered without us looking up your profile. Only this area identifier leaves the device for that purpose, not your position, and it is not linked to your User ID. Turning the roundup off unsubscribes the device.

3. Use of Firebase

We use Google Firebase, a platform provided by Google, to develop and operate our App. This means we utilize various Firebase services, which may include, but are not limited to:

• Firebase Authentication: To manage anonymous usage and social logins (Google, Apple, etc.), handling the authentication process securely.
• Firebase Firestore or Realtime Database: To store and sync your ride data and associated account information (User ID, email, the name you set in the App) across your devices.
• Firebase Crashlytics: To identify, track, and help us fix stability issues and crashes within the App.
• Firebase Analytics: To understand how users engage with the App, which helps us improve features and user experience. This typically involves collecting aggregated usage data and device information.
• Other Firebase services (like Cloud Functions, Cloud Storage) may be used as needed for App functionality.

Your use of the App means that Google, through Firebase, will process certain data as described in their policies. We encourage you to review Google's Privacy Policy and information about how Google uses data when you use partners' sites or apps: Google Privacy Policy and How Google uses data.

While we control the data stored within our specific Firebase project instance (like your rides linked to your User ID in Firestore), the underlying infrastructure and some data processing (especially for services like Analytics and Crashlytics) are managed by Google.

4. How We Use Your Information

Specifically, we may use information collected about you via the App and Firebase services to:

• Provide Core Functionality: Record rides, process sensor/GPS data, calculate/display statistics, store/sync ride history linked to your User ID (if logged in).
• Weather and Route Creation: Use your device's location to show local weather updates and forecasts, and to calculate routes from your position to the destinations you choose.
• Authenticate Users: Manage logins and anonymous access via Firebase Authentication.
• Improve the App: Analyze usage patterns (via Firebase Analytics), diagnose/fix crashes and bugs (via Firebase Crashlytics), enhance features, and develop new services.
• Aggregate Data Analysis: Compile anonymous, aggregated statistical data from usage and ride data for internal use or potential industry insights. This data will not personally identify you.
• Technical Communication: Use your stored email address for essential account-related communication (e.g., security updates), if necessary.
• Notifications: Tell you about new routes and roads near you, a weekly roundup of what's new in your area, app updates, and account or purchase events.

5. How We Share Your Information

We do not sell your personal information or individual ride data. We may share information in certain situations:

• With Google (via Firebase): As described above, using Firebase inherently involves sharing data with Google for the functioning of Firebase services (Analytics, Crashlytics, Authentication, Database hosting etc.). This includes Firebase Cloud Messaging (FCM), which delivers our notifications: it receives your device's notification token, the message, and, for the weekly roundup, the coarse area identifier your device subscribes to. Google processes this data according to its privacy policies.
• With Other Service Providers: We might use other third-party vendors beyond Firebase (though Firebase covers many needs). If so, we would share information only as needed for them to perform services on our behalf (e.g., a specialized mapping service not covered by standard OS maps) under confidentiality agreements.
• With Weather and Routing Providers: To show weather updates, we send your location coordinates (without your User ID or email) to our weather data provider, Open-Meteo. To create routes, the locations you route from and to are processed by our servers and by mapping and routing providers. These providers receive only the data needed to return the forecast or route.
• With Other Riders and Anyone With a Link (Social Features, Only If You Choose to Be Public):

  Your profile is private unless you choose to make it public. You make this choice yourself (nothing is preselected) and can change it at any time in the App's settings. Guest (anonymous) accounts are always private. If your profile is public, the following is shown to other riders in the App and on web pages that anyone with the link can open (these pages are marked noindex, so they are not listed by search engines):

  • Public Profile: the name you set in the App (always shown, and searchable by other riders), your avatar only if you uploaded it in the App (never the photo from your Google or Apple account; otherwise your initials are shown), your active motorcycle, a star if you have Angle Premium, and your public rides and routes. You can hide each of these individually, except your name, which you can change at any time.
  • Public Rides: new rides are public by default while your profile is public, and you can hide any ride. Each ride and route also has its own audience that you can change at any time: Everyone, your approved followers only, or only you. You can also set the default audience for new rides and routes in the App's settings. Rides recorded before you went public stay private. A public ride shows a trimmed map, distance, duration, elevation, lean angles (maximum left/right and the lean profile along the route), your photos, the ride title and the date. Lean angles are shown unless you hide them. Speed (average and top speed) and acceleration (maximum acceleration and braking) are hidden unless you choose to share them, either as your default or for an individual ride, and you can hide them again at any time. Lean angles and acceleration are never published for a ride whose motion sensor readings were unreliable. We never publish start or end times, the time of day, or the timestamps or speeds of individual points.
  • Privacy Trim: to protect places such as your home, the start and end of every public ride are removed before publishing: at least 1 km from each end (25% from each end for rides under 2 km), and each cut point is also at least 500 m in a straight line from the real start or end, plus a random offset of up to 300 m. If less than 500 m of track remains, only the ride statistics are shown, without a map. Photos taken inside the removed parts are not published, and location and other metadata (EXIF) are stripped from every published photo.
  • Public Rides Near Other Riders: while your profile is public, your public rides, and your profile with them, can be suggested to riders in the areas those rides pass through. Only coarse areas (about 40 × 20 km) crossed by the trimmed, published part of your rides that are shared with Everyone are used for this, never your home or current location, and these areas are not displayed to anyone. To stop it, make your profile private or change the audience of your rides. To show you public rides near you, the App searches by the coarse areas around your own location; they are not stored for this purpose.
  • Private Profile: if you choose a private profile, the name you set in the App, your avatar (only if you uploaded it in the App), and your follower, following and ride counts remain visible to signed-in riders in the App, and you can be found by your name in rider search. Other riders can ask to follow you; only riders whose request you approve can see your rides, routes and photos. Your motorcycle and the Premium star are not shown, and you are not suggested as a rider nearby. If you set an individual ride or route to Everyone, that ride or route is shown to anyone (for example in public rides near them or through a shared link) while your profile itself stays locked and does not list it.
  • Follows and Kudos: follower and following lists are visible to other riders, as are kudos counts. If you follow a rider, send a follow request or give kudos, the rider concerned and other riders may see your name and avatar in those lists and requests, linked to your profile (which stays locked to them if it is private).

  The legal basis for publishing this information is your consent (Art. 6(1)(a) GDPR). You can withdraw it at any time by making your profile private in the App's settings (your rides then remain visible only to the followers you approved; you can remove any follower), by hiding individual rides or items, or by deleting your account. When you hide a ride or delete your account, the public copies are removed, normally within about 5 minutes (web pages or images already opened or shared by others may remain in their browser or app until they refresh). Your private rides stay in your account. Blocking a rider removes follow links and pending follow requests between you in both directions. Reports you submit about content are reviewed by us and are not shown to the rider you report.

• Content Moderation (no third parties): To keep the community safe, what you make visible to other riders is checked for inappropriate content: your name, your avatar, ride titles and photos, and the routes and segments you share. Ride titles are checked automatically before they are published, and a flagged title is not published. All of this content is also reviewed after it is published, with the help of an automated model that runs on our own systems; no outside moderation service receives your content. Content that several different riders report is hidden automatically while we review it. If content breaks our Terms of Service, we may hide it, ask you to change it, or restrict or suspend your social and sharing features (see Device Identifier for Abuse Prevention in section 2). The legal basis is our legitimate interest in keeping the community safe and our obligations as a host of user content (Art. 6(1)(f) GDPR).
• By Law or to Protect Rights: If required by law, legal process, or to protect the rights, property, and safety of alovola, our users, or others.
• Aggregated/Anonymized Data: We may share aggregated or anonymized information that does not directly identify you.
• With Your Consent: For any other sharing, we will obtain your explicit consent first.

We will NOT share your specific, personally identifiable ride data (your exact routes, speeds at specific times linked to your User ID/email) with other third parties for marketing or unrelated purposes without your explicit consent. If you choose to make your profile public, only the limited, trimmed ride information described above is published: never your times, and your speed only if you choose to share it.

6. Data Storage and Security

• Storage Location: Your ride data and associated account information (User ID, email) are stored within our Firebase project (e.g., Firestore/Realtime Database), hosted on Google Cloud infrastructure. This data may be stored on servers located outside your country of residence (see International Data Transfers). Some data might also be cached locally on your device.
• Security Measures: We rely on the security measures provided by Google Cloud and Firebase for infrastructure security. We implement appropriate administrative and technical measures within our control (e.g., access controls within Firebase) to help protect the data we store. Firebase Authentication provides secure login processes. However, no system is 100% secure. We cannot guarantee the absolute security of your information.

7. Data Retention

We retain your User ID, email, and associated ride data stored in Firebase for as long as your account is active or as needed to provide you the App's services. You can typically delete individual rides within the App. If you delete your account (functionality depends on implementation), we will initiate the deletion of your User ID, email, and associated ride data from our active Firebase databases, subject to Firebase's deletion processes and any legal obligations to retain data. Data within Firebase backups may persist for a limited period. Anonymized data collected by Firebase Analytics/Crashlytics may be retained by Google according to their policies.

8. Your Privacy Rights

Depending on your jurisdiction (e.g., GDPR in Europe), you may have rights regarding the personal information alovola holds about you (specifically your User ID, email, and associated ride data under our control). These may include the right to:

• Access the personal information we hold.
• Request correction of your email address (if inaccurate).
• Request deletion of your account and associated data.
• Object to or restrict certain processing (though most processing is essential for App function).
• Withdraw consent (where applicable, though core functionality relies on processing necessary for the service).

To exercise these rights regarding the data controlled by alovola, please contact us using the details below. For data processed directly by Google via Firebase (like Analytics), you may need to manage settings through your Google account or device settings. You can manage App permissions (location, motion sensors) via your device's OS settings. To stop the weekly roundup of nearby updates, use the setting in your profile in the App, or turn off notifications for Angle in your device settings. Removing location permission stops location-based updates. You can also review our Data Safety section on the Google Play Store for a summary of how we handle your data.

9. Children's Privacy

The App is not intended for use by individuals under the age of 16 (or higher age if required locally). We do not knowingly collect personal information (like email via social login) from children under this age. If we become aware that we have, we will take steps to delete it.

10. International Data Transfers

By using the App and Firebase, your information (including User ID, email, ride data, usage data) will likely be transferred to and processed on servers managed by Google Cloud, which may be located outside of your home country (often in the United States). Google implements measures like Standard Contractual Clauses to ensure data transferred outside regions like the European Economic Area (EEA) is adequately protected according to requirements like the GDPR. alovola relies on these measures provided by Google for data transfers inherent in using Firebase.

11. Changes to This Privacy Policy

We may update this Privacy Policy. We will notify you of significant changes by posting the new policy within the App, or potentially via email if you have an active account. Changes are effective when posted. Your continued use of the App after the effective date constitutes your acceptance of the revised policy.