What you provide
You provide the customer or client message you paste into ReplyWise. You should avoid pasting sensitive personal, financial, medical, legal, or confidential information unless you have the right to share it.
Privacy Policy
This page describes the data behavior implemented in the current ReplyWise product surface.
How messages are used
Messages are sent to the ReplyWise generation API and then to the configured OpenAI model so a recommended business move and reply can be generated. An unsaved message is not persisted as a ReplyWise workspace record.
Account and workspace data
ReplyWise stores authenticated account details, settings, workspace records, usage events, and audit records in its configured Supabase project. When you choose Save to Workspace, ReplyWise persists the original message, the recommended business move, and the generated reply as a saved workspace record. Persistent commercial memory and third-party analytics platforms are not available in the current product.
Service providers
- Supabase provides authenticated account, session, and application database services.
- Vercel hosts the ReplyWise application and executes its production routes.
- OpenAI processes generation input to return the recommended move and reply.
- Resend delivers ReplyWise authentication emails.
- ImprovMX routes messages sent to ReplyWise public support, security, privacy, and abuse addresses to the monitored operations mailbox.
Deletion and operational evidence
Saved workspace records support soft deletion: they are removed from the normal active workspace view, but ReplyWise does not offer automated permanent deletion or data export from the dashboard. ReplyWise also stores sanitized terminal generation-failure evidence for operational investigation. That evidence does not include prompts, generated replies, credentials, or tokens; it expires 30 days after it is recorded, with expired rows cleaned during later evidence writes. Other service-provider logs may exist under the applicable provider configuration.
Data governance at a glance
| Data category | Purpose and location | Persistence and deletion | Retention evidence and request channel |
|---|---|---|---|
| Unsaved generation input | Sent through ReplyWise to OpenAI to generate a response. | Not persisted as a ReplyWise workspace record unless you save the result. | ReplyWise does not state a separate application-record retention period. Ask questions through the privacy contact. |
| Saved workspace record | Original message, recommended move, and generated reply are stored in Supabase so you can reopen your work. | Persisted when you choose Save to Workspace; the current workspace supports soft deletion. | No automated export or permanent deletion is available. Use the privacy contact for requests. |
| Account, settings, usage, and audit data | Stored in Supabase to operate accounts, workspaces, security, and required audit records. | Persisted as required by the implemented feature; deletion behavior varies by record type. | No general public retention period is declared. Use the privacy contact for questions. |
| Generation-failure evidence | Sanitized operational evidence is stored in Supabase to investigate terminal generation failures. | Persisted without prompts, replies, credentials, or tokens. | Expires 30 days after recording; expired rows are cleaned during later evidence writes. Use the privacy contact for questions. |
Contact
For privacy questions, use the verified privacy contact.