This privacy policy explains what personal data the AutoPool mobile app for iOS and Android (the “App”) processes, why, and what choices you have. AutoPool is developed and operated by Martin Huszti (Sealion), an independent developer (“I”, “me”).
1. Summary
- You can use AutoPool without an account. Your cars, trips and refuels are then stored only on your device.
- An account is needed only to use cloud features. Signing in stores your email address and basic device information, but not your logbook.
- A car’s logbook is uploaded only when its owner turns on AutoPool Cloud Sync (a paid feature) for that car. Everyone who joins that car can see its logbook.
- The App contains no advertising, no analytics and no crash-reporting tools, and does not access your location.
- Cloud data is stored with Google Firebase in the EU (Frankfurt, Germany).
2. Controller and contact
The controller responsible for your personal data is Martin Huszti (Sealion).
Email: seelowe.dev@protonmail.com
3. Using the App without an account
If you do not sign in, everything you enter stays on your device. This includes car names, odometer readings, trips, passengers, refuels, costs, comments and your settings. I do not receive this data.
- Backups. On Android, the App excludes its data from Google’s device backup and device-to-device transfer. On iOS, App data may be included in your device’s iCloud or computer backup if you use it, under Apple’s terms.
- On-device features. The iOS widget, Siri Shortcuts, Google Assistant shortcuts and the Android Auto “log your trip” reminder work on your device. They do not send logbook data to me. The Android Auto reminder only detects whether your phone is connected to the car, not where you are.
- Technical connections. The App includes Google Firebase components. Even without an account, these may contact Google’s servers, for example to prepare push notifications or to confirm that the App is a genuine copy (see section 8). These requests contain technical data such as an app instance identifier and your IP address, not your logbook data.
4. Your account
You can create an account with email and password, Google Sign-In, or Sign in with Apple (iOS only). Accounts are managed by Google Firebase Authentication. When you sign in, the following is processed:
- Account data: your email address, a user ID, the sign-in method and, if your Google or Apple account provides one, your display name. If you choose “Hide My Email” with Apple, I receive only Apple’s relay address. Passwords are handled by Firebase Authentication; I cannot see them.
- Email verification: if you register with email and password, Firebase sends you a verification email.
- Profile record: your email address and the date your account was created are stored in the cloud database.
- Device registration: for each signed-in device, a random installation ID, the platform (iOS or Android), your language and region setting, your distance, volume and currency settings and, if you allow notifications, a push token. This is used to deliver notifications in your language and units.
Signing in does not upload your cars, trips or refuels. Cars stay on your device until Cloud Sync is turned on for them.
5. AutoPool Cloud Sync and shared cars
AutoPool Cloud Sync lets the owner of a car back it up to the cloud and share it with other people. It requires an account and an active Cloud Sync purchase by the car’s owner. People who join a shared car need an account, but no purchase.
What is uploaded
When the owner turns on Cloud Sync for a car, its existing history and all later changes are stored in Google Cloud Firestore:
- Car: name, odometer, the names of regular drivers and passengers as entered in the App, and the join code.
- Trips: odometer reading, passengers, comment, the account that created or changed the entry, and timestamps.
- Refuels: odometer reading, fuel volume, cost, full-tank flag, who paid, settlement details, comment, the account that created or changed the entry, and timestamps.
- Members: each member’s role (owner or member), join date and the name shown to other members.
Who can see it
Everyone who is a member of a shared car can see and add to that car’s logbook, including entries made by others. Other members see you by the display name of your Google or Apple account. If there is none, they see a shortened version of your email address (for example “ma•••@example.com”). Your full email address is not shown to other members. Car owners can remove members and change or disable the join code at any time.
Please only enter information about other people (for example names of drivers and passengers) if you are allowed to share it with the members of the car.
6. Push notifications
If you are a member of a shared car and allow notifications, you are notified when another member adds a trip or refuel, marks fuel as paid, or joins the car. A notification contains the car name and, depending on the event, the odometer reading or the fuel volume and cost. It does not include the name of the person who made the change. Notifications are delivered through Firebase Cloud Messaging and, on iOS, Apple Push Notification service. You can turn notifications off at any time in your device’s system settings.
7. Purchases
AutoPool Cloud Sync is bought through the Apple App Store or Google Play. Payment is handled entirely by Apple or Google; I never receive your payment details.
To manage purchases, the App uses Adapty (Adapty Tech Inc.). After you sign in, Adapty receives your AutoPool user ID, your email address and your purchase and transaction history. Adapty’s software may also process technical device data, such as your device model, operating system and app version. The App tells Adapty not to collect your IP address or your device’s advertising ID (IDFA on iOS, advertising ID on Android). Adapty’s servers still see your IP address while the App connects to them, as any server does. I use this information only to show the purchase screen, confirm and restore your purchase, and give you access to Cloud Sync. It is not used for advertising.
Your Cloud Sync status (whether and until when it is active) is also stored in the cloud database, so that sharing permissions can be checked. It is deleted when you delete your account.
8. Security and app integrity
To protect the cloud service from abuse, the App uses Firebase App Check. It asks Google Play Integrity (Android) or Apple App Attest / DeviceCheck (iOS) to confirm that requests come from a genuine, unmodified copy of the App. This involves technical device and app information, but not your logbook data.
All data is encrypted in transit. Access to cloud data is restricted by security rules: only a car’s members can read it, and only you can read your own profile and device records. No method of storage or transmission is completely secure, but I take reasonable measures to protect your data.
9. What the App does not do
- No advertising and no advertising SDKs.
- No analytics or crash-reporting SDKs.
- No tracking across other companies’ apps or websites.
- No access to your location, contacts, camera or microphone.
- No sale of personal data.
If this changes, I will update this policy and the store privacy disclosures before the change takes effect.
10. Legal bases (EU/EEA and UK users)
- Performance of a contract (Art. 6(1)(b) GDPR): providing your account, Cloud Sync, car sharing, push notifications and purchases you request.
- Legitimate interests (Art. 6(1)(f) GDPR): keeping the service secure and preventing abuse (App Check), and the technical connections described in section 3.
- Legal obligations (Art. 6(1)(c) GDPR): keeping records where the law requires it, for example for purchases.
- Consent (Art. 6(1)(a) GDPR): push notifications, which you allow through your device’s permission prompt and can withdraw at any time.
11. Service providers and data location
I use the following service providers, who process data on my behalf or under their own terms:
- Google Firebase (Google Ireland Limited / Google LLC): Authentication, Cloud Firestore, Cloud Functions, Cloud Messaging and App Check. Cloud Firestore data is stored in Frankfurt, Germany, and Cloud Functions run in Belgium. Firebase Authentication and Cloud Messaging may process data outside the EU. Firebase privacy information
- Adapty (Adapty Tech Inc., USA): purchase management. Adapty privacy policy
- Apple and Google: Sign in with Apple, Google Sign-In, App Store and Google Play purchases, push notification delivery and app integrity checks, under their own privacy policies.
Where personal data is transferred outside the EU/EEA, for example to the United States, the transfer is protected by the EU–US Data Privacy Framework or the European Commission’s Standard Contractual Clauses.
12. Retention and deletion
- On your device: data stays until you delete it in the App or uninstall the App.
- Account data: kept while your account exists.
- Turning off Cloud Sync for a car you own: your device stops syncing the car. The cloud copy is kept, and members keep access to it until you delete the car from the cloud.
- Deleting a car locally and from the cloud: the car and its entries are removed from your device and marked as deleted in the cloud. Members lose access and the join code stops working. About a week later, so that members’ devices can remove the car too, the cloud copy is permanently erased: the car, all its trips and refuels, its member list and its join codes.
- Leaving a shared car: your membership is removed. Trips and refuels you added remain part of that car’s logbook, because they belong to the shared record of the car.
Deleting your account (Settings → Delete account) removes your Firebase Authentication account, your profile, your device registrations and your memberships, removes you from shared cars, deletes your Cloud Sync status, and deletes cloud cars you own. Those cars are first marked as deleted so that no one can access them anymore, and are permanently erased about a week later, as described above. A local copy of your cars stays on your device.
Trips and refuels you added to cars owned by someone else stay in those cars, as described above for leaving a car. Purchase records held by Adapty, Apple and Google are kept as required for accounting and legal purposes.
13. Your rights
Under the GDPR and similar laws you have the right to access your personal data, have it corrected or erased, restrict or object to its processing, and receive it in a portable format. Where processing is based on consent, you can withdraw it at any time. To exercise these rights, email seelowe.dev@protonmail.com. I will reply within one month.
You also have the right to lodge a complaint with a data protection authority, in particular in the EU country where you live or work. In Austria this is the Datenschutzbehörde (dsb.gv.at).
14. Children
The App is not directed at children under 13, or under the higher minimum age that applies in your country. I do not knowingly collect personal data from children. If you believe a child has given me personal data, please contact me and I will delete it.
15. Changes to this policy
I will update this policy when the App or the way it handles data changes, and change the “Last updated” date above. Where the law requires it, I will inform you of significant changes before they take effect.
16. Contact
For privacy questions or requests, email seelowe.dev@protonmail.com.