Updated: November 15, 2026

Security

Contents · 10 sections
  1. 1. What leaves your computer
  2. 2. What never leaves
  3. 3. How long code is kept
  4. 4. What usage records hold
  5. 5. Encryption and keys
  6. 6. Sign-in and access
  7. 7. Subprocessors
  8. 8. Reports and certificates
  9. 9. Your controls
  10. 10. Report a security problem

In short: Mikie reads your repository on your computer and sends only the files each request needs. That content is deleted when the request ends. Secret files are never sent, and your receipts hold numbers, never code.

1. What leaves your computer

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

  • 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.

Mikie returns the selected lines to your agent. Your agent sends them to your model provider under your own agreement with that provider. Mikie sends your code to no model provider and runs no models of its own.

Shadow mode for Codex also sends your prompt (up to 16 KB) and the text of source files Codex read (up to 256 KB each), compares once, and keeps counts and fingerprints. Shadow mode for Claude Code sends nothing extra.

2. What never leaves

  • .env files, private keys, .npmrc, .netrc, credentials files and secrets folders. The CLI skips them before anything is sent.
  • Files a request does not need. They stay on your machine.
  • Your GitHub repositories. Mikie does not connect to your GitHub account; signing in with GitHub shares your basic profile and email address.
  • Your passwords. Our sign-in provider handles them and we never see them.
  • Your card number. Stripe collects it on its own page.

3. How long code is kept

Zero data retention, for every account. File contents go into a temporary working copy that is removed when the request finishes. Between a request’s steps, its arguments and the list of files it may read wait encrypted with AES-256-GCM, bound to your account and that one request, and are deleted when the request finishes.

An abandoned request’s record expires 2 minutes after the request started and a cleanup job that runs continuously deletes it. Repository content is never written to logs, kept as telemetry or used to train models.

The privacy policy lists how long every other kind of record is kept.

4. What usage records hold

Receipts and usage records hold 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 hold source code, prompts, model or tool output, commands, credentials, environment values or raw repository paths.

5. Encryption and keys

  • Data is encrypted in transit between the CLI, the website and our service.
  • Each device holds its own signing key. Usage records are encrypted and signed on the device before upload.
  • Encryption and signing keys for the service are managed in Amazon Web Services key management.
  • IP addresses kept for abuse prevention are hashed before they are stored.

6. Sign-in and access

  • Sign in with email and password, GitHub or Google. Each account is for one person.
  • Every device is listed in your account. The account owner is told when a device is added. Revoke one with mikie device revoke.
  • Mikie's customer tools are read-only: eight MCP tools that read context and measurements. None of them writes to your repository.
  • All Mikie source is in one GitHub organization with one owner and no outside collaborators. Changes to the main branch go through a pull request.

7. Subprocessors

These providers process data for Mikie. Repository content reaches one of them: the API host, for the life of a request.

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

8. Reports and certificates

Here is what Mikie holds today and what it does not.

  • SOC 2: No. No report. No auditor is engaged.
  • ISO 27001: No. No certificate.
  • Third-party penetration test: No. None performed.
  • Zero data retention for code: Yes. Repository content is deleted when each request ends, for every account.
  • Content-free usage records: Yes. Receipts hold counts and IDs. They never hold source, prompts or paths.
  • No training on your code: Yes. Mikie runs no models and sends your code to no model provider.

If a report is what stands between your team and a trial, tell us at security@getmikie.com. A founder answers, and we will go through your security questionnaire with you.

9. Your controls

  • Export your usage records and workspace reports as CSV or JSON from your account.
  • Delete your usage records in Account → Privacy. Close your account by emailing security@getmikie.com.
  • Turn off product-health reports with MIKIE_TELEMETRY=0 or DO_NOT_TRACK=1.
  • Stop all data leaving a machine with mikie device revoke or mikie uninstall.
  • Start in shadow mode on a public repository. Nothing private is involved.

10. Report a security problem

Email security@getmikie.com with what you found and how to reproduce it. A person replies within 5 working days. Please give us time to fix the problem before you publish it, and leave other customers’ data alone while you test.

If a breach affects your personal data, we tell you and the relevant authorities as the law requires. The same contact is published at /.well-known/security.txt.