Privacy Policy
Maximum useful intelligence. Minimum personal data. Company Brain stays that company’s.
Who we are
Voyd operates Voyd at voyd.sh: website, desktop app, agents, Company Brain, Sentinel, Atlas, and integrations.
Privacy requests: hello@voyd.sh. This notice version is 2026-10-10.
This page describes the running product. It is not a guarantee against every claim. Counsel should review it for DPDP and other markets you serve.
Four layers
Voyd does not treat every byte as one pile to mine. Data sits in four layers.
Product intelligence: Usage, reliability, cost, latency, errors, retention. Makes Voyd better. No raw prompts, code, emails, or tokens.
Company intelligence: That workspace’s Company Brain, artifacts, and agent work. Stays in the workspace. Never other customers’ training corpus by default.
Aggregate intelligence: Cross-company benchmarks only after aggregation and re-identification checks. Not identifiable company reports.
Optional model improvement: Eligible examples for prompts, routing, or models. Separate opt-in. Off unless the user turns it on.
Private company content is not other customers’ training data unless you turn on model improvement.
What we process
Categories depend on the features you use. We do not need every class for every account.
Account and identity: Access, billing, support, security. Source: Sign-in, profile, session. Store: identity. Retention: Until account close, plus legal holds.
Product analytics events: Funnels, reliability, feature adoption. Source: Web and desktop, after analytics consent. Store: product_analytics. Retention: 90 days raw, then aggregate or delete.
Agent operational telemetry: Completion, cost, latency, retries, errors. Source: Agent runtime. Store: agent_telemetry. Retention: 90–180 days.
Prompts, outputs, and tool traces: Run the requested task and show history in that workspace. Source: Agent chats and tools. Store: company_brain. Retention: Until the user deletes the chat or workspace.
Company Brain and workspace knowledge: Memory for that company only. Source: User and agents in one company. Store: company_brain. Retention: Until delete or account end.
Source, prototypes, .env, build logs: Build and preview that company’s product. Source: CTO agent, code projects, GitHub. Store: artifacts. Retention: Until delete or account end.
Leads and outreach: Campaigns the user starts. Source: CMO tools, user lists, public sources the user authorizes. Store: company_brain. Retention: Until campaign/workspace delete; honor suppression.
Revenue and company outcomes: CFO/CEO work in that workspace. Source: User, Stripe connect, OS metrics. Store: company_brain. Retention: Until delete; billing copies follow tax law.
Sentinel monitoring: Watch what the user turned on. Source: User-configured sources and schedule. Store: company_brain. Retention: Alert metadata 90–180 days; evidence in workspace until delete.
Integration credentials and scopes: Act in the connected service. Source: OAuth and API keys the user connects. Store: integration_vault. Retention: Until disconnect, then invalidate.
Plans, credits, invoices: Charge and show usage. Source: Polar and account. Store: billing. Retention: As required for tax and accounting.
Atlas public profile fields: Public discovery the founder chose. Source: Founder publication flow only. Store: atlas. Retention: Until unpublished.
Voice dictation audio: Turn speech into text in the composer. Source: Mic, on-device whisper.cpp by default. Store: local_device. Retention: Discard after transcription unless a cloud STT path is separately disclosed.
Auth and abuse signals: Secure the service. Source: Login, API, rate limits. Store: security_logs. Retention: 90–180 days.
Notices, choices, withdrawals: Prove and enforce purpose limits. Source: Banner, settings, Atlas publish. Store: consent_audit. Retention: As long as needed to enforce the choice.
Optional model-improvement examples: Improve prompts, routing, or models as the notice says. Source: Only if model_improvement is granted. Store: intelligence_warehouse. Retention: Only while opt-in holds; withdraw and delete downstream copies.
We do not collect government IDs, home addresses, or date of birth for ordinary use.
How we use it
Run the product you asked for: accounts, agents, Company Brain, prototypes, Sentinel in the scope you set, outreach you start, billing, security.
Measure product health with operational events when analytics is on.
Publish Atlas fields only through the publication flow.
Improve models only when that optional purpose is granted.
We do not sell identifiable private workspace content, raw private prompts, or Company Brain records as a data product.
AI providers
A requested task may go to Voyd-hosted models (Azure AI Foundry) or a provider you connect with your own key.
The provider sees the context needed for that task. Their retention and training terms apply to that hop. Check the provider list on this page.
Google sign-in is identity only. Optional Gmail send is send-only. Voyd’s use of Google user data follows the Google API Services User Data Policy, including Limited Use. We do not use Google user data for ads, sell it, or train generalized models on it.
Company Brain
You keep rights in content you submit, subject to third parties.
We process workspace content to run that workspace. Other customers cannot open your private board through ordinary product access.
You must have rights to submit other people’s data (employees, customers, leads).
Integrations and outreach
Connected services process the scopes you grant. Disconnect in Integrations. That stops new access. Imported copies in the workspace stay until you delete them.
Lead generation may process business contacts from sources you provide or authorize. You are responsible for marketing, anti-spam, and platform rules. Honor opt-outs.
Atlas
Atlas shows fields you publish. Company Brain, private finance, and private chats do not become public because you opened Atlas.
Public pages can be copied or cached off Voyd after you unpublish.
Providers
Neon (Postgres) (core): Primary database. Accounts, workspaces, messages, OS state.
Azure AI Foundry / Azure OpenAI (core): Default hosted model routing. Task context needed for the requested generation.
Bring-your-own-key providers (optional): User-selected models (OpenAI, Anthropic, Google, Groq, NVIDIA NIM, others). Prompts and tool context for that request, under the user’s key and that provider’s terms.
Polar (core): Subscriptions and invoices. Email, plan, payment status. Not card PAN in Voyd..
Google Identity (optional): Sign in with Google. Name, email, profile photo.
Gmail send (optional) (optional): Outreach send the user starts. Send-only OAuth. No Gmail read from sign-in..
PostHog (optional): Product analytics. Feature events after analytics consent. No raw prompts or tokens..
Mixpanel (optional): Product funnel events. Same class as PostHog, if a token is configured and analytics is on.
Sentry (optional): Crash and error reports. Stack traces and diagnostic metadata. Redact secrets..
User-connected integrations (optional): GitHub, Vercel, Microsoft, Notion, Linear, Figma, X, LinkedIn, Stripe, others the user connects. Scopes the user grants; tokens in the integration vault.
Your choices
Service, security, and billing are required to run Voyd. They are explained here, not hidden in one “agree to everything” box.
Product analytics: Feature usage, funnels, performance. Not prompts, code, emails, or tokens.
Model improvement: Eligible examples to improve prompts, routing, or models. Off unless you turn it on.
Product emails: Voyd news and offers. Unsubscribe any time. Not required to run the product.
Settings → Privacy records the choice, notice version, and time. Withdraw the same way. Atlas publication is a separate per-field flow, not this toggle.
Access, correction, and deletion requests: hello@voyd.sh. We verify identity. Account export of consent records is available in Settings while signed in.
Withdrawal does not unwind processing that was lawful before the change.
Retention, security, transfers
Retention follows the inventory above. Backups rotate on a delay. We will not claim instant wipe from every backup if that is not true.
We use access controls, encryption in transit, credential isolation by workspace, and audit logs for team actions. No system is perfectly safe.
Processing may occur outside your country, including India, the US, and provider regions. Those laws may apply.
Children
Voyd is not for children under 13, and not for anyone who cannot legally contract in their place.
If a child was added by mistake, write hello@voyd.sh.
Changes
Material changes get a new notice version. We will not use a quiet edit to turn Company Brain into training if the law requires a new permission.