Privacy Policy

Last updated: May 22, 2026

1. Who we are

ClaurixTerm is built and published by SRG DOOEL (Skopje, North Macedonia), the data controller for the limited information described below. Throughout this policy, "Claurix," "we," "our," and "us" refer to SRG DOOEL.

2. What we hold centrally

Almost nothing. ClaurixTerm has no account system, no sign-in, and no central database. We don't know who downloaded the app, what hosts you connect to, what commands you run, or what you ask the AI agents.

The only thing that touches our servers is the auto-update check: the app fetches https://claurix.com/latest.json over HTTPS to learn whether a newer version exists. Like any HTTPS request, this leaves a standard nginx access-log entry (IP + user-agent + timestamp) on the server hosting claurix.com. Logs rotate within 30 days and are not joined with any other dataset.

3. What stays on your device

• SSH host configurations — hostnames, ports, usernames, and (encrypted) passwords or private keys.
• Command history — encrypted at rest in the app's local store.
• AI provider API keys (Claude Code, Codex, Gemini) — stored locally in the OS keychain or encrypted storage.
• App preferences — theme, groups, snippets, the last active agent.

None of this is uploaded anywhere by ClaurixTerm. Uninstalling the app removes it; clearing the local app-data directory is also enough.

4. What leaves your device (and to whom)

When you send a prompt to one of the built-in AI agents, the prompt and the relevant context are sent directly to that provider's API using your own API key. SRG DOOEL is not a processor for that request — it's a request from your machine to theirs. Each provider handles your data under their own terms:

• Anthropic (Claude Code) — anthropic.com/legal/privacy
• OpenAI (Codex) — openai.com/policies/privacy-policy
• Google (Gemini) — policies.google.com/privacy

SSH traffic to your hosts also leaves your device — but only to the hosts you've configured, encrypted by SSH itself. Nothing about that traffic is observable to SRG DOOEL.

5. Cookies and trackers on claurix.com

The website you're reading does not set cookies, does not run analytics, does not embed third-party trackers, and does not load fonts from anywhere other than Google Fonts (used purely for rendering, no user-identifying cookies). Cloudflare sits in front of the site as a CDN and may set a security cookie (__cf_bm) for bot-protection purposes.

6. Your rights

Because we don't hold a profile on you, most data-subject requests have a one-line answer: "we have nothing to access, correct, port or delete." You always retain the right to:

• Ask what (if anything) we hold tied to your identity
• Request erasure of any nginx access-log entries associated with an IP you control
• Lodge a complaint with the Macedonian data-protection authority (or your local equivalent)

For requests that concern data held by Anthropic, OpenAI or Google about your AI usage, you must contact those providers directly — we can't act on their behalf.

7. Children

ClaurixTerm is a developer tool not directed at children under 13. We don't knowingly collect any data from children. If you believe a child has provided personal information through any of our channels (e.g. email), contact us and we will erase it.

8. Changes

We'll post any updates to this policy on this page and bump the "Last updated" date. Material changes to how data is handled will additionally be noted in the next ClaurixTerm release notes.

9. Contact