Trust
Security boundaries you can explain to a client
Scoutate is built as a multi-tenant research platform: authorization is server-side, PostgreSQL is the system of record, and the Chrome extension stays narrowly scoped.
Tenant isolation
Workspaces are the tenant boundary. Clients and Projects nest inside a workspace. Membership and project ACLs are checked on the server — knowing a UUID is never enough.
Extension safety
- Manifest V3 with least-privilege host access focused on Amazon research flows.
- Extension sessions are revocable and isolated from Google credentials.
- Page JavaScript on Amazon does not receive Scoutate authentication tokens.
Operational controls
- Centralized rate limiting and audit logging for sensitive actions.
- Origin checks on cookie-authenticated browser mutations.
- Sheets sync is an integration output; research history remains in PostgreSQL.
Recommended: a Scoutate-only Google account
Many teams connect a dedicated Google account used only for Scoutate research spreadsheets, instead of a primary personal or company Google account. This is optional, but often preferred when you want Integrations access limited to Sheets created for research. See Privacy for how Google access fits with Scoutate’s data model.