No — not connection logs, not activity logs, not DNS queries. Accounts are anonymous, so there is no record tying traffic to a person. This is the point rather than a marketing line: data that was never collected cannot be requested by a court, sold to a broker or lost in a breach.

That is the case it was designed for. Relane runs several protocols including WireGuard and VLESS, shapes traffic to survive deep packet inspection, and moves to a different route when one stops working. No VPN can promise permanent success against a filter that keeps changing — what it can do is keep changing back.

10 GB a month at reduced speed, on one device, with access to every server and every protocol. It renews monthly and does not turn into a paywall.

One person, low overheads, no investors expecting a return. €3 covers bandwidth and servers with enough left over to keep building. If it ever has to change, you will hear the reason.

No. Sign-up is anonymous by design — which also means there is no “reset by email” path, so keep your account key somewhere safe if you are paying.

A spread across Europe with more added as demand and blocking patterns shift. The app chooses for you by default; you can pick manually if you prefer a specific exit.

Three devices on the paid plan, one on free.

Both are in development. Android came first because it is the platform most used in the regions Relane was built for. Ask on Discord or Telegram to be told the day they land.

You drop back to the free plan. Nothing is deleted, because there was nothing stored about you in the first place.

No, and that is the entire design goal. No API keys, no model names to research, no terminal, no agent framework to wire together. It finds or installs an engine itself and picks a model your machine can run.

Not by default. The model runs on your machine. Cloud models are optional and per-task — you choose to send a specific job out, and Activity records it when you do.

A modern laptop with 16 GB of RAM runs useful local models. More memory or a discrete GPU unlocks larger ones and faster image generation. If a task would be painful on your hardware, it says so instead of crawling.

Yes, on-device. The same principle as the text side: what you make on your computer can stay on your computer.

A chatbot answers in a window. OS One works across your files, apps and accounts as a layer over the desktop, remembers your projects, runs automations on a schedule, and holds a permission boundary exactly where actions become irreversible.

The permission split. Anything that leaves the machine or destroys something waits for an explicit approval, every single time, and every step it takes is recorded in Activity.

Both, from one codebase. Linux is not committed — say so on Discord if you want it and it moves up the list.

Undecided and worth arguing about. The local-first architecture is the substantive guarantee; source availability is a separate question I would rather answer honestly later than promise loosely now.

Not set. It will not be a per-message meter, because the work happens on hardware you already paid for.

No. Retold carries first-hand material from people at the scene, not articles about it. It is meant to sit alongside professional journalism as a source of evidence, not to replace reporters and editors.

You cannot stop them entirely, and anyone claiming otherwise is selling something. What Retold does is make fabrication expensive and visible: corroboration weighting, capture metadata, duplicate detection, manipulation checks, reporter history and verified organisations.

Nobody, deliberately. There is no editorial verdict — only a description of how much independent evidence a report has. Readers judge; the platform shows its working.

Set location precision low, use an anonymous handle, and upload over a VPN. The app assumes the network is hostile rather than treating that as an edge case.

Uploads are transcribed and translated automatically, so a report filed in one language becomes watchable in another within minutes.

Yes. Pinning a report to a place permanently is about the record surviving platform churn, not about trapping reporters.

Place instead of algorithm, evidence weighting instead of engagement ranking, permanence instead of a feed that forgets by Thursday, and an upload path designed for censored networks.

It is in development. Leave your address and you will hear when the first public build lands.

Encryption protects content; it does not remove the fact that a company holds a record of every conversation that passed through it. Taking the server out of the path removes the archive itself, not merely its readability.

An encrypted relay carries it. The relay cannot read anything, and it is a fallback rather than the default. Delivery stays reliable on carrier NAT and hostile networks.

No. If you are unreachable, a short-lived encrypted blob the server cannot open waits for you, and is deleted the moment it is delivered.

A permanent @username. Looking you up does not reveal your networking details — those are shared only once you accept.

On a direct connection, yes — that is inherent to peer-to-peer, and it is exactly the kind of thing that belongs in plain sight rather than a footnote. Using the relay path avoids it at the cost of a timing-visible middle.

That is the intention. A privacy claim you cannot verify is a marketing claim, and this one will need to be checkable.

Recon is the name. It was briefly shelved over a trademark question and is back in use.

Beta list first, and it will be small. The transport layer has to be genuinely solid before more people arrive.