Privacy policy

MetaBook has no server. There is no account to create, no analytics, no advertising and no tracking of any kind. Your books are a file on your phone. Your provider key is in the phone's secure storage. The only thing that ever leaves the device is the text of a model call, and it goes to the provider whose key you pasted — not to us, because there is no us to send it to.

1. Who this is about

MetaBook is published by Nick Meli (the "developer", "we"). Questions about this policy, or about anything below, go to null.htp@gmail.com. This policy covers the MetaBook mobile app and this website.

2. What the developer collects

Nothing. The app contains no analytics SDK, no crash-reporting SDK, no advertising library and no attribution library. It does not read the advertising identifier. It does not ask for your name, your email or your phone number, because there is no account and nothing to attach them to. The developer operates no backend service that the app talks to, so there is no server log with your requests in it.

This site is a set of static files. It sets no cookies, embeds no third-party scripts and runs no analytics. The one thing it stores in your browser is the paper/night preference you choose with the toggle, kept in your own browser and read by nothing else.

3. What leaves your device, and where it goes

MetaBook works under your own provider key — you create an account with the model provider and paste its key into the app. When you ask for an interview question, an outline, a chapter, or a rewrite of a passage, the app sends that request straight from your phone to the provider, over TLS, with your key in the header. Nothing is relayed through anything of ours.

The provider MetaBook is built against is OpenRouter (openrouter.ai), which routes the call on to the model you chose. What they keep and for how long is set by their policy and by the settings on your own OpenRouter account, and you can read it here: openrouter.ai/privacy and openrouter.ai/terms. That relationship is between you and them; your key is the proof of it.

What is in such a request

• The topic you typed, and your answers to the interview questions.
• The book's brief and its chapter outline.
• For a chapter: the synopsis, and the parts of the book kept as memory so that chapter ten still agrees with chapter one.
• For a rewrite: the passage you held, the surrounding chapter text, and the instruction you chose — simplify, expand, give an example, or the question you asked.

Nothing else is added to it. There is no device identifier, no location, no contact list and no usage telemetry riding along.

Two other times the network is used

• Getting a key. If you use the in-app route to obtain a key, the app opens the provider's own sign-in page in your browser and receives the key back through the app's URL scheme. The exchange is between you and the provider; the developer sees none of it.
• Reading your balance. The spend figures the app shows are read from the provider under your key, so that what the app says about your money agrees with what your provider says.

4. What stays on the device

Your books	Topics, briefs, outlines, chapter text, every earlier version of every chapter, reading positions and export history — a local database in the app's private storage.
Your key	Held in the platform's secure storage — the Android Keystore, the iOS Keychain. It is never written to a log, never included in an export, and is excluded from cloud backup and from device-to-device transfer.
Your spending	A local ledger of what each call cost, so the daily cap can be enforced on the device before a call is made.
Settings	Language, theme, chosen models, the daily cap.

None of it is uploaded anywhere. If you use your operating system's own backup, whatever it backs up is governed by Apple's or Google's policy, not this one — and the app explicitly keeps the key and any in-flight request out of that backup.

5. Speech

Having a chapter read aloud uses your device's own speech engine. The text goes to that engine, which is part of your operating system; whether it speaks entirely offline is a property of the engine and of your system settings, and it is documented by Apple or Google rather than here. The developer receives nothing from it.

6. Exports and sharing

Exporting a book writes a file — Markdown, EPUB or plain text — that you then hand to whatever you like. Once you share it, where it goes is decided by you and by the app you shared it with.

7. Buying the app

MetaBook is a paid app. The purchase is handled entirely by Google Play; payment details are given to Google, never to the app and never to the developer. What the developer receives is Google's aggregated sales reporting — country-level totals, not identities.

What you spend on model calls is a separate matter, between you and your provider, on the account your key belongs to. The developer takes no part in it and no share of it.

8. Children

MetaBook is not directed to children. It is a tool for adults who hold their own API key with a model provider, and it is neither designed for nor marketed to anyone under 13.

9. Deleting things

• A book: delete it in the app. It and all its versions go.
• Your key: clear it in Settings; it is removed from secure storage.
• Everything: uninstall the app. Because all of it is in the app's private storage, removing the app removes the data with it. There is no account of ours left behind, because there was never one.
• Anything held by your provider is deleted through your account with that provider.

There is no request to make of us to have your data deleted, and no form to fill in: we are not holding any. If you would like that stated to you directly, write to null.htp@gmail.com and it will be.

10. Generated text

Chapters are written by a large language model under your key. They can be wrong, and the app labels them as generated rather than presenting them as established fact. Nothing you generate is collected, reviewed or used to train anything by the developer.

11. Changes to this policy

If this policy changes, the new version appears at this address with a new effective date at the top. A change that alters what leaves your device will also be described in the app's release notes, because that is where somebody who has already installed it will actually see it.

Contact · null.htp@gmail.com · Nick Meli · metabook.store