Privacy Policy for ChronicHelper
This policy describes how DAB-IT processes personal data when you use the ChronicHelper app for iOS and Android. We have tried to write it in plain language. If you have questions, you are always welcome to write to us.
1. Data controller
DAB-IT is the data controller for the processing of your personal data in ChronicHelper.
Contact: developer@dab-it.dk
The app: ChronicHelper · iOS com.dabdeveloper.chronichelper.ios · Android com.dabdeveloper.chronichelper.android
2. In short
- You use the app anonymously. We never ask for name, e-mail, phone number or national ID number, and there is no password.
- We store what you choose to enter: nickname, avatar, user group, education and what you write in the forum.
- What you write in the forum may contain health information. That is your choice, and the content is visible to other users.
- Data is stored with Supabase in the EU (Frankfurt). We use no analytics or crash-reporting tools.
- The app shows ads via Google AdMob. Personalised ads are shown only with your consent; otherwise non-personalised ads are shown.
- Notifications are sent only if you turn them on, and they never contain other users' text.
- You can delete your account and all your contributions directly in the app. Deletion completes within minutes.
3. What data we process, why and for how long
| Category | Data | Purpose | Legal basis (GDPR) | Retention |
|---|---|---|---|---|
| Account | Anonymous user ID (random UUID), nickname, chosen avatar, user group (e.g. student/employee), optional education, which version of the terms you accepted and when | Create and operate your profile, show relevant content, document acceptance of terms | Art. 6(1)(b) (necessary for the contract on use of the app) | Until you delete your profile |
| Forum content | Posts, comments, channel titles and likes. The content may contain health information you choose to write | Operate the anonymous community and show the content to other users | Art. 6(1)(b). For health information: your explicit consent, Art. 9(2)(a), given when you publish the content and withdrawable by deleting the content or your profile | Until you delete the content or your profile |
| Blocks and reports | Whom you have blocked; reports you submitted (type, reason, optional note); reports about your content; any temporary suspension | Safe community, moderation, handling of abuse | Art. 6(1)(f) (our and the users' legitimate interest in a safe forum) | Your blocks and reports: until the profile is deleted. Reports about content: until the content or profile is deleted. Moderation log (which actions a moderator took, when and on which content): 1 year |
| Evidence preservation | When a profile whose content was reported or hidden is deleted: a copy of the reported content (post, comment or channel title), the nickname and the reasons and notes of the reports | Be able to preserve evidence, report illegal content (for example child safety) to the police and protect other users | Art. 6(1)(f) (and (c) where we are legally obliged). Any health information in the content: Art. 9(2)(f) (legal claims) | 90 days; longer only if an authority asks. The copy cannot be seen by other users |
| Exercises | Which mindfulness exercises you marked as completed, and when | Show your progress in the app | Art. 6(1)(b) | Until the profile is deleted |
| Notifications | Your notification preference, push token from Apple/Google and an installation ID for your device | Send notifications about new posts, replies and exercises | Art. 6(1)(a) (consent – you turn notifications on yourself) | Until you turn notifications off (the token is then deleted) or delete the profile. At most 3 devices can be registered per profile. Queue entries for sent notifications are deleted after 7 days |
| Technical receipts | A short fingerprint (digest) of each change you send to the server, and temporarily the response to it | Ensure the same action is not performed twice if the connection fails (idempotency) | Art. 6(1)(f) (stable and secure operation) | Responses are deleted after 30 days; the fingerprint is deleted after 90 days and cannot be used to reconstruct the content. The other receipts of a deleted profile are deleted immediately; the receipt for the deletion itself is kept for up to 1 year |
| Advertising | Advertising ID (IDFA on iOS/AAID on Android), IP address and approximate location derived from it, device information, ad impressions and clicks, your consent choice | Show ads that fund the free app; measure and cap impressions; prevent fraud | Personalised ads: Art. 6(1)(a) (consent via Google's consent dialog). Non-personalised ads: Art. 6(1)(f) | Processed by Google under Google's own retention periods. We do not store advertising data ourselves |
We do not process your precise location, contacts, photos or other data from your phone. We use no analytics SDK (e.g. Firebase Analytics) and no crash reporting.
4. Anonymous accounts
When you complete the onboarding, the app creates an anonymous account via Supabase Auth. The account is bound to a session stored locally on your phone. There is no e-mail or password, so we cannot recover your account if the session is lost (for example if you delete the app, change phone or clear the app's data). You can always create a new profile, but your old content cannot be transferred. A profile whose session has been lost stays in the system until it is deleted – profiles are not deleted automatically for inactivity. Anonymous accounts that never created a profile are deleted automatically after 7 days. See section 12 on how to ask us to delete an old profile.
Neither your nickname, your installation ID nor your user ID gives anyone else access to your profile.
5. The forum and health information
The forum is anonymous but public to all users of the app. You appear only with nickname and avatar. Health information is a special category of personal data. You decide whether to share anything about your illness, and we process only the health information you write yourself. We never use forum content or health information to target ads, and we do not pass it on to advertising partners.
Do not write information that could identify you or others. Content that shares other people's personal data is removed under the forum rules.
6. Ads, consent and tracking
ChronicHelper shows ads from Google AdMob (Google Ireland Ltd. for users in the EU/EEA). Ads appear as banners, as labelled cards in the forum feed ("Annonce"), as full-screen ads after a completed exercise, and as app-open ads when the app is opened after a longer pause. Ads are never shown during onboarding, while you write a post, or in the video player.
Consent (Google UMP / TCF)
Before the first ad is loaded, the app shows Google's consent dialog (User Messaging Platform), which follows IAB Europe's Transparency & Consent Framework. Here you can accept or decline personalised ads and see the advertising partners Google works with. If you decline, you receive non-personalised ads based only on context and approximate location – not on a profile of you.
App Tracking Transparency (iOS only)
On iOS the app additionally asks for permission to track ("Allow ChronicHelper to track your activity …"). If you do not allow it, Google does not get access to your advertising ID (IDFA) and ads are not personalised across apps.
Change your choice
- In the app: Mere → Privatlivsindstillinger (shown when required in your region).
- iOS: Settings → Privacy & Security → Tracking, and Settings → Privacy & Security → Apple Advertising.
- Android: Settings → Google → Ads (or Privacy → Ads), where you can delete or reset your advertising ID.
Google's processing is described in Google's Privacy Policy and "How Google uses information from sites or apps that use our services". Google may transfer data to the United States; see section 9.
7. Push notifications
If you turn on notifications, we store your notification preference, a push token and an installation ID. Messages are sent via Firebase Cloud Messaging (Google) and the Apple Push Notification service (Apple). To protect your privacy, notifications contain only generic texts such as "Nyt opslag i forummet" / "Se hvad der er nyt" (new post in the forum / see what is new) or "Nyt svar på dit opslag" (new reply to your post) – never text written by you or other users (not the post's subject, content or the channel's name). On Android the message is sent without text and the app shows the generic text itself. When you turn notifications off, sending stops and your push token is deleted. Apple and Google process the token and message to deliver it to your phone; Firebase Analytics is not enabled.
8. Recipients and processors
| Recipient | Role | What | Where |
|---|---|---|---|
| Supabase Inc. | Processor (database, authentication, server functions) | All account data, forum content, notification queue, receipts | EU – Frankfurt (AWS eu-central-1) |
| Google (Firebase Cloud Messaging) | Processor | Push token, notification content | EU/USA |
| Apple (APNs) | Processor/independent provider | Push token, notification content | EU/USA |
| Google AdMob | Independent controller for advertising data | Advertising ID, IP, approximate location, ad interactions, consent signal | EU/USA |
| YouTube (Google) | Independent controller | When you play a mindfulness video, it opens via YouTube, which processes your IP and playback data under Google's policy | EU/USA |
| GitHub (GitHub Pages) | Processor for these web pages | IP address and technical log data when you open these pages | USA |
| Other users of the app | – | Your nickname, avatar and what you write in the forum | – |
Articles may contain links to Danish public-sector websites (e.g. borger.dk, sundhed.dk, educational institutions and authorities). When you follow a link, that website's own privacy policy applies. We never pass your data on to authorities or other third parties unless legally required to do so.
9. Transfers outside the EU/EEA
Our own database is located in the EU. Google and Apple may process push and advertising data in the United States. Transfers are based on the European Commission's adequacy decision for the EU-U.S. Data Privacy Framework (where the provider is certified) and/or the European Commission's Standard Contractual Clauses (SCCs). GitHub processes technical log data for these web pages in the United States on the same basis.
10. Retention and deletion
- Account data, forum content, likes, blocks, reports, exercise completions and notification settings are kept until you delete your profile.
- Deletion disables the profile immediately and removes your contributions and registrations. An automatic process then deletes the account itself within minutes.
- Notification queue: Entries for sent or cancelled notifications are deleted after 7 days.
- Responses to stored changes are deleted after 30 days. The associated fingerprint (digest) is deleted after 90 days; it does not contain your content. The fingerprints and responses of a deleted profile are deleted immediately, except the receipt for the deletion itself, which is kept for up to 1 year so that a delayed repeat cannot recreate anything.
- Reported content at deletion: If your profile's content was reported or hidden when you deleted it, we keep a copy of the reported content, your nickname and the reasons for the reports for 90 days (section 3). The copy is then deleted. Reports about content or a profile that has been deleted are removed.
- Anonymous accounts without a profile are deleted automatically after 7 days.
- Backups: We take exports (backups) of the database ourselves; they are stored encrypted and are accessible only to DAB-IT. The exports are managed manually and replaced continuously; we keep them for at most five weeks. Deleted data can therefore exist in the exports for up to five weeks, but they are used only to recover from a failure, and on a restore we remove again the profiles that have been deleted since.
11. Security
All communication between the app and the server is encrypted (TLS). The database cannot be accessed directly from the app: all access goes through a small, fixed set of server functions that themselves check who you are and that you can only read and change what you are entitled to. Administrative keys are kept server-side only. Disabled profiles cannot use the app's functions even if an old access token has not yet expired.
12. Your rights
Under the General Data Protection Regulation you have the right to:
- Access the data we process about you (Art. 15).
- Rectification of inaccurate data (Art. 16) – nickname, avatar, group and education can be changed by you in the app.
- Erasure (Art. 17) – use "Slet profil" in the app or write to us.
- Restriction of processing (Art. 18).
- Data portability (Art. 20) for data you provided to us.
- Object to processing based on legitimate interest (Art. 21).
- Withdraw your consent at any time (ads and notifications) – without affecting the lawfulness of processing carried out before withdrawal.
You exercise your rights by writing to developer@dab-it.dk. Because the account is anonymous, we can only find, disclose or delete data if you help us identify the profile: state your nickname and user group, roughly when you created the profile, and the wording and time of at least one post or comment that only the owner would know (see Delete account). If we cannot identify the profile with reasonable certainty we cannot grant the request, because we would otherwise risk disclosing or deleting another person's data. We reply within one month at the latest.
You can lodge a complaint with the Danish Data Protection Agency, Datatilsynet, Carl Jacobsens Vej 35, 2500 Valby, Denmark, phone +45 33 19 32 00, www.datatilsynet.dk, or with the supervisory authority in your own EU/EEA country.
13. Children and young people
ChronicHelper is intended for users aged 16 and over. We do not knowingly collect data about children and young people under 16. If we become aware that a user under 16 has created a profile, we delete it. Parents or guardians can contact us at developer@dab-it.dk.
14. Automated decisions and profiling
We make no automated decisions with legal effect for you and carry out no profiling. The only automation is that a post or comment is hidden temporarily when it has been reported by at least three different users (reports from brand-new profiles and from profiles that report a disproportionate amount do not count), until a moderator has reviewed it. Channels and profiles are never hidden automatically. Google's ad personalisation happens only with your consent and can always be turned off.
15. Changes to this policy
We update the policy when the app or the law changes. Significant changes are announced in the app, and you may be asked to accept updated terms. The current version is always available on this page with date and version number.
16. Contact
DAB-IT
developer@dab-it.dk