A deliberate approach to data.
How CapZero handles personal information in the CapZero application, and on this public website.
CapZero product privacy notice
Version 2026-10-26.2 · Approved 2026-10-26
Who we are and what this covers
This notice covers the CapZero application at app.capzero.ai, its APIs and its MCP connectors (the “app”). The app is provided by Overtake Capital LLC, doing business as CapZero (“CapZero”, “we”). For privacy questions or requests, see Contact us.
Our two roles
- CapZero as controller. We decide how to use the information we need to run the app itself: people’s accounts and sign-in, security, billing contacts, support, and records of who accepted which terms. This notice describes that use.
- CapZero as processor. Organizations put their own data into the app: records, files, and mail or messages from accounts they connect. We handle that data only on the organization’s instructions, under the Data Processing Agreement. The organization decides how it is used, so questions about it are best sent to that organization; we help it respond.
Information we collect as controller
- Account: your name, email address and, if you sign in with Google, your profile picture; the organizations you belong to and your roles.
- Sign-in: the app has no passwords. You sign in with a 6-digit code we email you (stored only as a hash, and expiring after 10 minutes) or with Google. Two-step verification uses a passkey or an authenticator app with recovery codes, and is required for administrators and operators.
- Sessions and security: each session records the IP address, browser user agent and country. Bot checks on sign-up, sign-in code requests, access requests and public forms receive a check token and your IP address. Actions in the app are written to an audit log.
- Acceptance records: the version of the terms and privacy notice you accepted or acknowledged, with the time and organization.
- Billing contacts, when billing is enabled. Billing is currently in test mode.
- Support: what you send us when you ask for help.
The app uses no analytics, advertising trackers or error-tracking services. Platform logs must not contain record contents, tokens or secrets.
Information we process for organizations
As processor, the app holds what an organization and its people and agents add:
- records in the organization’s apps, and the files attached to them;
- search embeddings made from records’ text fields, except fields marked sensitive or hidden;
- mail from a connected Google or Microsoft account, when an administrator turns on mail sync: the first sync reads the last 30 days, then new mail every 5 minutes. Only messages involving people or organizations in the organization’s records are kept. The app stores the addresses, time, thread and subject, and the body only if the organization turns that on (up to 50,000 characters). Attachments are never kept;
- messages and channel information from a connected Slack workspace.
Integrations and the access they request
| Provider | Access | When and why |
|---|---|---|
openid, email, profile; optionally gmail.readonly, gmail.send | Sign-in, when you choose Google. Mail sync and sending mail from the app, only when an administrator connects a Gmail account. | |
| Microsoft | Identity scopes; optionally Mail.Read, Mail.Send | Identifying the connected account. Mail sync and sending mail from the app, only when an administrator connects a mailbox. |
| Slack | Identity scopes; bot scopes chat:write, chat:write.public, channels:read, groups:read, channels:history, groups:history | Posting messages to channels and reading channel lists and channel messages, only when an administrator connects a workspace. |
Credentials for connected accounts are encrypted with the organization’s own data key.
Why we use information, and legal bases
Where data protection law such as the GDPR or UK GDPR applies, these are the legal bases for our use as controller.
- Providing your account, sign-in and the app, and sending service email (sign-in codes, invitations, notifications, verification): performance of our contract.
- Keeping the app and its users secure, including bot checks, session records and the audit log: our legitimate interest in protecting the service and the people who use it.
- Recording acceptance of the terms: our contract, and our legitimate interest in showing what was agreed.
- Billing, when enabled: performance of our contract, and legal obligations such as accounting and tax.
- Support: performance of our contract, or our legitimate interest in helping you.
For data we process for an organization, that organization determines the purposes and its own legal basis.
Who receives information
We use these service providers to run the app. They process information on our behalf to provide their services to us. Google, Microsoft and Slack receive or provide information only when an organization connects them, under those providers’ own terms. Providers are listed by service name. The legal entity that provides each service, and its data protection terms, are available on request.
| Provider | What it does | Information it receives | Location |
|---|---|---|---|
| Cloudflare | Runs the app (Workers) and its platform logs; stores files (R2); makes search embeddings (Workers AI); runs bot checks (Turnstile); holds the environment master key (Secrets Store). | Everything the app handles passes through it. Turnstile receives the check token and the visitor’s IP address. Workers AI receives records’ text fields, never fields marked sensitive or hidden. | United States: the app runs near AWS us-east-1; files are stored in Eastern North America with backup copies in Western North America. |
| Neon | Hosts the Postgres database. | Account, organization and audit data, and the organization’s records. | AWS us-east-2, United States. |
| Postmark | Sends platform email: sign-in codes, invitations, notifications and verification messages. | Recipient address, subject and text body. | United States: Postmark’s data center outside Chicago, Illinois, and Amazon Web Services. |
| Anthropic | Provides the AI model behind the builder assistant. | The person’s request and the app’s draft definition. Never the organization’s records. | United States. |
| Stripe | Takes payments through its hosted checkout and billing portal, when billing is enabled. | Billing contact and payment details, which are entered on Stripe. CapZero never stores card details. | United States. |
We do not sell personal information or share it for advertising. We disclose information to others only when the law requires it, to protect people or the service from harm, or with your direction.
Google user data
CapZero’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
- What we access. Google sign-in requests
openid,emailandprofile: your name, email address and profile picture. Mail sync is optional and only starts when an organization’s administrator connects a Gmail account; it requestsgmail.readonlyto read mail andgmail.sendto send mail people write in the app. CapZero does not access Google Calendar or any other Google data. - Why. Sign-in data creates your account, signs you in and shows your name and picture in the app. Synced mail appears in the organization’s records, so its people can see correspondence with the people and organizations they work with, and send mail from the app.
- How it is stored. In the app’s database, isolated to the organization by row-level security, and kept only as described under mail sync above (no attachments; bodies only if the organization turns that on). Google credentials are encrypted with the organization’s own AES-256-GCM data key. Data travels over TLS.
- How it is shared. Only with the service providers that run the app, listed above, to provide its features; and when the law requires. Google user data is never sent to the builder assistant’s AI provider.
- What we never do. We do not sell Google user data, use it for advertising, or use it to develop, improve or train generalized AI or machine-learning models.
- Human access. CapZero staff do not read Google user data, except with your consent for specific messages, where needed for security (such as investigating abuse), to comply with the law, or when it has been aggregated and anonymized for internal operations.
- Removing access and data. See disconnecting an integration and deleting data.
How long we keep information
- Your personal account stays until you ask us to delete it. It is separate from any organization and remains if an organization you belong to is deleted.
- Emailed sign-in codes expire after 10 minutes.
- Sessions last 7 days and are renewed daily while you use the app.
- Audit log entries, including acceptance records, cannot be changed or deleted; we aim to keep them for 7 years.
- An organization’s data stays until the organization deletes it or the organization is deleted. Deletion has a 30-day grace period, then the organization’s files, records and keys are purged, leaving only a minimal record with an opaque identifier and timestamps.
- Backups: the database can be restored to any point in the last 7 days; daily production snapshots and file backup copies are kept for 35 days. Deleted data leaves the backups within 35 days.
- Export download links last 24 hours.
- Platform logs: request, error and background-job logs, which can include IP addresses, browser details and account identifiers, are kept for up to 7 days and then deleted automatically.
Disconnecting an integration and deleting data
Disconnect Google, Microsoft or Slack (organization administrators):
- In the app, open Settings → Connections.
- Choose the connection and select Disconnect.
- The stored credential is erased at once and mail sync stops. Slack tokens are also revoked at Slack.
- For Google and Microsoft, also remove CapZero’s access in your account, because the app does not revoke it there: Google at myaccount.google.com/permissions, Microsoft at myapps.microsoft.com.
Mail already synced is part of the organization’s data. It is removed when the organization is deleted; to ask for earlier removal, contact your organization’s administrator or [email protected].
Export an organization’s data (administrators):
- Open Settings → Export and start an export.
- Download the file; the link lasts 24 hours.
Delete an organization (administrators):
- An administrator requests deletion of the organization.
- The organization is suspended for a 30-day grace period.
- After the grace period, its files, records and keys are purged. Backup copies expire within 35 days.
Delete your personal account:
The app does not yet offer self-service account deletion. Email [email protected] from the address on your account and we will delete it. Deleting your account does not delete an organization’s records that mention you; ask that organization about those.
Security
Row-level security isolates each organization’s data in the database, stored credentials are encrypted with per-organization keys, and all traffic uses TLS. The security measures annex describes the controls in more detail.
Where information is processed
The app and its data are hosted in the United States: the database in AWS us-east-2, the app near AWS us-east-1, and files in Eastern North America with backup copies in Western North America. If you use the app from another country, your information is transferred to the United States. Where the law of the country you are in restricts such transfers, we rely on the European Commission’s Standard Contractual Clauses, with the UK International Data Transfer Addendum and the Swiss adaptations where they apply, and our service providers are bound to equivalent safeguards, such as the same clauses or certification under the EU-U.S. Data Privacy Framework and its UK and Swiss extensions.
Your rights
Depending on where you live, you may have the right to access your personal information, correct it, delete it, receive a copy, object to or restrict our use of it, and withdraw consent where we rely on it. You may also complain to your data protection authority.
To make a request, email [email protected], from the address on your account where possible. We may need to confirm your identity. If your request concerns an organization’s data, we will refer it to that organization or help it respond.
Children
The app is for organizations and their staff. It is not directed at children, and we do not knowingly collect children’s personal information. If you believe a child has given us information, contact us and we will delete it.
Changes to this notice
New versions are published at this address with a new version label. When a new version is approved, the app asks you to acknowledge it before you continue.
Contact us
For privacy questions or requests, email [email protected], or write to Overtake Capital LLC, 5900 Balcones Drive, Suite 100, Austin, Texas 78731, United States.
Website privacy notice
Last updated: October 30, 2026
This notice covers this public website, capzero.ai, only. Its statements about cookies and browser storage apply to this website; the app at app.capzero.ai uses the cookies listed in the product privacy notice.
Who to contact
Overtake Capital LLC provides this website. For questions about this notice, access to information you have sent us, or a correction or deletion request, email [email protected]. Tell us enough to identify the relevant correspondence without sending unnecessary sensitive information.
Visiting the website
The site does not add advertising trackers, analytics scripts, third-party embeds, cookies, local storage, or session storage. Fonts and visual assets are served with the site. There is no advertising profiling or sale of information implemented by this website.
The hosting provider processes technical request information, such as an IP address, requested URL, time, and browser information, to deliver pages and operate its network. The site is configured for Cloudflare Pages. Provider logging and retention depend on the hosting account’s configuration and service terms.
Using the contact form
The form builds a project brief in your browser. It does not submit the entered fields to a website server. “Prepare email” creates a draft link for your mail application; you choose whether to send it. “Download brief” saves a text file on your device. The site does not persist form entries in browser storage.
If you send the draft or write to us directly, CapZero receives the information in your email and uses it to evaluate and respond to your inquiry. Your chosen email provider and CapZero’s email services handle that correspondence under their applicable terms.
Only provide information appropriate for an initial business conversation. Do not send sensitive institutional records, credentials, or classified information through the form or an ordinary inquiry email.
Use, access, and retention
Inquiry information may be used to respond, clarify requirements, and maintain related business correspondence. Access should be limited to the people and service providers needed for that work. Correspondence may also need to be retained for an applicable legal obligation or an ongoing matter.
Contact us about retention of a specific record or to make a request. Our response will account for applicable obligations and the information needed to verify the request.
Links and local downloads
External links and email applications operate under their own practices. Downloaded briefs remain on your device until you manage or share them. The CapZero Budget demonstration uses illustrative data, and its scenario controls do not send information to a server.
Changes
Updates to this website notice will appear on this page. The date above identifies its latest revision.