As of 24 August 2026
The controller is Simon Weickert, freelance IT service provider, c/o IP-Management #9298, Ludwig-Erhard-Str. 18, 20459 Hamburg, Germany.
Email: hello@parity.family
Parity stores only what the week needs: first names of the two adults, first names or nicknames and an emoji for each dependent, handover times, anchors (who starts the week), weights, night windows, care windows (nursery and the like), together-time, the display mode and the household plan.
No birthdays, no children's addresses, no location, no required photos. A field for a later picture exists; a photo is never required and never implied.
There is no password account. The household hangs on a session secret on the device. The second person joins through an invite link.
Running the app and storing your week is contractual, Art. 6 (1)(b) GDPR, once you create a household or buy a plan.
Four of our own measuring points (setup done, week opened, invite sent, purchase) rest on legitimate interest, Art. 6 (1)(f) GDPR: to see whether the path through the product holds. No profiles, no ads, no third-party analytics.
Payment data is processed by the payment provider on their own responsibility. We only learn that a payment succeeded and which household it belongs to.
Household data lives with Supabase in the European Union (region eu-west-1, Ireland). We do not store it in the United States.
No payment provider is connected at present. When a fee is charged, this section will name who takes the payment.
The website is delivered by a hosting provider. Connection data such as an IP address may appear briefly. We set no trackers, no ad networks and no analytics cookies.
If you turn on the calendar feed you get a secret web address (ICS). Anyone who has that address can read the week. It is a secret, not a public link. You can replace it at any time; the old one dies.
Parity does not write into Google, Apple or Outlook. The calendar fetches the file itself. There is no Google OAuth.
Parity does not currently access Google accounts and does not read, store or share Google user data. The first-version calendar connection is an ICS subscription: Google Calendar can subscribe to the address if you paste it there. That is your action inside Google, not our access to your Google account.
If a direct Google Calendar connection ships later: we would use only the calendar data needed to write your Parity week as events into the calendar you choose. No advertising, no resale, no independent product analytics on Google user data, no transfer to third parties except subprocessors serving the same purpose. Any such access would comply with the Google API Services User Data Policy, including the Limited Use requirements. Until then it does not happen.
No cookie banner, because we set no tracking cookies. Language and the session secret live in your browser (localStorage), not as a cookie.
The four events setup_done, week_opened, invite_sent and purchase are written on our own server, in our own table. No IP address, no device fingerprint, no third party.
The week stays as long as the household exists. After a purchase the household stays until you delete it. Without a plan the week first lives on the device; once it is on the server it stays until you delete it.
Payment records at the payment provider follow their statutory retention periods.
Access, rectification, erasure, restriction, portability and objection to legitimate-interest processing: write to hello@parity.family.
Deletion means deletion: the household and its rows leave the server. JSON export is part of the product and must work from day one.
Complaint: Hamburgische Beauftragte für Datenschutz und Informationsfreiheit, Ludwig-Erhard-Str. 22, 20459 Hamburg, Germany, https://datenschutz-hamburg.de
We store first names and care times of children because otherwise the week cannot be drawn. That is as little as possible and no more. There is no analysis across households and no sale of this data.