Trust Center
How we isolate and protect your data.
This page sets out how VritantAI Discover handles your data: how tenants are isolated, which providers process data on our behalf, what we keep and for how long, and what we commit to on uptime.
Security posture
How we isolate and protect your data
Row-level tenant isolation
Every table is scoped by PostgreSQL row-level security to a tenant ID. No application query can return data across tenant boundaries.
Hashed API keys
API keys for the catalog push API are stored one-way hashed. The plaintext key is shown once, at creation, and never again.
HMAC-verified webhooks
Inbound WooCommerce and Shopify webhooks are HMAC-signature verified before being enqueued for processing.
Encrypted credentials at rest
Store connection credentials (Shopify access tokens, WooCommerce API keys and webhook secrets) and two-factor secrets are encrypted with AES-256-GCM before storage; the plaintext is never persisted.
Subprocessors
Who processes data on our behalf
We use the following subprocessors to deliver the platform. Each is bound by a data processing agreement appropriate to its role. We do not share your data with advertising networks, and we do not sell your data.
AI inference
Anthropic
One of the AI engines VritantAI Discover queries in citation benchmarks and hallucination sweeps, and the model that writes plain-language explanations of audit findings.
Data: Benchmark prompts that name the merchant's brand and products, and audit findings for the merchant's own pages, sent per request; no shopper data and no persistent identifiers.
OpenAI
One of the AI engines VritantAI Discover queries in citation benchmarks and hallucination sweeps.
Data: Benchmark prompts that name the merchant's brand and products, sent per request; no shopper data and no persistent identifiers.
Google (Gemini)
One of the AI engines VritantAI Discover queries in citation benchmarks and hallucination sweeps.
Data: Benchmark prompts that name the merchant's brand and products, sent per request; no shopper data and no persistent identifiers.
Perplexity
One of the AI engines VritantAI Discover queries in citation benchmarks and hallucination sweeps.
Data: Benchmark prompts that name the merchant's brand and products, sent per request; no shopper data and no persistent identifiers.
DeepSeek
One of the AI engines VritantAI Discover queries in citation benchmarks and hallucination sweeps.
Data: Benchmark prompts that name the merchant's brand and products, sent per request; no shopper data and no persistent identifiers.
Infrastructure
Supabase
PostgreSQL database hosting with row-level security enforced per tenant.
Data: All persisted platform data: account, catalog, audit and benchmark results, and billing records. Also holds the records of the retired VritantAI Convert product (shopper conversations, contacts, and orders) until they are deleted.
Redis
Managed Redis hosting for the background job queue and for short-lived caching of rate limits and session state.
Data: Queue payloads and cache entries; short-lived, not a system of record.
Payments
Paddle
Merchant of Record for subscription billing and invoicing.
Data: Billing contact details and subscription state; payment card data is held by Paddle, never by VritantAI.
Razorpay
Subscription billing in INR for customers in India, and purchases of prepaid usage credit.
Data: Subscription state, payment amount, currency, and payment status; card and bank details are held by Razorpay, never by VritantAI.
Messaging
Resend
Delivery of transactional email: account, security, support, and monitoring-alert emails to customer users, and results that website visitors ask us to email them.
Data: Recipient email address and the content of the email being sent.
Meta (WhatsApp Business Platform)
Retired with VritantAI Convert: no WhatsApp messages are sent or received. Listed until our Meta app is removed from connected WhatsApp Business Accounts and the product listings it synced to their Meta catalogs are removed.
Data: Product listings previously synced to a merchant's Meta catalog, and the link between our Meta app and the merchant's WhatsApp Business Account.
Twilio
Retired with VritantAI Convert: no SMS messages are sent. Listed until our Twilio account and its phone numbers are closed.
Data: Any records of SMS messages sent before retirement that remain in our Twilio account.
Observability
Sentry
Error monitoring across the API, workers, and dashboard.
Data: Stack traces and request metadata; scrubbed of known-sensitive fields before capture.
PostHog
Server-side product analytics: account milestone events such as catalog sync completion and subscription changes.
Data: Tenant ID and event details such as plan and billing provider; no shopper data, not used for advertising or cross-site tracking.
Data processing
Data processing summary
We do not train AI models on your data. Your catalog data and audit results are used only to deliver the service to you: audits, benchmarks, monitoring, and your own dashboard. They are never used to train or fine-tune any AI model, ours or a third party's.
Records from the retired VritantAI Convert product (shopper conversations, contacts, and orders) are no longer collected and are kept only until they are deleted as part of retiring Convert. Audit history is retained for 24 months.
A merchant, shopper, or their representative can request data access, correction, export, or deletion. Full details, including how we handle GDPR and India's DPDP Act, are in our Privacy Policy. A data processing agreement is available on request for enterprise customers: email business@vritantai.com.
Reliability
Uptime and incident communication
Our target for the dashboard and API is 99.9% monthly uptime, excluding scheduled maintenance windows, which we announce in advance by email and in-app notification.
Every API request carries a correlation ID that follows it into the background jobs it starts, so an incident is diagnosed against a specific request rather than by timestamp guesswork.
During an incident we post updates so you can tell whether an issue is on your end or ours before opening a support ticket. A public, independently-hosted status page is on our near-term roadmap; until it ships, email business@vritantai.com any time for the current status of your account and we will respond directly.
Security vulnerability disclosures: email business@vritantai.com and we will respond promptly. We do not publish a bug bounty program at this time.