Skip to content
notdocs
notdocs
Use itFeaturesEverything notdocs does, from the editor and query blocks to merges, search and agents, with the page that explains each.AgentsGive Claude Code, Cursor or any MCP client the workspace: tokens, tools, resources and prompts.CLIEvery notdocs command: documents, import, comments, tokens and the organization, for a local folder or a hosted workspace.TemplatesEvery built-in template with the file it starts, from a task to a data processing agreement.PricingFree for one person, Solo and Team for a few. What each plan allows.
Move inSwitch from NotionImport a Notion export as typed markdown documents in your repository.Switch from ObsidianImport an Obsidian vault and keep working on the same files.notdocs vs NotionMarkdown in your git repository or pages in Notion's database: how agents reach each, and what each tool does better.notdocs vs ObsidianBoth keep markdown files. What differs is where they live, who edits them, and how.ChangelogWhat changed in notdocs, from the CHANGELOG in the repository.
notdocsAboutWhy the repository should be the workspace, and the decisions notdocs is built on.SecurityWhere data lives, how access is scoped, and how to report a vulnerability.ContactHow to reach notdocs for support, privacy, security and legal matters.
PoliciesLegalEvery policy and agreement that applies to notdocs.
Legal

Data portability and exit

How to take your data with you and leave, and what it costs: nothing.

Last revised

On this page

The short version

Your data is in your git repository, in markdown, in a form every other tool reads. To leave notdocs, uninstall the GitHub App and ask us to delete your account. There is nothing to export, there is no switching fee, and there never will be one.

This page is the information the EU Data Act (Regulation (EU) 2023/2854, Chapter VI) asks a data processing service to publish about switching and exit.

What you hold

  • Documents. Markdown files with YAML frontmatter, in your repository.
  • Comments. YAML files under .notdocs/comments/ in your repository.
  • Configuration. notdocs.config.json and docs/_templates/ in your repository.
  • History. Your git history.

All of it is exportable data in the Act's sense and is already in your possession in an open, structured, machine-readable format. No notdocs software is needed to read it.

What we hold

  • Account, organization, project and membership records, and agent tokens.
  • An index of your documents: frontmatter, search text, embeddings and the text of versions we have seen.
  • A change log of who changed which document when.

None of this is needed to use your documents elsewhere. An owner deletes a project or an organization from its settings, which removes the index, the event records, the uploaded files and the texts of document versions no other project holds, at once. On request we provide the account and membership records as JSON within 30 days, and we delete the account within 30 days of your request.

How to switch

  1. Choose your next tool. Most of them read markdown folders directly; a git repository is the most common exchange format there is.
  2. Uninstall the notdocs GitHub App from your GitHub account. Our access to your repositories ends the moment you do.
  3. Revoke agent tokens, or let them expire with the account.
  4. Delete the organization from its settings (Danger zone), then write to privacy@notdocs.dev to delete your account. We confirm within 30 days.

You can do steps 1 to 3 without telling us and without any notice period. There is no minimum term.

Charges

None. We charge nothing for switching, for the data, or for early termination, and this will not change on 12 January 2027 or afterwards.

Functional equivalence and interfaces

Because the service stores no content of its own, there is no service-side export interface to document: the interface is git and the files. The features that depend on our index, search, boards and merges, stop when you leave; your files do not change.

Continuity

If we discontinue the hosted service we give at least 30 days' notice under the terms of service. During that time everything works as before; after it, your repository is untouched.