Privacy
Privacy policy
Kroni is built for families — and privacy is not something we tacked on afterwards. This policy explains what data we process, why, for how long, and what rights you have.
Introduction and controller
Nilsen Konsult (Norwegian business registration no. 931 405 861 MVA) is the data controller for the personal data processed through the Kroni app and the Kroni websites, including kroni.family. That means we determine the purposes and means of the processing, and we are responsible for ensuring it complies with the Norwegian Personal Data Act and the GDPR.
Kroni serves families internationally. The GDPR governs users in the EEA and the UK; if you live in the United States, the dedicated COPPA and US state-privacy sections below also apply to you. Wherever you live, the core dataset is processed in the EU (see section 08).
Kroni is a family app where a parent creates chores, allowance and rewards for their children. For the app to work, we have to process a minimum of personal data about both the parent and the child. Throughout, we have chosen solutions that collect as little as possible — for example, we never ask for the child's last name or email address, and no real money ever moves through the system. (Three optional features are described in section 02: chore photo proof, a chore's example photo and a voice message on a chore.) Privacy is built in, not bolted on.
For privacy questions or to exercise your GDPR rights, reach us at support@kroni.no.
What personal data we process
About the parent we process:
- Email address (used as login via our authentication partner Clerk).
- The Apple ID name if you choose «Sign in with Apple». Kroni uses the name as your display name in the family until you change it.
- Your name, email address, Google account ID and the address of your profile photo if you choose «Continue with Google». Google sends them, and Clerk keeps them with your account. Kroni uses the name as your display name in the family until you change it.
- An optional display name shown in the family (first name or nickname).
- Subscription state (free, trial, monthly, yearly, lifetime, ended) and a RevenueCat app-user-ID linked to your Clerk user ID.
- IP address and device/browser info on login and when contacting our server endpoints, used for security and debugging.
- Timestamps for events in the app (chore creation, approvals, logins).
- Optional language preference.
About the child we process:
- First name (typically what the parent calls the child day to day — a nickname is fine).
- Optionally a year of birth — only the year, never day or month. Used for age-tailoring; optional.
- Optionally a four-digit PIN, stored only as a one-way hash and never in clear text.
- A chosen avatar key pointing to one of the app's predefined icons. We do not store user-uploaded profile pictures.
- Device ID and push token to deliver notifications about new chores, approvals and rewards.
We do not collect the child's last name, full date of birth, email address, phone number, voice data, location, or other special categories of personal data about the child.
Helpers. A parent can invite another adult as a helper, such as a grandparent or a babysitter. The helper has their own Kroni account, with the same account data as a parent above. A helper sees the children's first names and avatars and that day's chores, and can mark chores as done and approve or send back chores that need no photo. A helper sees no money, rewards, history, photos, settings or other adults. The parents see the helper's name and email address, and the children's history shows which chores a helper approved. A helper's access ends when a parent removes them, on an end date the parent may set, or when the helper leaves.
Optional chore photo proof. A parent can switch on a setting for an individual chore that asks the child to take a photo as proof the chore is done (for example a tidied room). It is off by default and entirely optional, set per chore. When used, the photo is uploaded over an encrypted connection to private, encrypted object storage in the EU (operated by Scaleway in France), shown to the parent in the approval queue, and deleted as soon as the parent approves or declines the chore. Otherwise it is deleted automatically within a retention window the parent chooses in settings, anywhere from 1 hour up to 7 days, measured from when the parent first opens the photo. A photo that is never opened is deleted within 7 days at the latest. These photos are never shared, never used for any other purpose, and are not used to identify or profile anyone.
Optional example photo. A parent can add one example photo to a chore, a picture of what the chore looks like when it is done (for example a made bed), so the children can see what to aim for. We ask parents to photograph the result, not people. Before the upload, the app or the browser makes a new copy of the image, which leaves out its location and other metadata. The photo is stored in the same private, encrypted object storage in the EU (operated by Scaleway in France), shown to the parents and to the children who have that chore, and kept for as long as the chore exists. It is deleted when a parent removes or replaces it or deletes the chore, and with the family account. It is never shared, never used for any other purpose, and is not used to identify or profile anyone.
Optional voice message. A parent can record a short voice message on a chore, up to 15 seconds long, such as a reminder of where the towel goes, so the children can hear what to do. We ask parents to use their own voice. The message is stored in the same private, encrypted object storage in the EU (operated by Scaleway in France), can be heard only by the family's parents and the children who have that chore, and is kept for as long as the chore exists. It is deleted when a parent removes or replaces it or deletes the chore (deleting a child also deletes the chores only that child had), and with the family account. It is never shared, and never used for voice recognition, analysis or any other purpose.
Family links. A parent can make a private link that shows a relative, such as a grandparent, a child's goals. It is off until the parent makes one. For each link we store the name the parent gives the relative, the first name the parent approved for the page, whether wishes and amounts are shown, when the link was made, when it expires and when it was last opened. The key in the link is stored only as a one-way hash. The page shows the child's first name as the parent approved it, the avatar and open goals, and wishes and amounts only if the parent turned them on; never a last name, birth year, photo, balance, chores, times, location or other family members. A relative can send the child a ready-made cheer, say they will get one of the wishes, or say they plan to give a gift toward a goal. We store which, and when. The relative types nothing and gives us no name or contact details. Their IP address is used to limit how often the page can be tried, and is kept in our server logs as section 06 says, as for any visitor.
Closing the week. When a parent closes the week, they can leave each child a short note. In the money meeting (Kroni Family) the child also picks what to do next week from four set choices. We store the note, who wrote it, when the child read it, and the choice, and delete them with the child or the account.
Thanks in the family. A child can send a sibling or the family's grown-ups a ready-made thanks, and a parent can send one to a child. Nobody types anything: there are five set messages to choose from. We store who sent it, to whom, which message and when, and show it to the family for a day.
For purchases and billing, payment data (card data, billing address, etc.) is processed by the seller as merchant of record, see section 07. Kroni never receives card information, only details of the purchase itself, such as product id, purchase time, renewal time and trial status if any.
About app usage we process:
- Chores and chore templates (titles, amounts, frequency, assignments).
- Completions, approvals and declines.
- Rewards and redemptions.
- Virtual-kroner balances per child.
- Information about each device that uses Kroni: an install ID, the platform, app version, operating system version, device model and device type (phone, tablet or computer), and when the device was last used. For Kroni in a browser we store the browser, the operating system and the type of device instead. We use it to show parents which devices their children use Kroni on, and for customer support and troubleshooting. We also store whether each device lets Kroni send notifications (allowed, declined, not asked yet or not possible) and every change to that, with its time. We use it to see how many parents get notifications, and to remind a parent without them when a child is waiting for an approval.
- Product and diagnostic data sent to PostHog — app-usage and product analytics, crash and error reports with stack trace, diagnostic logs, and, on our backend, distributed traces, plus device, OS and app version. Events are linked by a pseudonymous user identifier: the parent's Clerk user ID (not their email address). Events about a child can carry the child profile's random internal ID, but never the child's name or contact details. Kroni does not track children: we use a child's usage and crash events only for internal operations, keeping the app stable and understanding how features are used in aggregate. We do not send email addresses to PostHog. Unlike the rest of our systems, which run on our own servers, PostHog is a third-party processor. It runs on PostHog Cloud's EU region (eu.i.posthog.com), so this data is stored in the EU, is covered by a data processing agreement, and is never used for marketing. Analytics and trace sampling is limited, and the rate can be turned down.
Age range from the app store. On devices where a law requires it, the app asks the App Store or Google Play for the user's age range. The app uses it only on the device, to meet that law, and neither stores it nor sends it anywhere.
How data is collected
Most data we get directly from the parent on registration, when creating child profiles, and through normal use of the app. The child's device pairs to the family via a six-digit code provided by the parent; the child does not enter personal data beyond what the parent has prefilled.
Technical data — IP address, device model, OS, app version, timestamps and similar — is collected automatically when the app contacts our server endpoints, and is necessary for the service to function and to detect abuse.
Subscription information comes from the seller of the subscription (see section 07). For purchases in the App Store or Google Play, it is mediated by our subscription platform RevenueCat.
Legal basis
We process personal data on the following legal bases under GDPR Article 6:
- Contract (Article 6(1)(b)): Processing necessary to perform the agreement with the parent — providing the family app, creating and maintaining the account, executing purchases and renewals.
- Consent (Article 6(1)(a)): Push notifications and any optional features that require your active consent. Consent can be withdrawn at any time.
- Legitimate interest (Article 6(1)(f)): Securing the service against abuse, debugging, aggregated statistics, and defending against legal claims.
- Legal obligation (Article 6(1)(c)): When we must retain accounting records under Norwegian bookkeeping law, or respond to orders from public authorities.
For children under 13 we rely on parental consent under GDPR Article 8, as implemented in Norwegian Personal Data Act § 5.
Purposes of processing
We process personal data to:
- create, operate and maintain parent accounts and linked child profiles;
- let the child mark chores as done and the parent approve them;
- maintain virtual-kroner balances and display them in the child's app;
- let a parent show a child's goals, and if they choose wishes, to relatives through a private family link, and pass the relatives' ready-made cheers to the child;
- send relevant push notifications, when consent is given;
- handle subscription, trial and renewal;
- answer customer-service and privacy enquiries;
- detect and prevent abuse, account takeover and breaches of the terms;
- improve the service based on aggregated, anonymised usage statistics;
- comply with legal obligations, including bookkeeping and orders from authorities.
We do not use personal data for behavioural advertising aimed at children, for profiling with legal or similarly significant effects, or for selling data to third parties.
Retention
We store personal data for as long as necessary for the purposes for which it was collected, and no longer than the law allows or requires.
- Active accounts: Data is retained while the agreement runs and the account is in active use.
- Inactive accounts: If nobody in a family has used Kroni for 12 months, we email the parents, and once more a week before the account is deleted. If nobody signs in within 30 days of the first email, we delete the family account as described under account deletion. This never happens while the family has a running subscription, trial or free period, or lifetime access.
- Completed and approved chores: Generally deleted or anonymised within 90 days of approval.
- Chore photo proof: Deleted as soon as the parent approves or declines the chore. Otherwise deleted automatically within a retention window the parent chooses, from 1 hour up to 7 days, measured from when the photo is first opened. A photo that is never opened is deleted within 7 days at the latest.
- Example photo of a chore: Kept while the chore exists. Deleted when a parent removes or replaces it or deletes the chore (deleting a child also deletes the chores only that child had), and with the family account as described under account deletion.
- Voice message on a chore: Kept while the chore exists. Deleted when a parent removes or replaces it or deletes the chore (deleting a child also deletes the chores only that child had), and with the family account as described under account deletion.
- Family links: A link works for one year unless the parent renews it. An expired link is deleted 90 days later, and a link the parent removes at once, each with every reservation and gift note sent through it. A cheer is deleted after 30 days. Deleting a child's profile deletes all of that child's links.
- Thanks in the family: Shown for a day, and deleted within 48 hours of being sent.
- Account deletion: When the parent deletes the family account, all personal data about the parent and the children is deleted within 30 days, except for accounting records (5 years) and evidence required for legal claims.
- Logs and security data: Typically 30 to 180 days.
- Customer service enquiries: Normally up to 24 months.
Recipients and processors
We do not share personal data with third parties for their own purposes. As an explicit principle we share as little data as possible, minimising the amount, the categories and the number of recipients. Some sharing is technically unavoidable for the app to work (login, billing, distribution), and where it occurs it is solely with processors bound by a Data Processing Agreement (DPA) under GDPR Article 28, or, for Apple, Google and Stripe, as independent controllers for the merchant-of-record role.
- Hetzner Online GmbH — operates Kroni's application servers and PostgreSQL databases. Machines are located in Hetzner's data centre in Finland, within the EU/EEA. The entire core dataset (accounts, child profiles, chores, completions, virtual balances) is held there.
- Scaleway SAS — provides the encrypted object storage in France (EU/EEA) that holds optional chore-proof photos for a short time, and a chore's optional example photo for as long as the chore exists. Photos sit in a private, server-side-encrypted bucket and are deleted as described in sections 02 and 06. Scaleway is a sub-processor bound by a Data Processing Agreement.
- Clerk, Inc. — authentication and account management for the parent. Processes email, login events, the Apple ID name if «Sign in with Apple» is used, and the name, Google account ID and profile photo address if «Continue with Google» is used. Clerk has its own privacy policy.
- RevenueCat, Inc. — handles subscription state and synchronises purchases / renewals across the App Store and Google Play. Receives an anonymised app-user-ID and purchase metadata; no card information. RevenueCat has its own privacy policy.
- Amazon Web Services EMEA SARL (Amazon Simple Email Service, in Sweden (EU/EEA)) — delivers our transactional emails from the sending domain
kroni.no(authenticated with SPF, DKIM and DMARC). Processes your email address (sourced from Clerk) and the body content of the messages we send you. The purpose is delivery of account-essential service emails — sign-up confirmation, password reset, email verification, billing notices (failed payment, subscription expiration) and household invitation links. The legal basis is contract (GDPR Art. 6(1)(b)) — we cannot operate the account without delivering these messages. Amazon SES is a sub-processor under the data processing agreement we have with you, and retains delivery logs per its published retention schedule; the email content itself is not stored long-term by us. These are essential service messages and cannot be opted out of while the account is active. Notices about your family's activity in Kroni, such as a child's first chore, and the notice that your free time is about to end are sent on the same basis, but follow your notification settings and can be switched off there. Amazon SES also delivers news and offers from Kroni, but only to parents who have turned on the setting for them. It is off by default. The legal basis for these emails is consent (GDPR Art. 6(1)(a)), and for them we process your email address, the setting and when it was last changed. Every such email has a link that unsubscribes you in one click, and you can withdraw your consent at any time by turning the setting off in the app or in your browser. We have chosen to send our own, localised emails matching Kroni's visual identity rather than Clerk's default templates, which are disabled. - Apple Distribution International Ltd. (App Store) and Google Commerce Limited (Google Play) — distribution and payment as merchant of record. Apple's and Google's privacy terms govern what they themselves collect.
- Stripe, through Link: merchant of record for the payments Stripe handles, and an independent controller for the data Stripe processes for those payments: payment, tax, fraud prevention and anti-money-laundering checks. Card data stays with Stripe, and Kroni never sees it. Stripe's privacy policy governs what Stripe itself collects.
- Expo (Expo Application Services) — relays push notifications from Kroni's backend to the user's device. Expo dispatches the messages to Apple Push Notification service (APNs) for iOS devices and Google Firebase Cloud Messaging (FCM) for Android devices. Apple and Google see the notification title and body plus the device's push token while the message is in transit; neither stores the content long-term, and it is not used for marketing or advertising.
- Your browser's push service: when you turn on notifications in a browser, Kroni stores that browser's push address and two keys, and sends notifications through the push service the browser itself uses: Google (Chrome and most other Chromium browsers), Microsoft (Edge), Mozilla (Firefox) or Apple (Safari). Kroni has no agreement with these services. Each one is run by the company behind the browser, on that company's own terms, and it is the browser, not Kroni, that picks it. Each notification is encrypted, so the push service cannot read it. It sees only the push address, the time and the size of the message. We delete the address when you turn notifications off, and otherwise no later than 60 days after that browser last visited Kroni. Signing out in that browser stops its notifications at once.
- Cloudflare, Inc. — DDoS protection and CDN for kroni.no.
- PostHog — product analytics and error tracking for the app, the backend and the website. Processes app-usage events, crash and error reports, diagnostic logs and, on the backend, distributed traces, linked to a pseudonymous user identifier as described in section 02, as well as the website usage and error data described in section 13. PostHog is a third-party processor bound by a Data Processing Agreement; the data is hosted on PostHog Cloud's EU region (eu.i.posthog.com) and is not used for PostHog's own purposes or for marketing. PostHog has its own privacy policy.
Relatives the parent chooses. When a parent makes a family link (section 02), whoever has the link sees what the parent chose for it: the child's first name, the avatar and open goals, and wishes and amounts if turned on. That person is not our processor. The parent decides who gets the link and can remove it at any time.
Personal data may be disclosed to public authorities where we are legally required to do so.
An up-to-date list is available by contacting support@kroni.no.
Transfers outside the EEA
Some of our processors — especially Clerk and RevenueCat — are established in the US and may have data flows there. Such transfers rely on the EU Commission's Standard Contractual Clauses (SCCs) per GDPR Article 46, supplemented by technical and organisational measures.
Data about payments that Stripe handles (see section 07) may be transferred to Stripe, Inc. in the US. Stripe, Inc. is certified under the EU-U.S. Data Privacy Framework (DPF), and the transfer also relies on the Standard Contractual Clauses (SCCs).
Kroni's core databases and application servers are operated by Hetzner in Finland, so day-to-day processing takes place within the EU/EEA. The «central» dataset — chores, completions, virtual balances and child profiles — therefore never leaves the EEA in normal operation. Optional chore-proof photos, example photos and voice messages are likewise stored within the EU/EEA, with Scaleway in France. Product analytics and diagnostic data is processed by PostHog on its EU cloud region, so it too stays within the EU.
Information security
We have implemented reasonable technical and organisational measures:
- TLS encryption on all traffic.
- Hashing of sensitive fields — the child's PIN is stored only as a one-way hash, never in clear text.
- Access control on a need-to-know basis.
- Logging and monitoring via PostHog, a third-party processor hosted in the EU, plus regular security updates.
- Regular database backups and restore procedures.
- We never process card numbers, CVC codes or BankID data.
Your rights
As a data subject you have the following rights under the GDPR:
- Access (Art. 15): See what data we hold and receive a copy.
- Rectification (Art. 16): Have inaccurate or incomplete data corrected.
- Erasure (Art. 17): Request deletion of personal data.
- Restriction (Art. 18): Have processing temporarily paused.
- Portability (Art. 20): Receive your data in a structured, machine-readable format.
- Objection (Art. 21): Object to processing based on legitimate interest.
- Withdrawal of consent (Art. 7(3)): Withdraw consent at any time.
Email support@kroni.no. We respond within 30 days.
Complaint to the Data Protection Authority
If you believe we process your personal data in breach of the rules, you have the right to lodge a complaint with the Norwegian Data Protection Authority:
Datatilsynet
P.O. Box 458 Sentrum, 0105 Oslo, Norway
Phone: +47 22 39 69 00
Web: datatilsynet.no
If you live in another EEA country, you may instead lodge your complaint with your own national supervisory authority.
We would still appreciate hearing from you first.
Children and parental responsibility
The age of digital consent under GDPR Article 8 is set at 13 in Norway. Children under 13 may only use Kroni through a child profile created by a parent or legal guardian, who consents on the child's behalf.
For children 13 or older the parent may take the child's own consent into account. Either way, all administration and account ownership remain with the parent.
A parent who makes a family link (section 02) decides who sees the child's goals, and answers for that choice. Nothing a relative sends reaches the child except ready-made cheers, and the child's profile says who can see their goals.
If you are in the United States, please also read the dedicated United States (COPPA) section below.
Personal data breaches
If a breach occurs, we notify the Data Protection Authority within 72 hours, per GDPR Article 33. If the breach is likely to result in a high risk to the persons affected, we will also notify you directly, per GDPR Article 34.
Changes to this policy
We may update this policy to reflect changes in the service or the law. Material changes are notified at least 30 days before they take effect.
Contact and DPO
For privacy questions and rights requests:
Nilsen Konsult
Email: support@kroni.no
Families in the United States (COPPA)
Kroni is a family app intended to be set up and managed by a parent or guardian. In the United States, the Children's Online Privacy Protection Act (COPPA) protects children under 13, and the following applies to them.
We collect a child's information only after a parent creates that child's profile. The parent provides the limited data described in section 02 — a first name or nickname, optionally a birth year (never a full date of birth), an optional avatar from a fixed set, and an optional four-digit PIN stored only as a one-way hash. The child does not create an account, is never asked for an email address, phone number, last name or location, and joins the family only through a six-digit code the parent shares.
If the parent switches on the optional chore-photo-proof setting for a chore, any photo the child takes is used solely so the parent can verify that one chore. It is stored encrypted in the EU and deleted as soon as the parent approves or declines the chore. Otherwise it is deleted within a retention window the parent chooses (from 1 hour up to 7 days), measured from when the photo is first opened, and within 7 days at the latest if it is never opened; see section 02. The parent controls this setting and can leave it off.
Once a child's device is paired, it sends what the child does in Kroni (the chores they tick off, and the rewards, wishes and goals they ask for). As persistent identifiers it sends an install ID and a push token, and usage and crash events under an anonymous ID that is never linked to the child's name. We use these identifiers only to support Kroni's internal operations: keeping the child signed in on that device, delivering notifications, showing the parent which devices the child uses, and finding and fixing errors. We never use them to build a profile of the child, to contact the child, or for advertising.
Parental consent and direct notice. Only a signed-in parent, whose email address our login provider has verified, can add a child. When they do, we record their consent: which parent, when, and which version of this notice. A few minutes later we email that parent a direct notice at the same address. It names the child and says what we collect from and about the child, why, how long we keep it, and how to review, change or delete it and so withdraw consent. A parent who did not add the child can reply, and we delete the profile. The collection is used solely to operate the chores, allowance and reward features (section 05), and we do not condition a child's use of Kroni on collecting more personal information than is reasonably necessary for those features.
We do not serve behavioural advertising to children, build advertising profiles of them, or sell or share children's personal information. We disclose it to no third party ourselves: only the service providers in section 07 handle it, on our behalf and under contract. The only exceptions are the parent's own choices: the helpers a parent invites (section 02), who see the children's first names, avatars and that day's chores, and a family link (section 02) the parent can make, which shows a relative the child's first name, avatar and open goals, and wishes and amounts if the parent turns them on. A relative can send the child only ready-made cheers, and the parent can remove a helper or a link at any time.
Retention and security. A child's information is kept only as section 06 says: completed chores up to 90 days after approval, chore photos up to 7 days, and everything within 30 days of deleting the child's profile or the family account. The consent record is deleted with the child's profile. We keep a written information security programme for children's data, with a named coordinator, a yearly risk assessment and review, and the safeguards in section 09.
Parental rights. A parent can review, edit or delete a child's information at any time by managing or removing the child profile in the app, or by emailing support@kroni.no, and can refuse any further collection by deleting the profile. Deleting the profile withdraws consent and deletes that child's information. Deleting the family account removes the children's personal data as described in section 06. For COPPA requests, contact support@kroni.no.
United States state privacy rights
We do not «sell» or «share» personal information as those terms are defined under the California Consumer Privacy Act (CCPA/CPRA), and we have not done so in the preceding 12 months. We do not engage in cross-context behavioural advertising.
Residents of California and other US states with comparable laws may request to know and access, delete and correct their personal information, and will not be discriminated against for exercising these rights. To make a request, email support@kroni.no; we accept requests from authorised agents.
Under California's «Shine the Light» law we do not disclose personal information to third parties for those parties' own direct marketing.
Where a US state law requires apps to ask the App Store or Google Play for a user's age range, Kroni does so as described in section 02: the answer is used only on the device and is neither stored nor sent anywhere.