Privacy Policy — LU6OLE

Version 1.5 — of 19 October 2026

In two sentences

LU6OLE protects the phone of a child aged 6 to 15: it closes the apps that their parents have not allowed, puts the phone to sleep at night, and lets the parents adjust all of this from their own phone. It has no account for the child, no advertising and no statistics — the parents, for their part, sign in to their page with their Google or Apple account: it reads neither messages nor the websites visited, and what it sends to the parents' page is limited to the settings, the list of apps on the phone, the state of the protection, the time spent today in each app, the child's requests and, if the parent has turned on the option, the phone's location when a parent asks for it — for thirty minutes at most, with no history, and with a message on the child's phone each time. Its website filter asks Cloudflare for Families whether a website name (for example "example.com") is for adults or dangerous; neither Cloudflare nor LU6OLE keeps a list of them.

1. Who is responsible for your data

Géry ROTSAERT EI, sole trader, trading name SOSBY — LU6OLE is a SOSBY product —, registered under SIRET 399 538 172 00020, 1 quai Maréchal Joffre, 69002 Lyon, France. The publisher's full identity appears in the legal notice.
Contact for any question or request relating to data: contact@lu6ole.app.

2. What is processed, why, and on what basis

LU6OLE is installed by a parent on their child's phone, and set up by them, behind a six-digit code that the child does not know. It is the data of this phone that is covered here.

What stays on the child's phone

DataWhyWhat LU6OLE does with it
The parent's codeTo protect the settings, the uninstallation and the Android settings that target LU6OLEKept as a fingerprint (hash), on the phone only; it never leaves the device
The child's month and year of birth, entered by the parentTo check that LU6OLE suits their age (6 to 15) and, at 15, to stop blocking anything and leave the choice of location to themKept on the phone only; they never leave the device (only the fact of being 15 leaves it, so that their parents know). Neither the day of birth nor the child's name is requested
The name of the app in the foregroundTo close an app that is not allowed, whose time for the day is used up, or any app at night (except the phone, emergency calls and SOSBY)Read at the moment the app opens, by the accessibility service (point 3); only its name is read, never its content
The time spent today in each appTo apply the time limits and the day's screen time, and to show it to the child as well as to their parentsReset every night at midnight; past days are not kept
The texts of the Settings screens and of the app installation screensTo recognise those that target LU6OLE (turning it off, uninstalling it) and to ask for the parent's codeRead on those screens only, at the moment they are displayed, then forgotten; never saved, never sent
The list of launchable apps (name and technical name)To show them to the parent so that they can choose, and to the child so that they can see what is allowedRead on the phone; sent to the parents' page (next table)

What leaves the child's phone

DataRecipientWhyLegal basis
A randomly generated identifier at the first connection, and a secret, of which the server keeps only the fingerprint (hash)The LU6OLE service (Cloudflare)To recognise this phone without ever reading a hardware identifier, a phone number or an accountPerformance of the contract (the service requested by the parent)
The settings: allowed apps, time limits, bedtime, the day's screen time, school days; the name the parent gave to the phoneThe LU6OLE service, then the linked parentsTo adjust the child's phone from the parent's page, and the reversePerformance of the contract
The list of launchable apps (displayed name, technical name, and whether it is always allowed)The LU6OLE service, then the linked parentsSo that the parent chooses what is allowedPerformance of the contract
The state of the protection: guardian running or not, uninstallation blocked or not, battery unrestricted, website filter on or bypassed, permanent notification displayed, code created, LU6OLE version, time of the last connectionThe LU6OLE service, then the linked parentsTo warn the parent when the protection stops, with the action to takeLegitimate interest (that the protection wanted by the parent holds)
The time spent today in the apps where the child has spent at least one minute (twenty at most)The LU6OLE service, then the linked parentsSo that the parent sees the same figure as the child, as parental control tools allowPerformance of the contract
The child's requests: to open a blocked app, to install one (the name they typed), or for more time; then the answer, the name the answering parent has given themselves ("Dad", "Granny"…) and the note they wroteThe LU6OLE service, then the linked parents; the answer comes back to the childSo that the child can ask, and their parents answerPerformance of the contract
The phone's precise location, its accuracy in metres, the time of the reading and the phone's battery level — only if the parent has turned on the "Locate" option on the child's phone, and only when a linked parent asks for it from their pageThe LU6OLE service, then the parent who requested it (and the other linked parents)To know where the child is, as parental control tools allow (the battery shows whether their phone is about to switch off). The phone sends its location every thirty seconds for thirty minutes at most; the child sees "Dad is looking at where you are, until 6:30 PM" for as long as it lastsPerformance of the contract; the option, Android's location permission and its use in the background are granted by the parent, and can be withdrawn at any time
Notification token (Firebase Cloud Messaging) of the child's phoneGoogle (Firebase), then the LU6OLE serviceTo alert the phone immediately when a parent changes a setting, answers a request or asks where it is, without waiting for its next connection. The message contains only a "look at your page" signal, never any contentPerformance of the contract
The licence: the LU6OLE version, the fingerprint of the certificate that signed the app, a Play Integrity token and, after a purchase, the Google Play purchase token and order number; with them, the phone's randomly drawn identifierGoogle Play, then the LU6OLE serviceCount the fifteen days of trial and the seven days of grace, check the purchase with Google (three phones at most per purchase) and refuse a modified copy of the app. Nothing about the child or what they doPerformance of the contract
The names of the websites requested by the phone's apps (for example "example.com"), never the full address of a page or its content — only if the parent has turned on the website filterCloudflare for Families (1.1.1.3 resolver), directly from the phone, without going through the LU6OLE serviceTo know whether the site is for adults or dangerous, and to block it. LU6OLE neither keeps nor sends the list of sites; Cloudflare undertakes not to keep the IP address of the query and to erase its logs within 25 hoursPerformance of the contract (the filter is turned on by the parent, after a screen that explains it)
IP address and technical connection informationCloudflareTo route the exchanges, limit code attempts (point 4), protect the service against abuseLegitimate interest
Google Play's age signal: if it is shared, the age range (for example "9 to 12 years"), its source (declared, managed by a parent, estimated or verified) and whether a parent has approved the latest significant change; otherwise, only "not shared" or "to be checked". With it, the country (and the state, in the United States) of the connection, deduced from the IP addressGoogle Play, then the LU6OLE serviceTo comply with the laws that require it (Texas, Brazil, then Alabama, California, Utah and Louisiana): where they apply, until Google Play has confirmed the age, no parent can be linked and nothing is sent to the service — the guardian, for its part, keeps protecting the child. The signal is used for nothing else, never for advertising or statisticsLegal obligation

What a parent's phone receives

The parents' page (lu6ole.app/parent) opens from a phone or a computer, with the parent's Google or Apple account. The first time, the parent types the six-digit code shown by the child's phone: that phone is then linked to their account, and they find it on all their devices when they sign in. Up to four parents (four accounts) can be linked to the same phone.

DataRecipientWhyLegal basis
The identifier of the parent's Google or Apple account, their email address and their first name, as Google or Apple pass them on when they sign in (Apple lets them hide the address); or only their email address if they prefer to sign in with a link sent by email (single-use, valid for 15 minutes; the address is the same as that of a Google or Apple account, it is the same account)The LU6OLE service; for the link, Cloudflare's email-sending serviceRecognise the parent on each of their devices, show them the phones linked to them, and write to them about the service if needed. Never advertising, never passed on to the child or to a third partyPerformance of the contract
A session cookie (a randomly generated token, of which the server keeps only the fingerprint (hash))The parent's browser, and the LU6OLE serviceStay signed in on that device, without typing againPerformance of the contract
The verification that the parent is an adult — only if the child's phone is in the United States or Brazil: the parent's email address, the child's country and a randomly generated reference; then the result ("verified") and the transaction identifier returned by Kids Web Services; or, in the United States, the parent's statement that the child is 13 or olderKids Web Services (Epic Games), then the LU6OLE serviceComply with the laws that require it: in the United States for a child under 13 (COPPA), in Brazil for a child under 16 (ECA Digital). Until it is done, the phone is linked but nothing is shown to the parent or sent to the service — the guardian, for its part, keeps protecting the child. Kids Web Services offers the parent a bank card (a few cents, refunded right away) or an official ID number; LU6OLE never sees the card or that number. Done once, it covers all of the parent's childrenLegal obligation; and the parent's agreement, given when they request the verification email after reading what will be collected

LU6OLE never receives the parent's password: signing in takes place at Google or at Apple. It asks only for the basic identity ("openid", email address, first name), never for access to their messages, their contacts or their files. If they choose, the parent receives notifications when a request arrives: their browser provides a subscription address for this, kept by the service, and the notification goes through their browser's notification service (Google, Mozilla, Apple or Microsoft). It contains only "New request" and the name given to the phone; the details are read on the page.

What LU6OLE does not do

3. The accessibility service (AccessibilityService)

LU6OLE uses Android's accessibility service, called "the guardian" in the app, for two things only:

  1. Knowing which app has just opened — its name, nothing else — to close those that the parent has not allowed, those whose time for the day is used up, those that turn on a camera or microphone the parent has not allowed them, and all of them at night except the phone, emergency calls and SOSBY. It then returns to the home screen: that is the only action it takes. It also counts the time spent today in each app, which the child sees on their screen and the parent on their page.
  2. On the Settings and app installation screens only, reading their texts to recognise those that target LU6OLE, and asking for the parent's code before it is turned off or uninstalled.

It never reads the content of other apps, nor messages, nor what is typed. It never turns on by itself: the parent turns it on, after a screen that explains all this to them and asks for their agreement. They can turn it off at any time, with their code, in Settings, Accessibility.

LU6OLE also uses, with the parent's agreement, a local VPN (Android's VpnService) for its website filter: only the questions "what is the address of such-and-such site?" go through it, never the pages, the videos, the messages or what is typed, and it leads to no LU6OLE server. LU6OLE itself blocks gambling and the services that would allow the filter to be bypassed, and forces safe search on Google, YouTube and Bing; it passes the other questions to Cloudflare for Families (point 4), which answers "site blocked" for adult and dangerous sites. Android shows a key at the top of the screen while it is running.

Camera and microphone, app by app. A parent can leave an app allowed while depriving it of the camera or the microphone. Android does not let LU6OLE take them away from the app; it only tells LU6OLE, without any permission, that a camera has just turned on or that a microphone is recording. If the app on screen is deprived of it, the guardian closes it like a non-allowed app, and the child reads why. LU6OLE sees and hears nothing, keeps nothing, and none of this leaves the phone. SOSBY and system apps (including the phone) are never affected.

LU6OLE also uses, again with the parent's agreement, Android's device administrator function, with no policy at all (neither lock nor wipe), for one thing only: preventing the child from uninstalling LU6OLE without the parent's code. It declares itself to Google Play as a parental control tool.

4. Who receives this data

Some of these providers are established in the United States: the transfers rely on the EU–US data protection framework and on the European Commission's standard contractual clauses.

The apps that the child uses (and SOSBY, which LU6OLE never blocks) are independent of LU6OLE and apply their own privacy rules.

5. For how long

6. Your rights

You have the rights of access, rectification, erasure, restriction, objection and portability, as well as the right to withdraw your consent at any time.

You may lodge a complaint with the CNIL (www.cnil.fr), 3 place de Fontenoy, 75007 Paris, or with the data protection authority of your country.

7. Children

LU6OLE is designed for the phone of a child aged 6 to 15. It is the parent who installs, sets up and activates it: they create the code, they turn on the guardian after reading the explanation, they link their page. The data described in point 2 is processed at the parent's request and under their authority, in the child's interest.

8. Security

The exchanges between the child's phone, the service and the parents' page are encrypted (HTTPS). The phone's secret and each parent's session token are never kept in clear, only their fingerprint (hash); LU6OLE never sees the parent's Google or Apple password. A six-digit code never says whether it has existed (the same answer for a wrong, expired or already used code), and attempts are limited. The parents' notifications are end-to-end encrypted up to their browser. The app's data is excluded from backups to Google Drive.

9. Residents of the United States

This section is in addition to the above; it does not replace it.

9.1 Children under 13 (Children's Online Privacy Protection Act — COPPA)

Who collects. The operator is Géry ROTSAERT EI (SOSBY), 1 quai Maréchal Joffre, 69002 Lyon, France, reachable at contact@lu6ole.app. No other operator collects data through LU6OLE.

What is collected from a child's phone, and why. A randomly generated identifier (never a hardware identifier); a Firebase notification token, which serves only to alert the phone; the list of installed apps; the time spent today in each; the state of the protection; the requests the child sends to their parents, including the name of an app they type; if the parent has turned on the option, the phone's precise location and battery level during a location requested by a parent (thirty minutes at most, no history). All of this serves one purpose only: that their parents set and follow their phone, as they wished by installing LU6OLE. No advertising, no profiling.

The parent's consent, and its verification. LU6OLE works only once set up by a parent: it is they who install the app, create the code, read the explanation of the accessibility service and turn it on. Then, when they link the phone to their page, they read on that page what will be collected and give their agreement by requesting the verification email; they then prove that they are an adult to Kids Web Services (Epic Games) by one of the methods named in the rule (16 CFR 312.5(b)): a bank card, with a transaction of a few cents that is refunded right away and notified to the cardholder, or an official ID number checked against a database. LU6OLE never sees the card or that number. The verification is done once per parent account; if the parent states that the child is 13 or older, it is not requested. Until then, the child's phone sends the service only what makes it work (its randomly generated identifier, its notification token, the country of its connection and Google Play's age signal), never its apps, its time, its requests or its location. Without verification within 7 days, the parent's link and their request are erased.

To whom it is disclosed. Only to the parents linked to the phone (four at most, each signed in with their Google or Apple account and linked by a code shown by the child's phone). We make no other disclosure, and sell nothing. Our processors (Cloudflare; Google Firebase; the browsers' notification services; Kids Web Services, for the parent's verification only) use this data only to provide their service to us.

The parent's rights. At any time, the parent can review on their page what is held, refuse that we collect more (by uninstalling LU6OLE) and have all the data deleted by writing to contact@lu6ole.app. We never make the use of LU6OLE conditional on providing more information than is necessary.

For how long (written retention policy): see point 5. Nothing is kept indefinitely.

9.2 State privacy laws

10. Changes

Any substantial change will be announced in the app or on lu6ole.app before it applies. The version in force is shown at the top of this document. This text exists in thirty-five languages; in the event of a discrepancy, the French version prevails, without prejudice to the rights you hold under the law of your country.

← Back to home