Privacy

Effective 24 October 2026

Who we are

memory.bike is built and run by Anphase Ltd in Aotearoa New Zealand. Questions about this policy go to privacy@memory.bike.

What the app stores on your device

Your theme choice, under mb.theme; unsent AI topic and explanation drafts, under mb.ai.intake; and your rides, under mb.rides, including starting explanations, answers, generated drafts, feedback, corrections and revisions. The explanations you save in Log and your verdicts on interpretations are kept under mb.record. They are saved in your browser's local storage on the web, and in the operating system's preference store in the iOS and Android apps, which keeps them out of Android cloud backups. If you turn on sync, this device's sync credentials and the key that seals your record are saved there too, under mb.sync.

Native builds also keep a browser-storage mirror for startup. These local stores are not encrypted by memory.bike. Access to an unlocked device can expose saved work. The native AI sign-in token stays in memory and is not saved with your learning record.

Sync across your devices, if you turn it on

Sync is off until you paste a pairing code into the log. Then your record is sealed on your device (AES-GCM) and stored in a box on svc.nz, a storage service also run by Anphase Ltd. The key that seals it never leaves your devices except inside a pairing code you copy yourself, so svc.nz holds only text it cannot read, along with a name you give each device. Every change is kept as a new version in the box.

This sync covers the Log explanation versions and interpretation verdicts in mb.record. It does not back up complete rides, unsent drafts or generated feedback. Sync remains optional and is still being tested in the private trial.

"Stop syncing here" makes that device forget its sync credentials. Revoking a device stops its access; deleting the box in svc.nz removes the stored copy. Deleting the app does not delete the box.

What the app sends

Starting an AI ride sends your topic and explanation to the private backend. Requesting comparison sends your answer; the backend includes the relevant draft when calling a model provider. Optional sync sends your sealed Log record to svc.nz. There is no telemetry, no crash reporting, no advertising identifier, no attribution SDK and no third-party code that phones home. The typefaces are served from the app itself rather than from a font network, so opening memory.bike does not contact a separate font provider.

Saved work and prepared examples can be read and edited offline. New AI drafts and answer comparisons require a reachable private backend and a valid sign-in. Optional sync also needs a connection.

Private AI requests and generation records

The current trial uses an authenticated private backend. Model requests prefer Anthropic and can fall back to OpenAI, so both providers may receive text during a ride. No other model provider is configured for this trial. Starting a ride or asking for comparison initiates those requests; reading saved work does not. Model keys remain on the backend.

The computer running the backend keeps generation files containing your starting explanation, model steps and generated draft. They remain until the operator deletes them. Active route and comparison context is also held in memory; comparison access expires after eight hours, and restarting the backend clears those active contexts. Signing out does not delete device work or generation files. Contact privacy@memory.bike about access to or deletion of trial generation records. This does not delete copies processed by model providers.

Crash diagnostics

We collect none. If the app crashes, Apple or Google may offer you the choice to send a diagnostic report to them under their own terms; we receive no personal data from those systems, and we have not enrolled the app in any crash-reporting service of our own.

Purchases

There are none today. memory.bike has no paid features, no subscription and no in-app purchases, so no payment information passes through it. Should that change, this page will say what the app store tells us — which, for both stores, is a purchase receipt and never your card details.

The website

memory.bike is served as static files from Cloudflare. We run no analytics on it, set no cookies and embed nothing from anyone else. Cloudflare processes the request in order to serve the page, as any host must, under its own privacy policy. The one part of the site that is not static is the updates form.

The updates list

If you give us your email address on this website, we store two things: the address, and the date you gave it. They are kept in a database on Cloudflare, in Anphase's own account, and nothing else is attached to them — not your name, not where you were, not what you did on the site.

We use the list once: to tell you when memory.bike is ready to use. Then we delete it. It is not a newsletter, it is not added to a mailing service, and it is not shared, sold or used for anything else. Until then, write to privacy@memory.bike and we will take your address off the list and tell you we have.

Cloudflare keeps a rolling history of the database so it can be restored after a mistake: 7 days on the free plan, 30 on the paid plan. An address we delete stays in that history until the window passes, and cannot be removed from it sooner.

To stop the form being flooded, Cloudflare counts how often each network address sends it, and turns away more than a few a minute. That count is kept by Cloudflare for a minute or so and is never stored with your email.

If you write to us

If you email us, we keep the message and your address for as long as it takes to answer you, and use them for nothing else.

Keeping and deleting your data

Device work, optional sealed sync, private-backend generation files and updates-list emails are stored separately. Removing one does not remove the others:

• On the web, clear browser site data for the address where you used the app.
• On iOS and Android, deleting the app removes it.
• A synced copy stays in your svc.nz box until you delete the box.
• Private trial generation files remain on the backend computer until its operator deletes them.

For help with trial generation records or updates-list deletion, write to privacy@memory.bike. Deleting the app or signing out does not request that deletion.

Your rights

The New Zealand Privacy Act 2020 gives you the right to access and correct personal information an organisation holds about you, and the GDPR and similar laws give comparable rights where they apply. For requests about information held in trial generation records, the updates list or correspondence, contact privacy@memory.bike.

Children

memory.bike is not directed at children. The private trial processes submitted text as described above; the same storage and network paths apply to anyone using it.

Changes to this policy

If what the app does changes, this page changes with it, and the effective date at the top moves. We will not quietly begin collecting something and leave this text as it was.

Contact

privacy@memory.bike — Anphase Ltd, Aotearoa New Zealand.