Origami Labs

Privacy · Origami Coder

Privacy Policy

Origami Coder runs on your own computer and sends nothing to Origami Labs. What leaves your machine is set by the model provider you choose and the servers you connect it to.

Effective date: 13 August 2026

The short version. Origami Coder has no account with us, no analytics, no crash reporting and no update check. Your prompts, your code and your sessions are never sent to Origami Labs. If you point it at a cloud model provider, your prompts and the file content the agent reads are sent to that provider, with your own key, under their privacy policy.

What leaves your machine, and when

Origami Coder is a coding agent. It reads files, runs commands and sends what it collects to a model. Where that model runs decides where your data goes. These are the cases:

  • Your model provider. Each prompt you type, plus the file content, command output and tool results the agent gathers, is sent to the model provider you configure. If the provider is a server on your own machine or your own network — for example LM Studio on http://localhost:1234/v1, or Ollama — the data does not leave that network. If the provider is a cloud service, the same data is sent over the internet to that service, with your own API key, and their privacy policy applies to it. Origami Coder does not pick the provider for you, and keeps no copy anywhere but your disk.
  • A client name in the request header. Requests to a few cloud providers carry the header HTTP-Referer: https://origami.gratis/. It tells that provider the request came from Origami. The header is sent to the provider. No request is made to origami.gratis.
  • An OpenRouter model list. If you save an OpenRouter API key, the VS Code extension asks OpenRouter for its model list and prices, so it can show you the free models. With no key saved, that request is not made.
  • The web tools, when the agent uses them. The agent has a webfetch tool that requests the exact address it is given, and a websearch tool that sends your search words to a search service. Both run only inside a turn, and only under the tool permissions you set.
  • Remote MCP servers you add. A remote MCP server is an address you write in your own configuration. Origami Coder sends tool calls to it, with the headers or the OAuth token you set for it.

Nothing else is sent. There is no analytics service, no crash reporter and no update service in the product.

What Origami Labs receives

Nothing. Origami Coder has no Origami Labs server to talk to. Four paths that could have carried data out are switched off in the code:

  • No analytics and no crash reporting. The product contains no analytics library and no error-reporting service.
  • No update check. The version check that ran shortly after every start is removed, and the upgrade command fails closed. Origami Coder does not ask any server whether a newer version exists, and never replaces itself.
  • No session sharing. A session transcript cannot be uploaded to a hosted viewer. The share code returns without sending, and the share command produces no link.
  • No model-catalogue download. The background download of the public model catalogue, and its hourly refresh, are switched off. Model data comes from the copy built into the product or from a file on your disk.

Origami Coder also downloads no third-party binaries by itself. The search tool ripgrep must be on your PATH; the product tells you to install it rather than fetching it. Language-server downloads and syntax-highlighting grammar downloads are off unless you turn them on with an environment variable.

Tracing, if you turn it on

Origami Coder can export OpenTelemetry traces and logs. This is off until you set the environment variable OTEL_EXPORTER_OTLP_ENDPOINT. With no endpoint set, no exporter is created and nothing is sent. When you do set it, traces and logs go to the collector at that address — your collector, on infrastructure you control. Origami Labs has no endpoint in this path and receives none of it. A separate configuration flag, openTelemetry, adds spans around model calls; it uses the same exporter and the same rule.

What is written to your disk

  • The product home, ~/.origami. It holds the engine binary in bin/, plus sessions/, skills/, settings.toml, and the global plans and memory files.
  • Your conversation history. Sessions, messages and their parts are stored in a SQLite database file, origami.db, in your own user data directory. Prompts and replies are kept there so you can reopen a session. They are stored locally only, and are never uploaded.
  • Provider credentials. API keys and OAuth tokens are written to auth.json in the same data directory, with file permissions set to owner-read and owner-write only.
  • Logs and caches. Written under your standard user data, cache and state directories.

All of this stays on your machine. There is no cloud sync and no backup service.

MCP servers, plugins and skills are other people's code

Origami Coder can load code that Origami Labs did not write and does not review. Treat it the way you treat anything else you install:

  • A local MCP server is a command that Origami Coder starts on your machine. It runs as you, in the working directory and with the environment variables you give it, and it can do whatever your user account can do.
  • A remote MCP server is an address you name. Tool calls, and any headers or OAuth token you configure for it, are sent to that address.
  • Plugins run inside Origami Coder. A plugin can change agents, commands, providers, models and the handling of credentials.
  • Skills are instruction files that the agent reads and follows.

Origami Labs does not host, review or approve any of it. Install only what you trust. How a third-party server or plugin handles your data is set by its author, not by this policy.

The local server

Origami Coder can run as a server for its web and terminal surfaces, with origami serve and origami web. The server is yours and runs on your machine. Origami Labs cannot reach it. Two points about it are yours to control:

  • The address it listens on. The default is 127.0.0.1, which only your own machine can reach. If you start it with --hostname 0.0.0.0, or with --mdns, which sets that address for you, other devices on your network can reach it. The server prints those network addresses when it starts.
  • The password. If ORIGAMI_SERVER_PASSWORD is not set, the server starts unsecured and prints a warning that says so. Anyone who can reach an unsecured server can read the sessions on it. Set a password before you put the server on a network.

Privacy · Origami Folio

Privacy Policy

Origami Folio collects nothing. No accounts, no analytics, no telemetry, no network requests. Your documents and settings stay on your device.

Effective date: 18 June 2026

The short version. Origami Folio has no sign-in, no analytics, no telemetry and no tracking. It makes no network requests to send your data anywhere. Everything you make stays on your own device, and we never see it.

What stays on your device

Everything. Specifically:

  • Your documents. The .origami.html files you open, create and edit are read from and written back to your own device, only when you explicitly open or save them.
  • Preferences and recents. Settings such as your theme, and the list of recently opened documents, are stored locally using the browser's storage API so the app can restore them next time.
  • Autosave and backups. While you edit, the Studio keeps local autosave snapshots and timestamped backups of the current document (in IndexedDB and the browser's private file storage) so your work isn't lost. These never leave your device. This is why the extension requests unlimitedStorage — documents can be several megabytes, and the default quota is too small for reliable local backups.

None of this data is transmitted to us or to any third party.

Permissions, in plain terms

  • storage / unlimitedStorage — store your preferences, recents, autosaves and backups locally, as above.
  • file:///* (and the file:// content script) — let the extension recognise an .origami.html file you double-click or choose, open it in the Studio, and save your edits back to that same file. It only touches files you explicitly open, and does not browse, collect or transmit your files. You also have to enable “Allow access to file URLs” for the extension.
  • nativeMessaging — used only by the optional Go Live feature, and only when you turn it on. A browser extension cannot open a local network port itself, so Go Live connects to a small companion app you install separately to serve the document you're editing from your own machine, over your own local network (for example, to open it on your phone via a QR code). It connects only to that local companion; nothing is sent to us or to any remote server. If you never use Go Live, this never runs.

Network activity

The extension makes no network requests for its own operation, and contains no analytics or telemetry. There are two cases where your content can cause network activity, both under your control:

  • Live embeds via Go Live. If you add an embed (for example a video or a dashboard) to a document and then use Go Live, your browser loads that embedded content directly from the third party that hosts it, subject to their privacy policy — not ours. Offline, embeds are shown as static link cards and load nothing.
  • Serving on your local network. When you choose Go Live, the document is served from your machine to other devices you point at it on your own local network. It is not uploaded to the internet or to us.

Export

Exporting to PowerPoint, Word or image formats happens entirely on your device. No document content is sent anywhere to perform an export.

Remote code

All of the extension's code ships inside the package; the extension never downloads or executes code from a remote server. For full transparency: the offline export feature uses a bundled third-party HTML-to-image library that internally uses new Function() on in-package data — no external code is involved.

Data sharing and sale

We do not sell or transfer your data to third parties. We do not use or transfer your data for any purpose unrelated to the extension's single purpose, and we do not use it to determine creditworthiness or for lending. There is no user data for us to share, because we never collect any.

Privacy · Origami Games

Nothing to collect yet.

Velkarn: The Darklands is pre-alpha and is not distributed. There is no build you can install, so there is no game software collecting anything.

Effective date: 13 August 2026

There is no download, no launcher, no account and no player data, because there is no released game. A privacy policy for a game describes software you can run; that software does not exist outside the studio yet.

When a build is distributed, its policy will be published here, on this tab, before you can install it.

The game page carries the current state of the work. The sections below apply to every Origami Labs product, this one included.

Every product

Rules that apply to all three

Origami Coder, Origami Folio and Origami Games handle data differently, so each has its own tab above. The rules below hold for all of them, whichever tab you are reading.

Data sharing and sale

We do not sell or transfer your data to third parties. We do not use or transfer your data for any purpose unrelated to a product's single purpose, and we do not use it to determine creditworthiness or for lending. There is no user data for us to share, because we never collect any.

The Origami Folio tab states this same rule in the form declared for the Chrome Web Store, which names the extension's single purpose. The two statements say the same thing. If one is changed, change both.

Children

The extension is a general-purpose document tool, is not directed at children, and collects no personal information from anyone. Origami Coder is a general-purpose developer tool, is not directed at children, and collects no personal information from anyone. Origami Games is not distributed, so there is nothing to collect anything with.

Changes to this policy

If this policy changes, the updated version will be published at this same location with a new effective date. Each product tab carries its own effective date, so a change to one product does not restate the others.

Contact

Origami Labs, at support@origami.gratis, or through the Support page. For Origami Folio you can also use the project repository at github.com/PassingByPixels/Origami-Folio.