01Your data stays local
Reges is built so that the things you show it and tell it are processed on your own computer. There is no Reges cloud service that receives your camera, microphone, files or conversations.
- Camera. Face recognition and hand tracking run on your PC. Frames go to your local vision model only when you ask what Reges sees.
- Microphone. Wake word and speech-to-text (Whisper) run locally; replies are spoken by a local voice.
- Thinking. The language model runs in LM Studio, Ollama, llama.cpp or another OpenAI-compatible server that you run.
- Memory. Facts, notes, tasks and the diary are files on your disk.
Reges uses the internet only for what you ask for: downloading Reges and models, updates, web research, the connectors you enable, and a cloud model if you choose to point Reges at one.
02Threat model
The threats we design against, and what Reges does about each.
| Threat | Mitigation |
|---|---|
| Another device on your network tries to drive the agent | The server binds to 127.0.0.1 by default. Requests from anywhere else need a session (the owner’s master password) or an API token. |
| A website you visit calls Reges’ local API | Cross-site requests are refused (Origin and Sec-Fetch-Site checks), and CORS only answers local or explicitly allowed origins. |
| DNS rebinding | Requests with an unknown Host header are refused before they reach any route. |
| Password guessing on a network install | Eight wrong passwords from one address lock it out for five minutes. |
| A document, email or web page tells the agent to send, pay or delete | Those actions are marked “confirm” and the server refuses them unless the operator explicitly approved that exact action. |
| A pasted API key or password ends up in memory | Everything the learning loop stores passes the secret scrubber first; credentials are redacted or the fact is dropped. |
| Someone else sits down at your desk | Lockdown: no actions until the owner’s face is verified or the master password is entered. |
| An integration token leaks | API tokens are created on the machine itself, shown once, stored only as a SHA-256 hash, and can be disabled. |
Out of scope: an attacker who already controls your operating system account, malware on your PC, and the security of third-party services you connect. Keep your system updated and use full-disk encryption.
03The confirm gate
Every action Reges can take carries a risk level: read (no side effects), write (changes Reges’ own local data) or confirm (leaves the machine or cannot be undone: sending email, posting, paying, calling, deleting, deploying).
A confirm action is refused unless the request carries an explicit confirmation. The agent may only add it after you approved that exact action in the conversation, never because a document, email or web page told it to. Connectors follow the same rule for publishing, messaging, moderating and deleting.
04Secret scrubbing
A hard filter, not a prompt instruction, removes anything credential-shaped before it is stored: API keys and tokens (OpenAI, Anthropic, GitHub, GitLab, Slack, Google, Stripe, Hugging Face, npm, SendGrid, Telegram, Discord), JWTs, AWS access keys, chat webhooks, private keys, payment-card numbers (Luhn-checked), passwords inside URLs, Bearer/Basic headers and “my password is …” sentences.
Each hit becomes [REDACTED:type]. The scrubber’s report lists types and counts only, never the secret. The developer connectors follow the same rule: a detected secret is reported by type and location, never by value.
05Loopback-only APIs
By default the Reges server listens on 127.0.0.1. A request counts as local only if it arrives on the loopback socket, with a loopback Host header and no proxy headers. Local requests from the owner’s own machine need no login.
A Reges for Business install that serves several people binds to the office network. Then every remote user signs in with the owner’s master password (an HttpOnly, SameSite=Strict session cookie that expires after 12 hours) or uses an API token, and only host names you list are accepted.
The master password is stored as a salted scrypt hash.
06This website
regescore.pro sets no cookies and loads no third-party scripts. It uses Umami, a self-hosted, cookieless analytics tool that runs on our own server, with no cookies, no personal data collected and no third party involved. Every response carries a strict Content Security Policy, HSTS, and headers that deny framing, sniffing and access to your camera, microphone and location. Fonts are self-hosted.
The contact and early-access forms store only what you type, on our own server. See the Privacy Policy and the Cookie Policy.
07Responsible disclosure
If you believe you have found a security issue in Reges or on regescore.pro, please tell us privately first. Write to info@likeakinginc.com or use the contact form with the topic “Security report”.
Please include
- What you found and where (version, URL or component).
- Steps to reproduce, and what an attacker could achieve.
- How we can reach you, and whether you would like to be credited.
We ask that you
- Give us a reasonable time to fix the issue before you disclose it publicly. We suggest 90 days and will agree a date with you.
- Do not access, change or delete data that is not yours, and stop as soon as you have shown the issue.
- Do not run denial-of-service tests, spam our forms, or use social engineering.
We will
- Acknowledge your report and keep you informed while we work on it.
- Credit you when the fix ships, if you want us to.
- Not pursue legal action against good-faith research that follows this policy.
We do not currently run a paid bug bounty. A machine-readable contact is published at /.well-known/security.txt.
Last updated 2026-09-26