Before you write
- Check status.reflections.ai for a current incident.
- Look up the error
codein Errors, or the decision’sreasons[].codein Reason codes. - For a sandbox problem, reproduce it with a supported endpoint and fictional inputs. For live reads, send request and object IDs without copying private license terms.
What to send
Request IDs help trace a report. Use fictional prompts and artifacts in the sandbox and send IDs
instead of their contents.
The documented production privacy policy remains: for a
deny or an escalation, the
prompt text is kept for 30 days for review and disputes, so there is no need to send it again,
unless the check sent prompt_handling.retention: "none". For an allow, the text was deleted once
the check was decided; the receipt keeps its digest.
What never to send
Do not send whole authorization or session tokens. The check or session ID identifies them.Rate limit increases
The proposed limits per account for a future live service are 200 checks per second, 50 generations per second, 1,000 concurrent sessions and 50 requests per second for everything else. They are not current sandbox capacity guarantees or an offer of live access. For a sandbox limit question, write with your account ID, the limit you need, your current peak, and when you expect it. See Rate limits.Decisions you disagree with
Sandbox decisions are simulated. Report an unexpected fixture result with its request ID. For future live integrations, support can explain a decision and fix an evaluation defect. It cannot change a license, widen it, or decide an escalation: those belong to the talent, their representatives, and the reviewer named on the escalation. To ask for a wider license, use thelicense_request or
license_change remedy with POST /v1/license_requests.
Security reports
Report vulnerabilities to security@reflections.ai, not to developer support. See Security.Related
Monitoring
Request IDs, alerts and the status page.
Errors
Every error code and what it means.