| 01 | No secrets in the shipped front-end | Page source and JavaScript bundles hold no private keys or tokens. Publishable IDs are told apart from real secrets. | P |
| 02 | Row-level security is on and strict | On Supabase or Postgres, every exposed table has row-level security enabled, with policies that limit users to their own rows. Confirmed by reviewing policies and grants. | S |
| 03 | Users can't reach each other's data | One test account can't view another's records, in the interface or through the API. Checked both ways with two accounts. | O |
| 04 | Users can't change each other's records | One test account can't edit or delete records owned by another, even through direct API requests. | O |
| 05 | Authorisation enforced on the server | Sensitive actions are checked on the server, not just hidden in React components. Confirmed by reviewing the API code. | S |
| 06 | Private uploads stay private | Private files can't be opened by signed-out visitors or other users. Storage policies reviewed, then checked against your own test files. | S |
| 07 | Users can't set protected fields | Requests that add fields such as role or price are rejected or ignored. Tested with your own test accounts, ideally on staging. | O |
| 08 | Admin routes are protected | Admin pages and admin API calls refuse signed-out visitors and ordinary test accounts. | O |
| 09 | Logging out ends API access | Once a test account logs out, its old session can no longer call protected APIs. | O |
| 10 | Costly actions are rate limited | Sign-in, password reset, email sending and paid API calls are rate limited. Checked at low, agreed volumes, never as a load test. | O |
| 11 | Handlers really write data | API handlers save what they claim to save and report failures, instead of always returning success. Traced from handler to database. | S |
| 12 | Contact submissions arrive | A controlled test enquiry is saved and reaches the right inbox. You confirm what arrived on your side. | O |
| 13 | Critical handoffs are actually wired | Key workflows complete end to end with test data: lead → record → email → admin, and payment → access. | O |
| 14 | Failed payments don't grant access | Declined, failed or cancelled payments don't unlock paid features. Tested in your payment provider's sandbox. | O |
| 15 | Webhook signatures verified | Payment webhooks reject events without a valid provider signature. Confirmed by reviewing the webhook handler. | S |
| 16 | Privacy policy covers visible third parties | Third-party services and tracking seen on your public pages are named in your privacy policy. Server-side processing isn't visible publicly; confirming it needs your processor list or configuration access. What the policy must cover depends on your data use and jurisdiction; this isn't a legal review. | P |
| 17 | Account deletion and export work | Where your product offers deletion or export, or local law requires it, a test account's data is removed or supplied as described. Full removal is confirmed only with configuration access. | O |
| 18 | Crawlers see real content | The first HTML response contains real headings, text and links, not an empty app shell. | P |
| 19 | Nothing clipped or scrolling sideways on phones | Pages fit narrow screens with no sideways scrolling or cut-off content. Checked with screenshots at several widths. | P |
| 20 | Core journeys work from the keyboard | Public journeys can be completed with Tab, Shift+Tab, Enter and Space, with visible focus. Signed-in journeys need test accounts. | P |