Privacy
Most privacy policies are long because the company collects a lot. This one is short.
What this website collects: your email address, but only if you type it into a form. If the form was a pilot sign-up, we also record one word (pilot) so we know which list you asked to be on. That is the whole list — no IP, no browser details, no referrer, no third-party analytics.
What the Urda device collects and sends us: nothing. There is no channel from your Base to us. There is nothing to opt out of.
The website
This page and the home page load no external resources — no fonts, no analytics, no tag managers, no third-party scripts. Nothing on this site reports your visit to anyone. You can verify that by viewing the source.
Our host records standard server logs (IP address, timestamp, requested URL) as any web server does. We do not build profiles from them and we do not connect them to your email.
The waitlist
If you submit the form, we store:
- your email address
- the time you submitted it
- which list you asked for — one word, either
waitlistorpilot
To stop the form being abused we also keep a one-way hash of the submitting IP address for a short window, and it deletes itself automatically. We never store the address itself.
We use the email to write to you when the product is real — a working device, a date, a price. We do not sell it, rent it, or hand it to an advertising network. Ask us to delete it and we will, without asking why.
The product
Urda is built so that this section can stay this short.
Recordings, transcripts and everything derived from them stay on hardware you own. Transcription and summarisation run on your Base. There is no account, no sync, and no telemetry. The software refuses to start if its inference endpoints point anywhere outside your own network — that is a check in the code, not a policy we ask you to trust.
The practical consequence, stated plainly: if your Base is lost or its drive fails, that memory is gone. We cannot recover it, because we never had it.
Remote access
By default, your Base answers only on your own network. Nothing crosses the internet, and the sentence on our home page is meant literally.
If you switch on remote access — so you can ask a question while away from home — your Base and your phone talk through an encrypted tunnel (WireGuard, via Tailscale or a Headscale server you run yourself). That traffic does cross the internet. It is encrypted end to end between two devices you own; we cannot read it, and neither can the service that helps them find each other. But we would rather state this plainly than let you assume otherwise.
Remote access is off until you turn it on. Leave it off and the literal version stays true.
Software updates
A box that can never be patched is a box with permanent security holes, so Urda can fetch updates. This is the second place where the wire is not cut, and it deserves the same plain statement as remote access.
Nothing is automatic. No timer, no daemon, no phone-home on boot. The Base checks for an update only when a person runs urda-update check. Left alone, it never contacts us at all.
When you do run it, the request is a single plain GET for a version file. It carries no machine identifier, no serial number, no usage counts, no telemetry — and none of your recordings, transcripts, or questions. We cannot tell one box from another, or one box from a stranger reading the same file in a browser.
Every release is signed with a key we hold offline. The updater refuses to install anything whose signature does not verify, and refuses to run at all if the signature library is missing rather than quietly skipping the check. If you would rather your Base never reach the internet for any reason, download the release on another machine and install it from a file: urda-update apply ./urda-1.0.0.tar.gz. That path is fully supported, not a fallback.
The direction matters. Updates are code coming in. Your recordings never go out.
Recording other people
Urda records audio, and the law on recording conversations differs by country and by state — in some places every participant must consent. Following those rules where you live is your responsibility. We build the restraint we can into the hardware: Stone has a physical switch that cuts power to the microphone, so that turning it off does not depend on trusting our software.
Children
Urda is not intended for anyone under 16, and we do not knowingly collect email addresses from them.
Changes
If this policy ever changes in a way that gives us more of your data, we will say so directly on this page rather than quietly editing it.
Contact
Questions, or a deletion request: privacy@urda.ai
This is a plain-language summary of our actual practices, not a legal document reviewed by counsel. It will be replaced with a reviewed version before the product ships.