Security

ChatPPC holds no SOC 2 report, no ISO 27001 certification, and has not had a third-party penetration test. This page describes the controls that exist. It claims no badge that does not.

An independent security review of token encryption, tenant isolation and both OAuth implementations is planned before any customer other than the founder is onboarded.

All data is encrypted in transit using TLS, and encrypted at rest. Amazon refresh tokens are encrypted at rest with a separate key, decrypted only inside the request handler that needs them, and are never written to a log, returned in an API response, or exposed to a language model.

Each seller’s data is logically isolated and enforced at the database layer rather than in application code, so a mistake in application logic cannot expose one seller’s data to another. No seller’s data is ever disclosed to, or aggregated with, another seller’s.

Every change ChatPPC makes to your advertising or your listing copy is a two-step operation.

• It proposes the change, showing exactly what will change and what it will change from.
• Nothing is applied until you confirm.
• Before applying, it re-reads the live state. If anything has moved since the proposal, it stops and asks again.
• Every applied change is written to an audit log with its previous state, and can be undone.

These are guarantees in the server, not features of whichever AI assistant you use. They hold regardless of how your assistant is configured.

Authorisation happens entirely through Amazon’s own Login with Amazon flow. ChatPPC does not ask for, accept, or store Amazon sign-in credentials, and does not operate your Seller Central session on your behalf.

Access to systems holding customer data is granted on the basis of job duties only, with multi-factor authentication required on every such system. Credentials are held in a password manager, never shared between people, and rotated at least annually or immediately on any suspected exposure.

Secrets are held only in managed environment variables and are never committed to source control. Automated secret scanning runs on every change to every branch.

A written incident response procedure is in place, with defined notification timelines: within 24 hours to Amazon for any incident involving Amazon information, within 72 hours to the Information Commissioner’s Office where a personal data breach is reportable, and to any affected customer without undue delay and in any event within 48 hours.

That 48-hour commitment to customers is contractual: it is what our Data Processing Agreement undertakes, and this page will never state a looser deadline than the one we have published there.

If you believe you have found a security problem, email support@chat-ppc.ai. Please include enough detail to reproduce it. We will acknowledge your report and keep you informed while we investigate.