VemiraPrivacy policy
Effective November 7, 2026
This policy explains how the Vemira app for Android and iOS and its backend services ("Vemira", "we") handle user data. The developer is Vemira Team. For any questions, email support@vemira.org.
Data we collect
| Data | Purpose |
|---|---|
| Email, name, password (stored only as a hash) or Google / Apple sign-in details (with Sign in with Apple you may hide your email; we then receive an Apple relay address) | Creating your account and signing in |
| Garages, cars (VIN, make, model, year, mileage, photo), garage members | Core app functionality |
| Pre-purchase car check, if you ask for the car’s details or a code explanation: that car’s VIN, the specs found for it, the fault code and the AI’s answer. The check itself stays on your phone and is not sent to the server | Answering about the car you are checking; looking up the same VIN again without using up another request |
| Service records, reminders, insurance policies, fuel logs | Keeping history and maintenance reminders |
| OBD adapter data: check results (fault codes, battery voltage), recorded trips and mileage | Check history, mileage tracking and mileage-based service reminders |
| Documents and photos you upload (receipts, policies, photos of problems and parts) | Storing documents, receipt recognition, AI diagnosis and parts lookup |
| Text and photos you send to AI diagnosis and parts lookup | Generating the AI answer |
| Google Play / App Store subscription data: purchase identifier, order number, subscription status and expiry | Verifying payment and extending access |
| Device push notification token | Sending reminders and notifications |
| Device advertising ID (free plan only; on iOS only if you allow tracking) | Showing ads via Google AdMob |
| App crash reports: phone model, OS and app version, where in the code the crash happened (no name, email or account ID) | Finding and fixing errors that make the app close |
| Reports from the “Report a problem” form: your description, phone model and OS version, app version and (unless you untick it) the logs of the last OBD checks — the adapter conversation, which may contain the car’s VIN | Investigating the problems you report |
| Server logs (IP address, request time and path) | Abuse prevention and troubleshooting |
Voice input is converted to text by your device's built-in speech recognition service; we only receive the resulting text. We do not collect location or contacts ourselves, and we do not sell your data. On Android 11 and lower the system requires the location permission to scan for a Bluetooth adapter, but the app does not read your location. On the free plan, Google AdMob may estimate your approximate location from your IP address to show ads.
Who we share data with
Only to the extent a feature needs it:
- Google (Gemini API) and OpenAI — car description, VIN (if NHTSA could not decode it, the AI searches the web for the specs by VIN), symptoms, OBD fault codes, questions and attached photos for AI diagnosis, cost estimates, parts lookup and document recognition. Your email and name are not sent.
- NHTSA (USA) — the VIN to decode vehicle specs, and make, model and year to check for recalls.
- RapidAPI — part numbers to find equivalents.
- Google Firebase Cloud Messaging — the device token for push notifications.
- Google Firebase Crashlytics — app crash reports: phone model, OS and app version, where in the code the crash happened. Your name, email and account ID are not sent.
- Google AdMob — ads on the free plan. If you watch a video for an extra AI request, we give Google your Vemira account identifier (random, no name or e-mail) so Google can confirm the view to us. In the EEA, UK and Switzerland the app asks for consent to personalized ads; on iOS the advertising ID is used only if you allow tracking when the system asks.
- Google Sign-In / Sign in with Apple — if you sign in with Google or Apple.
- Google Play and the App Store — subscription payments. Google or Apple processes the payment entirely; we never receive your card details. We only receive purchase details (identifier, status, expiry) and give the store your Vemira account identifier so the subscription is tied to it.
- Members of your garage — can see the cars and history in that garage. A public car history link can be viewed by anyone who has it; you can revoke it at any time.
Data is stored on servers we rent. Traffic between the app and the server is encrypted (HTTPS).
How long we keep data
For as long as your account exists. When you delete your account or a car, its data is removed from the live database immediately and from backups within 14 days. Service logs are kept for up to 30 days, AI usage records (account ID, feature, request size) for up to 90 days to track costs, and web server logs are removed as they are rotated. Pre-purchase check data is kept for up to 30 days; if you add that car to a garage, its VIN and specs stay on the car’s card.
Your rights
- view and correct your data directly in the app;
- delete a single car with all its history (garage owner);
- delete your account and all related data — see Account deletion;
- cancel your subscription at any time in Google Play (Payments & subscriptions → Subscriptions) or, on iPhone, in Settings → your name → Subscriptions;
- request a copy of your data or ask a question — email support@vemira.org.
Children
Vemira is not intended for children under 16, and we do not knowingly collect their data.
Changes
We will update this page and the date above whenever this policy changes, and announce significant changes in the app.