Oakward Privacy Policy

Last updated: 25 August 2026

Oakward is a family chore and reward app. A parent sets up a household, adds heroes for their children, and assigns quests. This policy explains exactly what data the app stores, where it goes, and how to delete it.

Who this policy is for

Oakward is designed to be set up and controlled by a parent or guardian. Accounts are created by adults. Information about children is entered by the parent, on the parent's judgement, and children use the app on devices the parent has explicitly enrolled.

That is also how Oakward is offered in the stores. It is a general audience household app, rated suitable for all ages, and the person we deal with is the adult who set it up. It is not listed in the App Store's Kids Category and is not distributed under Google Play's Families programme, because those require a formal verifiable parental consent process that Oakward does not implement — a child's name reaches the app because their own parent typed it in. Children are welcome to use Oakward; it is their parent, not the child, who agrees to this policy, holds the account, and can change or delete anything in it at any time.

What we collect

We do not collect photographs or any other images. Earlier versions of Oakward let a parent add a picture to a hero, a reward, or the family profile. That feature has been removed: the app no longer asks for camera or photo library access, cannot upload an image, and every picture previously uploaded has been deleted from our systems. Heroes and rewards use Oakward's own artwork.

We also do not collect dates of birth, ages, precise or approximate location, contacts, browsing history, advertising identifiers, or any biometric data. Face ID, where enabled, is handled entirely by your device. Oakward only receives a yes or no result and never sees your face data.

What we do not do

• No advertising of any kind, and no advertising SDKs.
• No product analytics, attribution, or behavioural tracking SDKs. Oakward does not measure which screens you visit, how long you spend in the app, or what your family does inside it. The one automated report the app does send is a crash report, only when something has actually gone wrong, and only while you leave it switched on — see Crash diagnostics.
• No selling or sharing of personal information. We do not "sell" or "share" personal information as those terms are defined under the CCPA and CPRA.
• No cross app or cross site tracking. Oakward does not request App Tracking Transparency permission because it does not track.
• No notifications, and no push token. Oakward never asks for notification permission, never sends a push alert or an on-device banner, and schedules no reminders. Nothing about your family is registered with a notification service, and no device carries a push token. Approval Hall shows what is waiting for you when you open the app.
• No spending inside the app. The Gold, Essence, potions, and prizes in Oakward are earned by completing quests. They cannot be bought with real money, they have no monetary value outside the app, and there is nothing a child can spend real money on. Oakward is sold as a household subscription, which is handled by the app store and is described under Payments and subscriptions below.

Crash diagnostics

When Oakward crashes, or hits an error it has to recover from with the "Something went wrong" screen, it sends an automatic diagnostic report using Firebase Crashlytics. This is on by default in every released version of the app, and it can be switched off. We use it for one thing: finding and fixing faults.

A report contains:

• The technical stack trace of the fault — the lines of our own code that were running when it happened — and, for an error caught by the recovery screen, which part of the app's interface was on screen.
• Device and app details: device model, operating system version, the Oakward version and build number, and whether the build is a production or development one.

That is the whole of it. No identifier of yours is attached to a report. Not your account ID, not your family ID, not the fact that the device is a parent's or a child's. And it does not contain your email address, your family or hero names, quest or reward content, PINs, balances, or anything else your family has typed into the app. Crashlytics does recognise reports coming from the same installation, using its own identifier for that copy of the app — that is how it can tell one repeatedly crashing device from a hundred separate ones — but that identifier is not connected to your account or to anything you have entered.

You can turn crash reports off. The switch is Share Crash Reports, under Parent Command → Family & Settings. With it off, no crash report leaves that device at all, and the app carries on working exactly as before.

Two limits on that switch, stated plainly rather than left for you to discover. It starts switched on, so a device sends reports until someone turns it off. And it is a setting on the device you change it on, not an account-wide one: it is stored on that device and is not synced to the rest of your family. Parent Command itself is only available on devices enrolled as parent devices, so on a device you have enrolled as a child's, there is at present no in-app switch and reports are sent. Those reports carry no identifier and none of your family's content, exactly as described above, which is why we have not treated it as urgent — but it is a limitation we know about and would rather fix than explain. If it matters to you, say so at the address at the bottom of this page.

Crashlytics is operated by Google, which acts as our data processor for it under the same Firebase Privacy and Security terms that cover the rest of our backend. Crash reporting is not advertising, is not behavioural or cross app tracking, and is not used to build a profile of you or your children, to measure what you do in the app, or for any purpose other than fixing faults.

Payments and subscriptions

Oakward is sold as a single subscription that covers your whole household. Billing is handled entirely by Apple's App Store or by Google Play, depending on where you downloaded the app. In practice that means:

• We never see, receive, or store your card number, bank details, or billing address. Those details go to Apple or Google and never reach us.
• Your subscription is viewed, changed, and cancelled through your App Store or Google Play account, not inside Oakward.
• Apple and Google provide us with aggregated sales and subscription reporting. It tells us how many subscriptions are active, not who you are.
• The app receives only a yes or no answer as to whether your household's subscription is currently active, so it knows whether to unlock. No payment information comes with it.
• The subscription unlocks the app. It does not buy Gold, Essence, or any in-game advantage, and there is nothing further to purchase once you have it.

To turn the store's receipt into that yes or no answer — and to make one subscription cover every device in your household rather than only the phone that paid — we use a subscription management service called RevenueCat, which acts as our data processor for subscriptions. To be exact about what it receives:

• Your household's family identifier, which is the random ID your family's account is stored under. RevenueCat uses it as the account key so that every enrolled device in your family sees the same subscription.
• Purchase and subscription information from Apple or Google — which product was bought, whether the subscription is active, when it renews or expires — along with the store receipt that has to be checked to establish those things.

Purchase history is the only kind of data RevenueCat's own privacy manifest declares that it collects. It does not declare a device identifier or diagnostics, and Oakward passes it nothing beyond the family identifier described above.

RevenueCat does not receive your card number or any other payment details, your name, your email address, or any information about your children — no hero names, no quests, and nothing else from inside the app. It is used for subscription management only, not for advertising, analytics, or tracking. Its handling of that data is governed by RevenueCat's privacy policy.

Apple's and Google's handling of your payment information is governed by their own privacy policies, not this one.

Where your data lives

Everything your family enters — heroes, quests, rewards, balances and history — is stored in two places: locally on each enrolled device, and in Google Firebase (Authentication, Cloud Firestore, Cloud Storage, and Cloud Functions), which acts as our data processor. Google's handling of that data is governed by the Firebase Privacy and Security terms. Data is transmitted over encrypted connections and is stored in a per family area that our security rules make readable only by devices you have enrolled in your family.

Three other services receive a narrow slice of data, and nothing beyond it. We are listing them by name so you can check them yourself:

None of these services is an advertising, attribution, or behavioural tracking service, and none of them receives your family's data for any purpose other than the one listed.

How long we keep it

We keep your family's data for as long as your account exists, because the app cannot function without it: quests, balances and history are the product. We do not keep it indefinitely, and we do not keep it for any purpose beyond running the app for you.

Uninstalling the app on its own does not delete your data, because your family may still be using other devices. Deleting your account does.

Deleting your data

You can delete your account and all of its data from inside the app, without contacting us. A step-by-step version of this section, including what to do if you can no longer reach the app, is on the delete your account page.

The route inside the app is:

Parent Command → Family & Settings → Delete Account.

This permanently erases your parent account, every hero, all quests, rewards, currency and history, and every enrolled device's access. It is immediate and cannot be undone. Individual items, such as a single hero or one category of data, can also be removed at any time from Clear & Reset Data on the same screen.

Two things sit outside that button, because they are not held in your family's area of our backend. Crash reports already sent to Crashlytics are held by Google and age out on Firebase's own retention schedule. They contain none of your family's content and no identifier of yours, only the technical detail described under Crash diagnostics — which is the honest reason we cannot pick yours out and delete them individually: with no identifier attached, there is nothing in them to look you up by. What you can do is stop any more being sent from a parent device, with the Share Crash Reports switch. Your subscription record at RevenueCat, and at Apple or Google, is a billing record and is kept by them; if you want that removed as well, write to us and we will make the request on your behalf.

Children's privacy

Oakward is a household utility operated by a parent. Any information about a child in the app is entered by that parent, is used solely to make the app work for their family, and is never used for advertising, profiling, or tracking. It is not disclosed to anyone outside the family's own enrolled devices, other than to the processors named under Where your data lives, each of which handles it only on our instructions and only for the purpose listed there.

Two points specific to children, so there is no ambiguity. First, a crash report sent from a child's device carries no identifier at all — not the child's name, not anything they have done in the app, and not the account the device is signed in to or the fact that it is a child's device rather than a parent's. It is a stack trace, a device model, an operating system version and an app version. The Share Crash Reports switch described above lives in Parent Command, which is reachable only on parent devices, so it turns reporting off for the device it is set on rather than for a child's device. Second, we never ask a child for personal information. A child's name, and every other personal detail in Oakward, is typed in by their parent. What a child's own device records is their play — a quest marked done, a reward requested, gold spent — and that stays inside their family's own area of our backend, exactly like everything else. A parent can review, change, or permanently delete everything about a child at any time using the controls described above. If you believe a child's information has been provided to us without a parent's involvement, contact us and we will delete it.

Your rights

Depending on where you live, you may have rights to access, correct, export, or delete your personal information, and to object to or restrict its processing. The in-app controls above give you direct access and deletion. For anything else, contact us and we will respond within the period required by applicable law.

Changes to this policy

If this policy changes materially we will update the date at the top of this page and, where the change affects how your family's data is handled, surface a notice in the app.

Contact

Questions about this policy or your data: info@redmontlabs.com