Privacy
Privacy summary
What Rhetica needs to run, what stays under user control, and where to adjust data and cookie settings.
What is used
Training data
Session content is used to run the exchange, generate feedback, and apply safety checks.
- Session text is processed so the sparring round, drill feedback, and Mirror brief can work.
- Jurisdiction messaging can use request geo headers when available; raw IP storage is not required for that layer.
- Saved history should stay configurable so deployments can choose short-lived or retained transcripts.
User control
Deletion and access
Users should be able to export what is stored and remove what they no longer want kept.
- Saved sessions should be deletable in product.
- Account export or deletion should include profile data, transcripts, Mirror briefs, and scoring artifacts.
- Operational logs should stay narrow in scope and limited in retention.
For the current operating summary and public beta boundaries, see Legal.
Cookies
Cookie use and control
Rhetica keeps cookies lean. Essential cookies keep the app working; optional cookies handle convenience and lightweight measurement.
- Essential cookies support login, session continuity, and core security behaviour.
- Optional experience cookies remember interface preferences between visits.
- Optional measurement cookies are for product improvement signals, not ad targeting.