Privacy
Effective the day Oathful launches on the App Store
Who we are: Oathful LLC, a Michigan limited liability company, 20813 Adrienne Dr, Macomb, MI 48044 · Contact: privacy@oathful.app (anything else: support@oathful.app)
This policy covers the Oathful iPhone app and the website at oathful.app.
The short version
Oathful locks the apps you lose time to and opens them when you prove you kept your word. To do that it keeps your locks (their days and times, never which apps), your keys and how each day went, and the proof you send. Photo proofs and second looks are checked by an AI, Anthropic's Claude. Nobody else using Oathful sees any of it. Oathful never charges for a miss and takes no card details.
We do not sell your data, we do not show ads, and we do not track you across other companies' apps or websites. The app has no third-party analytics: it records how it is used and its errors in our own database. A lot stays on your phone and never reaches us: which apps and websites you pick for a lock (Apple never tells us), your reminders, your motion readings, and your Apple Health data except the one total that proves a day.
What we collect, and why
Your account
| Data | Why | Where it goes |
|---|---|---|
| Email address | To sign you in (a code we email you) and to send account emails. | Our database (Supabase). Emails are sent by Resend. |
| Your name, if you save one, or the name Apple or Google gives us when you sign in with them. | Shown on your account. | Our database. |
| Sign in with Apple or Google | Apple or Google tells us your email address (Apple may give a private relay address instead) and your name if you allow it. Google also sends a link to your profile picture, which the sign-in service stores with your account; Oathful does not use or show it. For Sign in with Apple we keep a token Apple issues, so that deleting your account can disconnect Oathful from your Apple ID, as Apple requires. | Our database. |
| Time zone | Your day and your due times are worked out in your own time. | Our database. |
| Master keys and vacation: how many master keys you have left, the day you last used one, and the dates of a vacation. | So the rules hold on any phone you sign in on, and our server can refuse what they don't allow. | Our database. |
Your locks
| Data | Why | Where it goes |
|---|---|---|
| Each lock: its name and colour, the days it is on, when it starts (the start of the day or a bedtime), the time its keys are due by, how long a miss keeps it shut, a pause, a locked-in date, a change waiting for tomorrow, and how many apps it holds ("4 apps") with a code that points to Apple's selection on your phone. | To run your locks, keep them when you change phones, and hold the rule that a lock can't be loosened on a day it is on. | Our database. Never which apps or websites (see Screen Time). |
Your keys
| Data | Why | Where it goes |
|---|---|---|
| Each key: its name and sticker, the locks it opens, how it is proved and that proof's settings (for example what the photo must show, the place you pinned, the minutes, the steps or the Health reading), and the days and due time its locks give it. | This is the product. | Our database. |
| Each day's outcome: turned, missed, being checked, excused, and when it was recorded. | Your History and streak, and deciding misses. | Our database. |
| The wake-up alarm: the time, its days, how you prove you're up, and which mornings your iPhone really held the alarm for. | To ring it, and so a morning that never rang is never judged. | Our database; the alarm itself is set on your phone through Apple's alarm system. |
Proof
What you send depends on how the key is proved. Proof marked "AI" is sent to Anthropic's Claude to be judged (see Automated review).
| Proof | What we receive | Where it goes |
|---|---|---|
| Photo, wake-up photo | The photo, taken in the app's own camera, never from your library; and, for a wake-up photo, the photo of the spot you took when you set it up. AI. | Private storage on your account (Supabase), and Anthropic for the check. |
| A fingerprint of each photo (a short code worked out from it, not the picture) | To spot the same picture sent twice. | Our database. |
| The AI's verdict | Kept, didn't match or couldn't tell, the one-sentence reason shown to you, and which AI model decided. A note you add to a retake goes with it. | Our database. |
| Tap (I did it) | That you tapped, and when. Nothing else: no photo and no check. | Our database. |
| Timer and Phone down | When the session started and whether it ran its length. For Phone down, the phone's motion sensor is read on your phone to tell whether it is face down; the readings are not sent. | Our database (the times and result only). |
| Place, steps, Apple Health | See Location and Apple Health and steps. |
Keys made before 2026-11-18 with a proof the app no longer offers for anything new (a screenshot, before and after photos, a timelapse, the automatic place proofs, the Screen Time limit, or the older written, voice and link proofs) keep working as they were and send what those proofs always did: the picture or a few stills (AI), an outcome at the place's edge, or whether the day stayed under a Screen Time limit (never which apps or for how long).
Second looks
| Data | Why | Where it goes |
|---|---|---|
| A second look: the reason you pick and what you write, and up to two photos or screenshots, taken or chosen from your photos. | To judge it by the one rule every second look follows. | Our database and private storage, and Anthropic (with the key's proof settings and the proof you sent that day). |
Location
| Data | Why | Where it goes |
|---|---|---|
| The place you pin: its coordinates. You set it on the map by tapping, dragging, searching, or using where you are (one reading at that moment). | The pin is part of the key: the place you will be at. | Our database, with the key. |
| A place check-in (and the wake-up alarm proved by a place): one reading of your phone's location, only when you tap Check in, with "While Using the App" permission. | To confirm you were inside the 100 m (330 ft) circle around the pin. | We keep how far you were from the pin and whether it passed, not the coordinates. |
| Older automatic place proofs (only on keys made with them before 2026-11-18): "Always" permission. Your iPhone tells the app only when it crosses into or out of a pinned circle, never your position in between or your route. | To turn or miss the key without a tap. | We keep the outcome, when it happened, and whether the phone was watching that day. |
| Map search: the words you type in the map's search, and the middle of the map rounded to about a kilometre. | To find places by name or address. | Sent to Photon, a place search run by komoot (Germany) on OpenStreetMap data. Not sent with your name, email or account. |
| The map itself | To show the map. | Drawn by Apple Maps under Apple's privacy policy. |
Apple Health and steps
Only for a steps or Apple Health key (Premium) or a wake-up alarm proved by steps (Premium), and only after you allow it in Apple's own Health sheet. Oathful reads only, never writes to Health, and reads only the reading you chose: steps, sleep, workout minutes, mindful minutes or active energy. Entries typed into Health by hand don't count. A steps alarm also counts steps with your iPhone's own motion chip, on the phone.
| Data | Why | Where it goes |
|---|---|---|
| The day's total for that reading, or the steps counted after an alarm, stored when it turns the key (for example "10,432 steps"). | To record that the key was turned and show you why. | Our database, with that day's record. |
Your Health data is read on your phone and nothing else from Health leaves it. It is never sent to the AI reviewer, never used for advertising or marketing, and never sold or shared with anyone except our hosting provider, which stores it for us.
Screen Time (Family Controls)
Oathful uses Apple's Screen Time framework to run your locks. Oathful never learns which apps or websites you picked: Apple's list hands the app an anonymous token, it stays on your phone, and your iPhone does the locking, on the schedule the app gives it, even when Oathful is closed. The screen you see on a locked app (the lock's name and its next key) is drawn on your phone.
| Data | Why | Where it goes |
|---|---|---|
| For a lock: how many apps it holds, when it starts, its due time and its miss length (see Your locks). | To schedule the lock on your phone and keep it with your account. | Our database (the count and times); the apps' token stays on your phone. |
| Whether Screen Time access is on | To tell you when it is off, so your locks aren't working. | Read on your phone. |
Money from before 2026-11-17
Oathful no longer charges for a miss and no longer takes cards. In testing, before 2026-11-17, a commitment could carry money on a miss. Records from then (the agreement signed, any charge, and Stripe's customer reference with a card's brand and last four digits) are kept read-only, only as described under How long we keep it, so a past charge can still be answered for, including to a bank or to Stripe if a charge is disputed. Stripe keeps its own records of past charges as the law requires.
Premium subscription
| Data | Why | Where it goes |
|---|---|---|
| Whether you have Premium, which plan, until when, and whether the one-time offer has been shown to your account. | To give you Premium on any phone you sign in on, and so our server knows your plan (Locked in needs it). | Apple takes the payment; we never see your payment details. RevenueCat, which connects us to Apple's in-app purchases, receives your Oathful account ID and your purchase history, and tells our server. |
| A log of subscription events (the kind of event and when). | So each event from RevenueCat is handled once. | Our database. |
Notifications and emails
| What | What it holds | Sent through |
|---|---|---|
| Your phone's push token, and whether you want to hear when your apps open. | So results our server decides (an AI verdict, a second look's answer, a key settled at its due time) reach your phone when Oathful is closed. The notice's words, which can include a key's name, pass through Expo and Apple to reach you. | Our database; sent by Expo and Apple's push service. |
| Sign-in codes | A code. | Resend. |
Replies to our emails reach support@oathful.app.
Analytics and crash logs (first party)
Oathful records how people move through the app, and the errors it hits, in its own database. There is no third-party analytics or crash-reporting kit in the app, no advertising identifier, and none of it is used for advertising.
| Data | Why | Where it goes |
|---|---|---|
| App events: the app opened; each onboarding step (which screen, not your answers); sign-in and its method; the Premium offer shown and why; a purchase and its plan; a restore; making a key (its kind of proof and whether it opens a lock); sending and turning a proof (its kind); your answer to the notifications question. Each with its time, the app version, and a random ID made on your phone the first time you open the app. | To see where people get stuck and what to fix. | Our database, linked to your account. |
| Crash and error logs: the error message, a technical trace of where in the code it happened, the screen you were on, whether the app had to stop, the time, the app version, the platform and the same random ID. | To find and fix problems. | Our database, linked to your account. |
| Server failures your phone saw: when the app could not reach our server, and the error code. | To tell when Oathful was down, so those days are excused. | Our database. |
Never recorded: anything you type, such as lock and key names or second look reasons. Events from before you sign in wait on your phone and are sent with their own times once you have an account.
The website
| Data | Why | Where it goes |
|---|---|---|
| Your email address, only if you enter it in an early-access form. | To email you when Oathful is released. Every such email has a way to unsubscribe. | Our email provider. |
| Visit counts: which pages are viewed, how fast they load, the referring site, browser and country. | To see whether the site works and how many people visit. | Cloudflare Web Analytics, which sets no cookies and builds no profile of you. |
| Your browser's own storage: the date the early-access window was last shown. | So the window doesn't keep popping up. | Your browser only. Clearing your browser's site data removes it. |
The site sets no cookies and runs no advertising scripts. Our links to Instagram and X take you to those services, under their own policies.
Technical information
Like any online service, our servers and providers receive your IP address and basic request details (such as the app version) when the app or your browser talks to them. App updates are delivered through Expo, which receives the same kind of request details.
What stays on your phone
These never reach Oathful's servers:
- Which apps and websites you picked for a lock, and the locking itself, which your iPhone does.
- The screen on a locked app, drawn on your phone from what it already holds.
- Reminders before a key is due, scheduled by iOS on your phone, and the reminder the day before a free trial ends. They may show on your Lock Screen; iOS's notification settings control previews.
- The widget and the Live Activity, which read from storage on your phone.
- A photo until you send it.
- Your Apple Health data, except the single total described above.
- Motion readings during a Phone down session or a steps alarm (only the step count is sent).
- Your onboarding answers (for example how many hours a day you're on your phone, and the apps and keys you pick there).
Not offered
Friends, sharing, telling someone when you miss and doing it together are not part of Oathful. Nobody else using Oathful can see your locks, your keys, your History or your proof. If we ever offer these, we will update this policy first.
Automated review
Photos and wake-up photos are judged by an AI, Anthropic's Claude, not by a person, and so is every second look (there is no human review of second looks). Before your first AI check, and before your first second look, the app asks once for your agreement: "Anthropic's Claude checks it against what it must show · Never used to train AI · Kept only for your record". You can take it back in You › Privacy and terms (AI photo checks, Stop); the next one then asks again.
What Anthropic receives: the photo (and the photo of the spot, for a wake-up photo), the key's name and what you said the photo must show, the day being proved, any note you added to a retake, and for a second look your reason, your photos and the rule it is judged by. Not your name or email. Under Anthropic's commercial terms it does not use them to train its models. The verdict and its one-sentence reason are shown to you. No person looks at your proof in the ordinary course. A person at Oathful reads what you send to support, and may look at the day it is about, to answer it.
Who else sees it
Service providers who process data for us, under contract, and only to provide the service:
| Who | What for | What they receive |
|---|---|---|
| Supabase | Our database, file storage and sign-in. | Everything we store, on our behalf. |
| Anthropic (Claude) | Automated review of proof and second looks. | What is listed under Automated review. |
| RevenueCat | Premium subscriptions. | Your account ID and purchase history. |
| Resend | Sending emails. | Your address and the email's content. |
| Expo | Delivering app updates and push notifications. | Basic request details; your push token and the notice's words. |
| Apple | Sign in with Apple, the App Store and its in-app purchases, Apple Maps, push notifications, and on your phone alarms, Health and Screen Time. | What each of those services needs; alarms, Health and Screen Time run on your phone. |
| Sign in with Google, if you use it. | What Google sign-in needs. | |
| komoot (Photon) | Map search. | The words you search and a rounded map centre, not linked to your account. |
| Cloudflare | Hosting oathful.app and counting visits. | Website requests and visit counts. |
| Stripe | Records of charges made in testing, before 2026-11-17. Nothing new is sent. | Past charges only. |
We share personal data with no one else, except where the law requires it, and as said under Money from before 2026-11-17.
No tracking, no ads, no selling
Oathful shows no ads, uses no advertising identifiers, does not track you across other companies' apps or websites, does not sell your personal information, and does not share it for advertising.
How long we keep it
| Data | How long |
|---|---|
| Your account, locks, keys, wake-up alarm, record, master keys and vacation, AI verdicts, second looks, analytics and crash logs | For as long as you have an account. Deleting your account deletes them. |
| Proof photos and second look photos | 90 days after they were taken, then they are deleted automatically (the files themselves, not only the link). Deleting your account deletes every one of them at once, sooner. The photo of the spot you took when you set up a wake-up alarm, and the photo of what a key must show, stay as long as that key does, because each day is compared with it. The AI's verdict and its reason stay with your record. |
| A key you delete | Marked deleted and kept with your record, with its days and proof, until you delete your account, so its days stay in your History. |
| Your History on Free | All of it is kept; Free shows this month and last, and Premium every month. |
| Agreements to money and charge records from before 2026-11-17 | Kept read-only after you delete your account, without your name, your account or the commitment's name: we keep the amounts, the times, the sentence agreed to and the schedule, deadline and kind of proof, and drop the place, the receipt link and anything else typed. They are deleted 7 years after the account was. Stripe keeps its own records of past charges as the law requires. |
| The subscription event log | Kept after you delete your account, with an account number that no longer leads to anyone. |
| Your RevenueCat record, and any Stripe customer record and card left from testing | Deleted with your account. |
| An early-access email address | Until Oathful is released and we've told you, or until you ask us to delete it, whichever comes first. |
| Request logs and backups at our providers | As each provider keeps them; data deleted from Oathful leaves backups as they roll over. |
Your choices
- Delete your account in the app (You › Account › Delete account), at any time, even while a lock is on. This deletes your account, locks, keys, alarm, record, every proof photo, analytics and crash logs, deletes your record at RevenueCat and any Stripe customer record left from testing, and disconnects Sign in with Apple. Records of charges from before 2026-11-17 are kept as described above. Deleting your account does not cancel a Premium subscription: cancel it in your Apple ID settings (the app offers a link).
- Download your data: in the app (You › Account › Download my data: your locks, keys, alarm, History and app logs as one file).
- AI checks: agree before the first one, or take your agreement back in You › Privacy and terms.
- Notifications: switch each kind off in You › Notifications, or in iOS Settings.
- Location, camera, photos, motion, Apple Health and Screen Time can be turned off in iOS Settings at any time; the keys that need them will tell you. If you turn off the access a proof needs, your phone can no longer vouch for that key's days. Turning off Screen Time access stops your locks, and counts as a miss unless it is back on before your next key is due (see the Terms).
- Access, correction and deletion: write to privacy@oathful.app. We'll reply within 30 days. Depending on where you live, including California and the European Union, you may have further rights under local law, such as the right to object to processing or to complain to a data protection authority. We won't treat you differently for using any of them.
Children
You must be 13 or older to use Oathful, and we do not knowingly collect data from anyone younger. If you think a child under 13 has an account, write to privacy@oathful.app and we will delete it and everything in it.
Teens (13 to 17). A teen may use Oathful with a parent's or guardian's permission, and where the law asks for a parent's consent to the use of a teen's data (up to age 16 in some EU countries), that consent is needed. We collect the same data from a teen as from anyone (above) and nothing more; we never sell it, never show ads, and nothing a teen makes is shown to anyone else. Photo proofs are checked by an AI, Anthropic's Claude, and the app says so before the first check and asks for agreement. We follow Anthropic's guidelines for products used by people under 18 and the children's privacy laws that apply to us, including COPPA in the United States (which is why no one under 13 may use Oathful). A parent or guardian can ask us at privacy@oathful.app to see or delete a teen's data.
Where it's stored
Oathful is based in the United States. Your account data is stored by Supabase in the United States (AWS, Ohio, us-east-2). Anthropic, RevenueCat, Resend, Expo and Cloudflare are US companies; map searches go to komoot's Photon service (Germany).
Security
Data is encrypted in transit and at rest by our providers. Your proof photos are in private storage that only your account can read, and once a proof is sent it cannot be swapped for another. Access on our side is limited to what running the service requires. No system is perfectly secure, and we will tell you if something goes wrong with your data.
Changes
If we change this policy, we'll update it here and change the date at the top. If a change affects how we use information you've already given us, we will tell you in the app before it takes effect.
Contact
Oathful LLC · 20813 Adrienne Dr, Macomb, MI 48044 · privacy@oathful.app