Tenant isolation
Every customer record carries a company or agency boundary. Signed-in access is checked in the application and by PostgreSQL row-level security. Cross-workspace foreign-key triggers and unique provider-resource assignments reject mismatched links. Raw integration credential tables are server-only and are not granted to browser roles. Privileged support access is revocable and separately recorded.
Identity and permissions
Supabase Auth provides user sessions and verified-email checks. Company and agency roles limit which workspaces and management actions a user can reach. Invitations are scoped to a company or agency. Administrators should remove departed users promptly and protect their email and connected-platform accounts with phishing-resistant multifactor authentication where available.
Connections and secrets
Provider authorization uses OAuth where supported. Access and refresh tokens are handled on the server and encrypted with AES-256-GCM using a fresh nonce and authenticated ciphertext. Encrypted values carry a key version so keys can rotate without taking every connection offline. Browser responses omit token and lease fields. Secrets are stored in restricted production environment settings.
Application safeguards
The service uses HTTPS, HSTS, a content security policy, frame blocking, content-type protections, strict referrer handling, request validation, bounded network fetches, SSRF protections, same-site redirects, HMAC checks for provider webhooks, rate and credit controls, and provider-response redaction. Public website research does not use an authenticated session and checks robots.txt before a page is read.
AI safety
Imported pages, ads, reviews, connected records, and page context are treated as untrusted evidence. They are not system instructions. Read-only questions do not expose workspace mutation tools. Requested edits become review cards and do not directly publish an ad, change a budget, edit a CRM, or modify a store. Evidence and important claims still require human review.
Operations
Growth Intelligence records support cases, AI run status, connection health, research checkpoints, and sensitive control changes. Backups and provider retention protect availability. Incident procedures cover declaration, containment, affected-tenant scoping, evidence preservation, recovery, and customer notice. Subprocessors are listed on the Subprocessor page.
Reporting a concern
Report a suspected security or privacy issue to erkan@consultdemy.com with the affected workspace, time, and observed behavior. Do not include passwords, tokens, or unnecessary personal data. We will acknowledge and prioritize credible reports.