Privacy Policy

1. Information We Collect

1.1 Personal Information

We collect information you provide directly:

• Contact Information: Name, email address, and phone number.
• Profile Information: Profile photos and other data you provide to customize your profile.

1.2 User-Generated Content

• Photos and Videos: Any media you upload as part of trips, posts, or portfolios is stored securely on our servers in Digital Ocean, Bangalore, India.

1.3 Usage and Analytics Data

We use third-party analytics and attribution tools, including Amplitude, Google Analytics, and the Meta (Facebook) App Events SDK, to collect:

• Interaction Data: Pages visited, actions taken.
• Device Information: Device type, operating system, IP address, mobile advertising identifiers where the platform permits.
• App Events: App installs, sign-ups, sessions, and key in-app actions (e.g. trip completion, post creation) — used to measure advertising performance and attribute installs.
• App performance and crash data.

These third parties may process the data on their own infrastructure under their own privacy policies. You can limit advertising-related tracking via your device's OS-level privacy settings (e.g. iOS "App Tracking Transparency" and Android "Limit Ad Tracking").

1.4 Location and Trip Data

Motoavir is a ride-logging and motorsport community app. To deliver its core features, the app records location and motion data while you are actively using a tracking feature. Collection is feature-driven, never silent.

• Foreground & explicit: We do not track location in the background outside of an active trip or session. Location collection is started only when you initiate a feature such as a trip, a track session, an event check-in, or place discovery, and stops when you end that activity.
• Trip & route data: During an active trip we periodically record GPS coordinates (latitude, longitude), timestamps, and derived signals such as speed, distance and duration. This is used to draw your route, compute trip statistics, and let you save and review your rides.
• Performance & telemetry metrics: From trip and track-session data we derive performance metrics such as top speed, average speed, fastest segment, lean angle (where supported by your device or paired hardware), distance covered, and session timing. These metrics are stored against your account.
• Track & race sessions: When you record a track day, closed-course session, or competitive event, the same telemetry is captured at higher frequency to support lap timing and session review. Track sessions are intended for use on closed courses or legal racing venues only.
• Visibility you control: By default, your trips and sessions are private to your account. You can choose to make individual trips, sessions, or your aggregate performance metrics public, share them with clubs you have joined, or submit them to leaderboards. See Section 10 for how public visibility and leaderboards work.

2. How We Use Your Information

• Provide and improve services: Enhance features, performance, and app functionality.
• Communicate with you: Send updates, notifications, or relevant information.
• Personalize your experience: Tailor content and recommendations.
• Ensure compliance: Enforce our Terms and Conditions and legal obligations.

3. How We Share Your Information

We do not sell your personal information. We may share information only in the following cases:

• Service Providers: Third-party providers that help us operate the app (hosting, storage, push notifications, analytics, crash reporting).
• Authentication Providers: When you sign in via a third-party identity provider such as Google, Apple, or Facebook, that provider receives basic request data (e.g. that you initiated a login) and we receive the profile fields you authorize.
• Advertising & Attribution Partners: Aggregate and event-level data is shared with platforms like Meta (Facebook) via their App Events SDK so we can measure ad performance and attribute installs. This sharing is governed by the partner's own privacy policy.
• Publicly Visible Content: Content you choose to make public — including public trips, leaderboard entries, public profile fields, posts, and motorsport predictions — is visible to other users of the app and may be visible to the public internet where the app exposes it.
• Legal Compliance: If required by law or legal processes.
• With Your Consent: Only if you explicitly agree.

4. Data Security

We implement reasonable technical and organizational measures to protect your data. However, no system is completely secure.

5. Data Retention

We keep your data as long as your account is active or as needed to provide services. Certain data may be retained for legal obligations or legitimate business purposes.

6. Your Rights

• Access, Correction, Deletion: You can request to access, correct, or delete your personal data.
• Data Portability: You may request a copy of your personal data in a structured format.
• Opt-Out: Unsubscribe from promotional communications anytime.

7. Children's Privacy

• The app is not intended for users under 13 years old.
• We do not knowingly collect information from children under 13.
• If we discover data from children under 13, it will be deleted immediately.

8. In-App Purchases (Future)

If enabled, payment information will be collected via the Apple / Google payment system, and we do not store any financial information on our servers.

9. Motorsport & Predictions

Motoavir includes a Motorsport section with race schedules, statistics, and a community prediction system. This section describes how we handle data related to these features.

• Prediction Data: When you submit race predictions (winner, podium, fastest lap, safety car), we store your selections, the timestamp of submission, and the Oracle Points earned. This data is linked to your user account and used to calculate your analyst tier and leaderboard ranking.
• Analyst Profile: Your prediction accuracy, total predictions, correct predictions, Oracle Points, and analyst tier (Rookie through Oracle) are stored as part of your public analyst profile. Other users can see your tier and prediction record.
• Discussion Content: Posts, comments, and analysis you contribute to motorsport discussion threads are user-generated content subject to the same policies described in Section 1.2 (User-Generated Content). This includes stat debates, prediction rooms, and live race threads.
• Third-Party Data Sources: Race schedules, driver statistics, team information, and race results are sourced from third-party motorsport data providers. We do not control the accuracy or availability of this data and are not liable for errors in third-party race data.
• No Gambling: The Oracle Points prediction system is for entertainment and community engagement only. It does not involve real money, wagering, or any form of gambling. Oracle Points have no monetary value and cannot be exchanged, transferred, or redeemed for cash or prizes.

10. Trips, Performance Metrics & Leaderboards

This section describes how data generated from trips, track sessions, and performance metrics is used within community-facing features such as leaderboards and public profiles.

• Default privacy: Trips, sessions, and the performance metrics derived from them are private to your account by default.
• Public & club visibility: You may choose, on a per-trip or per-session basis, to publish the route, statistics, and media to your public profile, to a club you have joined, or to a verified members area. Once you publish, that content can be viewed, screenshotted, and discussed by other users until you change its visibility or delete it.
• Leaderboards: Leaderboards (for example: distance covered, fastest segments, lean angle, lap times, prediction accuracy) are populated from data generated by your activity. Entry on a leaderboard typically requires both (a) the underlying trip or session being eligible — for example marked as public, completed on an approved venue, or otherwise meeting the leaderboard's rules — and (b) you not having opted out of community ranking in your settings. Leaderboard entries display your username, profile photo, rank, and the metric being ranked. Other personal details are not published as part of the leaderboard entry.
• Anti-cheat & corrections: We may remove, recalculate, or exclude leaderboard entries that appear to be the result of GPS error, vehicle modification beyond the leaderboard's class, tampering, simulation, or use that violates these terms or the leaderboard's rules. We may also reset leaderboards periodically.
• Data sources: Performance and leaderboard rankings depend on GPS, motion sensors, and (where supported) data from paired hardware or third-party services. These signals can be inaccurate, especially in tunnels, dense urban areas, or under heavy weather. We do not guarantee the accuracy of any metric, ranking, or comparison and do not treat them as official timing for any sporting purpose.
• Removal: You can delete a trip, session, or leaderboard entry at any time from the app. Deletion removes it from public visibility and from active leaderboards; backups and analytics aggregates may retain a copy for a limited period as described in Section 5 (Data Retention).

11. Facebook Login & Meta Integration

Motoavir integrates with Meta Platforms (Facebook) in two distinct ways. Each is opt-in in the sense that you must take a positive action — either signing in with Facebook, or installing the app from an ad — for any data to flow.

• Facebook Login (authentication): If you choose to sign in or register using Facebook, Meta authenticates you and returns to us only the profile fields you authorize on Facebook's consent screen — typically name, email address, and profile photo. We use this only to create or sign you into your Motoavir account. We do not post to your Facebook timeline, message your friends, or read your Facebook content. You can revoke this connection at any time from your Facebook account settings; doing so will not delete your Motoavir account.
• Meta App Events SDK (advertising & analytics): The app includes Meta's App Events SDK so that when Motoavir runs ads on Meta platforms we can measure their performance — for example to know that an install or registration came from a specific ad. The SDK sends a limited set of standard and custom app events (such as app open, registration, key in-app milestones) along with device-level identifiers permitted by your OS-level privacy settings. Meta processes this data under its own data policy.
• Your controls: You can limit what is shared with Meta by (a) declining "Allow tracking" prompts on iOS, (b) enabling "Limit Ad Tracking" / "Opt out of Ads Personalization" on Android, (c) signing in with a non-Facebook provider, and (d) managing app permissions and ad preferences in your Facebook account settings.

12. Changes to This Policy

We may update this Privacy Policy. Significant changes will be communicated in-app, and continued use of the app constitutes acceptance of the updated policy.