← Meldom Privacy policy

Privacy policy

Last updated 24 August 2026

Meldom is a desktop application that runs on your Mac. Your projects, tickets, conversations and files stay on your own machine. We do not collect them, and we have no way to read them.

Who this is about

Meldom is made and operated by Vildan Bina (“we”, “us”), the sole operator of meldom.com. Questions about anything on this page go to [email protected].

Where your data lives

Everything Meldom records — projects, tickets, notes, comments, agent conversations, attachments and diagnostic logs — is written to a database and a set of files on your own disk, under ~/.meldom. Nothing is uploaded to us. Deleting that directory deletes your data; we hold no copy and cannot restore one.

No telemetry

Meldom sends no telemetry, no usage analytics and no crash reports. Diagnostic logs are written locally to ~/.meldom/logs and are never transmitted anywhere. If you want us to see a log, you have to send it to us yourself.

What does leave your machine

Four things in normal use, plus optional sync if you switch it on (below):

• License activation. When you activate Meldom, the app sends your license key, a device fingerprint, a device name and the app version to our licensing service at https://app.meldom.com. The fingerprint is a one-way hash derived from a random identifier generated on your machine — it is not your serial number, your hardware ID, or anything that identifies you personally. The device name defaults to your computer’s hostname, which is what lets you tell your machines apart when you manage activations. The service returns a signed token that the app stores locally.
• License checks after that are offline. Once activated, Meldom verifies that stored token on your machine with no network request at all. The app contacts the licensing service again only to refresh the token periodically, or when you activate or deactivate a device.
• Update checks. The app asks https://app.meldom.com/v1/desktop/latest whether a newer version exists, sending only the version you are running. Nothing is downloaded or installed unless you choose it.
• Your own AI provider. Meldom drives Claude Code and Codex using your accounts and subscriptions. When you run an agent, your prompts and the code it reads go to Anthropic or OpenAI under their terms, exactly as they would if you ran those tools in your own terminal. They do not pass through us, and we never see them.

Optional sync, if you turn it on

Meldom can sync tickets between your own machines. It is off by default, and it is off unless you enable it per project and supply a git repository you control. When it is on, your data travels between your machines through your repository — never through us. We operate no sync server.

Payment

Purchases are handled by Lemon Squeezy, which acts as the merchant of record for every sale. They collect and process your payment details, your billing address and any tax information required; card data never touches Meldom’s systems and we never see it. What we receive from them is your email address and the fact that an order was placed, so we can issue and email your license key. Their handling of your data is governed by Lemon Squeezy’s privacy policy.

What we store

On our own systems we keep only what is needed to sell and license the software: your email address, your license key, which devices it is activated on (a fingerprint hash, a device name and timestamps), and your order record. We keep it for as long as your license exists, and as long afterwards as tax and accounting law requires. We do not sell it, and we do not share it with anyone beyond the payment and email providers needed to complete the sale.

This website

meldom.com automatically loads PostHog analytics on their EU servers. Your browser sends those analytics requests to r.meldom.com, a Cloudflare Worker operated for Meldom, which forwards them to PostHog’s EU service. Cloudflare handles the proxied traffic in transit and PostHog remains the analytics processor; the relay does not turn this into first-party processing.

PostHog uses cookies and browser storage to assign a persistent visitor identifier and recognise returning visits. Its regular web features can collect pages and referrers, device and browser details, approximate location, clicks and interactions, errors and performance data, surveys, and session replay. Which remote features run can change with this PostHog project’s settings; the site does not disable them in its client configuration.

Your rights

You can ask us what we hold about you, ask for it to be corrected, or ask for it to be deleted. Write to [email protected] and we will answer. Deleting your licensing record deactivates your license, so ask only if that is what you want. Data on your own machine is yours to delete at any time and needs no request to us.

Changes

If this policy changes, the date at the top changes with it. Material changes will be announced by email to license holders.