Due Diligence Reference

    Data Residency & AI Infrastructure

    Where your data lives, which AI models process it, how it is protected, and every third party involved: the four questions every due diligence review asks, answered in one place.

    Last updated: November 2, 2026

    1. Data Storage & Hosting

    Yes, Voltade stores personal data on behalf of its customers: typically business contact records (names, phone numbers, email addresses), conversation and message history, and the operational data customers connect to the platform. Voltade acts as a data intermediary (processor); the customer remains the data controller.

    These data-protection commitments 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 team@voltade.com.

    Primary region: AWS Asia Pacific (Singapore), ap-southeast-1

    Production databases, file storage, and encrypted backups reside in the AWS Singapore region, with 14-day point-in-time database recovery. Amazon Web Services is Volty's cloud infrastructure provider; Cloudflare provides DNS, CDN, WAF, and DDoS protection at the network edge. Microsoft Azure provides Entra ID sign-in and is one of the model hosts described below; it stores no customer data.

    Data is stored in Singapore, but AI processing is not: to generate a reply, the conversation content that reply needs is sent through OpenRouter to a model host, mostly in the United States, which processes it under zero data retention and does not store it or use it for training.

    2. AI Model Infrastructure

    Every model call Volty makes goes through OpenRouter. 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. We do not train, fine-tune, or host our own foundation models, and customer data is never used to train any AI model: inputs are processed ephemerally (retrieval-augmented generation) and are not retained by OpenRouter or the model host.

    Model ProviderPurposeProcessing LocationSafeguards
    OpenRouterModel gateway that every Volty model call goes throughUnited StatesZero data retention and data collection denied on our account; traffic restricted to an allowlist of model hosts
    Anthropic (Claude)Primary models for agent reasoning and draftingAllowlisted model host, mostly in the USZero data retention through OpenRouter; not used for training
    OpenAI (GPT)Reasoning, vision and embeddingsAllowlisted model host, mostly in the USZero data retention through OpenRouter; not used for training
    Google (Gemini)Reasoning and grounded web searchAllowlisted model host, mostly in the USZero data retention through OpenRouter; not used for training
    xAI (Grok)Reasoning for selected tasksAllowlisted model host, mostly in the USZero data retention through OpenRouter; not used for training
    Open-weight models (DeepSeek, Zhipu GLM, Moonshot Kimi, Xiaomi MiMo)Lower-cost tiers of agent workAllowlisted model host, mostly in the USServed by the allowlisted hosts, never by a first-party DeepSeek, Moonshot, Xiaomi or Z.AI endpoint; zero data retention; not used for training

    The specific model versions in use evolve with the frontier; the providers, controls, and no-training guarantees above are contractual and stable. The models serving your organization are available on request.

    3. Privacy & Security Protocols

    • Encryption: AES-256 at rest and TLS 1.3 in transit for all customer data, including backups
    • Tenant isolation: per-tenant data isolation enforced with database row-level security across the multi-tenant platform
    • Data minimization towards AI providers: only the minimum context required for a given task is sent to a model; credentials and secrets are never included in model context
    • Access control: least-privilege, role-based access with MFA on privileged accounts; customer data access by Voltade staff is need-based and logged
    • Monitoring: audit logging, alerting, and observability across production (see Security Principles)
    • Assessments: CASA Tier 2 penetration tested (9.7/10), CSA Cyber Essentials certified, DPIAs for new personal-data processing

    Beyond encryption and isolation, dedicated privacy-enhancing technologies (e.g. homomorphic encryption, differential privacy) are not currently deployed; data minimization, contractual no-training terms, and ephemeral processing are the operative safeguards for AI workloads.

    4. Third-Party Providers

    Every third party involved in delivering Voltade's services is published in our sub-processor register: AWS (Volty database, backups and transactional email, Singapore ap-southeast-1), Cloudflare (edge network), Microsoft Azure (Entra ID sign-in, and a model host under zero data retention, holding no customer data), OpenRouter (model gateway), the model hosts it allows (Anthropic, OpenAI, Google (AI Studio and Vertex), Amazon Bedrock, Microsoft Azure, xAI, Fireworks, Together, DeepInfra, Novita and SiliconFlow), and Sentry (error tracking). Each is bound by a written agreement with data protection obligations equivalent to those we owe our customers, per our Personal Data Protection Policy. No other party processes customer data without the customer's knowledge and agreement.

    5. How the Platform Handles Your Data

    Inside the product, the AI agent operates on customer records under a set of standing constraints. These are properties of the system rather than settings that have to be switched on.

    • Tenant isolation: Every customer record lives in an organization-scoped table protected by row-level security, and the isolation is pinned by tests. A contact scoped to a single inbox cannot be attached to organization-wide records.
    • Gated actions: Every action the agent can take carries a risk and impact tier. Reads are low-risk, ordinary writes apply inline, and destructive or closing actions require human approval before they take effect. Custom fields are not exempt: there is no path that skips the checks because a field is customer-defined.
    • Audited justifications: High-impact actions require a stated justification, recorded as an audit event, so every sensitive action carries both a reason and an actor.
    • Compliance-floor fields: A contact or company field can be marked compliance-floor, covering identity documents, national ID numbers, and anything else that must never be handled casually. A compliance-floor field can never be written automatically without review, and an automated process can raise the flag on a field but never lower it.
    • Stated contact details are claims, not identity: When someone states an email address or phone number in conversation, it is recorded as unverified and non-primary, with a record of where it came from. An unverified detail never becomes the primary contact method, never receives outbound messages, never resolves incoming messages, and never authenticates anything, so a mistyped or maliciously supplied address cannot capture another person's future conversations. It is promoted only by proof of ownership: a message arriving from that address, or a staff member confirming it.
    • Two-tier deletion: Deleted material is soft-deleted first, with an undo window, then permanently purged by a nightly job 30 days later. Entirely removed is true at 30 days.
    • Per-organization provider keys: Model provider credentials are scoped per organization, so one customer's model traffic is never keyed as another's.

    Need detail for your organization?

    For a due diligence questionnaire, DPA, or the exact data flows of your organization, contact team@voltade.com.