Updated: November 15, 2026

Privacy policy

Contents · 12 sections
  1. 1. Who we are
  2. 2. What we collect
  3. 3. Your code: what leaves your computer
  4. 4. How we use it, and why we're allowed to
  5. 5. Who processes it for us
  6. 6. Cookies and browser storage
  7. 7. How long we keep it
  8. 8. Your rights and choices
  9. 9. International transfers
  10. 10. Security
  11. 11. Children
  12. 12. Changes

(Previous version)

In short: Mikie reads your repository on your computer and sends only what each request needs, for that request. Your usage records hold numbers, never code. We don’t sell data, and you can export or delete it. Recordings of how visitors use our public pages are processed for us by PostHog, and you can turn them off.

1. Who we are

Mikie (“Mikie”, “we”) runs getmikie.com, the Mikie CLI and native relay, and the hosted service behind them. We are the controller of the personal data described here. Questions, requests and complaints: privacy@getmikie.com.

2. What we collect

  • Account. Email address, display name, and the ID of the sign-in provider you use (email and password, GitHub or Google). Passwords are handled by our sign-in provider; we never see them.
  • Billing. Stripe collects your card and billing address on its own page. We receive your subscription status, a Stripe customer ID, invoices, and your card brand, last four digits and expiry date.
  • Teams. Email addresses of people you invite, member roles and display names. Teammates and organization admins can see members’ display names, roles and team usage, including the leaderboard where your organization turns it on.
  • Devices. A device ID, the device’s public signing key, CLI version, update channel and last sign-in time, plus what the device reports about itself once a day so you can tell your devices apart: its operating system, chip and coding client, and the approximate city, region and country of its connection, as ChatGPT and Codex show for devices (looked up on our servers from the connection’s IP address in a bundled copy of IP Geolocation by DB-IP (opens in a new window), licensed CC BY 4.0; the IP address itself is not stored; left out when DO_NOT_TRACK=1 or MIKIE_TELEMETRY=0 is set). When a device beyond your first is added, we tell the account owner in the dashboard and any alert channels they set up; they can turn this off in Alerts. To spot shared logins, we note days on which five or more of a person’s devices signed requests within the same half hour. This uses only the signed-request records we already keep, and it never blocks the account.
  • Usage records (Evidence). While you use Mikie, the CLI records content-free facts about each request: session and turn IDs, client and tool names, language category, mode, file counts, token counts, retries and durations. They are encrypted and signed on your device before upload. They never contain source code, prompts, model or tool output, commands, credentials, environment values or raw repository paths.
  • Product health (“Help improve Mikie”). On by default, except in the EU, EEA, UK and Switzerland, where it stays off until you turn it on (the CLI uses your computer’s region setting, and the dashboard your country). The CLI reports how Mikie itself behaves: which of its tools, hooks and commands ran, their outcome or error code, timings, result counts and sizes, whether a time limit was hit, a coarse token range per session, your operating system, coding client and Mikie version. For the usage band above the Claude Code prompt, it reports when the band was shown, opened, collapsed, closed or brought back, whether by button or command, how long it stayed in each view, how many times it was closed, its style, and your plan use as a range (such as 50–75%). These reports are content-free by schema: every text field is a fixed name or a short code, so they never contain source code, prompts, model or tool output, file names, paths or error messages. They are kept for 90 days. We also add each report to anonymous daily totals (counts and timings by Mikie version, operating system, coding client, tool, outcome, language and repository size) that contain no account, person or device and cannot be linked back to you; these totals are kept to improve Mikie and are not deleted when you turn reports off. Turn them off at any time with the switch on your Meter dashboard or in Account → Privacy (which also deletes what was sent), with mikie privacy analytics off, or by setting MIKIE_TELEMETRY=0 or DO_NOT_TRACK=1; they are also off in CI. mikie privacy analytics shows the reports waiting to be sent.
  • Local usage counters. To fill in receipts, the CLI reads model names and token counts from Codex and Claude Code session files on your computer. Only the counts are uploaded, as part of the usage records above.
  • Daily savings totals. To show your savings on your profile, mikie usage works out on your computer, from your Codex session files, what each session Mikie was in cost and what it would have cost without Mikie. It uploads one line per day: the number of those sessions, the two costs at provider list prices, and the accuracy of the calculation it used. Nothing about an individual session, repository, prompt or code is sent. The totals are signed by your device and shown only on your own private profile and the card images you choose to copy or download. They are not sent when DO_NOT_TRACK=1 or MIKIE_TELEMETRY=0 is set.
  • Website analytics. Vercel Web Analytics and Speed Insights record the page address (without query strings), referrer, browser, operating system, country and page-speed measurements. They set no cookies. If your browser sends Global Privacy Control or Do Not Track, we do not load them.
  • Session recordings and heatmaps. On our public home, pricing, about, careers, developers, blog, docs, guides and tools pages, PostHog records for us how you use the page: mouse movements, clicks, scrolling, what the page displays, and device and browser details. Form fields are masked in your browser and never uploaded, and recorded page addresses have their query strings removed. We do not record sign-in, account, dashboard, billing, invitation, contact or legal form pages. We do not link recordings to your Mikie account, PostHog builds no profile of you, and we set it to discard IP addresses. In the EU, EEA, UK and Switzerland, or if we cannot tell where you are, recording starts only after you allow it. Elsewhere it is on until you turn it off. If your browser sends Global Privacy Control or Do Not Track, we do not load it. See your choices.
  • Logs. Our servers log requests, including IP addresses, to run and secure the service. Log lines record the route, outcome, error codes, timings and IDs; they never contain your code, prompts, file paths or tool arguments. IP addresses used for abuse prevention are hashed before they are stored.
  • Legal requests. If you use the arbitration opt-out, informal dispute or copyright complaint form, we keep what you enter (your name and email, and for a copyright complaint your address, phone number, signature and the details of the complaint) to handle the request and as a record of it. For a copyright complaint, we may share the rights holder’s name, your email and the details of the complaint with the person who posted the material.

3. Your code: what leaves your computer

Mikie reads the repository you connect on your own machine. When your coding agent asks Mikie for context, the CLI sends our service:

  • the agent's request (the tool name and its arguments, such as a search query);
  • a list of the repository's file paths with their sizes and fingerprints; and
  • the contents of the files needed to answer that request.

Zero data retention, for every account. This content is used only to build the context for that request, and none of it is kept after the request ends. File contents go into a temporary working copy that is removed when the request finishes. Between the request’s steps, its arguments and the list of files it may read wait encrypted, and they are deleted when the request finishes. If a request is abandoned partway, that record expires 2 minutes after the request started and our cleanup job, which runs continuously, deletes it. None of it is written to logs, kept as telemetry or used to train models. Mikie runs no models, so it needs none of your content for abuse monitoring or training. The CLI skips .env files, private keys, .npmrc, .netrc, credentials files and secrets folders. Mikie returns the selected lines to your agent, and your agent sends them to your model provider under your own agreement with that provider. Mikie itself does not send your code to any model provider.

Mikie does not connect to your GitHub account or read your repositories from GitHub. Signing in with GitHub shares only your basic profile and email address.

Shadow mode (optional, Codex). If you run mikie mode codex shadow, the CLI also sends your Codex prompt (up to 16 KB) and the text of source files Codex read (up to 256 KB each) so Mikie can work out what it would have sent instead. Dot-files, secret-named paths and text that looks like a credential are skipped. The comparison runs once and keeps only counts and fingerprints, never the prompt or file text.

Shadow mode (optional, Claude Code). If you run mikie mode claude shadow, Mikie’s hooks leave your Claude Code sessions unchanged and send nothing extra: no prompt and no file text is sent for the comparison. The CLI only notes, in a small file in the project’s .mikie folder on your computer, that the session ran in shadow mode, so it can be compared with sessions Mikie worked in.

4. How we use it, and why we're allowed to

  • To provide the service you signed up for: sign-in, building context, receipts, billing and support (performance of a contract).
  • To secure the service, prevent abuse and fix problems, using logs and usage records (our legitimate interests).
  • To understand how the website is used and keep it fast, using aggregated analytics (our legitimate interests; switched off by Global Privacy Control or Do Not Track).
  • To see how our public pages are used and improve them, using session recordings and heatmaps: in the EU, EEA, UK and Switzerland only with your consent, which you can withdraw at any time; elsewhere under our legitimate interests, and you can object by turning them off.
  • To find and fix problems and improve Mikie, using content-free product-health reports: outside the EU, EEA, UK and Switzerland until you turn them off (our legitimate interests; you can object at any time with the switches above, and we stop and delete them); in those regions only after you turn them on (your consent, which you can withdraw at any time).
  • To keep tax and accounting records and respond to lawful requests (legal obligation).

5. Who processes it for us

We use these providers. Each processes data only to provide its service to us.

ProviderPurposeLocation
VercelWebsite hosting, Web Analytics and Speed InsightsUnited States
PostHogSession recordings and heatmaps of our public pagesUnited States
RenderAPI hosting and databaseUnited States
SupabaseSign-in, sessions, sign-in emails and the tokens our API checksProvider-selected regions
StripeCheckout, subscriptions, invoices and card paymentsUnited States and other countries
Amazon Web ServicesEncryption and signing key managementUnited States
GitHub and GoogleSign-in, if you choose themUnited States and other countries
npm (GitHub)CLI downloads and the CLI update checkUnited States

PostHog processes session recordings and heatmaps only on our instructions, under a data processing agreement. We have opted out of PostHog using our data to develop its products or train its models.

We do not sell your personal information or share it for cross-context behavioural advertising. We disclose data to authorities only when the law requires it, and to a buyer if Mikie is sold, under this policy.

6. Cookies and browser storage

Our own cookies are only those needed for the site to work. Session recordings set no cookies and use no browser storage: PostHog keeps its state in page memory, which is cleared when you leave or reload the page.

  • Sign-in session cookies from Supabase (sb-*), kept while you stay signed in.
  • Short-lived security cookies for CLI sign-in (10 minutes or less), checkout (30 minutes) and team invites (15 minutes).
  • Browser session storage for a few interface settings and a random, per-tab ID for guide-page analytics, cleared when you close the tab.
  • Browser local storage for your session-recording choice and when you made it, kept until you clear it.

7. How long we keep it

  • Repository content and request arguments: not kept (zero data retention). They are deleted when the request finishes; an abandoned request's encrypted record expires after 2 minutes and is then deleted by a cleanup job.
  • Product-health reports: 90 days, or until you turn them off; a cleanup job deletes expired reports for every account. Anonymous daily totals, which cannot be linked to you, are kept.
  • Session recordings: 30 days. Heatmap data (clicks, scroll depth and mouse positions, without the recording): up to 12 months.
  • Account, team, device and usage records: while your account is open, then deleted after you close it, except as below.
  • Billing and tax records: as long as tax and accounting law requires, typically up to seven years.
  • Server logs: up to 30 days, then deleted by our hosting provider.
  • Legal requests sent through our forms: as long as needed to handle them and as legal records, which for an arbitration opt-out is at least as long as your account and any claim about it could be brought.

8. Your rights and choices

You can access, correct, export or delete your data, object to or restrict how we use it, and withdraw consent.

  • Export: download your usage records and workspace reports (CSV or JSON) from your account.
  • Delete usage records: Account → Privacy → “Delete my identity from Meter”.
  • Close your account or anything else: email privacy@getmikie.com from your account’s address. We respond within 30 days (45 days for California requests where the law allows).
  • Stop data leaving your computer: revoke the device with mikie device revoke or uninstall with mikie uninstall. Turn off the CLI update check with MIKIE_NO_UPDATE_NOTICE=1.

Session recordings: No choice saved in this browser.

This choice applies to the browser you use it in. Recordings we hold no account link for can be hard to find, so to ask about one, email privacy@getmikie.com.

California residents have the right to know, delete and correct personal information, and not to be treated differently for using these rights. We do not sell or share personal information, and we honour Global Privacy Control. If you are in the EU, UK or Switzerland you can also complain to your local data protection authority.

9. International transfers

We are based in the United States, and our providers process data in the United States and other countries. When data moves out of the EU, UK or Switzerland, we rely on safeguards such as the European Commission’s Standard Contractual Clauses in our providers’ data processing terms.

10. Security

Data is encrypted in transit. Usage records are encrypted and signed on your device, request content is kept only for the life of the request, identity data is protected with managed encryption keys, and stored IP addresses are hashed. No system is perfectly secure; if a breach affects your personal data, we will tell you and the relevant authorities as the law requires.

11. Children

Mikie is not for anyone under 16, and we do not knowingly collect their data. If you think a child has signed up, email privacy@getmikie.com and we will delete the account.

12. Changes

We update this policy when what we collect or how we use it changes, and change the date above. For material changes we notify signed-in customers by email or in the product before they take effect. Your product-health choice is tied to a specific policy version, shown in Account → Privacy.