Barake Privacy Policy
Last updated: September 14, 2026
Barake lets a parent and their teen agree on a contract: a few chores, a duration, rewards and a consequence. The parent writes and signs it, the teen reads it and signs it, then checks off their chores while the parent approves them.
Teens use this app. We designed data collection to stay minimal, especially on their side, and we do not sell data to anyone, ever.
1. Who is responsible for your data
Orizon42, a French limited liability company (SARL) registered under SIREN 989 845 896, with its registered office at 200 rue de la Croix Nivert, 75015 Paris, France.
Questions: orizon42.com/contact
2. What we collect
From the parent who creates the account
- Email address — to sign you in and send you your sign-in codes. If you continue with Apple or Google, we receive the email address and the name they share with us (possibly a private relay address).
- First name — for display inside the app and on the contracts you send.
- Password, only if you choose to use one — stored as a one-way hash. We never have access to it.
- Language and time zone, so that reminders go out at the right local time and in the right language.
- A referral code, if you entered one when signing up.
About the teen
- A first name, entered by the parent.
- An age in years, optional, entered by the parent — for example "14". It is a whole number, not a date of birth.
- What the teen calls the parent ("Dad", "Mom", a first name), entered by the parent, shown on the contract and in the teen's notifications.
The teen has no account. When they open the app to sign, an anonymous session is created on their phone: a technical identifier, with no email address, no password and no phone number. We never ask a teen for an email address, a date of birth, a phone number, or any information that would let anyone contact them outside the app.
The content of contracts
- The terms: chore titles and the days they happen, start and end dates, rewards (type, title, completion level, and amount if it is pocket money), the consequence chosen and its text if the parent wrote one, reminder settings and automatic renewal.
- Signatures: the first name typed by each signer and the time of signing.
- The teen's suggestions: the changes they ask for and the short note that goes with them, then the parent's answer.
- Daily follow-up: each chore checked off by the teen and when, each approval or refusal by the parent and when, and the reason for a refusal if one was given.
- The end of the contract: the note the parent leaves if they end it early, the final percentage, the reward reached, and the date the parent marked it as given.
- A log of the reminders sent, so that the same reminder never goes out twice.
Technical data
- A notification token and the platform (iOS or Android), if notifications are allowed on the phone.
- Last opening of the app: the date for everyone; on a parent's session only, the platform and the IP address seen at the first and at the most recent opening. We use them to secure accounts, detect abuse and answer support requests. IP addresses are erased 90 days after they are recorded. No IP address or platform is recorded on a teen's session.
- Sign-in sessions: our authentication provider (Supabase) keeps, for each session, the IP address and the browser or app version it was opened from. They are erased with the account or the teen's anonymous session.
- Failed contract code attempts, with the IP address they came from. They are erased after 24 hours.
- Crash reports (Firebase Crashlytics): the error, where it occurred in the app's code, and the device model and system version, with no account identifier attached.
- Messages you send us from the app, with the context we need to answer: your email address, first name, account identifier, subscription status, device model and app version.
On the parent's phone only: audience measurement and subscriptions
These tools run only on a parent's session. None of them is started on a teen's session.
- Firebase Analytics (Google) — how the app is used: screens reached, steps of setting up a contract, subscriptions started. Linked to your account identifier. No contract content is sent.
- AppsFlyer — where new parents come from (which campaign led to an install or a subscription). On iOS, the advertising identifier is used only if you allow it when Apple asks; refusing changes nothing in the app. On Android, your device's advertising ID settings apply.
- RevenueCat — the state of your Premium subscription, tied to your account identifier.
What stays on your phone
- Your teen's phone number. When you send a contract, you pick your teen in your phone's contacts. Barake keeps only that number, only on your phone, to prefill the text message. It is never sent to our servers, never logged, never measured. We do not read or upload the rest of your contacts.
- The text message itself leaves from your own Messages app, with your own phone plan. Barake sends no text messages.
- The clipboard. When the teen opens the app for the first time, it reads the clipboard once, only to look for a barake.app contract link, so that the teen does not have to type their code. On iOS, the system shows that the app pasted. Nothing else is read, kept or sent. The contract page and the parent's app write to the clipboard only when you tap to copy a link or to install the app.
What we do not collect
No photos, and no camera or photo library access. No microphone. No location. No contact list uploaded. No advertising shown in the app. No audience measurement, advertising identifier or subscription tool on a teen's session.
On the barake.app website: the waitlist
Before the app is released, you can join a waitlist on barake.app with your first name and email address. They are sent by email (through Resend) to our inbox, to write to you when Barake launches, and for nothing else. They are not stored in the app's database. To be removed, reply to that email or write to us through orizon42.com/contact; we delete them at the latest one month after launch.
3. The contract page at barake.app/c/CODE
A contract is sent as a link containing a five-character code. Anyone who holds that link can read the contract while it is waiting for the teen's signature: the first names of the parent and the teen, what the teen calls the parent, the dates, the chores, the rewards and their amounts, and the consequence. Once the contract is signed, ended or expired, the page only shows its status, not its content. A draft never has a link.
To keep that page discreet:
- it is not indexed by search engines, not kept in any cache, and does not pass its address on to the App Store or Google Play;
- repeated attempts with wrong codes are blocked for a while;
- it loads no third-party resource, no audience measurement and no ads.
Share the link with your teen only.
4. Children's and teens' privacy — COPPA
A teen cannot use Barake on their own. The parent creates the account, adds the teen and sends the contract; the teen joins with the link. Creating the account and adding a teen constitutes the parent's consent to the collection of the limited information described above.
We collect from teens only what is reasonably necessary to take part in a contract: the first name and optional age supplied by the parent, their signature, their suggestions and note, and their check-offs — plus, to operate the service, the anonymous session identifier and its sign-in session record, the notification token, the date of the last opening and crash reports. No IP address of the last opening is recorded for a teen. We never condition a teen's participation on disclosing more than that, and we use none of it for advertising or audience measurement.
As a parent, you may at any time:
- review your teen's information and contracts in the app,
- correct their first name, age and what they call you,
- remove your teen from your family, which deletes their contracts and erases their information,
- delete your account entirely, which erases your family's data.
You may also reach us through the contact page on our website, and we will act within 30 days. A teen may write to us too.
We display no third-party advertising in the app and do not disclose teens' information to third parties for advertising.
5. Why we process this data
| Purpose | Legal basis (GDPR) |
|---|---|
| Provide the service: account, contracts, signatures, check-offs, approvals | Performance of a contract |
| Teens' data | Parental consent, given when the parent adds the teen |
| Send sign-in codes and answer your messages | Performance of a contract |
| Reminders and notifications | Your consent, given in the phone's settings and revocable at any time |
| Manage subscriptions | Performance of a contract |
| Secure accounts, prevent abuse, block code guessing, fix crashes | Legitimate interest |
| Measure how parents use the app and where they come from | Consent where required (Apple's tracking prompt); otherwise legitimate interest |
6. Who else sees this data
We rely on a small number of processors, each for a specific role:
| Provider | Role | Location |
|---|---|---|
| Supabase | Database and authentication | European Union |
| Resend | Sign-in codes and support emails | United States |
| Expo | Relaying notifications to Apple and Google | United States |
| Apple / Google | Sign-in, subscription payments, notification delivery | United States |
| RevenueCat | Subscription management, parents only | United States |
| Google Firebase | Crash reports; usage measurement, parents only | United States |
| AppsFlyer | Install attribution, parents only | United States |
Notifications contain first names and, sometimes, the short note of a suggestion or of an early end: they pass through Expo, Apple or Google to reach the phone.
These providers act on our instructions and may not use your data for their own purposes. The barake.app website runs on a server operated by Orizon42.
We do not sell your personal information. Install attribution data collected on a parent's phone is used only to measure our own advertising campaigns.
7. How long we keep it
- Account, family and contract data: as long as the account exists.
- A teen's information (first name, age, contracts, anonymous session, notification token): until the parent removes the teen from the family or deletes the account. Either one erases it immediately, unless the teen also belongs to another family on Barake.
- An anonymous session that never joined a contract: erased after 30 days without use.
- Notifications (their text, including first names and notes): 30 days after they are created.
- Log of reminders sent: until 30 days after the end of the contract it concerns. Only the record that an automatic renewal could not take place stays with the contract, so that the renewal is never attempted again.
- IP addresses seen when the app is opened: 90 days after they are recorded.
- Failed code attempts: 24 hours.
- Crash reports: up to 90 days, at Firebase.
- After account deletion: erased from our database immediately, including the teen's information; copies in our backups disappear within 30 days. Only what the law requires us to retain is kept.
8. Your rights
If you are in the United States
Depending on your state — California, Colorado, Connecticut, Virginia and others grant comparable rights — you may request access to your personal information, its correction, its deletion, and a portable copy. You may also opt out of sale or of sharing for targeted advertising: we do not sell, and the only advertising-related tool, AppsFlyer, runs on a parent's phone and can be refused through Apple's tracking prompt or your Android advertising settings. We will not discriminate against you for exercising any of these rights.
If you are in the European Union or the United Kingdom
You have the right to access, rectify, erase, restrict, and port your data, to object to processing, and to withdraw your consent at any time. You may lodge a complaint with your national data protection authority — in France, the CNIL.
Account deletion is available directly in the app, under Profile. For anything else, reach us through the contact page on our website. We respond within 30 days.
9. International transfers
Our database is hosted in the European Union. Some providers listed above operate from the United States. Transfers out of the EU are covered by the European Commission's Standard Contractual Clauses or by the EU–U.S. Data Privacy Framework.
10. Security
Traffic is encrypted in transit. Data is isolated per family at the database level itself: one family cannot technically read another's data, and a teen reads only their own contracts. Signatures, check-offs and approvals are verified by the database: a teen cannot sign in their parent's place or approve their own chore. Contract codes are protected against guessing. We never receive payment details.
No system is perfect. If a breach occurs that presents a risk to your rights, we will notify you and the relevant authority within the legally required time.
11. Changes
If we change this policy materially, we will tell you in the app before the change takes effect.
12. The terms that go with this policy
Your use of Barake is also governed by our Terms of Service.