Privacy Policy

This policy covers Volty, our self-serve, managed AI teammate. Volty is a pooled multi-tenant service; each organisation's data is isolated at the database layer by Postgres Row-Level Security. Volty's runtime guardrails are documented at AI Governance & Guardrails; the full architecture is at the Volty platform whitepaper. The runtime architecture for the agents themselves (capability scoping, audit trail, human-in-the-loop) is separately documented at /ai-governance.

§8 (international transfers), §9 (retention and deletion), §10 (security and breach notification), §11 (your rights), §12 (children's data) and §15 (contact) also apply to personal data Voltade Pte. Ltd. processes or retains from previous solutions it built or operated for customers. Requests about that data go to the same contact, team@voltade.com.

Volty stores the data you and your team add directly, plus the data that flows in from the channels you connect.

Volty runs a bounded, journalled "wake" per conversation: the agent sees only the conversation it is scoped to, its context is drawn from the connected channel and your organisation's knowledge drive, and every model call goes through OpenRouter under zero data retention, as described in §5. Volty's runtime is documented in detail at AI Governance & Guardrails.

• Per-customer scope — for an inbound message from contact X, an agent has access to that contact's record, conversation history, and your organisation's knowledge base. It does not see other customers' data.
• Bounded execution — every agent run has a token budget and a defined exit; long-running work is queued asynchronously.
• Trace records — we record per-call usage (feature, model, token counts, estimated cost, and the model provider's response id). OpenRouter and the model hosts behind it run under zero data retention, so neither keeps the prompt or the response.
• Output guardrails — model responses pass through a sanitiser that removes leaked internal instructions or chain-of-thought before reaching customers.

• To provide, operate, and improve the Services you've subscribed to.
• To run the AI agents you've configured — analysing inbound messages, drafting replies, retrieving relevant records, and escalating to humans when guardrails require it.
• To process payments, issue invoices, and administer your account.
• To respond to support requests, security incidents, and lawful regulatory obligations.
• To produce aggregated, de-identified diagnostics that help us measure reliability and improve the product.
• To send service-related communications (account, billing, security). Marketing communications are sent only with your consent and you can opt out at any time.

Voltade Services use multiple large language model providers. Every model call in Volty goes throughOpenRouter. Our OpenRouter account enforces zero data retention, denies data collection, and only allows these model hosts: Anthropic, OpenAI, Google (AI Studio and Vertex), Amazon Bedrock, Microsoft Azure, xAI, Fireworks, Together, DeepInfra, Novita and SiliconFlow. To generate a reply, the conversation content that reply needs is sent through OpenRouter to one of those hosts, mostly in the United States. The host does not store it or use it for training.

The model families in use are:

• Anthropic (Claude) — primary reasoning model for Volty. Anthropic Commercial Terms.
• OpenAI (GPT) — used across Volty for reasoning, vision (Volty drive extraction), and embedding generation. OpenAI API content is not used to train OpenAI models. OpenAI Enterprise Privacy.
• Google (Gemini) — reasoning and grounded web-search results in Volty.
• xAI (Grok) — reasoning model available to Volty.
• Open-weight models — DeepSeek, Zhipu GLM, Moonshot Kimi and Xiaomi MiMo models, available to Volty for cost-tier selection. These run on the model hosts listed above, not on the labs that trained them: no first-party DeepSeek, Moonshot, Xiaomi or Z.AI endpoint receives your data.

In Volty, model selection is tiered by your subscription plan; the agent uses the highest-quality available model in your tier and falls back to the next-ranked model on provider failure. We may add or substitute model providers as the field evolves. Material changes are reflected in this page and, where relevant, in the subprocessor list at §7.

We send the minimum context an agent needs for the task at hand — recent messages and the relevant slice of your knowledge base or drive, not a full database dump.

When you authorise an integration (Microsoft 365, Google Workspace, Salesforce, Shopify, WooCommerce, Odoo, HubSpot, Meta channels, and others), you grant Voltade scoped access to that connected account. We use that access only for the features you've turned on. You can revoke an integration at any time from inside the product or from the third-party platform; we will stop processing immediately and begin deletion of cached data within 30 days.

The current authoritative integrations list is published at /integrations.

We work with the third parties below to deliver Volty. Each is bound by confidentiality and, where applicable, a Data Processing Agreement.

We do not sell personal data. Customer business data in Volty is never shared with advertising networks. The only data that reaches an advertising network is the website and signup measurement described in §13.

Volty customer data is stored in Singapore (AWS Aurora Postgres, S3, and SES in ap-southeast-1).

Some subprocessors operate outside Singapore. To generate a Volty reply, the conversation content that reply needs is sent through OpenRouter to a model host, mostly in the United States (Anthropic, OpenAI, Google (AI Studio and Vertex), Amazon Bedrock, Microsoft Azure, xAI, Fireworks, Together, DeepInfra, Novita and SiliconFlow), under zero data retention: the host does not store it or use it for training. Channel providers (Meta, Google Workspace, Microsoft 365) operate across multiple jurisdictions. Where personal data leaves Singapore, we rely on contractual safeguards meeting PDPA Section 26 standards of protection.

Account and billing records are retained for the life of the account plus 7 years to meet Singapore tax and accounting requirements.

Volty:

• Volty contacts, conversations, knowledge drive, memory — retained for the life of your organisation. Soft-deleted conversations, contacts, and inboxes hard-purge after a 30-day grace period; drive trash purges after 30 days.
• Organisation deletion — enters a 30-day grace period (logins blocked, cancellable). After 30 days, all customer data for the organisation is purged.
• User account deletion — anonymised immediately on request (email replaced with a placeholder, name and phone scrubbed, sessions hard-deleted).
• Contact Forget — anonymises the contact record and redacts merge snapshots; you can additionally request purge of conversation history under this contact.
• Operation events (agent audit trail) — retained for approximately 3 months.
• Admin audit and inbox audit — retained up to 12 months per policy.
• Postgres backups — a 14-day point-in-time recovery window on managed Aurora Postgres.

You can request deletion of your data at any time by emailing team@voltade.com, or (for Volty) directly from within the product. We will action the request within 30 days unless a legal obligation requires longer retention, in which case we will tell you.

This section also applies to personal data Voltade Pte. Ltd. processes or retains from previous solutions it built or operated for customers. You can request deletion of that data at the same address, on the same terms.

We encrypt data in transit (TLS 1.2+) and at rest. Production access is restricted, MFA-enforced, and logged. We hold:

• Singapore CSA Cyber Essentials Mark.
• CASA Tier 2 Cloud Application Security Assessment.

Volty-specific controls. Tenant isolation is enforced at the database layer by Postgres Row-Level Security policies keyed on the customer's organisation identifier, applied per-transaction; the Volty application database role cannot bypass Row-Level Security. Contact-triggered agent wakes run with a further-de-escalated read scope confined to a single conversation and contact. Sensitive configuration secrets (channel access tokens, connected-mailbox credentials, third-party integration credentials) are envelope-encrypted at rest with per-domain key encryption keys. Model-inference calls go through OpenRouter under zero data retention, restricted to an allowlist of model hosts.

Breach notification. We will notify affected customers and the Singapore Personal Data Protection Commission of any notifiable data breach within 72 hours of confirming that the breach meets the PDPA notification threshold. The full register of certifications and controls lives in the Trust Centre.

Under the PDPA you may:

• Confirm whether Voltade holds personal data about you and request a copy.
• Correct any inaccurate or incomplete personal data — including memory entries an agent has stored about you.
• Withdraw consent (we will tell you the consequences before doing so).
• Revoke any third-party integration you previously authorised.
• Lodge a complaint with the PDPC if you believe we have not handled a request properly.

Submit requests to team@voltade.com. We respond within 30 days. A reasonable administrative fee may apply for repeated or voluminous requests.

These rights also cover personal data Voltade Pte. Ltd. processes or retains from previous solutions it built or operated for customers. Requests about that data go to the same address.

For Volty specifically, you can inspect and edit your organisation's knowledge drive entries and per-contact memory from inside the product. Data export for Volty is currently on request via team@voltade.com; a self-serve export tool is in development.

Our Services are designed for businesses. Some of our customers operate childcare, schools, and education services — in those cases the customer is responsible for obtaining parental consent before submitting any child's data through the Services, and Voltade processes such data only as a data intermediary on the customer's behalf.

This section covers visitors to voltade.com and the Volty signup page (volty.voltade.com/signup). It does not cover the data in your Volty workspace, which never carries these tags.

We may update this policy as the Services evolve. The "Last updated" date at the top of the page reflects the most recent change. For material changes we'll notify you directly.

For privacy questions, requests, or complaints contact our Data Protection Officer at team@voltade.com or by post to Voltade Pte. Ltd., 75 Ayer Rajah Crescent, #01-16, Singapore 139953.