Data & privacy
This page explains how ReleaseProof handles the data you provide when you prepare, run, and share a review.
You can review real lead scenarios. Remove names, phone numbers, email addresses, and anything else that directly identifies a person before uploading a case.
Project setup, test cases, criteria, and optional assistant access tokens are stored in this browser as part of the draft. Deleting the account from History clears that draft in the browser where you confirm the deletion. Tokens are never written to the database. When a test endpoint is called, the relevant token is sent through the ReleaseProof server for that request.
After you run an evaluation, the project, responses, criteria, and results are stored in Supabase. Vercel hosts the app. The data stays until you delete the evaluation, project, or account from History. Only the workspace owner can read it. Your email address is used only to send one-time sign-in links.
A report becomes available by link only after you publish it. The link does not expire. Anyone who opens it can read the customer inputs and both replies until you unpublish the report.
When replies are generated from version instructions, each customer input and the relevant instructions are sent to the OpenAI API with storage disabled. For semantic criteria, the customer input, both replies, and criterion text are sent to the OpenAI API with storage disabled. If you set an assistant endpoint, the customer input and optional access token are sent through the ReleaseProof server to that endpoint. ReleaseProof does not use this content to train a model and does not save assistant access tokens to the database. The OpenAI key stays on the server.
Enterprise data-processing agreements, regional hosting selection, and automatic deletion schedules are not included. You can remove saved evaluations, projects, and account data from History.