Mason33

Privacy Policy

Last updated 24 August 2026

Mason33 is a private practice. It is built so that there is almost nothing to collect, and so that what little exists belongs to you and can be destroyed by you in two confirmations.

This policy covers the Mason33 mobile application for Android and iOS. It is written to match exactly what the application actually does.

The app works with no account at all

An account is optional and always has been. If you never sign in, nothing whatsoever reaches us. Your practice record, your written reflections and your Proofs are held in the application's own storage on your phone. No server of ours is involved, no network request is made, and we receive nothing — not an install ping, not a crash report, not an anonymous statistic.

One thing is worth stating exactly, because "it stays on your phone" is not quite the whole truth. Android and iOS both back up app data to your own cloud storage unless you have turned that off — your Google Drive or your iCloud, under your account, governed by their terms. Mason33 does not send it, cannot read it, and cannot delete it, and it never reaches us. It does mean that reinstalling can restore what the app held, and that deleting the app may not remove every copy. How to clear it is set out in Deleting your account and data.

What is collected if you choose to sign in

Signing in with Google or Apple exists for one reason: so that years of practice survive a lost or replaced phone. When you sign in, one document is created for you, and it holds only:

Your written entries are the most personal thing here, and they are stored as you wrote them so that they can be restored to a new phone. They are readable only by your own signed-in account. They are never shown to another member, never used to train anything, and never read by us for any purpose.

What is never collected

Signing in with Google or Apple takes one opaque identifier and nothing else. The app does not request, receive or store your name, your email address or your photograph, and it has nowhere to put them if it did.

DataCollected
NameNo
Email addressNo
Phone numberNo
Postal addressNo
ContactsNo
Photos, videos or filesNo
CalendarNo
Location, precise or approximateNo
Advertising identifiers (IDFA, AAID)No
Device identifiers or fingerprintsNo
Health or fitness dataNo

No sharing, no selling, no advertising, no analytics

Your data is not shared with any third party, and it is not sold, rented or licensed to anybody under any circumstance.

Mason33 contains no advertising SDK and no analytics SDK. There is no tracking, no attribution, no behavioural profiling, and no cross-app or cross-site tracking of any kind. On iOS the app never presents an App Tracking Transparency prompt, because it has nothing to ask you for.

Nothing in the app is social. There is no feed, no messaging, no profiles, no leaderboard, and no way for one member to discover or see another. This is enforced in the database rules themselves: no member can read another member's document, and the member collection cannot be listed by anyone at all.

Where it is stored

If you sign in, your document is stored using Google Firebase (Authentication and Cloud Firestore), which provides authentication and hosting infrastructure on our behalf as a service provider. Firebase processes the data only to operate the service, not for its own purposes. Data is encrypted in transit.

Signing in also means that Google or Apple, as your identity provider, knows that you authenticated with an app. That exchange is governed by their own privacy policies, and it gives them no access to your practice record.

Deleting everything

The app has a screen called Leaving. It offers two things plainly:

There is no retention period afterwards, no thirty-day grace window, and no archived copy. Deleted means deleted. You never have to email anyone to ask for it, and you are never asked why you are leaving.

One case is worth stating plainly, because the app states it plainly too. Deleting the sign-in account itself occasionally fails — identity providers require a recent sign-in before they will honour a deletion. When that happens, your Record is still destroyed, on the device and in the cloud, but the empty sign-in account may outlive it. The app tells you so on the screen rather than reporting a clean success, and you can then remove the credential at Google or Apple directly. The account that remains holds no practice data of any kind, because that data is already gone.

Children

Mason33 is not directed at children and does not knowingly collect data from anyone under 13. It contains nothing unsuitable for a general audience, but it asks for a twelve-year commitment, which is an adult's decision to make.

Your rights

Depending on where you live, you may hold rights of access, correction, portability, erasure and objection over your personal data. Mason33 satisfies all of them inside the app, with no request process: your Record is visible to you at all times, editable by you, exportable by you, and erasable by you. If you would rather exercise a right by contacting us, use the address below.

Changes

If this policy changes materially, the date at the top changes and the revised policy is published here before the change takes effect. A change that would collect something new will not be applied retroactively to data already held.

Contact

Questions about this policy, or about your data: mason33light@gmail.com

See also Deleting your account and data, which sets out step by step how to destroy everything and exactly what is removed, and the Terms of Use.