Console
Documentation/Security, access and retention

Security, access and retention

Protect credentials and customer conversation data.

Access boundaries

Customer organizations are isolated. API keys restrict access by project, capability and optionally number. Agency staff receive explicit client-organization membership. A supplied resource ID never bypasses these checks.

Keep Meta access tokens server-side and encrypted. API keys are stored as hashes; display them only at creation. Rotate compromised credentials, revoke old ones and inspect audit events.

Message retention

Content and media are retained for 90 days by default, with shorter organization settings. The same limits apply to imported history. Export and deletion requests are scoped to the authorized organization. Operational metadata and required financial records may have separate documented policies.

Webhook safety

Verify Meta's raw-body signature before accepting its payload. Verify customer webhook signatures before processing forwarded events. Outbound endpoints must not resolve to private, loopback or metadata-service addresses. Redirects must not bypass these checks.

Logs and support

Do not log tokens, message bodies or raw credentials in routine service logs. Support should use request IDs, connection states and redacted error details. Access to customer content for support must be explicit and audited.

Your agent

Your harness controls model providers, tool access and data transfer. Treat incoming messages as untrusted input and document any external processors used by your application. Sqkii does not train a hosted agent on customer messages.

Privacy and data-protection questions: [email protected].

Export and deletion

GET /api/v1/export returns JSON for the authorized organization's content and operational resources, including conversation notes and media metadata. It requires organization write access plus the read scopes for the included resources. The JSON export is not a ZIP archive of attachment bytes: download each available media item through its authenticated download endpoint before deleting the source. Download URLs expire after five minutes.

Conversation-content deletion removes messages, notes and media metadata, redacts event payloads and cancels related queued work. Object deletion runs through the durable worker. The Meta account-deletion status remains pending while its object cleanup is incomplete. Backups follow the deployment's separate expiry and restore procedures; restore operators must reapply recorded deletions before reopening access.

OAuth grants

Remote MCP OAuth tokens bind the approved scopes to the selected organization. Requests recheck current organization membership and role, so a removed member loses access and a role downgrade reduces the effective grant. Access tokens have a fifteen-minute lifetime. API keys remain independently revocable.

Prepared 18 November 2026 · Sqkii Pte. Ltd.