Security, privacy and compliance overview

This page is for anyone who needs to know how instruction.md handles their work: writers, team leads, and the people who approve new tools at a company. It says where your data is kept, who else handles it, how it is protected, and what we don't claim.

In short: your instructions are kept on servers we run ourselves. The assistant is the one part that sends your work to an outside company: OpenAI, in the United States. Apart from it, only what you choose to connect, such as an AI app or your company's sign-in, receives anything.

Your data stays on servers we run, except what you send the assistant.

Where your data is kept and processed

The site, the database, sign-in, email and the usage statistics all run on servers we operate ourselves. We don't use a cloud provider's ready-made services for them. Production runs on one machine. Its backups go to a separate storage service, so the database can be brought back on another machine.

We don't publish the hosting location on this page. If your company needs it, write to us and we will tell you in writing.

The assistant is the exception. The editor's AI assistant is a model run by OpenAI. When you ask it something, your message, the text of the instruction you have open and what it looks up are sent to OpenAI, which processes them in the United States. In a spoken conversation, your voice goes there too. It is not processed in the European Union.

  • OpenAI doesn't use what it receives to train its models. It may keep it for up to 30 days to watch for abuse.
  • OpenAI isn't told who you are. It gets a scrambled identifier that only tells one person's requests from another's.
  • We keep no conversation and no audio. The conversation you see is kept in your browser.
  • If you never open the assistant, nothing is sent. An organization's owners and admins can turn it off for everyone: see The assistant on or off.

The full details are in What is sent, and what is kept.

Who else handles your data

Who What for When
OpenAI (United States) The assistant Only when someone uses the assistant
Stripe Taking payment for a paid plan Only when you pay for a plan. Payment isn't switched on yet
Your company's sign-in provider Signing your people in Only if your organization sets up its own sign-in. This isn't available yet
The AI apps and agents you connect Reading the instructions you let them read Only what you connect, and only what you allow

Everything else is ours:

  • Email is sent from our own mail server.
  • Usage statistics come from Plausible, which we run ourselves. It sets no cookies, keeps nothing in your browser, and never receives an instruction's text or a name. Choose Necessary only in the cookie notice, or turn off Share anonymous usage in Your account ▸ Privacy, and nothing about you is counted.

We don't sell your data, and we don't share it with anyone for their own purposes. The Privacy page is the full account of what we keep and why.

How your data is protected

On the way

Every connection to instruction.md is encrypted. That covers the editor, the site, sign-in, and every AI app and agent that connects. Inside our servers, the parts that talk to the database check that they reach the real one.

Where it is stored

Your data is stored on machines we operate. We don't claim that the disks or the backups are encrypted, because what we run today doesn't show it. Ask us for the current state if your company needs it.

The keys that sign your versions are never stored as files. They are worked out inside the service each time from one secret we keep in a separate secret store.

When we must not read it: sealed workspaces

A sealed workspace encrypts its instructions on its people's own devices, before they reach us. We store and deliver them, but we can't read them. The same goes for conversations with agents that follow a sealed instruction. Only the people, agents and company services that hold the workspace's key can open them.

The assistant can't work on a sealed instruction, because it would need to read it.

Sealed workspaces are in beta, not yet independently reviewed. Until that review, keep your most sensitive material out of them. See Sealed workspaces.

Plans On Team and Enterprise

Signing in

There are no passwords. You sign in with a passkey: your phone, your computer or a security key, unlocked with your fingerprint, your face or a PIN. We keep only the public half of each passkey. Someone who gets into your inbox can't use it to get into your account: see the emails we send. See also Passkeys.

Signing: who published a version

Every version is signed when it is published, with your organization's own key. You don't need to set anything up.

A signature proves two things: which organization published the version, and that its text hasn't changed since. An agent that requires signatures holds back a version that doesn't pass, and keeps the one it had.

A signature doesn't say the instruction is good, safe or correct. It says who published it. To check one yourself, open History, choose a version, then Check signatures.

"Signed" says who published something. "Sealed" says who can read it. They are separate: a version in a sealed workspace is both. See Only signed versions.

Who at instruction.md can see what

Who What they can see
The service itself What isn't sealed, as any online service can: it has to, to show and deliver your work
The people who run our servers They can reach the machines that hold the database, to keep the service running
Our support staff The requests you send from Support or Contacts. They have no role in your organization, and the editor gives them no way to open your instructions
Nobody at instruction.md What is in a sealed workspace

If you need content we can't read at all, put it in a sealed workspace.

How long things are kept

What How long
Your instructions, versions and comments Until you delete them
What you delete 30 days in Trash, then deleted for good
Which agents read which version, and when 90 days, unless your organization chose another period
What a connected AI app did as you 90 days
Your organization's activity log As long as the organization exists
A download of your data or of an instruction 7 days
Backups of the database 30 days: changes are saved all the time, and a full copy is made every night
Requests to our support 24 months after they are answered; 12 months if nobody touches them; spam 7 days
Assistant conversations Not kept by us

Because backups are kept 30 days, something you delete is gone from them within 30 days too.

Your organization's Activity lists who published, shared, changed or deleted what, and when. Owners and admins can read it and download it for an auditor. See The activity log.

Plans On Team and Enterprise

To take your data with you, see Download or delete your data and Export.

Service status and incidents

instruction.md has no status page yet. Changes you will notice are on What's new. If something seems down, check Something isn't working, then ask us.

What we don't hold yet

  • No security certification, such as SOC 2 or ISO 27001.
  • No published independent security test. The encryption of sealed workspaces waits for its independent review.
  • No promise of uptime. The Terms of Service provide the service as it is.
  • No published data processing agreement. Ask us if your company needs one.
  • The assistant isn't processed in the European Union.

Report a security problem

If you find a security problem, don't post it in public. Write to us, choosing Security. A person reads every report. Developers will find what to include on Security disclosure.

Common misunderstandings

  • "Signed means it's safe." A signature says who published a version, not that its rules are right.
  • "The assistant runs on instruction.md." It runs on OpenAI, in the United States. Turn it off if your content may not go there.
  • "Sealed is finished." Sealed workspaces are in beta, not yet independently reviewed.
  • "Deleting is instant everywhere." Deleted things wait 30 days in the trash, and leave the backups within 30 days.

Last checked against the product:

Was this page helpful? Report a problem