Security

Security at Chataut AI

Businesses run their customer conversations, websites and ad accounts on Chataut AI. We build and operate the platform to protect that data, theirs and their customers'.

Security lead

Roberto Castillo, Tech Lead

Security leadership

Security at Chataut AI has a named, accountable owner.

Security lead

Roberto Castillo

Tech Lead, Chataut Labs, Inc.

security@chatautai.com

A computer and IT engineer specializing in cybersecurity, Roberto leads security for the Chataut AI platform and is the point of contact for vulnerability reports and security incidents.

Responsibilities

  • Secure development
  • Infrastructure hardening
  • Vulnerability management
  • Incident response

How we protect your data

These are the controls in place on the platform today, described in plain terms.

Identity and access

  • Sign-in and accounts

    Sign-in is handled by Clerk, a dedicated authentication provider.

    As a result, passwords for Chataut AI accounts are never stored on our servers. Administrative functions are restricted to authorized administrators.

  • AI assistant access (MCP)

    Connecting an AI assistant to Chataut AI uses OAuth with PKCE and an explicit consent screen.

    Access tokens are short-lived, valid only for our MCP server and stored only as keyed hashes. You can revoke a connection at any time from your account settings, and organization membership is re-checked on every request. When an assistant asks to buy or renew a domain, or to create a business mailbox, the charge is made only after the user approves it inside Chataut AI.

Data protection

  • Encryption in transit

    Our website, app and API are served only over HTTPS.

    Plain HTTP requests to them are redirected to HTTPS, and our API sends HSTS. Customer websites, on chatautai.com subdomains or on their own domains, get TLS certificates automatically.

  • Encryption at rest

    Our database runs on Supabase's managed PostgreSQL, which encrypts all data at rest with AES-256.

    On top of that, the application itself encrypts certain secrets with AES-256-GCM and versioned keys, including the access tokens for the Facebook, Instagram and Meta Ads accounts connected for publishing and ad management, and business mailbox passwords.

  • Payments

    Card details are entered directly into the secure payment forms of Stripe and our other payment providers.

    Card numbers never reach our servers, and we never store them.

Infrastructure and operations

  • Hardened infrastructure

    Production servers sit behind a cloud firewall and a host firewall that open only the ports each service needs.

    Internal application and cache ports are not reachable from the internet. The web app and customer websites on chatautai.com subdomains are served through Cloudflare, and both our API and all customer websites enforce per-IP rate limits.

  • Safe releases

    New versions of our app and API reach production through our CI pipeline.

    Each version must pass health checks when it goes live; if it doesn't, the previous version is restored automatically.

  • Monitoring and incident response

    Our backend sends automatic alerts on critical errors.

    The app and API expose health checks that we verify on every release. Security incidents are handled by our security lead, from containment through remediation and follow-up.

Integrations and hosted websites

  • Verified webhooks

    Webhooks from Stripe, our other payment providers and Clerk are verified by their cryptographic signature.

    If the signature can't be verified, the request is rejected before we process it.

  • Secure hosted websites

    Websites hosted by Chataut AI, on chatautai.com subdomains or on customers' own domains, are stored as structured content blocks validated against a strict schema.

    AI fills in the content but never writes the HTML or code we serve: all text is escaped when the page is rendered, and pages are served with a strict Content-Security-Policy that allows only the scripts our renderer generates.

Vulnerability disclosure policy

We welcome reports from security researchers and anyone who finds a potential vulnerability in Chataut AI. If you act in good faith and follow this policy, we will work with you to understand and resolve the issue quickly.

How to report

Email security@chatautai.com, in English or Spanish. Please include:

  • A description of the vulnerability and its potential impact.
  • The affected URL, endpoint or component.
  • Steps to reproduce it, with a proof of concept if you have one.
  • The accounts, identifiers or test data you used.
  • How we can reach you, and whether you would like public credit.

If you'd rather share details over an encrypted channel, email us first without the technical details and we'll arrange one.

Our commitments

  • Acknowledge your report

    We reply within 3 business days to confirm we received your report.

  • Keep you informed

    We share our assessment and keep you updated until the issue is resolved.

  • Fix by severity

    We prioritize each fix by severity and real-world impact, and tell you when it is deployed.

  • Give credit

    With your permission, we will publicly acknowledge your contribution once the issue is fixed.

  • Protect your identity

    We won't share your name or contact details outside Chataut Labs without your permission, unless the law requires it.

Scope

In scope

  • chatautai.com, www.chatautai.com

    Public website

  • ecommerce.chatautai.com

    Chataut AI web application

  • api.chatautai.com

    Platform API

  • Customer sites on *.chatautai.com

    Only the Chataut AI platform that serves them (routing, TLS and page rendering)

Out of scope

  • Denial-of-service attacks or volumetric and load testing.
  • Social engineering or phishing against our team or our customers.
  • Physical attacks against offices, devices or data centers.
  • Third-party services we use, such as Stripe, Meta or Clerk. Report those directly to the vendor.
  • Email hosting at mail., webmail., cpanel. and autodiscover.chatautai.com, which is operated by our hosting provider.
  • Content published by our customers, and their custom domains.
  • Automated scanner output without a working proof of concept.
  • Missing best-practice headers or settings without demonstrated impact.
  • Spam, or testing that sends unsolicited messages to our users or their customers (for example, through WhatsApp, Instagram, Messenger or email).

Not sure whether something is in scope? Ask us before you test it.

Rules of engagement

  • Test only against accounts you own or have explicit permission to use.
  • Don't modify or delete data that isn't yours. If you gain access to another user's data, access only the minimum needed to prove the issue, stop, and report it to us right away; don't keep copies of it.
  • Stop as soon as you have confirmed a vulnerability, and report it to us.
  • Don't exfiltrate data, maintain persistent access or pivot to other systems.
  • Don't degrade the service for other users.
  • Keep the details confidential until the issue is fixed or 90 days have passed since your report, whichever comes first, and coordinate the disclosure date with us.

Safe harbor

We consider security research conducted in good faith and in accordance with this policy to be authorized, and we will not initiate or support legal action against you for it, including for accidental, good-faith violations of this policy. We waive, on a limited basis, the restrictions in our Terms of Service (including the Acceptable Use Policy) that would otherwise prevent such research. This authorization covers only the systems listed as in scope: we cannot authorize testing of third-party systems or services, and you remain responsible for complying with all applicable laws. If a third party takes legal action against you for activities that complied with this policy, we will take reasonable steps to make it known that you acted in compliance with this policy. If in doubt, contact us before going further.

Recognition

We don't currently run a paid bug bounty program. With your permission, we will publicly acknowledge researchers who report valid vulnerabilities to us.

Questions about security?

Send security reports and questions to this address, in English or Spanish.