Privacy Policy for “My Auto”

Effective date: 18 September 2026

Developer / data controller: Ravil Novruzov (“Developer”, “we”, “us”). Privacy contact: Myautoapp.iOS@yandex.ru.

1. Scope

This Privacy Policy applies to all users of the “My Auto” mobile application (the “App”), regardless of their country of residence, unless applicable local law provides otherwise.

If the laws of your country provide additional rights regarding personal data, those rights remain available to you regardless of this Privacy Policy.

2. Privacy summary

The App is designed to help users keep records about vehicles, mileage, trips, expenses, maintenance, fuel fill-ups or charging sessions, and related notes.

The App’s main user records are stored locally on the user’s device. The Developer does not receive, store, or view the vehicle records, receipts, photos, notes, mileage, trips, expenses, fuel or charging records that the user enters into or records with the App.

The App can record trips and use location services for that purpose, including in the background, if the user grants the relevant permission. Trip data, including route coordinates, stays on the user’s device and, where syncing is enabled, in the user’s own iCloud storage. See section 6 for details.

The App uses Firebase Analytics / Google Analytics for Firebase to collect limited technical, aggregated, and pseudonymous analytics about App usage. This helps the Developer understand how the App is used, improve the interface, detect product issues, and evaluate features such as OCR, import/export, statistics, paywall screens, and purchases.

The App does not use Firebase Auth, Firestore, Realtime Database, Remote Config, Crashlytics, AdMob, Google Ads, IDFA/AdSupport, advertising SDKs, or marketing trackers. The App does not request App Tracking Transparency permission.

The App does not sell users’ personal data and does not use it for behavioural advertising or tracking across third-party apps and websites.

3. Data the user may enter into the App

The user may choose to add vehicle-related data to the App, including vehicle name, vehicle photo, fuel type, mileage, trip records, expense records, maintenance records, fuel or charging records, custom categories, photos of receipts, service documents or other documents, and text recognized from receipts through OCR.

The content of these records is controlled by the user. Depending on what the user enters or attaches, these records may contain personal information, such as photos, document numbers, addresses, vehicle registration numbers, or other details.

4. Data received by the Developer

The Developer does not receive access to the data stored by the user inside the App, including vehicle records, mileage, trips and their route coordinates, expenses, fuel or charging records, photos, documents, custom category names, comments, notes, or recognized receipt text.

The Developer may receive analytics reports through Firebase Analytics / Google Analytics for Firebase. These reports may include technical and pseudonymous usage data, such as an app instance identifier, automatically collected app events, and custom events described in this Privacy Policy. These analytics events are designed not to include the user’s local vehicle records or the contents of user files.

The Developer may also receive personal data if the user voluntarily contacts the Developer, for example by email. In that case, the Developer may process the user’s email address, name, message content, and any technical information the user chooses to provide for support purposes.

If the user makes a purchase or subscribes through the App Store, the payment is processed by Apple. The Developer does not receive or store the user’s payment card details. The App may use purchase or subscription status information to unlock paid functionality. The Developer receives this purchase and subscription status information through RevenueCat, as described in section 9, and may send basic purchase-related analytics events to Firebase Analytics as described below.

5. Local storage and backups

The App’s main data is stored locally on the user’s device.

The user may export or import data, for example through a JSON file or PDF report. The user decides where exported files are stored and with whom they are shared.

If iOS backups, iCloud, or other Apple system features are enabled on the user’s device, App data may be included in those backups depending on the user’s device settings and Apple’s rules. The Developer does not control Apple backups and does not have access to them.

Storage of trip data, including route coordinates, is described in section 6.

6. Trip recording and location data

The App can record the user’s trips, including the route travelled, the distance covered, and the start and end time of each trip.

To record trips, the App requests access to location services, including access while the App is in the background (the “Always” location permission in iOS). This permission is requested the first time the user starts recording a trip, not when the App is launched.

Once a trip has started, route recording continues in the background, including while the App is not on screen or the device is locked, and stops when the trip ends.

If the “Auto-record” feature is enabled in the App’s settings, the App detects the start and the end of a trip by itself and records such trips without any separate action by the user. While that feature is enabled, the App accesses the device’s location in the background. If “Auto-record” is turned off, trips are recorded only after the user starts recording manually.

Granting location access is optional. Without this permission the App continues to work, and the user can enter trips and mileage manually.

Location access can be withdrawn or restricted at any time in iOS settings. Trips recorded before the permission is withdrawn remain stored in the App.

Trip data, including route coordinates, is stored locally on the user’s device. If the user has iCloud syncing enabled, that data is stored in the user’s own private iCloud storage. The Developer has no access to that storage.

Trip data is not transmitted to the Developer’s servers and is not disclosed to third parties. It is not used for advertising or tracking and is not shared with data brokers.

Addresses are resolved from coordinates by Apple’s standard services for maps and geocoding. Apple’s handling of those requests is governed by Apple’s privacy policy.

The user can delete any trip inside the App. Deleting a trip also deletes the location data associated with it.

Deleting the App removes local trip data. Data that has been synced to iCloud is deleted through iCloud.

Trip data is retained until the user deletes it.

7. Camera, photos, and OCR

The App may request access to the camera or photo library only for features chosen by the user, such as attaching a vehicle photo, service document, receipt, other document, or recognizing receipt data.

In the current version, receipt recognition is performed locally on the device. Photos and recognized text are not uploaded to the Developer’s servers or to Firebase Analytics.

The user can manage camera and photo access in iOS settings.

8. Firebase Analytics / Google Analytics for Firebase

The App uses Firebase Analytics / Google Analytics for Firebase only for product analytics. Firebase Analytics may automatically collect technical and pseudonymous analytics data, including:

• a unique app installation identifier, such as an app instance ID;
• number of users and sessions;
• session duration;
• first opens, app opens, and app updates;
• device model, operating system, App version, and related technical information;
• device language and locale;
• approximate geography, such as country or region, derived from technical data such as IP address;
• basic information about in-app purchases or subscriptions if available through Google Analytics / Firebase.

Approximate geography is not GPS location and is not the user’s precise address.

The App may manually send Firebase Analytics events about actions inside the App, including:

• completing onboarding;
• adding a vehicle or switching between vehicles;
• adding an expense, maintenance record, fuel record, or charging record;
• starting receipt OCR and whether OCR succeeded or failed;
• attaching a photo to a record;
• opening statistics or changing a chart type;
• successful JSON import/export or PDF export;
• opening a paywall, starting a purchase, successful purchase, monthly or yearly subscription purchase, purchase error, and restore purchases action.

The App sends only general, non-personal parameters with these events, such as fuel type (petrol, diesel, or EV), selected App region, input method (manual or OCR), whether a photo is attached, record type, category type (default or custom), currency, chart type, paywall source, OCR result, and the number of maintenance items in a maintenance record.

The App does not send the following data to Firebase Analytics:

• VIN;
• vehicle registration number or license plate;
• vehicle name;
• photos of receipts, vehicles, or documents;
• contents of PDF or JSON files;
• user comments, personal notes, or custom category names;
• recognized OCR text or full receipt text;
• precise addresses;
• route coordinates or other location data from recorded trips;
• exact expense descriptions;
• expense amounts, mileage, fuel volume, charging amounts, or other detailed vehicle records.

9. Purchases and subscriptions (RevenueCat)

The App uses the RevenueCat SDK to handle in-app purchases and subscription status. The payment is always processed by Apple through the App Store. Neither the Developer nor RevenueCat receives the user’s payment card details.

The RevenueCat SDK sends the following data to the servers of RevenueCat, Inc. (United States):

• an anonymous user identifier generated by the SDK itself ($RCAnonymousID);
• an operating system level device identifier (IDFV);
• transaction and subscription information from the App Store, such as product identifier, purchase and expiration dates, subscription status, store country, price, and currency;
• technical information, such as App version, device model, and operating system version.

The App does not send a user account identifier, name, or email address to RevenueCat and does not use RevenueCat’s customer attribute or attribution features. For this reason, the data listed above is not linked to the user’s identity.

RevenueCat, Inc. acts as a data processor on the Developer’s instructions. RevenueCat’s privacy policy is available at: https://www.revenuecat.com/privacy/.

10. Purposes and lawful bases

For users in the European Economic Area and the United Kingdom, the Developer acts as a controller only for the data that the Developer actually receives or can access, such as support emails, subscription status information, and analytics data available in Firebase Analytics / Google Analytics for Firebase.

Data is used for the following purposes: providing App functionality; displaying and storing user records locally on the device; recording trips and calculating distance travelled on the device at the user’s request; responding to support requests; confirming purchase or subscription status; understanding App usage; improving App design and functionality; measuring feature usage; detecting product issues; evaluating OCR, import/export, paywall, and purchase flows; and complying with applicable legal requirements.

Depending on the situation, the lawful basis may be performance of a contract with the user, legitimate interests in supporting, protecting, and improving the App, the user’s consent where required by law, or compliance with legal obligations.

Location access for trip recording, including background access, relies solely on the user’s consent, which is given through the iOS system prompt and can be withdrawn at any time in iOS settings.

11. Sharing data with third parties

The Developer does not share the user’s local App records with third parties because the Developer does not receive access to those records.

Analytics data is processed by Google through Firebase Analytics / Google Analytics for Firebase. Google’s processing of analytics data is governed by Google’s and Firebase’s applicable terms and policies.

Purchases and subscriptions are processed by Apple through the App Store. The user’s relationship with Apple is governed by Apple’s terms and policies.

Addresses are resolved from trip coordinates by Apple’s standard services for maps and geocoding, subject to Apple’s privacy policy. The recorded routes and trip coordinates themselves are not disclosed to the Developer, Google, RevenueCat, or any other third party.

Data about purchase and subscription status is additionally processed by RevenueCat, Inc. on the Developer’s instructions, as described in section 9.

If the user contacts the Developer by email, the message may be processed by email service providers used to deliver and store email.

The App does not use third-party advertising networks, AdMob, Google Ads, or SDKs for tracking users across third-party apps and websites.

12. International data transfers

Because the App’s main user records are stored locally on the device, the Developer does not transfer those local records internationally. The same applies to trip data, including route coordinates.

Analytics data processed through Firebase Analytics / Google Analytics for Firebase may be processed by Google in different countries according to Google’s terms, policies, and applicable law.

Analytics data and data about purchase status may be transferred to and stored on the servers of Google and RevenueCat, Inc. in the United States and other countries.

If the user contacts support by email or makes a purchase through the App Store, relevant data may be processed by Apple, email providers, Google, or other infrastructure providers in different countries according to their own policies and applicable law.

13. Retention and deletion

Local data remains on the user’s device until the user deletes individual records, deletes the App’s data, or deletes the App from the device.

Trip data, including route coordinates, is retained on the same terms: it is removed when the user deletes the trip, the App’s data, or the App itself. Data that has been synced to iCloud is deleted through iCloud.

The Developer cannot remotely delete or modify the user’s local data because the Developer does not have access to it.

Firebase Analytics / Google Analytics data is retained according to the retention settings of the relevant Google Analytics property and Google’s applicable policies. The actual retention period should be checked in the Google Analytics property settings.

Support messages may be retained for as long as necessary to respond to the user, resolve an issue, protect the Developer’s legitimate interests, or comply with legal obligations.

Purchase and subscription information is stored and processed by Apple according to Apple’s rules.

To request deletion of subscription data processed by RevenueCat, the user sends a request to the Developer by email at Myautoapp.iOS@yandex.ru. The Developer then instructs RevenueCat to delete the record, because RevenueCat acts as a processor only on the Developer’s instructions.

14. User rights

The user can view, change, export, or delete local records, including trip records, inside the App where the relevant feature is available, or delete the App from the device.

Users in the European Economic Area and the United Kingdom may have the right to request access to personal data, rectification, erasure, restriction of processing, data portability, objection to processing, and withdrawal of consent where processing is based on consent.

Because the Developer does not receive local App data, the Developer may be technically unable to provide a copy, correct, or delete data that exists only on the user’s device.

A request to delete subscription data processed by RevenueCat is sent to the Developer by email, after which the Developer instructs RevenueCat to delete the record, because RevenueCat acts as a processor only on the Developer’s instructions.

To exercise data rights or ask privacy questions, contact us at Myautoapp.iOS@yandex.ru. Users may also have the right to lodge a complaint with their local data protection authority.

15. Children

The App is not intended for children under 13. In countries where a higher age of consent is required for processing children’s data, the App is not intended to be used by children without the consent of a parent or legal guardian.

The Developer does not knowingly collect personal data from children. If you believe that a child has provided personal data to the Developer, please contact us at Myautoapp.iOS@yandex.ru.

16. Security

The Developer takes reasonable steps to design the App with local data storage and data minimization in mind.

The security of local data also depends on the user’s device, iOS settings, device passcode, backups, and the user’s own actions.

Users are encouraged to protect their devices with a passcode, Face ID, or Touch ID and to be careful when sharing exported files or photos of documents with third parties.

17. Changes to this Privacy Policy

The Developer may update this Privacy Policy when App features, technologies, App Store requirements, or applicable laws change.

The current version of the Privacy Policy will be published on the page listed in the App Store and/or inside the App. The effective date is shown at the beginning of the document.

18. Contact

For privacy questions, data processing questions, or user rights requests, contact the Developer by email: Myautoapp.iOS@yandex.ru.