Privacy Policy

Last updated: 6 October 2026 · Working draft, pending owner and legal review

This draft describes the website and licensing service alongside the desktop app. Supplier configuration, retention periods and final policy wording are still under review.

Zerds is developed by Uhstray.io, LLC. Local recordings and transcripts are separate from the purchase and licence information handled by the website.

Recordings and optional integrations

Local capture, transcription and on-device AI run on your machine. If you choose a remote AI endpoint, transcript text is sent to that endpoint for processing. Discord integration also makes network connections. Review the network-call list below and the app documentation for these optional features. Recordings and transcripts are not part of the website's licensing records.

Purchase and licence information

Stripe handles checkout and sends purchase information, including the buyer's email address, to the licensing service. The service processes that address to issue and recover licence keys; it does not store the address or buyer's name in its licensing database.
The licensing database stores the licence key, Stripe purchase-session identifier, purchase date, revocation details, and a keyed email lookup value used for recovery. This lookup is pseudonymous, not anonymous.
Download permissions contain an identifier, licence reference, platform and timestamps. Payment-event and licence-email records contain identifiers and timestamps used to avoid duplicate processing and limit repeated messages.
If you use licence recovery, the submitted address is used to look up a purchase. When licence email is enabled, the delivery provider receives the recipient address and licence message. The recipient is taken from the purchase record held by Stripe.
If you email us for support, your email address and the information you include are part of that correspondence. Avoid including recordings or transcripts unless they are needed for your request.

Service providers

Stripe provides checkout and purchase records. The website and licensing service run on a DigitalOcean server behind Cloudflare, which proxies requests. Installer downloads and backups will use Cloudflare object storage once it is set up. The licence-email provider is still to be confirmed in this draft. These services process information needed to provide their functions.

Operational data and retention

The licensing service uses IP-derived rate-limit entries in memory to limit abuse; those entries are not written to its licensing database. Service logs record operational events, errors and release or backup metadata. Hosting, network and delivery providers may also keep their own operational records.

The service's hourly cleanup removes expired download permissions and payment-event processing records older than seven days. That cleanup does not erase licence records, email-delivery records or copies in backups. This draft does not yet specify retention periods for those records, support correspondence or provider and server logs.

Browser storage and measurement

The website saves your light or dark theme preference in your browser's local storage.
The site does not load advertising trackers, third-party pixels, or fonts and scripts from third-party CDNs. The site does not send analytics events to a server at launch.
These statements concern this website. Stripe's hosted checkout and optional app integrations are separate services with their own data handling.

App network calls

This is the same network-call list used in Privacy & your data and Security. It describes app features separately from website purchase and download processing.

Every network call Zerds makes. There are no others.
Call	When	Where to
Model download	The first time you use a model, then cached and run offline. Nothing of yours is sent — it is a file download, and every file is checked against a build-time checksum before it is used	huggingface.co hf-mirror.com (fallback, if huggingface.co is blocked) github.com (k2-fsa/sherpa-onnx, microsoft/onnxruntime releases) raw.githubusercontent.com (uhstray-io/zerds-public — ours) registry.ollama.ai (only for Ollama models)
Model catalogue	When you open the model list in Settings, to see which models exist and how big they are. Asks for a file listing — nothing of yours is part of the request	huggingface.co
ONNX Runtime download	First run, if the runtime is not already present. Checked against a build-time checksum before it is used	github.com (microsoft/onnxruntime releases)
Bug report / feedback form	Only when you click Report a bug or Send feedback. Opens a form in your browser — Zerds sends nothing to it, and attaches no recording, transcript or log	docs.google.com (opened in your browser, not by Zerds)
Your remote AI endpoint	Only if you configure one. Transcript text goes to the server you chose	whichever endpoint you configure — nothing by default
Discord	Only during a Discord recording you start	discord.com
Store ownership confirmation	On launch, on a Microsoft Store build. Windows confirms the licence you already own — no Zerds account, and no transcript, recording or filename is part of it	Windows licensing services — no Zerds server

Contact

Questions about privacy or the information handled by the service? Email [email protected].