Privacy policy

Tideline · last updated October 8, 2026

Tideline has no accounts and never asks for your name, email, phone number, contacts, or location. From version 1.1 it uses Google AdMob to show optional reward videos, and from the version after 1.1 it uses Google's Firebase to understand how the game is played and to find crashes. What each involves is listed below. Version 1.0 uses neither.

• The app has no accounts and no sign-in.
• Your progress (stars, Daily Light results and streaks, Pearls, lives), settings, and a record of what you have bought are saved only on your device. Deleting the app deletes them. We run no servers of our own; the only data that leaves your device is what this page describes.
• In-app purchases are processed by Apple through the App Store, and Apple's privacy policy covers those transactions. The app asks Apple which items you own so it can unlock them; we never see your payment details.
• Reward videos (Google AdMob, version 1.1 and later). Videos are only ever shown when you tap an offer, such as more moves, a life, a hint, or a second tide chest; there are no banners and no ads that interrupt play, and none in the Daily Light. To find and show a video, Google's Mobile Ads SDK receives information such as your IP address (and the approximate location it implies), device model, OS and app version, an app-specific identifier, and how you interact with the videos. Tideline never asks to track you, so Google does not receive your device's advertising identifier, and ads are not personalized from your activity in other apps. In the EEA, the UK, and Switzerland you are asked for consent first, and can decline; you can change your choice at any time under Settings > Ad privacy choices in the app. Google's use of this data is covered by Google's privacy policy for partner apps. Keeper's Pass holders get every reward without a video.
• Gameplay analytics and crash reports (Google Firebase, versions after 1.1). Tideline uses three parts of Firebase. Google Analytics for Firebase receives an app-specific instance identifier, device model, OS and app version, country and region (from your IP address), session times, and game events: levels started, won, lost and left with stars, moves and time, Daily Light results, Pearls and lives earned and spent, shop visits, videos offered and watched, and in-app purchases (product and price). Firebase Crashlytics receives crash reports with the device model, OS and app version, and the level being played. Firebase Remote Config lets us change a few settings, such as whether reward videos are offered, without an update. None of them receives your name, email, contacts, precise location, or advertising identifier; Tideline never sets a user ID, and the data is not used for advertising or sold. You can turn analytics off at any time in Tideline's Settings under "Share play data". Google's handling of this data is described in Firebase's privacy information. (Version 1.1 included GameAnalytics, which was never switched on and sent nothing.)
• Reminders. If you allow notifications, the app schedules them on your device (lives refilled, the evening Daily Light reminder). Nothing is sent to a server, and you can turn them off in Tideline's Settings or the Settings app.
• If you are signed in to Game Center, your Daily Light results, total stars, and achievements are posted to Apple's Game Center under your Game Center name, under Apple's terms. You can sign out of Game Center in the Settings app.
• When you tap Share after a Daily Light puzzle, the text you share (your stars, moves, streak, and the puzzle's colors) goes wherever you send it. Nothing is shared unless you choose to.
• Tideline is not directed at children under 13, and we do not knowingly collect their data.

If this ever changes, this page will be updated before the app does.

Questions: see the support page.