Security

Security is built into how AskBrew is designed, not bolted on. This page explains the main measures we use to protect customer and visitor data. AskBrew is a product of Xaptis Solutions LLP.

Data isolation

Every workspace's data is separated at the database layer using PostgreSQL row-level security, so one workspace can never read another's knowledge, conversations, or settings. Widget and API requests are scoped by a workspace's public key and its allowed website origins.

Encryption

• All traffic is served over HTTPS/TLS in transit.
• Data at rest is encrypted by our infrastructure providers.
• Sensitive secrets — such as integration access tokens and tool credentials — are additionally encrypted at the application layer with AES-256-GCM before being stored.
• Secrets are never returned to the browser and are decrypted only server-side at the moment they are used.

Authentication & access

• Accounts are authenticated through our identity provider (Supabase Auth).
• Optional two-factor authentication (TOTP) adds a second factor for customer accounts.
• Dashboard actions are permission-checked by workspace role; sensitive actions require admin access.
• Internal staff access is limited and audit-logged.

Verified visitor identity

When the assistant looks up a visitor's account data, that visitor's identity is cryptographically verified — either by a short-lived token your server signs, or, on Shopify, by Shopify's signed App Proxy. A lookup only ever returns data belonging to the verified visitor. Private claims used solely to authorize an action are never included in the prompts sent to the AI.

Integration & action safety

• Integration tokens are stored encrypted and requested with the minimum scopes needed (for example, read-only order and customer access on Shopify).
• Outbound calls from custom tools are restricted to HTTPS public endpoints and validated to prevent server-side request forgery.
• Inbound webhooks from providers are verified with HMAC signatures before being trusted.
• Customer messages are treated strictly as data, with guardrails against prompt-injection attempts.

Infrastructure & subprocessors

AskBrew runs on managed, industry-standard infrastructure. Our core subprocessors are Supabase (database, auth, storage), Vercel (hosting), OpenAI (answer generation and embeddings), and Paddle (billing). We rely on these providers' compliance and security programs, and request the minimum data each needs to operate.

Payments

Payments are processed by Paddle as merchant of record. AskBrew does not see or store full card details.

Reliability

Data is backed up by our infrastructure providers, and a failure in one request is contained so it does not affect others. Rate limiting protects the service against abuse and overload.

Responsible disclosure

If you believe you have found a security vulnerability, please report it privately to support@askbrew.com with enough detail to reproduce it. Please do not publicly disclose an issue until we have had a reasonable chance to address it. We appreciate good-faith research and will work with you on a fix.