Privacy information
This page explains what the StealthRL Demo processes when you submit text to the research preview.
Who runs this demo
The StealthRL Demo is operated by Suraj Ranganath and Atharv Ramesh for research demonstration and evaluation purposes.
What data is processed
- Submitted text. The text you paste is sent to the demo backend so a paraphrase can be generated and returned to your browser.
- Generated output. The paraphrased output and lightweight text-shape metrics are produced for the current request.
- Quota metadata. The service stores daily usage counters in SQLite. Public quota subjects and API-key subjects are hashed before storage.
- Optional feedback. If you click thumbs up or thumbs down, the service stores the request identifier, rating, hashed client identifier, optional API-key label, and timestamp.
- Connection metadata. Hosting, reverse proxy, tunnel, or server logs may process technical metadata such as IP address, user agent, timestamp, and request path.
- Optional API key. If you enter an API key in the browser, the browser stores it in local storage so you do not need to retype it. The server receives it only with requests you submit.
What is not intentionally stored
The demo application does not intentionally persist submitted source text, generated paraphrases, or per-request model outputs in its quota and feedback database. Do not submit private, sensitive, confidential, or regulated text, because request content may still pass through infrastructure logs or external inference services depending on deployment.
External inference services
The public preview may run in a no-cost mock backend or in a real StealthRL inference backend. If a deployment is configured to call Tinker or another model service, the text you submit is transmitted to that service for generation under that provider's terms and privacy practices.
How the data is used
- To return a paraphrased output for the text you submit.
- To enforce the public daily quota and any API-key quota.
- To understand whether demo outputs are useful through optional thumbs feedback.
- To monitor, debug, secure, and improve the research demo.
Retention
Quota counters and optional feedback events may remain in the configured SQLite usage database until the operator deletes or rotates that database. Browser local storage remains on your device until you clear it. Infrastructure logs, if present, follow the retention policies of the deployment environment.
Your choices
- Do not use the demo for sensitive or private text.
- Clear your browser storage if you want to remove a saved API key.
- Use an API key only if one has been issued to you by the operators.
Contact
For privacy or demo-operation questions, contact the project maintainers through the public project links on the demo page.
Changes
This page may be updated as the demo deployment changes. The version shown here applies to your current visit.