Security
A summary of the controls this platform actually implements, each one something you could verify by reading the code rather than a claim you have to take on faith.
Tenant isolation
Every tenant's data is isolated from every other tenant's by database-enforced access rules, so one account can never read another's lists.
Credential material is unreachable, not just protected
Signing keys, usage records and the audit log are stored apart from your list data and are not reachable through any public API.
No public data API
No application table is exposed through an automatic public API. Autocomplete reads only your published list.
Publishable vs. secret credentials
A publishable key is not a secret — it ships in your client bundle and is assumed observable. It carries scope (owner, list, version, origin allow-list, billing identity), never write access. A secret key, where one exists, never leaves the server side.
Origin allow-lists
Every publishable key carries an origin allow-list, checked by exact match against the browser's own Origin header. This is a filter, not the authorization boundary — quota and rate limits still apply to every request regardless of origin.
Usage limits are enforced on every request
Every request is authorized and checked against your plan's usage allowance before it is served, so limits cannot be bypassed by repeating a request.
Published artifacts are immutable
A publish produces a new, immutable version. A client never sees data mixed from two versions, and activation only happens once the new version has verified.
Key revocation reaches the edge directly
Revoking or disabling a publishable key rewrites its edge record synchronously as part of the action you took — not on a delayed sweep — so a revoked key stops resolving on its very next request.
What this page does not claim
No compliance certification, no completed penetration test, and no uptime guarantee is claimed here, because none of those exists yet for this product. Per-IP rate limiting is an open item rather than a shipped control — this page describes what is built, not a roadmap dressed up as a feature.
Report a vulnerability
Found a way tenant isolation, a credential or quota enforcement could be broken? Email support@autosugges.com with what you found and how to reproduce it. Reports are read and acted on directly — there is no bug-bounty program or dedicated security team, only the person who builds this.