Privacy policy.
Standards for iOS · In effect 13 September 2026 · Last edited 13 September 2026
In short
Standards is an accountability app. You write down something you said you would do, and later you answer honestly for whether you did it.
Everything you write stays on your phone. Your commitments, your answers and your Record are stored only in Standards' own storage on your device. They are not uploaded, not backed up to any server operated for Standards, and not readable by the developer or by anyone else.
There is no account and no sign-in. One thing leaves your device today, and it does not contain a word you wrote: your subscription status, handled by Apple and by RevenueCat, so the app knows whether you currently have access.
1. Who is responsible
Standards is made and published by Sam Marsh, an individual developer based in New Zealand. There is no company.
Privacy enquiries: privacy@yourstandards.app
Support: support@yourstandards.app
2. Scope
This policy covers the Standards iOS app and this website. It does not cover Apple's own services, or the services of the processors named in section 4, each of which handles information under its own privacy policy.
This website collects nothing. It is a set of static pages. There are no cookies, no analytics, no embedded third-party content, no fonts loaded from anywhere else and no JavaScript. Your browser requests pages from Cloudflare, which serves them and keeps its own operational logs as any web host does.
3. What Standards stores on your device
All of the following is written to Standards' private storage inside the app's container on your device. None of it is transmitted anywhere by Standards.
Your record
- The text of every commitment, stored exactly as you wrote it apart from trimming surrounding whitespace.
- The calendar day each commitment is for.
- The date and time each commitment was created.
- Your answer to each commitment — kept, not kept, or not yet answered.
- The date and time each answer was given.
- An optional reminder time for each commitment.
- A record identity: a random identifier generated on your device the first time your record is created. It is not derived from you, your device, your Apple Account or anything you have written. It is never displayed and never transmitted. It exists so that two people who happened to write identical commitments on identical days do not see an identical Record drawing.
Your settings
- Whether you have completed the introduction.
- Your evening reminder time, if you set one.
- Whether Standards has already asked you for notification permission.
Subscription memory
The last answer the subscription provider gave about whether your subscription is active, whether it is a trial, whether it renews, and when the current period ends. This is stored so that the app still opens if you are offline. It is not a receipt and it is not proof of purchase.
Quarantined data
If saved data cannot be read — for example because it was damaged — Standards copies it aside rather than overwriting it, so that nothing is destroyed by the act of failing to read it. This copy stays on your device and is removed by Delete everything.
Device backups
Standards' storage lives in the app's container. If you have iPhone backups enabled, that container is included in your backups in the ordinary way, under your own Apple account and Apple's terms. Standards neither creates nor controls those backups.
4. What leaves your device today
In the app as it stands
4.1 Subscriptions
Standards lets you experience the core loop with one word before a subscription is required for creating further words. Access is handled in two parts.
Apple. The purchase itself is made with Apple through the App Store. Apple takes the payment, manages the subscription, decides free-trial eligibility, and handles renewals, cancellations and refunds. The developer never receives, and never has access to, your payment details, your Apple Account credentials, or your name and address as held by Apple. Apple's handling of that information is governed by Apple's own privacy policy. Apple makes aggregated and anonymised sales reports available to developers through App Store Connect; these do not identify individual people.
RevenueCat. Standards uses RevenueCat to check and manage subscription status. RevenueCat, Inc. is based in the United States and acts as a processor for this purpose.
What is sent to RevenueCat:
- The product identifier of the subscription being purchased or checked.
- App Store transaction and receipt information, so that the subscription can be validated with Apple.
- An anonymous app user ID generated by RevenueCat itself. Standards supplies no identity of any kind: the SDK is configured with a null app user ID, which is RevenueCat's anonymous mode.
- The device's IP address, which is necessarily visible to any server a device connects to.
What is not sent to RevenueCat:
- No commitment text, no answers, no Record, and no record identity.
- No email address, name or other contact detail.
- No advertising identifier and no device identifier. Standards does not call RevenueCat's device-identifier collection and uses no attribution integration.
- No user identification of any kind — Standards never logs anyone in to RevenueCat, never sets an attribute, and never sets a display name, email address or push token.
RevenueCat therefore holds a subscription record that is not linked to your identity. Because the anonymous ID is generated per installation, deleting and reinstalling the app produces a new one. That is why Restore purchases exists, and why it works from Apple's own receipt rather than from anything Standards remembers. RevenueCat processes this information under its own privacy policy.
4.2 Reminders
Standards can send you two kinds of reminder. Both are local notifications, scheduled by your device and delivered by your device. Nothing is sent to a server. There is no push notification service, no push token and no remote notification of any kind.
- A reminder for a specific commitment, at a time you choose. This reminder contains the sentence you wrote, because that is the thing being reminded about.
- An evening reminder, if you turn one on, that says only “You have a word to answer.” It is sent only on evenings when something is actually unanswered.
One consequence is worth stating. iOS shows notification content on the lock screen by default. A commitment reminder therefore displays your own sentence where someone holding your phone could read it. Nothing has been transmitted anywhere — this is your device showing you your own words — but if you write commitments you would not want visible on a lock screen, you can turn off previews in iOS Settings → Notifications → Standards, or set no reminder on that commitment.
Permission for notifications is requested only after you have answered your first commitment, never on first launch. If you decline, Standards does not ask again from inside the app.
4.3 Nothing else
Standards' own code makes no network requests. There is no Standards backend, no over-the-air update mechanism, and no content downloaded at runtime.
5. Approved, and not switched on
Not in the app as it stands
Two things have been decided and are deliberately not running. They are described here so that the decision is public before the code is, and so that nobody has to take a later version of this page on trust. Neither is collecting anything today.
5.1 Crash diagnostics
Standards has crash reporting written into it, using Sentry, so that a fault can be found and fixed. It is not enabled. The reporter requires a configuration value supplied at build time; no such value is present, and without one the app does not initialise the reporting software at all and sends no diagnostics of any kind.
When it is enabled, this policy will say so before the first build that has it enabled reaches anyone — never after. What a crash report would then contain has already been fixed by how the app is built:
- A stack trace: where in the code the failure happened.
- The device model and operating system version.
- The app version and build number.
- A randomly generated per-installation identifier, assigned by Sentry's own software so that repeated crashes from one installation are recognised as one fault rather than many. It is not derived from you, your device, your Apple Account, your subscription or anything you have written, it is never sent with any content you wrote, and it changes if you delete and reinstall the app.
And what it could not contain, by construction rather than by intention:
- None of your commitments, none of your answers, and no part of your Record.
- No record identity.
- No screenshots and no capture of what was on screen.
- No view hierarchy.
- No breadcrumbs or activity trail. The breadcrumb limit is set to zero, which also holds for failures in the device's native layer.
- No session tracking, no performance tracing, no profiling and no user-interaction tracking. All are switched off.
- No console output and no network request logs.
- No email address, name or contact detail of any kind.
Crash reports would be sent to Sentry's European Union data region.
5.2 Product analytics
Limited product analytics has been approved in principle and is not built. There is no analytics software in the app, no key, no identifier and no event. The app records nothing about what you do in it.
The shape it has been approved to take is fixed in advance, and the limits are the point:
- A small, fixed set of events about which parts of the app are reached and whether a word was kept. Not a general-purpose tracker.
- A random identifier for the installation, held on your device and reset by Delete everything. It is not your record identity, which seeds the Record's drawing and will never leave the device in any form.
- No session replay, no advertising identifier and no cross-app tracking.
- Never sent
That last row is a list rather than a promise, and it is worth writing out. Never leaving the device, to any processor: commitment text or any fragment of it, the length of anything you wrote, any freeform text, the exact time you set a reminder for, the days you chose, screenshots, your clipboard, your contacts, your Record's shape, your record identity, or any advertising identifier. Counts would travel in ranges rather than exactly, elapsed time in coarse ranges and never as a time of day, country but not region or city, device class but not exact model.
If and when it is built, this policy will be updated before the build that carries it ships, and the app's Settings screen will be updated to describe the same data practices before analytics is enabled.
6. What Standards does not do
- No account. No email address, no password, no username, no sign-in and no profile. Nothing identifies you to the developer.
- No advertising, and no tracking. Standards shows no advertising, contains no advertising software, and does not track you across other apps or websites. No data is shared with data brokers.
- No developer server. There is no Standards backend. The developer operates no server that receives your information.
- No access to your words. The developer has no technical means to read your commitments, your answers or your Record.
- No selling of personal information, ever.
7. Why this information is processed
- Everything stored on your device (section 3)
- To provide the app itself. It is under your control and is never transmitted by Standards.
- Subscription information (section 4.1)
- To determine whether you currently have access, to complete purchases and restores, and to meet the tax and accounting obligations that fall on Apple and the developer. Where the UK or EU General Data Protection Regulation applies, this is processing necessary for the performance of a contract with you.
- Local reminders (section 4.2)
- To remind you of something you asked to be reminded of.
Crash diagnostics are not processed at all today. The lawful basis for them will be stated here before they are switched on.
8. How long information is kept
- On your device: until you delete it, or until you delete the app. Standards applies no expiry of its own and never deletes your record automatically.
- Subscription information held by RevenueCat and Apple: under their own retention policies, and for as long as required for their records.
9. Deleting your information
Delete everything. Settings → Your record → Delete everything permanently removes, from your device, your commitments, your answers, your Record, your record identity, your quarantined data and your settings. This cannot be undone, and Standards has no copy anywhere to restore from.
Two things it deliberately does not do:
- It does not cancel your subscription, and it does not delete anything Apple or RevenueCat holds. Destroying your record is something you do to your record; it must not quietly cancel something you are paying for. Cancel a subscription in your Apple Account settings.
- It does not remove the remembered subscription status, which is not part of your record and is re-answered by the store on the next launch.
Individual words cannot be deleted once answered. A commitment can be edited or removed before it is answered. After it is answered it stands as given, because a record you can edit is not a record. Delete everything is the only exit.
Subscription records held by Apple and RevenueCat are not deletable from inside the app. To make a request about them, use the address in section 1 and read section 12 first — the practical limits there are real.
10. Uninstalling, reinstalling, and export
Deleting Standards removes the app's container from your device, and everything described in section 3 goes with it. This is iOS behaviour, not something Standards controls.
- If you have device backups enabled, a copy may persist inside your own backups until those backups are deleted or rotated. Those backups are yours and are governed by Apple's terms.
- Reinstalling gives you an empty record, unless iOS restores the app's data from one of your backups.
- Reinstalling generates a new record identity and a new RevenueCat anonymous ID. Neither carries across.
- Your subscription does carry across, because it belongs to your Apple Account rather than to the installation. Use Restore purchases.
There is no export. Standards V1 provides no way to export your record. If you delete the app without a backup, your record is gone and cannot be recovered by anyone, including the developer. This is stated plainly because it is a real consequence of the app storing nothing on a server.
11. If your subscription ends
Your record is not deleted. Nothing in Standards removes a record because a subscription lapsed, and nothing can: the only code that deletes a record is the Delete everything control you press yourself. Your record stays on your device, unchanged, for as long as Standards is installed. Resubscribing, or restoring an existing subscription, returns you to it exactly as you left it.
12. Your rights
Standards holds almost nothing about you, and what the processors hold is not linked to your identity — which affects what can practically be done with a request.
Under the New Zealand Privacy Act 2020 you have the right to ask for access to, and correction of, personal information held about you. Information stored on your own device is already wholly in your possession: you can read it in the app and delete it at any time.
If the UK or EU General Data Protection Regulation applies to you, you also have rights of access, rectification, erasure, restriction, portability and objection, and the right to complain to your own supervisory authority.
The practical limit is worth stating rather than burying. Subscription records are not linked to your identity: there is no email address, name or account to search against, and the identifier involved is a random per-installation value generated by RevenueCat. In most cases the developer will have no way to locate information as belonging to a particular person, and will say so rather than guess.
Requests go to privacy@yourstandards.app. If you are not satisfied with how one is handled, you may complain to the Office of the Privacy Commissioner (New Zealand) at privacy.org.nz, or to your own supervisory authority if one covers you.
13. Information sent overseas
The developer is in New Zealand. The processors are not:
- Apple — United States and other jurisdictions, under Apple's own terms.
- RevenueCat — United States.
- Cloudflare — serves this website from data centres worldwide. It receives no information from the app.
Information described in section 4 is therefore disclosed outside New Zealand. Sentry's European Union data region would join this list if crash reporting is enabled.
14. Children
Standards is not directed at children and is not designed for them. It collects no age information and has no way to determine a user's age.
15. Security
Your record is stored in Standards' private container on your device and is protected by your device's own protections, including your passcode and iOS file-level encryption. Standards adds no encryption of its own, and stores nothing on a server that could be breached. Information in transit to Apple and RevenueCat is sent over encrypted connections.
No system is perfectly secure. Because Standards holds your words only on your device, the most important protection is the one you control: a device passcode, and keeping your device software up to date.
16. Changes to this policy
If this policy changes, the updated version will be published at this address and the date at the top will change. Material changes — in particular any change to what leaves your device — will be described rather than made quietly, and will be published before the build that makes them true, not after.
17. Terms
Standards is licensed under Apple's standard Licensed Application End User Licence Agreement. There is no separate agreement of our own to read. Read Apple's standard EULA.
18. Contact
Privacy: privacy@yourstandards.app
Support: support@yourstandards.app
Sam Marsh, New Zealand.