MyGarage Privacy Policy

1. Scope and controller contact

This policy covers the personal MyGarage app and supporting website/services. Contact the MyGarage operator at support@griffify.com or https://mygarage.griffify.com for privacy requests. The Fleet product has separate policies. This policy describes implemented functionality; it does not enable planned or optional features.

2. Account, vehicle and service data

Google Sign-In/Firebase Authentication provides identity, email, display name, profile image and authentication identifiers/tokens. We process vehicle specifications/VIN/license plate, odometer and mileage-source/confidence/audit history, ownership/garage relationships, fuel/expenses, loan/lease and insurance/registration/inspection details, maintenance history/custom intervals, uploaded documents/photos/receipts, settings, shares/blocks, feedback and purchase/entitlement information that you provide or generate. Payment-card details are handled by the purchase provider rather than entered into MyGarage. Local caches/outboxes support supported offline workflows; not every edit works offline.

3. Optional GPS/background location

When enabled and permitted, GPS tracking processes precise location coordinates, timestamps, accuracy, speed and movement to estimate distance and update the selected vehicle's mileage. It may operate while the screen is locked, the app is backgrounded or the app UI is closed. Android displays a location foreground-service notification for supported tracking. Session/segment data, distances, times, confidence, mileage history and any route information supported by that feature may be kept locally or synced through authenticated APIs. Local GPS diagnostic files can include rounded coordinates and session/vehicle information after a trip ends; they are not guaranteed to be anonymous. We do not promise that all coordinates disappear at session end. Disable tracking and/or revoke location permission to stop future collection. Prior records/logs are not erased just by disabling the feature. Do not enable tracking of another person's journeys without authority.

4. Optional Bluetooth and OBD monitoring

Bluetooth scans/connections process adapter or associated vehicle-device identifiers, names, pairing/association settings and connection status, including supported background detection. Bluetooth is not limited to OBD adapters: associated Bluetooth devices may help identify vehicle usage. A compatible OBD reader may provide supported odometer/distance/speed, VIN, fuel/engine readings, diagnostic trouble codes, trip/session data and calibration baselines. Mileage-source/confidence and calibration records can sync to the server. Local OBD logs can contain readings, identifiers and diagnostic details. Disable monitoring, remove an association or revoke permissions to stop future collection; prior records may remain. Some Android versions require location permission for Bluetooth discovery.

5. Optional remote crash reporting versus local logs

Remote crash/error/performance reporting uses Firebase Crashlytics and Sentry when you explicitly opt in; the diagnostics choice defaults off until chosen and can be changed in Privacy & Data settings. Reports can contain app/device/OS versions, stack traces, exception messages, request metadata, breadcrumbs and performance events. Sentry default personal-information collection is disabled, but technical messages may still contain identifiers or user-entered values; we do not guarantee absolute anonymity or the absence of vehicle data. Revocation stops future collection as supported by the SDK; existing reports are not automatically recalled, and restarting may be necessary to apply all error-handler settings. Local GPS/OBD diagnostic files are separate from remote crash consent. Submitting feedback or sharing a log intentionally sends its contents to support; review it first.

6. AI, OCR, imports and backup/export

Optional AI requests send prompts and relevant vehicle/maintenance/financial/OBD and selected-document context to the configured inference service; our current backend supports Heroku-managed inference and configured model providers. We store account-linked conversations and usage/quota records. Provider processing has its own terms; do not submit secrets or unrelated sensitive personal data. Camera/photo/file permissions allow chosen photos, receipt scanning, OCR, documents and CSV/spreadsheet imports. Processing can be local or uploaded where the selected feature requires it. Exports, shared files and optional Google Drive/OneDrive or other connected backup destinations leave the app's control and are governed by the chosen provider and your access settings. We do not claim access to all files, photos, contacts or cloud contents merely because you use Google Sign-In.

7. Notifications, purchases, feedback and server logs

Push notifications use Firebase Cloud Messaging device tokens; scheduled email/digests and support notifications may use Resend. We process notification preferences, reminder data and delivery/deduplication records. Notifications can appear on a lock screen depending on device settings. Billing uses store transaction tokens/IDs, products and receipt verification to calculate subscription/add-on entitlements. Feedback may include contact details, categories, app/device/vehicle metadata and diagnostic attachments you submit. Backend/hosting providers process IP addresses, request/security/error logs and operational metadata to deliver and protect services.

8. Advertising and external lookups

Ad-supported experiences use Google Mobile Ads/AdMob, which can process device/advertising identifiers, IP address, ad interactions and related diagnostics under Google's policies and applicable consent settings. Do not assume all ads are non-personalized or that accepting this policy supplies any legally required advertising consent. MyGarage does not intentionally send your GPS route or maintenance records as an ad-targeting dataset. Platform privacy/ad controls and paid ad-free entitlements affect advertising. VIN decoding/specification and enabled recall/valuation lookups send needed vehicle/query data to providers such as NHTSA and configured valuation/data services. Opening external links sends data under that site's practices. Paid VinAudit is not enabled for Build 75; future integrations need updated disclosures as applicable.

9. Sharing and identification limits

VIN-linked maintenance history is a community feature: service information can be shared automatically with other users of that VIN, including service date/type, mileage, costs, service provider, description and notes. Account deletion removes direct uploader/account links from retained VIN history, but a VIN/free text can still identify a vehicle or person. Do not put names, addresses or sensitive details in record text. Hiding a community record affects your view rather than deleting everyone's copy. Authorized uploaders can use supported deletion controls. Deliberate vehicle/garage sharing can expose broader supported records to chosen recipients; verify access before inviting/sharing. Account identity/credentials, purchase data and AI chats are not intended to be public VIN records. Support/admin staff may access necessary data to operate services and investigate issues under access controls.

10. Service providers and disclosures

Providers include Google/Firebase (sign-in, authentication, messaging, diagnostics, ads, stores/optional backup), Sentry (optional diagnostics), Neon/PostgreSQL (database), Heroku and configured inference services (hosting/AI), Resend (email), Apple (where its purchase/platform services are used), Microsoft (if you connect OneDrive), and enabled vehicle-data services. They receive the data needed for the feature described above. We do not sell vehicle-history or GPS datasets to data brokers. Advertising processing may be treated as sale/sharing or targeted advertising under some laws, so we do not make an unconditional legal 'no sharing' promise. Data may also be disclosed with your direction, to comply with law, protect rights/security or in a business transfer subject to applicable safeguards.

11. Security and retention

Production user data uses HTTPS APIs with verified authentication and scoped database access; the release app does not connect directly to PostgreSQL using an embedded database password. Sensitive credentials use platform secure storage; other preferences, caches and diagnostic files may be in application storage and are not all encrypted. No system is perfectly secure. We retain service data while needed for the account/features, security and legal obligations. GPS/OBD local log buffers have limits, but there is not a universal automatic deletion deadline for all on-disk files or synced records. App controls can clear supported logs; uninstalling usually removes local app data but not server/provider copies. Controlled staging/testing may use production-derived database copies and must be protected accordingly. Backups, diagnostic providers and billing/security records can have separate retention periods.

12. Your choices, deletion and rights

Use available settings to control tracking, associations, notifications, diagnostics and sharing, and operating-system permissions to restrict location/Bluetooth/camera/files. Declining an optional feature does not by itself prevent basic app use. You can correct supported records, export available data, and request access/correction/deletion through in-app account controls or support@griffify.com. Not every server-side operational record is included in an app export; contact support for broader requests. Account deletion is different from vehicle parking/delete/restore and does not cancel store subscriptions. Private account-linked app data is removed through the deletion workflow; retained VIN history, de-identified feedback, backups and legally necessary records have the limits described above. Feedback/free text may need additional redaction; contact support. We verify requests and apply lawful exceptions rather than promise a fixed universal deletion deadline.

13. Children, international processing and legal rights

The app is not directed to children below 13 or a higher local minimum; we do not knowingly collect their data without legally required authorization. Contact support about a child's data. Providers may process data outside your country, including in the United States; applicable transfer safeguards and provider terms apply. Depending on your jurisdiction you may have access, correction, erasure, portability, restriction, objection, consent-withdrawal, advertising opt-out and complaint rights. Contact support or your competent regulator. Core account processing supports the service contract; optional processing relies on applicable consent, and security/retention may rely on legitimate interests or legal obligations. We do not waive non-excludable rights or promise that every right applies identically everywhere.

14. Website storage and policy changes

The website uses preference storage such as a theme cookie shared across griffify.com subdomains; sign-in/admin functions can use additional authentication/session storage. External embedded or linked services have their own practices. Native app storage and ad SDK processing are not equivalent to 'no tracking.' Material changes receive a new dated agreement/version and require renewed explicit acceptance in supporting app versions. Review this policy and contact support@griffify.com with questions.