BarakeDiscover Barake

Barake Privacy Policy

Last updated: October 29, 2026

Barake lets a parent choose which apps are limited on their child's phone, and lets the child earn tokens, called B: by doing chores the parent approves, by passing quizzes on their school curriculum, and with a daily bonus. The child trades their B for screen time, which unlocks the limited apps until it runs out, or for a reward the parent offers in their shop.

Children use this app. We designed data collection to stay minimal, especially on their side. Barake locks and unlocks apps; it never reads what a child does in them. 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: our contact form

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 — shown inside the app, including on your child's phone.
  • What your child calls you (for example "Mom"), if you set it.
  • 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 and the evening summary go out at the right local time and in the right language.
  • Your notification preferences.
  • A referral code, if you entered one, and which account it came from.

About the child, entered by the parent

  • A first name.
  • A school year (from the first year of primary school to the end of high school, or "other"), so that quizzes follow the right curriculum.
  • A color, to tell children apart at a glance.

We never ask for a child's age, date of birth, email address or phone number.

The child has no account. Their phone is linked to the parent's account with a short code shown on the parent's phone (typed, or scanned as a QR code). It then signs in with an anonymous session: a technical identifier, with no email address and no password.

The child's phone: limits, B and screen time

  • The phone itself: whether it is an iPhone or an Android phone, when it was linked, whether blocking has been allowed on it, on iPhone whether it belongs to your Apple Family Sharing group, when it last synced, and the state of its setup. We do not record its model or its system version.
  • The limits you set: the daily cap on screen time that B can buy, bedtime, the morning reopening time, whether traded time expires at midnight, and whether the daily bonus is on, with its maximum.
  • The apps you limit:
    • On iPhone, Apple's Screen Time hands Barake an encoded selection that only Apple can read. Barake cannot see the names of the apps, categories or websites you chose. We store that encoded selection, so that the phone can apply it, and the number of categories, apps and websites it contains.
    • On Android, we store the categories you chose and the package names of the apps you picked one by one (an identifier such as com.example.game), so that the phone can block them.
  • B: each movement in the child's piggy bank — a chore approved, a quiz passed, a daily bonus collected, B you give as a gift, B traded for screen time or for a reward, B given back — with its date and, for a gift, the short note you may add.
  • Screen time: the minutes traded for B, and the minutes used, reported by the child's phone in 5-minute slices, day by day. We do not receive which app the minutes were spent in, or when.
  • The daily bonus: for each day it is collected, the streak and the B it earned; and the days when blocking was turned off on the child's phone, since the bonus cannot be collected on those days.
  • A parent code of four digits, which protects Barake's settings on the child's phone. It is stored as a one-way hash.
  • Linking codes, valid for 30 minutes, and a permanent reconnection code for each child, shown in the child's settings on the parent's phone, which lets their phone be linked again after a reinstall.

Chores

  • What you set up: the chore's name and icon, the B it earns, the days it comes back, whether a photo is required, and which children it is for.
  • Each completion: the day, its status (sent, approved, declined), the time, and the short note the parent may add.
  • Proof photos, only for chores that require one. The photo is taken with the child's phone camera at that moment — Barake has no access to the photo library. It is stored in private storage, reachable only through temporary links given to the members of the account. It is deleted 30 days after it is taken, or sooner if you remove the child or delete your account.

The shop

  • What you set up: each reward's name, icon and price in B, the amount if it is pocket money, which children it is for, and a photo if you add one. You pick that photo on your own phone with the system photo picker: Barake receives only the photo you choose, never the rest of your library. It is stored in private storage, reachable only through temporary links given to the members of the account, and deleted when you remove the reward from the shop, replace its photo, or delete your account.
  • Each trade: the reward's name, icon and price at the time, its status (waiting, handed over, declined, canceled), when it was requested and answered, and the short note you may add.

Barake handles no money: pocket money is handed over by the parent, outside the app.

Quizzes

For each quiz: the subject and chapter, the start and end time, the score and whether it was passed. For each question: when it was shown and answered, the answer chosen, and the result — correct, wrong, out of time, or lost because the child left the app. Questions and correct answers never reach the phone before the child answers: grading happens on our servers.

History and notifications

An activity history (chores approved or declined, quizzes, B earned, given and traded, rewards requested, cap reached) is shown to the parent; the child sees their own, without declined chores. Notifications carry first names, chore and reward names, B, minutes, scores and, sometimes, the parent's short note.

What Barake never sees on the child's phone

  • On iPhone, blocking goes through Apple's Screen Time technology (Family Controls). Barake never sees the names of the apps, nor messages, photos, websites visited or anything shown on the screen. Screen Time data is never used for advertising and never shared with analytics tools.
  • On Android, Barake uses Android's accessibility service and usage access, only once the parent has turned them on:
    • the accessibility service reads only the identifier of the app that comes to the foreground, on the phone, to decide whether to show Barake's blocking screen. It is set up so that it cannot read what the screen displays, and it never reads what is typed on the keyboard;
    • usage access is read on the phone to count the minutes spent in the limited apps. Only the number of minutes is sent to us;
    • the list of installed apps, with their names and icons, is shown in Barake's app picker on the phone and is never sent to us. Only the package names of the apps picked one by one are (see above).

Technical data

  • A notification token, the platform (iOS or Android) and the app version, if notifications are allowed on the phone. The version tells us which notifications that phone understands.
  • 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 at opening on a child's phone.
  • Sign-in sessions: our authentication provider (Supabase) keeps, for each session — the child's anonymous session included — the IP address and the app version it was opened from. They are erased at the latest with the account.
  • Failed code attempts (a wrong linking code), with the IP address they came from. They are erased after 24 hours.
  • Crash reports (Firebase Crashlytics), on the parent's and the child's phones: 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 in-app contact form, with the context we need to answer: your email address, first name, account identifier, subscription status, the first names and roles of the people on your account, language, platform, device model, app version and the date your account was created;
    • by email from the app, a draft that already contains the app version, the device model, its system version, the language and, during setup, the step you are on. You see it and can edit it before sending.

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 child's phone, and no Screen Time data is ever sent to them.

  • Firebase Analytics (Google) — how the app is used: screens reached, steps of the setup, subscriptions started. Linked to your account identifier. On iOS, it runs only if you allow tracking when Apple asks.
  • 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 subscription, tied to your account identifier.

What we do not collect

No location. No microphone. No contacts. No access to the photo library, except the single photo a parent picks for a reward. No browsing history. No content of messages, photos or apps. No advertising shown in the app. No audience measurement, advertising identifier or subscription tool on a child's phone.

On the barake.app website

The website runs no audience measurement and no advertising, and loads nothing from third parties. If you arrive through a campaign link (?utm=…), a cookie remembers that source for 30 days so that the App Store link can carry it; it is read only by your browser.

The website's contact form sends us your email address, your message and, if you give it, your first name, through Resend. We use them only to answer you, and keep them in our mailbox as long as needed to follow up on your request. To limit abuse, the server counts the messages sent from each IP address for ten minutes, in memory only; that count is never stored.

Before the app was released, you could join a waitlist with your first name and email address. We use them only to tell you that Barake is available, and we delete the list at the latest one month after launch. To be removed sooner, write to us through our contact form.

3. Children's privacy — COPPA

A child cannot use Barake on their own. The parent creates the account, adds the child, then links the child's phone and allows blocking on it. Creating the account and adding a child constitutes the parent's consent to the collection of the limited information described above.

We collect from children only what is reasonably necessary to run the service: the first name, school year and color entered by the parent; their chores, photos and quiz answers; their B, daily bonus and trades; the screen time traded and used; and, to operate the service, the anonymous session, the notification token and crash reports. We never condition a child'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 child's chores, photos, quiz results, B, trades and history in the app,
  • correct their first name, school year and color,
  • unlink their phone, which ends its session,
  • remove your child, which erases their chores, completions, photos, B, trades, minutes, quiz results, history, limited apps, reconnection code and linked phone,
  • delete your account entirely, which erases your data and your children's.

You may also write to us through our contact form, and we will act within 30 days. A child may write to us too.

We display no advertising in the app and do not disclose children's information to third parties for advertising.

4. Why we process this data

Purpose Legal basis (GDPR)
Provide the service: account, children, linked phones, limits, chores, quizzes, B, the shop, screen time Performance of a contract
Children's data Parental consent, given when the parent adds the child
Lock and unlock apps on the child's phone Parental consent, given when the parent allows blocking on that phone
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

5. Who else sees this data

We rely on a small number of processors, each for a specific role:

Provider Role Location
Supabase Database, authentication and photo storage (chores and rewards) 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
WhatsApp (Meta) Support conversations, only if you choose to write to us there United States

Apple's Screen Time and Android's accessibility and usage features run on the child's phone itself: Barake sends nothing to Apple or Google through them.

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.

Support over WhatsApp is optional: it appears only while we choose to offer it, and nothing is sent until you tap the button and write a message. The message is prefilled with the app version and, during setup, the step you are on. What you write there reaches us through WhatsApp, under Meta's own privacy policy rather than this one. Email remains available and stays within the providers listed above.

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.

6. How long we keep it

  • Account data, children, limits, chores, B, the shop and its rewards, trades, minutes, quiz results and history: as long as the account exists.
  • A child's information: until the parent removes the child or deletes their account, which erases it immediately.
  • Proof photos: deleted 30 days after they are taken. Removing the child or deleting your account deletes them within the hour.
  • Reward photos: deleted within the hour once you remove the reward from the shop or replace its photo, and when you delete your account.
  • Linking codes: erased one day after they expire. Failed code attempts: 24 hours.
  • Notifications (their text, including first names and notes): 30 days after they are created.
  • An unfinished quiz: closed the next day; its answers stay with the child's results.
  • IP addresses seen when the app is opened: 90 days after they are recorded.
  • Anonymous sessions that are no longer linked to any child: erased after 30 days without use.
  • Crash reports: up to 90 days, at Firebase.
  • After account deletion: erased from our database immediately, including your children's information; copies in our backups disappear within 30 days. Only what the law requires us to retain is kept.

7. 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, in Settings. For anything else, write to us through our contact form. We respond within 30 days.

8. 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.

9. Security

Traffic is encrypted in transit. Each parent's data is isolated at the database level itself: one account cannot technically read another's, and a linked phone reads only its own child's data. B and screen time are credited by our servers, never by the phone: a child cannot approve their own chore, collect a bonus on a day when blocking was off, or trade more than the daily cap, and quiz answers are graded and timed on our side. The parent code and linking 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.

10. Changes

If we change this policy materially, we will tell you in the app before the change takes effect.

11. The terms that go with this policy

Your use of Barake is also governed by our Terms of Service.