Cruiser Care — Privacy Policy

3.1 Account and authentication

• Firebase Authentication (Google): We use Firebase Authentication to create and manage your account session.
• Sign in with Apple: If you choose Sign in with Apple, Apple shares an identity token with Firebase; we may receive a private relay email or the email you choose to share, and name information if you provide it on first sign-in.

3.2 Profile and preferences (cloud)

We store profile and preference fields associated with your user ID in Cloud Firestore, including for example:

• Country or region (for market-appropriate content and units)
• Distance unit preference (miles or kilometers)
• Service reminder bias settings (mileage and day margins)
• Subscription-related fields maintained in our database (see Subscriptions below)
• AI chat quota fields (e.g. remaining messages, exhaustion timestamps, daily quota configuration) used to enforce fair use

3.3 Vehicle and maintenance data (cloud)

To provide garage, maintenance, and related features, we process:

• Vehicle identifiers and descriptive data you enter (including VIN where you provide it)
• Odometer readings, service schedules, and logbook entries (e.g. service, fuel, repairs, modifications)
• Other vehicle fields you add in the App

VIN registry: To help prevent duplicate VIN claims across accounts, we maintain a normalized VIN-to-user mapping in Firestore. This is used for registration checks and is removed when you delete a vehicle or your account, subject to successful backend operations.

3.4 Photos

If you add a vehicle photo, the image is uploaded to Firebase Storage under your user-scoped path and associated with that vehicle in our systems.

3.5 Articles, knowledge base, and usage quotas

We may fetch articles and knowledge base content from Firestore and track article view quotas (including unique article identifiers and counts) to enforce free-tier limits and improve the product. Remote Config may be used to deliver configuration such as vehicle specification reference data used inside the App.

3.6 AI features (vehicle expert chat and related)

The App includes AI-assisted features implemented using Firebase AI Logic with Google’s generative AI backend. When you use the vehicle expert chat (or similar features), we send prompt inputs to Google’s services via Firebase, which may include:

• Your current question and prior conversation turns in that session (as implemented in the App)
• Context about your vehicles (e.g. garage summary, primary vehicle description, odometer-related values, and market or unit context as described in the App’s AI integration)

Do not submit health information, passwords, government ID numbers, or other highly sensitive categories of data in AI chat unless the App explicitly asks for them.

3.7 Subscriptions and purchases

We use RevenueCat to validate and manage auto-renewing subscriptions and entitlements. RevenueCat processes transaction-related identifiers and may receive your app user ID (typically aligned with your Firebase user ID) and subscription state. Apple processes payment through the App Store; we do not receive your full payment card number.

3.8 Widgets and on-device data

• App Group (shared container): The App and optional widgets share limited data via the iOS App Group (e.g. selected vehicle information for display and a flag indicating whether a Pro entitlement is active). This data stays on your device within Apple’s sandbox for that group.
• Local persistence: We use Realm (and related local stores) on your device for features such as saved expert chat and AI knowledge caching. This data is stored locally; portions may sync with or mirror cloud state depending on feature design.
• Images: Kingfisher (or similar libraries) may cache images from network URLs on your device for performance.
• Notifications: We may schedule local notifications (e.g. mileage-based reminders). Your notification preferences may be stored on-device and keyed to your user identifier where applicable.

3.9 Diagnostics and analytics

Unless we state otherwise in-product or in a separate notice, we do not intend to use invasive cross-app tracking for advertising in this Privacy Policy’s scope. Firebase and Apple may still collect limited diagnostic, crash, or usage metadata as part of providing their SDKs and platform services—see their respective policies.