Legal

Privacy Policy

Last updated: 29 September 2026

1. Who we are

TripBell is made by Emirhan Serin, trading as Emirhan Serin APP-LOYAL SOLUTIONS, a sole proprietorship registered in Poland (NIP 9462760106), based in Warsaw, Poland. We are the controller of the personal data described in this policy.

For anything about privacy, write to privacy@tripbell.app.

2. What stays on your phone

TripBell is built to work without a server of ours. The following is stored only in the app's own storage on your iPhone. We cannot see it:

• Your location while a trip is running. The app uses it to measure the distance to your stop and to decide when to wake you.
• The places you choose: your recent destinations, the places you save, and any names you give them.
• Your settings, such as units, alarm sound and default wake distance.
• The current trip, so it survives if iOS closes the app, and a count of trips used, for the free plan.

Some of this is shared with other parts of TripBell on the same phone: the lock screen Live Activity and widgets show the current trip, and your saved places are made available to Siri and the Shortcuts app so you can say "wake me at Home".

If you back up your iPhone to iCloud or to a computer, this data can be part of that backup, which Apple and you control under your Apple Account. Deleting TripBell deletes it from the phone, with the one exception described next. You can also remove saved places inside the app at any time.

What stays after you delete TripBell

To keep the free plan fair, TripBell also keeps a small record of when you started trips in the last 62 days in the iPhone’s Keychain. Each entry is a random trip ID and the time the trip was started. It contains no location, no destination, no place names, no settings and nothing that identifies you or your phone.

iOS keeps Keychain items when an app is deleted, so this record stays on your iPhone after you delete TripBell. That is its purpose: if you reinstall the app, the free trip you already used this month is still counted. The record never holds more than the last 62 days: older entries are dropped each time a new trip is recorded.

This record never leaves your phone. It is not sent to us or to anyone else, it is not synced to iCloud Keychain, and it does not move to a new iPhone through a backup, so a new phone starts fresh.

How TripBell uses location

• TripBell asks for location access "While Using the App". It never asks for "Always".
• It tracks your position only while a trip is armed. iOS shows its location indicator for as long as that lasts. Tracking stops when the trip ends or you cancel it.
• If you have allowed location access, the app may also read the position your phone last knew, without starting tracking, to centre the map and to rank search results near you.
• If you do not allow location access, TripBell still sets its backup alarm by the clock.

3. Apple services TripBell uses

TripBell uses features built into iOS. When it does, the data goes to Apple, not to us, and Apple handles it under the Apple Privacy Policy:

• Place search and the map (MapKit). What you type in the search field, and — if you have allowed location access — the position your phone last knew, as the centre of the area to search, are sent to Apple to find matching places. When you pick a point on the map, its coordinates are sent to Apple to look up the name of the place. Map images for the area on screen are loaded from Apple.
• Alarms (AlarmKit). Both of TripBell's alarms are scheduled by iOS on your phone.
• Siri and Shortcuts. If you use Siri with TripBell, Apple processes your request as it does for any Siri request.

4. Crash reports — Firebase Crashlytics

When TripBell crashes or hits a serious error, it sends a crash report to Firebase Crashlytics, a service of Google. A report contains:

• technical details of the error: the code that was running and the state of the app at that moment;
• your iPhone model, iOS version, TripBell version, available memory and storage, and the time of the crash;
• two random identifiers that Firebase creates for this installation of the app (a Crashlytics installation ID and a Firebase installation ID), so that repeated crashes on one phone can be told apart from many phones crashing once.

If you have agreed to share usage data (section 5), a crash report also lists the usage events recorded just before the crash.

A crash report contains no location, no destination, no name and no e-mail address, and TripBell does not use Apple's advertising identifier.

Why: to find and fix bugs, which for an alarm matters. Legal basis: our legitimate interest in keeping the app working (Art. 6(1)(f) GDPR). How long: Google keeps crash reports and their identifiers for 90 days, then deletes them.

5. Usage data — Google Analytics for Firebase, only if you agree

After the permission questions, TripBell asks you once whether to share usage data. Until you tap Share usage data, nothing described in this section is collected. You can change your answer at any time in Settings → Privacy → Share usage data; turning it off stops collection straight away.

If you agree, the app sends Google Analytics for Firebase, a service of Google, short records of how the app is working:

• events such as: a trip was set; which of the two alarms woke you; whether an alarm was turned off in the app or from the lock screen; whether location tracking weakened or recovered during a trip; whether a permission was granted; and whether the free allowance or the Premium screen was shown;
• details of those events, only as fixed categories and yes/no values — for example a band of wake-up distances, or which of the app's location methods was in use — never a place, an address, coordinates, a distance in metres, a time of day or anything you typed;
• what Google Analytics records for every app that uses it: first opens, sessions and app updates, your iPhone model, iOS version, TripBell version and language setting, and a random identifier that Firebase creates for this installation of the app (the app instance ID);
• your country and region, which Google works out from the IP address of your connection. We have turned off city-level location and detailed device data in Google Analytics, and Google Analytics does not store the IP address.

TripBell does not collect Apple's advertising identifier or its identifier for vendors, sends no advertising signals, does not use Google signals and does not link this data to Google Ads. Usage data is not linked to your name, your e-mail address or anything else that identifies you, and we look at it only as totals — for example, how often the location alarm wakes people and how often the backup alarm has to.

Why: to learn whether TripBell really wakes people before their stop, and where it fails, so we can fix it. Legal basis: your consent (Art. 6(1)(a) GDPR), which you can withdraw at any time in Settings without affecting what was collected before. How long: Google keeps event-level usage data for 14 months, then deletes it.

6. Travel-speed updates — Firebase Remote Config

When you choose to be woken "a few minutes" before your stop, TripBell converts minutes into a distance using a typical speed for each kind of transport. The app has these speeds built in, and occasionally it asks Firebase Remote Config, a service of Google, whether we have updated them. The same request also tells the app whether the version you have is still supported, so that it can ask you to update if an old version has a serious problem.

That request contains the Firebase installation ID, the app's identifiers and version, the iOS and SDK version, and your device's country and language settings and time zone. It contains nothing about your trips or your location.

Legal basis: our legitimate interest in keeping the wake-up estimates accurate and the app working (Art. 6(1)(f) GDPR). How long: Google keeps the installation ID until we delete it, and removes it from its systems within 180 days after that.

As with any internet request, Google necessarily sees the IP address of your connection when the app sends a crash report or usage data, or checks for updates. Google processes this for us under the Firebase Data Processing and Security Terms. We do not receive it.

7. When you contact us

If you write to us, we receive your e-mail address, your message, and anything you choose to include. When you use "Contact support" in the app, the draft already contains your TripBell and iOS version; you can delete that line before sending.

Our e-mail addresses are forwarded by Cloudflare (Email Routing) to a mailbox hosted by Google (Gmail). We use your message only to answer it. Legal basis: our legitimate interest in answering you (Art. 6(1)(f) GDPR). How long: we delete support e-mails no later than 24 months after our last exchange.

8. Purchases

If you buy TripBell Premium, you pay Apple through the App Store, under Apple's own terms and the Apple Privacy Policy. We never receive your payment details, your name or your Apple Account.

To know whether you have Premium, TripBell uses RevenueCat, a service of RevenueCat, Inc. that checks purchases with Apple and keeps a record of them for us. When the app starts, and when you open the Premium screen, buy or restore a purchase, RevenueCat receives:

• a random ID the app creates the first time — not your name, e-mail address or Apple Account;
• Apple's identifier for vendor, an ID iOS gives each app maker on your iPhone, which RevenueCat's software sends with every request;
• the purchases Apple reports for TripBell on your Apple Account: which product, when, the price and currency, the store country, whether a subscription will renew, and Apple's transaction identifiers;
• the app's version, the iOS version, your iPhone's model and your device's language setting.

RevenueCat receives no location, no destination and nothing about your trips, and it does not receive Apple's advertising identifier. Purchase data is not linked to your name or e-mail address and is not used for advertising or for tracking you.

Why: to give you the Premium you paid for, including on a new phone when you tap Restore. Legal basis: performing our agreement with you (Art. 6(1)(b) GDPR). How long: RevenueCat keeps the purchase record for as long as we use RevenueCat, or until we delete it — for example when you ask us to.

9. Our website

tripbell.app sets no cookies, runs no analytics and loads nothing from third parties; its fonts are served from the site itself. Our hosting provider, Google (Firebase Hosting), processes the technical data every web server receives — IP address, browser type and the page requested — to deliver the site and protect it from abuse.

10. What we do not do

• No account, no sign-up, no login.
• No advertising, and no advertising identifier.
• No tracking across other companies' apps or websites.
• No selling or sharing of personal data, and no profiling.

11. Who processes data for us, and where

• Google Ireland Limited / Google LLC — Firebase Crashlytics, Google Analytics for Firebase (only if you agree), Firebase Remote Config, Firebase Hosting, and Gmail for our support mailbox.
• Cloudflare, Inc. — forwarding of e-mail sent to our addresses.
• RevenueCat, Inc. — records of Premium purchases (section 8).

These providers may process data outside the European Economic Area, including in the United States. Where they do, the transfer relies on the EU–U.S. Data Privacy Framework, for a provider certified under it, or on the European Commission's Standard Contractual Clauses.

12. Your rights

Under the GDPR you can ask us for access to your personal data, and to correct it, delete it, restrict its use or receive a copy of it. You can also object at any time to processing based on our legitimate interests, and withdraw your consent to usage data at any time in Settings → Privacy. Write to privacy@tripbell.app; we answer within one month.

Because TripBell has no accounts, and crash reports and usage data carry no name or e-mail address, we usually cannot tell which of them came from your phone. If you write to us, we will explain what we can find and delete.

You also have the right to complain to a data protection authority. In Poland that is the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych, ul. Stawki 2, 00-193 Warszawa, uodo.gov.pl); you can also contact the authority in the country where you live.

13. Children

TripBell is not directed at children under 16, and we do not knowingly collect personal data from children. The app asks nobody for information that identifies them.

14. Security

Data on your phone is protected by iOS app sandboxing and device encryption. Crash reports, usage data, update checks, purchase checks and e-mail travel over encrypted connections.

15. Changes to this policy

If the way TripBell handles data changes, we will update this page and the date at the top before the change reaches you. If a change is significant, we will also say so in the app's update notes.

16. Contact

Emirhan Serin APP-LOYAL SOLUTIONS · privacy@tripbell.app

Back to TripBell