Last updated: 2026-09-05 · Applies to: Sovatela v1.8.4
How this was written, since you are entitled to know. By the publisher, not by a lawyer. It is written to be accurate about what the software does, and that half is checkable rather than asserted: every destination named in § 4 was confirmed by capturing the network traffic of the 1.7.3 released build — the most recent one published at the time of writing — and the code that decides each one is public. What has not had professional review is the legal characterisation in § 5 — who is a controller for what. That is said here rather than left to be discovered, because an unreviewed policy you can read beats a reviewed one you cannot.
Jacob Bergmann Larsen is the publisher of Sovatela and the data controller for the limited processing described in § 5. Sovatela is published by an individual rather than a company, and is provided free of charge.
Contact: info@anaubi.com — for privacy requests and everything else. A
postal address is available on request to that address, and to any supervisory
or enforcement authority that asks for it.
Sovatela collects nothing. It has no server, no account system, no telemetry, no analytics, and no crash reporting. The publisher receives no data from the application — not usage statistics, not error reports, not your messages.
Your data goes to two places: your own device, and the AI providers you choose to connect, using your own accounts with them.
All on your device, in your operating system's application-data folder or a folder you nominate:
| Data | Where | Removable by |
|---|---|---|
| Conversations and attachments | conversations/ in your data folder, or a folder you choose |
Settings → Privacy & data; or delete the folder |
| Remembered facts, projects | Your data folder | Settings → Privacy & data |
| Preferences and provider configuration | settings.json |
Delete the folder |
| Local usage and cost estimates | usage.json |
Settings → Usage & cost → reset |
| API keys | Your OS credential store (com.anaubi.sovatela) |
Settings → Scaleway API key → Remove key from this app |
Recording of conversations can be switched off entirely, in which case no conversation text, attachment or generated image is written to disk. Other things still are: your settings, the usage and cost tally, any facts you have approved for memory, and any projects you have made. Those are listed in the table above with where each one lives and how to remove it. This sentence used to say "nothing is written", which was broader than the truth.
Full instructions: Uninstall and data deletion.
The application transmits data using your own credentials, to the providers you
configured. Three destinations are not providers, and are listed here rather
than left to be discovered: sovatela.eu when you press Check for updates,
raw.githubusercontent.com when you press Check for updated prices, and —
while web search is on — whichever public page the model decides to read. See
Security for what each one sends, which in the first two
cases is nothing about you:
| Provider | Receives | When |
|---|---|---|
| Scaleway (France) | Your Scaleway key, and nothing else — GET /models, asking whether the key still works |
Automatically, once, when the app starts. This is the connection dot in the corner |
| Scaleway (France) | Your messages, attached file text, images, and system context | Every message |
| Your search provider (Linkup / Qwant Staan / your SearXNG) | Search queries the model generates | Only when web search is on |
| Your image provider (OVHcloud / Black Forest Labs / your endpoint) | Image prompts | Only when you generate an image |
Terminal access (claude-glm) is a separate case, because what it sends is
not chosen by this app. If you set it up under Settings → Advanced, Claude Code
runs on your machine and sends your prompts and whatever repository context it
gathers through a local proxy to Scaleway. But Claude Code is an agent: it also
runs commands, installs packages, fetches web pages, and talks to any MCP
servers you have configured, and those reach hosts of their own — including
outside Europe. Sovatela neither controls nor observes that traffic. If this
matters to you, the section names a firewall profile that bounds it, and the
feature is off until you install it.
Each provider processes that data under its own terms and privacy policy, which you accept when you create an account with them. Links to each provider's policy are shown in the app where you enable that provider.
The app makes no other network connections. One is automatic by default, and it is the first row of the table: at startup the app asks your Scaleway endpoint whether your key still works, which is what the coloured dot beside the model name is reporting. It sends your key and nothing else — no message, nothing about you or your machine. Turning off the key removes it; there is no setting that suppresses it while a key is stored.
A second automatic call exists only if you switch it on. Settings ▸ About ▸ Check for a new version when Sovatela starts is off until you enable it. When enabled, the app reads the same static version file that the Check for updates button reads — no query string, nothing about you or your machine — and tells you if a newer version exists. Nothing installs itself; updating remains a download you choose.
It is there because a security fix otherwise reaches only the people who think to press a button, and because the usual remedy for that — a mailing list — would mean this project holding a database of email addresses to solve a notification problem. It holds none: there is no sign-up, no account and no list, and this call leaves nothing behind at the other end beyond an ordinary web request. The release feed is the same trade made the other way round, with your feed reader doing the asking.
Being told about a new version collects nothing. There is no mailing list and no signup, and that is a deliberate choice rather than an omission: a list of subscribers would be personal data held by the publisher, taken on to solve a notification problem for a project whose whole claim is that it holds nothing about you. Instead the subscription is at your end — a release feed your reader fetches, or GitHub's Watch → Releases only, which GitHub holds and the publisher never sees. Neither involves telling anyone here who you are, and the application itself does not fetch the feed; your reader does.
Everything else waits for you. The three non-provider destinations above are each a button you press. Nothing is reported about you or your machine, no remote resource is loaded into the interface, and there is no automatic updater — the version check is a button in Settings ▸ About, and it fetches a static file.
This paragraph is corrected. Through 1.6.0 it said that nothing happens on its own and that nothing runs in the background. The launch connection check has existed since before that was written, and Security has described it accurately since 1.5.2 while this page did not. A privacy policy that is wrong about the one automatic call is worse than one that says nothing, so it is stated here first and in the table above.
The publisher is a controller for one narrow thing:
| What | Legal basis |
|---|---|
| Direct correspondence — support, security and privacy email | Legitimate interests (Art. 6(1)(f)): answering the message you sent |
That is the whole of it. The website is not a second entry — it is hosted by GitHub Pages, and we keep no logs of it. See § 6.
The application itself is outside this. It has no server component and sends the publisher nothing, so there is no processing to have a basis for — the publisher is not a controller and not a processor of your conversations, and has no access to them.
Your relationship with Scaleway and your other providers is direct: your account, your key, their terms. The publisher is not a party to it and cannot act on your behalf there.
https://sovatela.eu — the download page and these policy pages.
The site is hosted by GitHub Pages. We run no server for it, so we keep no access logs and receive no visitor data — not your IP address, not which pages you read, not what you downloaded. There is nothing for us to hand over, because there is nothing for us to hold.
The site sets no cookies and runs no analytics. There is no tracking script, no tag manager, and no consent banner, because there is nothing to consent to.
GitHub serves the pages and the installer downloads, and processes requests — including your IP address — under GitHub's privacy statement, as it would for any site it hosts. We do not receive that data and cannot access it.
Aggregate counts are the one thing we can see: GitHub reports how many times each release file has been downloaded, and page-view totals for a public repository. Both are numbers only — no IP addresses, no identifiers, and nothing that distinguishes one visitor from another.
Under the GDPR you have rights of access, rectification, erasure, restriction, portability, and objection.
For data held by the publisher: the application sends us nothing and the
website gives us nothing, so in practice this is only the correspondence you
have sent us. Contact info@anaubi.com; we respond within one month.
For data on your device: you exercise these rights directly — the data is in files you own, and the app can delete them for you.
For data held by Scaleway or other providers: contact them. We cannot act on your behalf, as we have no relationship with your account there.
You may lodge a complaint with Datatilsynet (the Danish Data Protection Agency).
Keys are stored in the OS credential store, never in files. Generated artifacts
run sandboxed with no network or filesystem access. See
SECURITY.md, which documents what the design does not
protect against as well as what it does.
Material changes get a new "last updated" date above and a note in the release notes. Prior versions are available on request.