Skip to main content

Current controls

Encryption in transit: connections to the Pureframe AI API use HTTPS with TLS 1.2 or later. Encryption at rest: uploaded content and service data are encrypted at rest. Account isolation: authenticated requests are scoped to the account associated with the credential. API key controls: a key’s secret is shown only when you create it. Key creation and revocation require an authenticated dashboard session. Use separate keys for separate integrations and revoke a key if it may be compromised. Rate limiting: API requests are rate-limited per key. See Rate limits.

Current limitations

The public service does not currently include the following assurances: If your organization requires one of these assurances, contact us before uploading production or sensitive content. Do not assume an Enterprise agreement includes a control unless it appears in your contract.

Reporting a vulnerability

Email security@pureframe.ai with a description of the issue, its potential impact, and the steps needed to reproduce it. Do not include sensitive customer content unless the security team asks for it through an approved channel.