Privacy.
Roqer has no account and no server. Your place, your chats, and your keys stay on your computer, and a model turn goes from your machine straight to the provider you chose.
The app
Chats, diffs, evidence, run history, and settings are kept on your computer only. Roqer never uploads your place, and nothing the agent reads or writes is sent to Roqer.
A model turn can include your prompt, relevant conversation and script source, tool results, and selected screenshots or attachments. With a ChatGPT or Claude subscription, the Codex app or Claude Code sends it under the account you signed into there; Roqer does not receive or store your provider credential. With your own endpoint, Roqer sends it from your machine to the address you entered. An API key is encrypted with your operating system's credential protection and stored only on your computer; it is never sent to Roqer. In every case, that provider's terms and data controls apply.
If you add a Roblox Open Cloud key so Roqer can publish assets to your Roblox account, it is kept the same way and never sent to Roqer. A file goes to Roblox only when you approve an upload of it, or run in Full auto.
Roqer checks the project’s GitHub releases for updates, so GitHub receives that request. Unless you turn it off under Settings → App, your Discord profile shows that Roqer is open and whether it is busy — never your place, scripts, or tasks.
This website
This site runs no analytics scripts or advertising trackers, and sets no cookie unless you sign in to an account from an earlier release. The showcase videos on the home page are YouTube embeds, and YouTube’s own privacy policy applies to them.
Accounts from earlier releases
Roqer releases before 0.1 signed in to a Roqer account. That service still runs for those releases. Prompts, conversation text, script source, place structure, tool arguments and results, screenshots, evidence, and model responses are not written to Roqer storage after a request finishes or is cancelled. What it keeps:
| Data | Examples | Kept |
|---|---|---|
| Action usage | The desktop's run and action identifiers and the time of each action, used to apply a plan's action limit. Never the tool, its arguments, or its result | 13 months |
| Hosted per-turn usage | Identifiers, model and effort, token counts, cost, timing, outcome | 13 months |
| Account state | Verified email, plan, allowance, standing | While active; erased or de-identified within 30 days of deletion |
| Authentication and security | Sign-in outcome and keyed device or network hashes | 90 days |
| Diagnostics | Request identifier, service stage, bounded error code, timing | 30 days; never customer content |
On a legacy plan that still includes hosted models, Roqer's service sends prompts, relevant conversation and script source, tool results, and selected screenshots or attachments to a third-party inference provider and its downstream model processors. See the processor list and retention disclosures.
Roqer does not use your content to train or fine-tune models, and does not sell it.
To delete an account, email support@roqer.dev from the account's address. Once the request is verified and accepted, sessions are revoked and account data is erased or de-identified within 30 days. Active runs must finish or be stopped first. Records required for documented billing or security purposes may be retained with restricted access. Backups age out within 35 days. Do not email scripts, screenshots, or credentials.