Controls used to protect account and workspace data. These measures do not guarantee that incidents cannot occur or certify compliance with every legal or platform requirement.
Row-level policies and server-side checks restrict access to account and workspace data. Authorized team members may access their shared workspace.
Public API keys are stored as SHA-256 hashes and shown to you exactly once at creation. We can never display a key again — only revoke and reissue.
Every inbound webhook is verified with HMAC signatures — Meta for Instagram events, Cashfree for payment events. Invalid signatures are rejected fail-closed.
Instagram connect flows use the official Meta OAuth with a state parameter to prevent cross-site request forgery and authorization injection.
Authentication, supported API operations and messaging paths use rate-limit controls. Provider limits can also delay or reject requests.
Application secrets are configured server-side. Instagram access tokens are stored in a server-accessible Supabase credential table, not returned through the browser credential client. This describes access controls, not an independent encryption certification.
Account deletion is available in Settings. We also handle Meta data-deletion and deauthorization callbacks. Contact support for questions about retained records or provider backups.
Admin-level database keys live exclusively on the server. The browser client never touches them — it only ever talks to row-level-secured endpoints.
Found something we should know about? Email [email protected] and we'll take it seriously.