Privacy Policy
Last updated: July 15, 2026
The short version: your meetings are processed and stored on your own device. Audio is never uploaded. In v1.0.4, raw meeting audio stays in Mityu-managed local storage until you delete the meeting. This website sets no cookies and runs no advertising trackers. App analytics is off by default, and v1.0.4 sends no analytics events because no processor key is embedded.
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. v1.0.4 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, using local Whisper or Parakeet models. Your audio never leaves your machine.
- Raw-audio retention in v1.0.4: the recording remains in Mityu-managed local storage until you delete the meeting. Automatic deletion immediately after transcription is not implemented in this version.
- 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.
- 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.
- 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. The v1.0.4 production build deliberately embeds 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.