Privacy

What Saybooks keeps, and what it doesn't

Effective 2026-09-05. Saybooks is operated by Peter Varga, the sole founder, and this page is written by him rather than by a template. If something here is unclear, write to hello@saybooks.io.

The short version

What we store

DataWhyHow long
Your Google identity when you sign in: account id, email, name, profile pictureTo know whose books are whose and to let you invite people by emailUntil you delete your last space and ask us to remove the account
Everything in your books: customers, invoices, orders, postings, payments, the company profile and logoThat is the productUntil you delete the space
The audit log: every command, who ran it (you, an invited person, or an agent holding your key), the reason given, and refusalsThe record is the point; it is what makes an agent safe to let inUntil you delete the space; exported with it
Keys you mint for agents and invitations you sendSo an agent can act as your delegate, with your permissions, until you revoke itUntil revoked or the space is deleted
Usage counts per workspace: number of calls, writes, agent calls, first and last activityTo see whether the product is used at all; counts only, never contentRolling; sandboxes' rows go with the sandbox
Where you came from: the referring site's host name, the page you landed on, and any utm tags in the linkTo learn which channel brings people who stay30-day cookie; one row per workspace
Standard web server logs (IP address, path, time, browser string)Abuse protection and debuggingBriefly, on the server

Cookies

All first-party. sb_sess keeps you signed in (30 days). sb_space remembers which of your spaces you opened last. otc_ws ties a browser to an anonymous demo sandbox. sb_oauth lives for ten minutes during Google sign-in. sb_src records the first page you arrived on and the site that sent you (30 days). There is no third-party analytics script and no advertising pixel.

Who else sees anything

Agents and AI

When you connect Claude or another agent, it reads and writes your books through the same commands you use, under the role of the key you minted, and every action lands in your audit log with the agent named as the actor. Saybooks itself does not call any AI model and does not send your data to one; whatever your agent sees is governed by your agreement with its provider.

Your controls

Open source

The whole system is published under AGPL-3.0 at github.com/alviso/saybooks. If you would rather not trust a hosted service, run it yourself; the code that handles your data is the code you can read.

Changes

If this page changes in a way that matters, the change is dated here and announced on the site. Prices, where they exist, change with twelve months' notice.