Glidedown
Privacy policy
The short version
- Glidedown has no account, and we have no server or cloud database for it. Your plan, logs and settings are saved on your phone.
- Usage stats are off until you turn them on. They never include what you use, how much or what you pay.
- Crash reports: in the EU/EEA, the UK and Switzerland they follow your usage-stats choice. Elsewhere they are on until you turn them off.
- Purchases go through Google Play. RevenueCat checks them for us with an anonymous ID. It never gets your plan or logs.
- No ads, no advertising ID, and we never sell your data.
- Glidedown is for adults 18 and over.
Who is responsible
Glidedown is made by Fjord Studio. Fjord Studio is a trading name of Langsæter Labs (org. no. 937939493, Norway), the data controller for Glidedown and this website. Contact: support@glidedown.app.
What stays on your phone
Everything you enter is saved in the app's private storage on your phone:
- your plan: the products you use, their strength, how many a day, the price you pay, your pace and your weekly step day, and any changes you make;
- your logs, the days you confirmed as nicotine-free, your SOS sessions and your milestones;
- your settings, such as reminders, quiet hours, currency and Reduce motion, and your choices for usage stats and crash reports.
What you use and how much can say something about your health. That is why it stays on your phone. We have no server or cloud database for Glidedown, so we can't see it.
Export. Settings → Data & privacy → Export my data saves a JSON or CSV file where you choose, through Android's Save dialog. The file isn't sent anywhere.
Reminders and the widget. Reminders are scheduled on your phone. Glidedown uses no push service. On the lock screen a reminder shows only "Glidedown" and "Open the app to see today's plan.", never your numbers. If you don't allow notifications, the app can open your calendar app with a reminder for the end of your free week filled in. It can't read your calendar.
Android backup and new phones
If Android backup is on, your plan, logs and settings are included in your phone's backup to your Google account, but only when Android can encrypt the backup end to end. Then neither Google nor we can read it. If your phone can't encrypt it, the app's data is left out of the backup.
If you move straight from an old phone to a new one with a cable or Wi-Fi, Android copies the same data to the new phone. Android doesn't require encryption for that kind of transfer.
Your purchase status, your choices for usage stats and crash reports, and RevenueCat's own cache are never included. On a new phone the app asks about usage stats again, and your purchase comes back when you tap Restore.
Usage stats (Google Analytics for Firebase)
Usage stats are off until you turn them on, on the setup screen "Before you start" or later in Settings → Data & privacy → Share usage stats. This is the same in every country.
When they are on, the app sends events about how it is used: which setup step you reached, the pace and length in weeks of the plan you were shown, that the price screen was shown, which option was selected first and which you tapped, roughly how long the price screen stayed open, whether a purchase or restore worked (and a short error code if a purchase didn't), that you logged at least once that day (sent at most once a day, never how many) and whether it was from the app, the widget or a notification, SOS use, weekly steps, milestones, your reminder choices, whether the widget was added, that the app asked Google Play to show its rating card, and that you exported your data. A milestone is sent as its name only, such as "first nicotine-free day" or "saved 100".
Events never include what you use, how much, the strength, the prices you entered or anything you type.
Google Analytics adds an app instance ID, device and app details, and an approximate location worked out from your IP address. While usage stats are on, Google Analytics also records in-app purchases by itself, with the product and its price.
Events from before you make your choice are held in the phone's memory only. They are sent if you say yes and dropped if you say no.
Glidedown doesn't collect the advertising ID. Google's settings for ad storage, ad user data and ad personalisation are always off. Usage stats are never linked to Google Ads and never used for ads.
Turning usage stats off stops collection. Delete all data also resets the analytics data on your phone.
Crash reports (Firebase Crashlytics)
In the EU/EEA, the UK and Switzerland, crash reports follow your usage-stats choice until you set Crash reports yourself, so nothing is sent before you say yes. The app counts your phone as being there if its SIM card, mobile network, language settings or time zone point to one of these countries, or if it can't tell. Elsewhere, crash reports are on from the start, and the setup screen says so.
You can turn them off at any time in Settings → Data & privacy → Crash reports. Off applies from the next time the app starts, and reports still waiting on your phone are deleted.
A crash report has the error details, the device model, the Android version, the app version and a Crashlytics installation ID. It never includes what you use or how much. Firebase Sessions, which Crashlytics uses to count sessions without crashes, follows the same choice.
Install campaign (Google Play install referrer)
Only while usage stats are on, the app reads Google Play's install referrer once per install. It says which campaign, if any, led to the install. The app keeps only the source, medium, campaign and content fields, on your phone, and sends them once to Google Analytics. Ad click IDs are never kept or sent. With usage stats off, the referrer isn't read. If you turn usage stats off before the fields are sent, they wait on your phone and are sent only if you turn usage stats on again. Delete all data removes them. If you then turn usage stats on again, the app reads the referrer and sends the fields once more, because Google Play keeps it for 90 days after the install.
App settings (Firebase Remote Config)
The app gets a few settings from Firebase Remote Config: for example which price option is selected first, a short maintenance message, the oldest app version that still works, and the fingerprint of the code app reviewers use. It first fetches them after you have seen the setup screen "Before you start".
The request uses a Firebase installation ID, which Firebase creates on your phone, with basic app and device details, such as the app version and your phone's language. It carries nothing about your plan or logs. The app needs these settings to work, so they are not behind the usage-stats switch. Delete all data deletes the Firebase installation ID. That step needs an internet connection: if your phone is offline, the ID stays on it until you delete again while online or uninstall the app.
Purchases (Google Play and RevenueCat)
Payments go through Google Play. Google handles your payment under its own terms, and we never see your card or payment details.
RevenueCat Inc. (USA) checks purchases with Google Play for us and tells the app whether Pro is active. It is our processor. RevenueCat receives:
- an anonymous ID that the app creates, shown as Purchase ID in Settings → Data & privacy;
- the purchase token and the purchase status;
- your device model and brand, Android version, language and Google Play country;
- your IP address, which it sees when the app connects.
RevenueCat never receives your name, email address, plan, logs or what you use. The app turns off RevenueCat's collection of device identifiers and sends it nothing else about you. RevenueCat starts after you have seen the setup screen "Before you start".
When you have a purchase, RevenueCat's code saves the anonymous ID in Google Block Store, a small store tied to your Google account. That way the purchase can be found again on a new phone when you tap Restore.
RevenueCat processes this data under its data processing agreement, which includes the EU Standard Contractual Clauses (module 2). Its sub-processors are in the USA. To have your purchase record at RevenueCat deleted, see Delete your data.
This website
This website (glidedown-app.web.app) is served by Firebase Hosting (Google), which processes your IP address and browser details to deliver the pages. The website has no cookies, scripts, analytics, ads or trackers, and loads nothing from other websites.
Email to support
If you email support@glidedown.app, we receive your email address, what you write and any attachments. We use them only to answer you and handle your request. Please don't send us your logs or other health details.
Legal basis
- Usage stats and install campaign: your consent (GDPR Art. 6(1)(a)). Because these events can show that you use nicotine, which is health data, this is also your explicit consent under Art. 9(2)(a). You can withdraw it at any time with the switch.
- Crash reports: in the EU/EEA, the UK and Switzerland, your consent (Art. 6(1)(a)). Elsewhere, our legitimate interest in finding and fixing crashes (Art. 6(1)(f)). You can object at any time by turning the switch off.
- App settings: our legitimate interest in running the app reliably (Art. 6(1)(f)).
- Purchases: performance of our contract with you (Art. 6(1)(b)).
- This website and support email: our legitimate interest in providing the website and answering you (Art. 6(1)(f)).
What you use and how much stays on your phone, and we don't process it.
Who receives data
We don't sell personal data and don't share it for advertising. Only these service providers receive data:
- Google LLC, USA (Firebase and Google Analytics)
- Our processor for app settings and the Firebase installation ID, usage stats if you turn them on, crash reports as described above, and hosting this website.
- Google Play
- Payments, subscriptions and the install referrer, under Google's own terms.
- RevenueCat Inc., USA
- Our processor for checking purchases, as described under Purchases.
- Our email provider
- The inbox where we read and answer support email.
We may also disclose data if the law requires it.
Transfers outside Europe
Google LLC and RevenueCat Inc. are in the USA, so the data described under usage stats, crash reports, app settings, purchases and this website may be processed there. RevenueCat's data processing agreement includes the EU Standard Contractual Clauses. Google's data processing terms include the same clauses, and Google is certified under the EU-U.S. Data Privacy Framework. You can ask us for more information about these safeguards.
How long data is kept
- On your phone
- Until you delete it in the app, clear the app's storage or uninstall Glidedown.
- In your Android backup
- Until Android replaces the backup with a newer one, or you delete the backup in your Google account.
- Usage stats
- 2 months in Google Analytics, the shortest period Google offers. The period does not restart when you use the app again. Reports built from totals can stay longer, because they no longer contain anything about you.
- Crash reports
- 90 days.
- App settings requests
- Not stored by us. The settings contain no personal data.
- Purchase record at RevenueCat
- Until you ask us to delete it. We delete it within 30 days of your request.
- Support email
- As long as we need it to handle your request.
Your rights
You have the right to access, correct and delete your personal data, to restrict or object to how it is processed, to data portability, and to withdraw consent at any time. Most of this is in the app, under Settings → Data & privacy:
- Share usage stats and Crash reports turn each kind of data on or off.
- Export my data saves your plan and logs as a JSON or CSV file.
- Delete all data removes everything on the phone. See Delete your data.
- Purchase ID shows the anonymous ID RevenueCat knows you by, so you can ask us about your purchase record.
Your plan and logs are only on your phone, so we can't see, export or delete them for you. The app does that. For anything else, email support@glidedown.app with your Purchase ID. We reply within one month.
If you think we haven't handled your data properly, you can complain to Datatilsynet, the Norwegian data protection authority, or to the data protection authority where you live.
Security
Data sent from the app is encrypted in transit. Your plan and logs stay in the app's private storage, and they leave the phone in a cloud backup only when the backup is encrypted end to end. Reminders don't show your numbers on the lock screen. To report a security problem, see security.txt or email us.
Adults only
Glidedown is for adults 18 and over and is not directed to children. The first screen asks you to confirm that you are 18 or older. If a child has used the app, Delete all data or uninstalling the app removes what is on the phone. Email us if there is a purchase record to delete.
Changes
We post changes here and update the date at the top. If a change sends a new kind of data from your phone, the app asks for your consent again.
Contact
Fjord Studio, support@glidedown.app. Fjord Studio is a trading name of Langsæter Labs (org. no. 937939493, Norway).