Privacy Policy
LAST UPDATED · JUNE 10, 2026
Verity One ("Verity One," "we," "us," or "our") provides a personal, reviewable knowledge-graph and vault-sync service. This Privacy Policy explains what information we access, how we use it, and the choices you have — with particular attention to information accessed through Google APIs. Your local node is the source of truth; we broker, we do not own.
1. Information we access
- Google account profile. When you sign in with Google, we receive your email address, basic profile information (such as your name), and a Google account identifier. We use this solely to authenticate you and to associate your session with your Verity One account.
- Google Drive — narrow per-file access (
drive.file). If you choose to connect Google Drive, Verity One requests only the per-filehttps://www.googleapis.com/auth/drive.filescope. This grants access only to files and folders that Verity One itself creates, or that you explicitly open with Verity One — it does not grant access to your entire Google Drive. We use it to create a dedicated "Verity One" folder in your Drive and to synchronize the notes and documents in your Verity One knowledge vault to and from that folder.
2. How we use Google user data
We use the access described above exclusively to provide the features you enable:
- Sign-in: your Google profile authenticates you to Verity One.
- Vault sync: the
drive.filescope is used only to mirror your Verity One vault between your own device(s) and your own Google Drive. We do not read, index, or process any Drive files outside the Verity One folder.
Your vault content remains in your Google Drive and on your local Verity One node. Verity One brokers the synchronization; it is not a service that retains a separate copy of your vault.
3. How your Google credentials are handled
The OAuth authorization is brokered by our hosted service (verityone.app) and delivered to your local Verity One node via a sealed credential handoff: the access token is sealed (libsodium asymmetric box) to an ephemeral public key your local node generated, so only your local node — which holds the matching private key — can open it. Our hosted service exchanges Google's authorization code for the access token and immediately seals it to your node's ephemeral public key; it never writes the plaintext token to storage — only the sealed ciphertext is persisted (briefly, single-use), and only your local node can open it. We never receive or store your Google password. The credential hand-off is single-use and short-lived.
4. Limited Use disclosure
Verity One's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Specifically: we use Google user data only to provide and improve the user-facing features that are prominent in Verity One; we do not sell this data; we do not use it for advertising; we do not transfer it to others except as necessary to provide or improve the feature, to comply with applicable law, or as part of a merger or acquisition; and humans do not read your Google user data except with your consent for specific files, where necessary for security purposes (such as investigating abuse), or to comply with applicable law.
5. Data we do not access
We do not access your full Google Drive, Gmail, Google Calendar, Google Contacts, or any other Google data beyond the scopes listed in Section 1. We do not sell your personal data to anyone.
6. Your choices and rights
- You can revoke Verity One's access to your Google account at any time at myaccount.google.com/permissions, or by disconnecting Google Drive from your Verity One dashboard.
- Revoking access stops further synchronization. Files already synced to your Drive remain under your control in your own Google Drive.
- Disconnecting a workspace revokes its authorization tokens and credentials, deletes that workspace's hosted mirror data (synced memories, journal entries, Drive file records), and destroys its per-workspace encryption key. Once the key is destroyed the hosted copy is permanently unrecoverable — even by us.
- Deleting your account (from your dashboard, after disconnecting your workspaces) removes your account record and all associated account data — sessions, authorization grants, hosted node registrations, and agent credentials.
7. Data retention
We retain account and authorization metadata only for as long as your Verity One account is active or as needed to provide the service. When you disconnect a workspace or delete your account, authorization tokens are revoked and the data described in Section 6 is removed as part of that action — not on a deferred schedule.
We retain a minimal, tamper-evident security audit log (which workspace was connected or disconnected, when, and by which account — never your memory content) for up to 365 days after the event, for security and abuse-investigation purposes. This log does not contain decrypted content and is the only record kept after deletion.
8. Children
Verity One is not directed to children under 13, and we do not knowingly collect personal information from them.
9. Changes to this policy
We may update this Privacy Policy from time to time. The "Last updated" date above reflects the most recent revision. Material changes will be reflected on this page.
10. Contact
Questions about this policy or your data: support@verityone.app.
See also the Terms of Service · Return home.