Security
Built so a mistake can’t become a disaster.
What protects your account, in plain terms. Everything here describes how the service works today.
Sign-in without passwords
You approve access on Amazon’s own sign-in page (Login with Amazon). The connector receives a token, never your password. Only the advertising scope is requested. Amazon requires you to approve again every 365 days; if you don’t, access stops automatically.
Short-lived, rotating tokens
Your assistant signs in to the connector with OAuth 2.1 and PKCE. Access tokens last one hour. Refresh tokens change on every use; if a replaced one turns up again after a short retry window, the whole session is revoked. The connector stores only one-way hashes of these tokens.
Encrypted and isolated
All traffic uses TLS. Amazon tokens are encrypted at rest with authenticated encryption. Each advertiser’s data is separated by row-level security enforced in the database itself, so one account’s data can’t be read in another account’s session.
Limits on every change
Changes are planned first and checked on the server: maximum size per change, allowed bid and budget ranges per currency, and a cap on items per change. Plans expire after 15 minutes and run only after you confirm.
No blind overwrites
Before writing, each value is re-read from Amazon; if it changed since the plan, that item is skipped. Only one change per item can be in flight at a time. After writing, the value is read back to confirm Amazon accepted it.
Logged, and stoppable
Every planned and applied change is recorded with before and after values and the result. Writes can be switched off instantly for one account or for everyone, while reading keeps working. Requests to Amazon identify themselves as an automated agent.
Data
Where it lives, and when it goes.
- Application
- Render (United States)
- Database
- Neon (managed Postgres)
- Website, DNS
- Cloudflare
- Kept
- While you are connected or a client
- Deleted
- Within 30 days of your request, or within 72 hours of a request from Amazon
Full details are in the privacy notice.
Incidents
If something goes wrong.
Security incidents involving Amazon data are reported to Amazon within 24 hours, as Amazon’s data protection policy requires, and to affected clients as the law requires. Writes can be switched off for everyone while an incident is investigated.
To report a vulnerability, email hello@samiullah.app. Please don’t test against accounts that aren’t yours. This site also publishes a security.txt.
What it doesn’t have
Said plainly.
PPC Connector is run by one person. It has no SOC 2 or ISO 27001 certification and has not had an independent security audit. It is in an invite-only pilot, and it has not yet been used with live Amazon data: that waits for Amazon’s approval of its API access.
If any of this matters for your business, ask me before you connect, and I’ll answer in writing.