Encrypted HTTPS traffic for public application and API endpoints.
Security at ReadPrompt
Designed to keep control
close to your team.
Security is part of the prompt lifecycle: who can change a prompt, what runs in production, how keys are handled, and what information is retained.
Current controls
Practical controls for real production workflows.
ReadPrompt is built around organization boundaries, least-exposure defaults, and clear operational visibility. We will continue to add controls as the platform and its customers grow.
Organization-scoped access control and role-based workspace permissions.
Execution API keys are stored as non-reversible hashes and can be revoked or given an expiry.
Provider credentials are encrypted at rest and are not returned through the management API.
Execution input and output payload retention is disabled by default; operational metadata is retained for reliability and troubleshooting.
Audit and execution logs provide visibility into workspace changes, routing decisions, and request outcomes.
Beta transparency
What we are still building.
ReadPrompt is in an early, founder-led beta. We do not currently claim SOC 2 certification, enterprise SLAs, or SSO. If your team has a security questionnaire, data-handling requirement, or architecture review, contact us before onboarding and we will discuss the fit directly.
Security questions
Need a closer look
at the architecture?
We are happy to discuss your data flow, access model, and requirements before a pilot or production rollout.