Zamok · effective September 16, 2026
Zamok is a personal household tool, built and operated by its author for his own household's Gmail accounts. It is not offered to the public, does not accept outside sign-ups, and this policy describes the only way it is actually used.
Zamok connects only to Google accounts that the household administrator
explicitly links. It requests the openid scope and the
read-only Gmail scope
(https://www.googleapis.com/auth/gmail.readonly) — never a
scope that can send, modify, or delete mail.
Messages are streamed to a credential-free local component that applies deterministic mail-handling policy, then discarded from that component. Any link target inside a message's text is stripped before the message is released to anything downstream, so only the hostname survives — a consumer of the released text can never be handed a followable link. Data is processed on infrastructure the operator controls and is never used for advertising, never sold, and never used to train machine learning models.
Zamok keeps a local, encrypted database of household state — linked accounts, applied policy, and evidence for any message withheld by policy, so the administrator can review that decision. Backups of this database are encrypted. Restoring a backup does not restore Google credentials; every account must be explicitly reauthorized afterward.
Zamok does not share Gmail data with any third party, and no other person or service has standing access to it. The only consumer of released message text is the household's own agent tooling, running on infrastructure the operator controls.
The household administrator can disable or unlink any account at any time, which revokes Zamok's Google authorization. Any account holder can also revoke access directly from their Google Account permissions page at any time.
If this policy changes, the date above will be updated.