Sheet 02 — Privacy

Privacy

Four of the five apps never send your data anywhere.

This policy covers the website at plainpoint.net and every app listed on it. It is written per app, because the honest answer differs per app: most of them have no server to send anything to, and one of them does. Where an app stores something off your device, this page says exactly what.

Last updated: 27 August 2026.

At a glance

Analytics
None
Advertising
None
Tracking cookies
None
Data sold or shared
Never
Apps with a server
1 of 5

This website

plainpoint.net sets no cookies, runs no analytics, executes no JavaScript and loads nothing from a third party. The typeface is served from this domain. There is no form to fill in and nothing to sign up for.

The site is hosted on GitHub Pages. Like any web host, GitHub receives the requests your browser makes and may log technical information such as your IP address and user agent in order to serve the page and protect its service. That logging is GitHub's, not mine — I have no access to it and receive no report from it. It is governed by GitHub's Privacy Statement.

  • No cookies
  • No scripts
  • Host logs apply

The short version, per app

AppWhere your data lives
Life Balance IndexYour browser only
MidoriYour browser only
VialYour browser only
VolumaYour browser only
RunawayA server, because it is shared
  • 4 of 5 on-device
  • 1 of 5 on a server

The on-device apps

Life Balance Index, Midori, Vial and Voluma have no accounts, no servers and no sync. Everything you enter is written to your browser's own storage on the device you entered it on.

  • Assessment answers, scores and weekly check-ins (Life Balance Index)
  • Accounts, transactions, budgets and recurring items (Midori)
  • Patient names, dosages, clinic days and treatment notes (Vial)
  • Audio files, which are read into the page and never uploaded (Voluma)

None of it reaches me or anyone else. Clearing your browser's site data for that app erases it permanently, and there is no copy elsewhere to request or delete. Any export file these apps produce is written by you, to your device, at the moment you ask for it.

Vial in particular: it was built for one nurse to track injections, and the patient information in it stays on that nurse's device. Because it never leaves, protecting the device — a screen lock, a private browser profile, an encrypted disk — is what protects the records.

  • No account
  • No transmission
  • You can erase it yourself

Runaway

Runaway is a shared run log, so a server is unavoidable — the whole point is that your friends see your runs. It uses Supabase for its database and sign-in.

What is stored

  • Your Google account identifier and email address, through Supabase Auth
  • Your display name and profile picture URL, taken from your Google profile
  • A generated friend code
  • Each run: distance, duration, date and any notes you write
  • Your friend connections and their pending or accepted status
  • Clubs you create or join, and their loss-pool settings
  • Push notification endpoints, if you turn notifications on

Who can see it

Your runs, name and picture are visible to people in the same club and to friends you have accepted — that is the feature. Nothing is public to the open internet, nothing is sold, and nothing is shared with advertisers. There are none.

Removing it

Deleting your profile deletes everything attached to it: runs, friendships, club memberships and notification endpoints are all removed with it. Ask through the GitHub link below if you want an account removed and cannot do it yourself.

  • Google sign-in
  • Server component (Supabase)
  • Visible only to your club

Everything else

Children

None of these apps are directed at children, and none knowingly collect information from them.

Legal bases and your rights

For the on-device apps there is no processing by me to have a basis for — I never receive the data. For Runaway, the basis is your consent, given when you sign in, and you can withdraw it by deleting your account. You may ask what is stored about you, ask for it to be corrected, or ask for it to be erased.

Changes

If this policy changes, the date at the top of this page changes with it, and the previous wording stays in the site's public git history.

Contact

Questions and data requests can be raised at github.com/SEEHIGHxb, by opening an issue on the repository for the app concerned.

  • Consent-based
  • Erasure on request