Privacy Policy

Last updated: September 15, 2026

1. This website

This site sets no cookies, runs no analytics or advertising trackers, and loads no third-party resources in your browser. Vercel hosts the site and may process short-lived request/security logs such as IP address, user agent, and request path under its service terms. If you email us, we receive the information you include in that message.

Downloading the app. The download requires no account, name, email address, or marketing consent. Mityu does not offer or store a product-update signup because an email-ownership verification flow has not yet been approved and deployed. We keep only an aggregate download counter. To limit automated abuse, the endpoint derives a keyed HMAC token from the request IP address using a server-only secret and keeps only a request counter under that token. The token expires no later than 15 minutes after the first request; later requests do not extend the window. The KV rate-limit record contains neither the IP address nor the HMAC secret, and the endpoint does not store the user agent, referrer, meeting content, audio, or contact details.

2. The app: local-first by design

• Recording & transcription run entirely on your device by default, using local Whisper, Parakeet, or NVIDIA Nemotron 3.5 Transcribe (30B-A4B MoE served on `localhost` via vLLM or NVIDIA NIM). Your audio never leaves your machine unless you explicitly configure a non-loopback Nemotron endpoint URL.
• Raw-audio retention (unchanged through v1.2.1): the recording remains in Mityu-managed local storage until you delete the meeting. Automatic deletion immediately after transcription is not implemented yet.
• Storage uses SQLCipher when the operating-system credential store can provide the database key. A fresh or already-plaintext database has a documented local-first plaintext fallback if key acquisition or conversion fails; an existing encrypted database is never opened without its key. Recording and export files rely on operating-system and filesystem protection rather than application-level encryption.
• Summaries are generated locally by default (built-in local model, or your own model via Ollama). If you choose to connect a cloud provider with your own API key, only the transcript text you ask to summarize is sent to that provider — never audio, never your library.
• Ask this meeting answers a question from one finished meeting’s transcript, using the same model choice as summaries. With a local model nothing leaves your device; with a cloud key, your question and the transcript passages retrieved for it go to that provider. Answers are marked AI-generated, and a line the model cannot trace to the transcript is dropped rather than shown.
• Live copilot (beta, off by default). When you turn it on under Settings → Beta, the panel follows a recording you start: it holds that meeting’s transcript in memory while you record, writes nothing to disk on its own, and releases the buffer when the recording stops or the copilot is switched off. An answer you request is built from the last few minutes of transcript text after your redaction rules have run, together with the wording of the meeting mode you selected, which is sent as written and is not redacted. Whether it may reach a cloud provider at all is governed by a separate setting, “Allow cloud insights”, under Settings → Beta. It is off by default, and while it is off the copilot answers only with a model running on this device and refuses rather than sending anything away. Turning it on sends that text to the AI provider you configured under Summary with your own key — on every press of an action button, with no further prompt. Audio is never involved. The only thing the copilot can save is a note you pin, which is written into the meeting’s summary as a draft when you save the meeting.
• API keys you add are stored in the operating system's secure credential store and are only ever sent to the provider they belong to.
• Speaker separation runs live with NVIDIA Nemotron 3.5 Transcribe (up to eight anonymous speakers) or on your device after a recording ends. It stores anonymous labels and timings only — Mityu never attaches a name to a voice and keeps no voice print.
• Models and updates. Transcription, summarization and speaker-separation models are downloaded only when you ask for them, from Hugging Face and from GitHub; no meeting content is uploaded with those requests. The app may also check the Mityu GitHub release endpoint for signed update metadata.
• Optional redaction can strip emails, phone numbers, card/ID numbers, and your own custom terms from transcripts before they are stored or sent to a summarization model.

3. Usage analytics — optional and off by default

Mityu ships with analytics disabled and opt-in. Production builds (through v1.2.1) deliberately embed no PostHog project key, so enabling the preference remains a local no-op and sends no analytics event to a processor. A future release may enable a bluedev-owned processor only after its region, retention, erasure process, access controls, processor terms, and this notice are updated and approved.

Analytics code is designed to exclude meeting content, transcripts and recordings; file names, meeting titles and metadata; audio and voice patterns; participant details; API keys; paths; and AI input/output. You can keep the preference off or turn it off again at any time.

4. Purchases & licensing

When purchasing is available, payments are processed by the merchant-of-record identified at checkout; Mityu does not receive card details. Activating a license sends the license key, public organization ID, Polar activation ID, and a random pseudonymous device label to Polar. Licensed installations validate in the background at most once every seven days; meeting content is never part of that request. The app trial requires no account, but obtaining the installer makes an ordinary website request to Vercel as described in Section 1.

5. Recording other people

Mityu shows a consent prompt before recording, but obtaining any consent required by the laws that apply to you (for example KVKK in Türkiye, or GDPR and local recording laws elsewhere) remains your responsibility.

6. Your rights and control

• All meeting data stays on your device: you can view, export, and delete it directly in the app, without asking anyone.
• Deleting the meeting through the app removes its Mityu-managed raw recording; independently exported or copied files remain under your control. Closing the app or editing transcript text does not delete the recording.
• Because we do not hold your content, most statutory data rights (access, erasure, portability) are things you can exercise yourself, instantly and locally.
• For licensing, a future analytics processor, a purchase, or any legacy website lead record, contact us to request access, correction, withdrawal, or deletion where applicable.

7. Changes to this policy

If this policy changes in a way that matters, we will say so in the application's release notes and update this page. The "last updated" date above always reflects the current version.

8. Contact

Questions about privacy? Write to info@bluedev.dev.