How we protect your data.

Infrastructure

• The website and dashboards run on Vercel. The assistant, the search service and the Agentic Intent Exchange run on AWS, with data stores in the United States.
• All traffic uses HTTPS (TLS). Data at rest is encrypted with provider-managed keys.
• Production access is limited to named accounts with multi-factor authentication. Secrets live in the hosting providers' encrypted configuration, never in source code.

Agentic Intent Exchange

• A handoff carries a structured shopping brief, never the conversation. Names, contact details, account and device identifiers are stripped before anything leaves, and each destination sees its own pseudonym for the task.
• Health and other sensitive topics are suppressed and not stored. Shoppers in the EEA, the UK and Switzerland are shared only after they click a store link under a one-line notice.
• Receipts are signed (ES256) with keys held in AWS Key Management Service; private keys never leave the service. Receivers verify the issuer, integrity, recipient binding and expiry before their agent reads the brief.
• Each receiving organisation gets its own derived secret for webhook signatures and acknowledgments. API keys are shown once and stored hashed.
• Intents expire within a day of their task and are deleted on a fixed schedule; receipts are deleted after their retention window. Publishers can delete a shopper's session on request through the API.
• Receivers get intent only for domains they have verified, and paid delivery runs only inside a campaign they started.

Customer data

• Publisher and retailer accounts are managed through Clerk, with organisation roles. Payments and payouts are processed by Stripe; Brambles never stores card numbers.
• A Data Processing Addendum is available for enterprise customers on request.
• If we become aware of a security incident affecting your data, we notify affected customers without undue delay.

Reporting a vulnerability

Email hello@brambles.ai with the affected URL or endpoint, steps to reproduce and your contact details. We acknowledge reports within three business days, keep you informed while we fix the issue, and credit researchers who report responsibly. Please don't access other people's data, degrade the service, or publish details before we have fixed the issue. Our machine-readable contact is at /.well-known/security.txt.