Privacy policy
What data Parki processes, why, for how long, and what rights you have.
Updated 12 November 2026
This policy describes how Parki handles your personal data. It is written to be readable; where it has to be legal, a plain explanation sits beside it.
Not yet reviewed. This is a first draft and must be checked by a lawyer before publication, particularly the processor agreements and the named controller.
Who is responsible
Parki is published by Code by Gizmo, based in the Netherlands. For questions about this policy or your data: support@getparki.app.
What we process
Account data. Your name, your email address and, if you sign in with Apple or Google, the identifier Apple or Google gives us for Parki. These are needed to find your account when you log in.
What you record yourself. Your medication schedule and dose history, your motor state, logged falls, freezing episodes and pain moments, your check-ins, your emergency card, your notes and your self-test results.
Health data from Apple Health. Only with your permission, and read-only: walking speed, step length, sleep and activity. Parki never writes to Apple Health.
Subscription. If you take Parki+, whether your subscription is active and until when. We never see payment details; those stay with Apple or Google.
Technical data. A notification token if you enable notifications or the dose on your Lock Screen, one session per device, and the error reports needed to keep the app working.
This website only uses cookies if you allow them; see Cookies on this website. The web server keeps access logs (IP address, page requested) for a short time, only to trace outages and abuse.
In the app we use no ad networks, no third-party trackers and no profiling.
What we use it for
Only to make the app work: showing you your data, sending your reminders, assembling your report, and giving access to the people you invited into your care circle. We resell nothing and share nothing with third parties for their own purposes.
The legal basis is performance of the contract with you (Article 6(1)(b) GDPR). For health data, your explicit consent applies in addition (Article 9(2)(a) GDPR), which you can withdraw at any time by deleting your account.
Security
Everything you write in your own words and everything that identifies a person is stored encrypted. Traffic between the app and our servers runs over TLS. Backups are made nightly, carry their own archive password, and are stored in Europe (Amsterdam) with a seven-day write lock.
Encryption defends against a stolen backup or a stray database dump; not against the application itself, which holds the key by definition. That is why authorisation rules separately determine who may see which data.
Who can see your data
Only you, and the people you invited into your care circle, and then only the categories you switched on for that person. Following along is read-only by default; only if you switch on “May also record” can someone add something for you, and then with their name on it. You can stop access at any moment.
Processors
To run the service we use these parties. They process solely on our instructions and receive only what their task needs.
| Party | What for | Where |
|---|---|---|
| DigitalOcean | Hosting the servers and the database | Amsterdam (EU) |
| Backblaze B2 | Encrypted nightly backups | Amsterdam (EU) |
| Cloudflare | DNS for getparki.app and forwarding mail to support@getparki.app | global network |
| Postmark (ActiveCampaign) | Sending email from the app: address confirmation, password reset, invitations | US |
| RevenueCat | Keeping track of whether your Parki+ subscription is active | US |
| Apple | Sign in with Apple, Parki+ payments, notifications and the dose on your Lock Screen | US/EU |
| Sign in with Google, Parki+ payments on Android; on this website Google Tag Manager and Google Analytics, only after consent | US/EU |
Where a party processes outside the EU, it does so under the EU-US Data Privacy Framework or the European Commission’s standard contractual clauses. Your health data itself lives only on our servers and in our backups in Amsterdam; Postmark receives only the email address and the text of the message we send.
Cookies on this website
This section is about the website getparki.app, not the app. The app uses no cookies and no trackers.
On your first visit we ask what you are comfortable with. You choose per category:
- Necessary (always on). We only remember your choice, in your own browser’s storage, so we do not ask on every page. The choice lasts twelve months.
- Statistics. With Google Analytics we see which pages are viewed, where visitors come from and which buttons they use, such as the buttons to the App Store and Google Play. Google Analytics sets cookies for this and uses a shortened IP address.
- Marketing. This measures whether our ads work, for example how many people download the app after seeing an ad. Google (and, if we later run ads there, that platform) may set cookies for it.
Until you give consent, we do not load Google Tag Manager and nothing goes to Google. If you do, Google processes that data as our processor and in some cases as an independent party; this can involve a transfer to the United States, under the EU-US Data Privacy Framework. Google keeps statistics data for at most fourteen months.
You can change or withdraw your choice at any time through Cookie settings at the bottom of every page.
How long we keep it
For as long as your account exists. Delete your account and all associated data is deleted immediately and permanently, including your sessions and notification tokens. Existing backups hold your data until they rotate out, at most three months.
Your rights
You have the right to access, rectification, erasure, restriction and portability of your data, and you can object to processing. Access and erasure you can handle yourself in the app; for the rest, email support@getparki.app. You can also lodge a complaint with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens).
Children
Parki is not intended for use by children under 16.
Changes
If this policy changes, we update the date at the top and announce it in the app before the change takes effect.