Privacy Policy

1. Who we are

YoloIt is published by BM NODEX SRL, Intrarea Catedrei 17-23, Et. 1, Ap. 11, Sector 1, 014162 Bucuresti, Romania (trade register J2018013360402, CUI 39887391). We are the data controller for the limited data described below.

On the App Store, the app ships under the same company’s Apple Developer account, Team ID 768R7DDJL8. On Google Play, it is listed under the developer account named Easy solutions. In both stores, the publisher and the data controller is BM NODEX SRL.

Questions, requests and complaints: privacy@yoloit.app.

2. The short version

YoloIt turns real-world challenges into screen time: you do a small thing in the real world, you earn minutes, and the app you chose to block opens for those minutes.

3. What stays on your device

The following is written to the app's private storage on your phone. It is not transmitted to us or to anyone else, and we have no way to read it, with two exceptions: the Support code in the table below travels with the app’s request for its own settings (section 4.3), and a technical log (sections 4.8 and 4.9) can record some of it, such as your minute balance and settings, but never the apps you block. Legal basis for keeping and using this data on your phone: performing our contract with you, that is, providing the app and the features you use (Art. 6(1)(b) GDPR).

Uninstalling YoloIt removes all of it from the phone. On Android, from release 8, none of it is included in Android’s backups either, so a reinstall starts fresh with a new Support code. On iPhone, if you back up your phone, iOS includes this data in your own iCloud or computer backup, as it does for most apps; that copy is held under your Apple Account or on your computer, we cannot read it, and restoring the backup brings the data back, Support code included. You can also wipe it from inside the app — see section 10.

3.1 Screen Time on iPhone and iPad

On iOS, YoloIt uses Apple's Screen Time (Family Controls) framework to block apps. This matters, so it is worth being precise:

• When you pick apps to block, iOS does not tell YoloIt which apps you picked. Apple hands the app an opaque token per app — a meaningless identifier only iOS can resolve. YoloIt can count your tokens; it cannot read them.
• Those tokens are stored only on your device and are never sent anywhere.
• YoloIt does not request Apple's "Family Controls App and Website Usage" entitlement. It never reads your Screen Time usage statistics — not what you opened, not how long you used it.
• Since 3 November 2026, unlock minutes count only while you use the apps. While an unlock is running, YoloIt asks iOS to tell it when the apps you unlocked have been in use for each further minute of that unlock, so that the minutes you spent are used up by actual use, not by the clock. iOS answers only “another minute of use was reached” — never which app, never a total — and that answer is handled on your device and never sent anywhere. If a technical log is on (sections 4.8 and 4.9), it notes the minutes left in the unlock, never which app.

3.2 Usage access and the block overlay on Android

Android has no Screen Time framework, so blocking works differently:

• During onboarding YoloIt asks you to grant Usage access and Display over other apps in the Android settings. You grant them by hand; the app cannot grant them for you.
• With Usage access, YoloIt checks which app is in the foreground. That check happens entirely in memory on your phone; the answer is compared with your own block list and then discarded. The app’s name is not saved to disk, not written to any log and not transmitted. If a technical log is on (sections 4.8 and 4.9), it notes only whether the app in front is one you blocked, YoloIt itself or another app, and when the block screen was shown, never which app.
• If the foreground app is one you blocked, YoloIt draws a full-screen overlay over it. The overlay reads nothing from the app underneath.
• Since 3 November 2026, unlock minutes count only while you use the apps. While an unlock is running, the same foreground check also adds up how long the apps you unlocked are in front, so that the minutes you spent are used up by actual use, not by the clock. That running total lives in memory on your phone for the length of the unlock and is then discarded; it is never written to a log with an app’s name and never transmitted. If a technical log is on (sections 4.8 and 4.9), it notes the minutes left in the unlock, never which app.
• Declining either permission is fully supported — YoloIt still works, it just cannot enforce the block at the operating-system level.

A background service keeps this running while YoloIt is closed. Android requires it to show a permanent notification, so you can see when it is on; on Android 13 and later, if you turn off YoloIt’s notifications, Android shows it only in the list of active apps in Quick Settings.

3.3 Other Android permissions

4. What does leave your device

4.1 Crash reports — Google Firebase Crashlytics

When YoloIt crashes or hits an unexpected error, a crash report is sent to Firebase Crashlytics so we can fix it.

• What is in it: the error and its stack trace, your device model, operating system version and app version, the device’s state at the time (such as free memory and storage, screen orientation and whether it is rooted or jailbroken), and an identifier Crashlytics generates for the installation.
• What is not in it: your name, your email, your app block list, your challenge history or your minute balance. The app never attaches a user identifier, and a fixed "never log" list drops anything resembling an app package name, an app label, notification text, a device identifier or a file path before it can be attached to anything leaving the device. If an error that the app’s own code reports contains an app’s package name, the name is replaced with a placeholder before the report is sent; a crash inside the phone’s native code is reported with the message the system gives it.
• When: in every version you can install, store and test versions alike; only development builds on our own machines send nothing.
• Why: to keep the app working. Legal basis: our legitimate interest in a functioning product (Art. 6(1)(f) GDPR).

4.2 App analytics — Google Firebase Analytics

Store versions collect no analytics. This section describes what older test versions sent, and what every newer version does not. Firebase Analytics lets us see, in aggregate, how the app is used.

• What is sent: the standard measurements the Firebase SDK collects automatically — app opens, session starts, app version, device model, operating system and language, and a randomly generated app instance identifier. Google derives an approximate location (at most city level, never a precise position) from the network address the data arrives on.
• What is never sent: app package names, app display names, your block-list selection, notification text, device identifiers and file paths are all on a hard-coded "never log" list and dropped before an event can carry them. The app also refuses to send any event that is not on a fixed, reviewed list of event names.
• In those older test versions YoloIt itself sent no custom analytics events; what Google's SDK collected automatically was the whole of it.
• No advertising. No advertising SDK, no advertising identifier, no link between analytics and advertising.

Analytics is switched off in newer versions. Older test versions (see the start of section 4) collect the automatic measurements listed above from the first time the app is opened. Newer versions, store versions included, ship with Firebase's analytics collection set to off and collect no analytics at all. If you have an older version, updating turns it off. Legal basis for what older test versions collect: our legitimate interest in seeing how test versions are used, so that we can improve the app (Art. 6(1)(f) GDPR); you can object as described in section 8.

4.3 Challenge content — Google Firebase Firestore

YoloIt ships with a built-in set of challenges. Older test versions use only that built-in set and download no challenge content.

Newer versions also download an updated set when they can and, from Android release 6 and iPhone build 12, the app’s settings too, such as how many minutes a challenge earns. The app also reads a document that names the oldest version we still support, so that an outdated version can ask you to update. Every copy of the app fetches the same public documents in the same way: the request carries none of your data, nothing in it identifies which copy of the app is asking, and a store version writes nothing unless you turn on “Help fix bugs” (section 4.9). The one exception, from Android release 7 and iPhone build 13, is the phone’s own document described below. As with any download, Google's servers see the network address the request comes from. If the download fails, the built-in set and settings are used and the app works normally.

The Support code (newer versions only). The app creates a random number the first time it runs and keeps it on your phone; the number itself never leaves the phone. Profile → About shows a one-way scrambled form of that number as your Support code, which cannot be turned back into the number (earlier test versions call it the tester code). Neither is derived from your device, and neither says anything about you. The phone’s own document below, a test version’s registration and debug log (section 4.8) and the optional bug log (section 4.9) are all filed under the Support code, so Google’s servers see the code in each of those requests. We only learn which code is yours if you choose to send it to us, for example in an email asking for help. Resetting the app or reinstalling creates a new number and a new code, and the phone goes back to the standard challenges and settings until you send us the new code.

The phone’s own document. Each time the app starts and its last check is more than about 5 minutes old, it checks for updated challenges and settings and also asks for one document of its own, filed under your Support code. That is where our team can set a different challenge set or settings for a tester’s phone, or complimentary Premium on our team’s test phones. The request names the Support code, so Google’s servers see it each time. The code is pseudonymous, and we can connect it to you only if you have sent it to us. We do not keep a record of these requests. Most phones have no such document, and the answer is simply that nothing is set. Test versions from before Android release 7 and iPhone build 13 worked differently: they downloaded a list of codes inside one of the public documents and checked it for their own code on the phone.

Why: to keep the challenges and settings up to date, to tell an outdated version that it needs an update, and to apply what our team set for a phone. Legal basis: our legitimate interest in a working, up-to-date app (Art. 6(1)(f) GDPR).

4.4 Notifications

Every notification YoloIt shows is scheduled locally by your own device: the daily reminder (you can turn it off or change its time in Profile), a reminder two days before a free trial ends, a notice when the minutes you earned have landed, on iPhone a notice that brings you back to YoloIt after you tap the button on a blocked app’s screen, and on Android the notices in section 3.3, including an “Unlock ended” notice if the block cannot come back by itself when your minutes run out. There is no push server; we send you nothing and cannot see whether you opened a notification. You can turn YoloIt’s notifications off in your phone’s settings.

4.5 When you write to us

The addresses on this site and in this policy — support@yoloit.app, privacy@yoloit.app, legal@yoloit.app and hello@yoloit.app — are real mailboxes. If you email one, your message, your email address and anything you put in it reach our mail host (section 5) and stay there until we delete them. We use them only to answer you, and we do not add you to any mailing list. To answer support@yoloit.app faster, a program we run reads each new message there and sends the name in its From line, its subject and its text (including your Support code, if the message carries it) to Anthropic, whose Claude model drafts a reply. A person on our team reads every draft, together with a copy of your message, before anything is sent; nothing is ever sent to you automatically. The program keeps the sender address and subject of each message for 90 days, so that it never drafts the same message twice. Apart from the companies named in section 5, we pass your messages to no one. If our website shows a waitlist form, it sends nothing by itself: it opens your own mail app with a message ready to send, and nothing reaches us unless you send it. The app’s “Get help” button works the same way: it opens your mail app with a message to support@yoloit.app that includes your Support code (section 4.3), which you can edit or discard before sending.

Legal basis: our legitimate interest in answering people who contact us (Art. 6(1)(f) GDPR); for privacy requests under section 8, complying with a legal obligation (Art. 6(1)(c) GDPR). We keep ordinary correspondence for up to 12 months after the matter it concerns is closed, and then delete it. Messages that are a request under section 8 we keep for 3 years, because we have to be able to show that we handled them properly.

4.6 What we do not do

• No advertising, no ad networks, no ad identifiers.
• No selling or sharing of personal data.
• No tracking of you across other companies' apps or websites.
• No user accounts and no password; the app never asks for your email address.
• No location collection by the app.
• No access to your photos, contacts, microphone, camera or files.

4.7 Purchases and subscriptions — Apple and Google only

YoloIt Premium is sold through the App Store and Google Play, as auto-renewing subscriptions. Some test versions show the subscription screens in a preview mode, marked “Test build — nothing is charged”: a preview purchase takes no payment, is kept only on your phone, and contacts no store. When you buy for real, this is what happens:

• The payment is made to Apple or Google through your App Store or Google Play account, using Apple’s and Google’s own in-app purchase systems. They handle your payment details under their own privacy policies; we never see your card, your name or your full billing address.
• What stays on your phone: the store tells the app, on your phone, whether your subscription or purchase is active, and the app keeps that answer there to unlock Premium. Restoring a purchase on a new phone works the same way, through the same store account. A reset or an uninstall removes the app’s copy; the store keeps its own.
• What we receive: nothing from your phone. We run no purchase server and use no purchase service other than Apple’s and Google’s own, so the app sends no receipt, transaction identifier or customer id to us or to anyone but Apple or Google. The stores give us the sales reports they give every developer: for each sale, an order number, the product, the price and taxes, the buyer’s country and, on Google Play, the buyer’s region or postcode where Google provides it and the device model. Google Play also lists each order for us and lets us look an order up by its order number or by the buyer’s full email address; we do that only to check or refund an order you ask us about. The reports do not contain your name, your email or your card details.
• In the logs: a test version’s debug log and the optional bug log (sections 4.8 and 4.9) record which plan is active (free, trial, Premium or the old Lifetime), never a receipt or a transaction identifier.
• Why: to unlock what you paid for and keep it unlocked, and to handle refunds through the store. Legal basis: performing our contract with you (Art. 6(1)(b) GDPR); for keeping the stores’ sales reports and refund lists as Romanian accounting and tax law requires (section 6), complying with a legal obligation (Art. 6(1)(c) GDPR).

4.8 Test versions: registration and debug log

Test versions help us find faults before a release. A test version is a build we give testers through TestFlight on iPhone or a Google Play testing track on Android and whose Profile → About says it is a test build (see “How you can tell” below); a build from TestFlight or a testing track whose About says nothing of the kind works like a store version. Versions from the App Store or the public Google Play listing do none of what this section describes; the one thing a store version can do, only if you switch it on, is the bug log in section 4.9. A store version can also keep the same technical log on the phone if you turn it on yourself (seven taps on the version line in Profile → About); that log stays on your phone unless you share it. If you test through TestFlight, Apple also passes us crash logs from the test build and, if you use TestFlight’s feedback feature, your screenshots and comments together with your email address; you control that in the TestFlight app, under Apple’s TestFlight terms.

• The debug log on the phone: some test versions keep a technical debug log on the phone. You can view it and share it yourself from Profile → About → Debug log.
• What is in the log: timestamped technical events — which screens you open, when the app starts and goes to the background, how smoothly its screens draw (frame timings), how its timers and blocking behave, your minute balance as it changes, your settings and the setup answers you give (never your age or how you heard about YoloIt), which challenge set and subscription state it is on, and errors with their technical details.
• What is never in it: the same “never log” list as crash reports applies before anything is written: no app names or package names from your block list, no notification text, no device identifiers, no file paths. There is nothing you type into it.
• Registration: test versions register the phone with our team, filed under its Support code (section 4.3): the platform, the app version and build number, the operating-system version (for example “16”), the phone model (for example “SM-A256B” or “iPhone15,2”), and when the app was first seen, last seen and last hit an error. They update it about 5 seconds after each launch and then at most every 10 minutes while the app is open, or every minute after an error, to record when it last hit one. Registration happens even when the debug log is not being sent.
• Sending the log: test versions also send the debug log to Google Firebase Firestore, filed under the same code: while the app is open (every 30 seconds to 5 minutes, depending on how much is new), when it goes to the background, and straight after an error, up to a daily limit. Before a line is sent, the internal ids of your challenges, completions, unlock sessions and saved challenges are removed, and lines recorded before sending was switched on are never sent. You can switch sending off in Profile → About → Debug log; the log then stays on your phone unless you share it, and the registration continues.
• How you can tell: Profile → About says so — “This test build registers this phone with the YoloIt team and sends a debug log” or, with sending switched off, “This test build registers this phone with the YoloIt team. The debug log stays on this phone.”
• Who sees it, and for how long: only our team’s administrators, through our admin page. It is stored in Google’s Europe multi-region. Each log upload is deleted automatically about 14 days after it was sent, and the registration about 14 days after the phone was last seen; the clean-up runs nightly, so either can take up to a day longer. We can connect any of it to you only if you have sent us your Support code.
• Pausing from our side: we can pause a test version’s registration and log sending remotely, for every test phone or for one phone. While paused, the version registers nothing and sends nothing, and Profile → About says “Paused by the YoloIt team.”
• Why: to find and fix faults in test versions before they reach everyone, and to know which phones and versions a fault happens on. Legal basis: our legitimate interest in shipping a working app (Art. 6(1)(f) GDPR). If you would rather not register or send a log, use a version from the store, or write to privacy@yoloit.app with your Support code and we will delete what we have.

4.9 Store versions: the optional bug log

A version from the App Store or Google Play never registers the phone and never sends a log on its own. On the phones of people we have invited to help us test, it offers one switch, Help fix bugs, in Profile → About. It is off unless you turn it on.

• What turning it on does: for the next 30 days, the app sends us a technical log of the same kind as in section 4.8 — which screens you open, how its timers and blocking behave, your minute balance as it changes, whether you are on the free plan or Premium, and errors with their technical details. Each upload also carries the platform, the app version and build number, the operating-system version and the phone model, and all of it is filed under your Support code (section 4.3). We may limit what is sent to the lines around an error. Nothing recorded before you turned the switch on is ever sent.
• What is never in it: the same “never log” list as in section 4.8: no app names or package names from your block list (a package name in an error message is replaced with a placeholder), on iPhone not even how many apps you picked, no notification text, no device identifiers, no file paths, nothing you type, never your age or how you heard about YoloIt, and the internal ids of your challenges, completions, unlock sessions and saved challenges are removed before a line is sent. We never collect your name.
• How it ends: the switch turns itself off after 30 days, and Profile → About shows the date. You can turn it off earlier at any time; sending stops at once. Turning it on again starts a new 30 days.
• Who sees it, and for how long: only our team’s administrators, through our admin page. It is stored in Google’s Europe multi-region and deleted automatically about 14 days after upload; the clean-up runs nightly, so it can take up to a day longer. To have it deleted sooner, write to privacy@yoloit.app with your Support code.
• Why, and on what basis: to find and fix faults that happen on phones like yours. Legal basis: your consent (Art. 6(1)(a) GDPR), which the switch gives and withdraws. Withdrawing it does not make what was already sent unlawful; that data is still deleted about 14 days after upload, or sooner if you ask.

4.10 This website

This website, yoloit.app, is served from a server we run ourselves. It sets no cookies, runs no analytics or tracking, and loads nothing from other companies: even its fonts come from our server. Like any web server, ours receives your network address and the page you ask for, so that it can send you the page. We keep no access log for this site: the address is used to answer the request and is not stored. Legal basis: our legitimate interest in running this website (Art. 6(1)(f) GDPR). The email links, and the waitlist form whenever the site shows one, only open your own mail app (section 4.5).

5. Who else sees this data

No one else. We use no other analytics, attribution or advertising tool, and no support tool other than the reply drafting described in section 4.5. Each company in this table that handles data for us (Google for Firebase, Anthropic, and our web and email hosts) may use it only to provide its service to us and must protect it at least as well as this policy describes; Apple and Google Play handle the store relationship and purchases on their own account, under their own privacy policies. How we protect it: everything the app and this website send travels encrypted (HTTPS/TLS). In our Firebase project, a phone can read the public challenge and settings documents and its own settings document, which it must ask for by its exact Support code; it can add bug-log uploads (and a test version can update its own registration), but it can never read a log back. Only our team’s administrators, each signing in with their own account, can read or delete logs, list or delete registrations and see crash reports. Our mailboxes are reached only over encrypted connections. If a breach put your data at risk, we would notify the data protection authority and, where the law requires it, you.

6. How long we keep it

• On your device: until you delete it, by resetting inside the app (a debug log kept on the phone is cleared separately, section 10) or uninstalling. We have no ability to reach it.
• Crash reports: retained by Firebase Crashlytics for 90 days, after which Google begins removing them from its live and backup systems.
• Emails you send us: up to 12 months after the matter closes; 3 years for a rights request under section 8. Support drafting records: the sender address and subject of each message to support@yoloit.app, kept by our reply-drafting program for 90 days (section 4.5). Anthropic deletes what it receives for a draft within 30 days, unless it must keep it longer to enforce its usage policy or to comply with the law. TestFlight feedback (section 4.8) is handled like an email to us; TestFlight crash logs stay in App Store Connect for as long as Apple keeps them.
• Analytics: newer versions, store versions included, collect none (section 4.2). Measurements already collected by older test versions are kept at the individual level for 2 months, after which Google deletes them; aggregated reports that contain no individual-level data are not subject to that limit. You can ask us to delete your data sooner (section 8).
• A test phone’s registration: deleted automatically about 14 days after the phone was last seen; the clean-up runs nightly, so it can take up to a day longer (section 4.8).
• Settings our team sets for one phone (a challenge set, settings, or complimentary Premium on our team’s test phones): kept while that phone is part of our testing, then removed (section 4.3).
• Debug logs (test versions that send one): deleted automatically about 14 days after upload; the clean-up runs nightly, so it can take up to a day longer (section 4.8).
• Bug logs from a store version (section 4.9): sent only while your “Help fix bugs” switch is on, at most 30 days per switch-on; each upload is deleted automatically about 14 days after it was sent.
• Purchase records: Apple and Google keep them under their own policies. The app keeps only the store’s current answer (active or not) on your phone, which a reset or an uninstall removes; we hold no purchase records of our own beyond the stores’ sales reports and refund lists (section 4.7), which we keep for as long as Romanian accounting and tax law requires us to keep accounting records, and then delete.

7. Children

YoloIt is not designed for or directed at children under 16. You must be at least 16 to use it. That minimum is never lower than the age at which a person in Romania can consent on their own when an online service relies on consent to process their data (Article 8 GDPR).

YoloIt uses Apple's Family Controls framework — the same framework parental-control apps use — but YoloIt is a self-control app. It blocks the user's own apps at the user's own request on the user's own device. There is no parent/child pairing, no remote supervision and no way for one person to restrict another's device.

8. Your rights

Wherever you live (the GDPR applies to everything we process, because we are established in Romania), you have the right to ask for access to your personal data, its correction or deletion, a copy in a portable form, restriction of or objection to processing, and to withdraw consent where processing is based on consent. Your right to object: where we rely on our legitimate interests (crash reports, section 4.1; the analytics of older test versions, section 4.2; the phone’s own settings document, section 4.3; answering and drafting replies to your emails, section 4.5; a test version’s registration and debug log, section 4.8; running this website, section 4.10), you can object at any time, on grounds relating to your particular situation, by writing to privacy@yoloit.app. We will then stop, unless we can show compelling legitimate grounds that override your interests, rights and freedoms. You can also complain to a data protection authority. Because the controller is established in Romania, ours is the National Supervisory Authority for Personal Data Processing (ANSPDCP), dataprotection.ro; you may also complain to the authority where you live, where you work or where you believe the infringement took place.

In practice, for this version of YoloIt: most of your data is only on your phone, and you can delete that yourself with the in-app reset or by uninstalling. For any other request, and for data held elsewhere, such as your emails to us or the crash and analytics data held by Firebase, write to privacy@yoloit.app. Crash reports and the older analytics carry no Support code or any other identifier you can see, so we can usually find yours only from details you give us (your phone model, the app version and when it happened), and where we genuinely cannot identify you we will say so rather than guess; they are also deleted on their own (section 6). For a bug log, a test phone’s registration or the settings we set for a phone, send us your Support code (Profile → About). We answer within one month.

9. If we add accounts later

Accounts, cloud sync and push notifications are designed but not built in this version. Nothing in the app signs you in, and no account exists. If and when accounts ship:

• this policy will be updated before the feature is released, and the update will be visible in the app and here;
• the app will offer account deletion from inside the app, as Apple requires of any app that offers account creation;
• what we would then store will be described here specifically, not in general terms;
• data export on request will be available.

Until then, this section describes nothing that exists.

10. Deleting your data

11. Changes to this policy

If this policy changes materially we will update the date at the top, publish the new version at https://yoloit.app/privacy, and — where the change affects what we collect — tell you in the app before the change takes effect. This policy is published in English and in Romanian (yoloit.app/ro/privacy); the version in the language your device is set to applies to you.

12. Contact

BM NODEX SRL
Intrarea Catedrei 17-23, Et. 1, Ap. 11
Sector 1, 014162 Bucuresti, Romania
Trade register J2018013360402 · CUI 39887391
privacy@yoloit.app