Privacy

Who is responsible

Taivo Pungas operates mex.taivo.ai and the mex telemetry service. For a privacy question or request, email taivo@pungas.ee.

Website delivery

Cloudflare serves this website. It processes ordinary request and security information—such as your IP address, requested page, browser details, and timing—to deliver and protect the site. This necessary processing is based on the legitimate interest in operating a reliable and secure public website.

Optional website analytics

If you choose Allow analytics, the site loads Google Analytics. It measures page visits and when agent instructions are copied, along with general information such as the referring page, approximate location, browser, and device type. Google Analytics uses first-party cookies scoped to mex.taivo.ai to distinguish visitors and sessions. They are separate from analytics cookies on other taivo.ai sites.

Nothing is sent to Google Analytics before you allow it. Refusing analytics does not change the site, and you can change your choice from the footer at any time. Analytics is based on your consent. Its cookies expire no later than 395 days after they are set. Google Analytics retains event data according to the property’s retention setting; aggregate reports may remain for longer. Your choice is saved in your browser until you change it or clear the site’s data. A choice made on withmex.com does not carry over to mex.taivo.ai; the new site asks again.

Optional command-line telemetry

The mex command-line tool starts with telemetry off. If you explicitly opt in, it sends daily aggregate counts of the mex version, command, outcome, stable error and warning codes, and a coarse duration bucket. It does not send media, paths, file names, command arguments, prompts, transcripts, logs, result envelopes, IP address, location, host details, or hardware. Cloudflare still processes ordinary request metadata in transit; the mex service does not copy it into D1 or custom logs.

Anonymous mode uses a random installation identifier. Verified-email mode links all retained activity for that installation—including activity sent earlier in anonymous mode—to the email address you verify. You can inspect the exact scope, disable future collection, or request erasure through mex telemetry. Setting MEX_NO_TELEMETRY, even to an empty value, prevents all collection and telemetry network requests.

The CLI keeps unsent aggregates for no more than 31 days and retries at most one request in a process after multi-day backoff. The service retains routine aggregates and verified identities for up to 24 months, or deletes active rows earlier when you request erasure. Cloudflare recovery history may retain deleted rows for its limited recovery window; any restoration must reapply the erasure ledger before ingestion resumes.

Field reports

A person or agent may prepare a short report about what worked or failed. Nothing is sent until you see and approve that exact report and destination. You may send it directly by email, or use the first-party endpoint anonymously. Email and verified-endpoint reports are attributable; anonymous endpoint reports are not linked to an installation.

Reports contain only the structured text and command outcomes shown in the preview, never attachments. They are retained for up to 24 months or until earlier erasure where they can be connected to a verified identity. Direct email is also processed and retained by the operator’s email provider.

Providers and your choices

Cloudflare hosts the site and telemetry endpoint and stores telemetry in D1. Resend delivers verification messages; Google processes analytics only after website consent. These providers may process data outside your country under the safeguards in their privacy terms.

You can withdraw website analytics consent from Privacy choices in the footer. You may also ask to access, correct, or delete personal data that can be connected to you, object to necessary processing, or complain to the Estonian Data Protection Inspectorate.