O OpenBook ← Back to OpenBook

Privacy Policy

The short version: we collect as little as possible, we never sell it, and you can read the code that proves it.

Last updated June 2026. Written in plain language, on purpose.

Most privacy policies are long, vague, and written to protect the company. This one is written to be understood. OpenBook is open source, so anything this page describes can be checked against the actual code on GitHub. If the policy and the code ever disagree, that is a bug, and you can tell us.

What we collect

Only what the platform genuinely needs to work:

What we do NOT do

We never sell your data.

Not to advertisers, not to data brokers, not to anyone, no matter how large the offer. This will not change.

We do not track you across the web.

No advertising pixels, no third-party ad networks, no hidden trackers following you onto other sites.

We do not build a hidden profile to manipulate you.

There is no secret model of your behaviour quietly tuned to keep you scrolling or to sell ads against your attention.

Your data is yours

You can manage, export, or delete what you share at any time. When you delete something, it is actually removed, not just hidden from view. Closing your account removes your account data. You are in control, not us.

Where your data lives

OpenBook runs on standard cloud infrastructure (a web host for the app, a managed database for your account and posts, and object storage for the photos and videos you upload). These providers process data only so the service can run. They are not allowed to use it for their own advertising, and we do not hand them your data to sell.

Cookies

We use the bare minimum, and never for advertising. The full details are on our Cookies page.

Changes to this policy

If this policy ever changes, the change lands in the public code history first, so there is a permanent, timestamped record. There are no quiet edits.

Contact

Questions about your privacy on OpenBook? Open an issue on the GitHub repository. It is public, it is tracked, and you will get a real answer.

Read our mission Read the code on GitHub