Security

How we keep your docs safe.

Data hosted in the EU, no customer code on our servers, and access scoped to what each person needs.

Data hosted in the EU

Typemark's servers and its PostgreSQL database run in DigitalOcean's Amsterdam data center. That's where your account, your docs and the Git repositories behind them live. Cloudflare sits in front for DNS, TLS and DDoS protection, and caches published pages at its edge so readers get them fast wherever they are.

Typemark is made in Estonia by lightfulweb OÜ, and handles personal data under the GDPR. See the privacy policy for the details.

Your MDX is never executed as JavaScript

MDX can contain JavaScript: import and export statements, {expressions} and computed component props. On a shared platform that would let one customer's page run code on our servers. So before any page is compiled, Typemark removes every construct that could run code. Only Markdown, our components and literal values like cols={3} get through.

The compiler runs as a separate process with none of the application's secrets in its environment, and each compile has a time limit. The server that renders published pages starts the same way.

Locked-down published sites

Published docs are served with a strict Content Security Policy: scripts load only from your docs site itself and our privacy-friendly analytics. Files served straight from your repository are limited to static media: images, video, fonts and PDFs. Dotfiles like .git or .env, source files and anything outside the repository are never served.

On Pro, you can add your own analytics and scripts. Google Analytics, Plausible and Fathom, set up by their ID, load only their own vendor's script, on any address. Your own scripts, Google Tag Manager, Hotjar and Intercom run only on your verified custom domain, never on a typemark.dev address.

Scoped GitHub access

GitHub is optional. When you connect a repository, Typemark uses a GitHub App, not a personal access token, so it only sees the repositories you pick when you install it. Before using an installation, we check that it belongs to you.

For each sync, Typemark asks GitHub for a short-lived installation token (GitHub expires them after an hour) and hands it to the single Git command that needs it. Tokens are never written into the repository's .git/config on disk. Incoming webhooks are rejected unless their signature checks out.

Role-based access

Every project member has a role, and the server checks it on every change:

  • Viewers can read the project in the dashboard and editor, but can't change anything.
  • Editors can write content: pages, navigation, images and AI writing.
  • Owners also manage settings, publishing, the custom domain, GitHub and members.

Who can read your docs

Published docs are public unless you say otherwise. On Pro, a site can ask readers for a password. On Enterprise, it can let in only the people you choose: anyone with an email address on your domains, by a sign-in link, or through your single sign-on.

Private sites are never cached, indexed or served to AI agents through the MCP server, and the password lives in our database, never in your repository. If you leave the plan, a private site stays private until you make it public.

Accounts and abuse protection

Passwords are stored as bcrypt hashes, or you can sign in with GitHub. Any account can turn on two-factor authentication with an authenticator app, on every plan. On Enterprise, your team signs in through your identity provider, over SAML or OpenID Connect, and you can require it for everyone on your verified domains.

Login, signup, password reset, invitations, search, AI and uploads are rate limited per IP address. AI search also has a daily cap per site: past it, readers get regular search results instead of an error.

Who else touches your data

  • Cloudflare: DNS, TLS and caching for typemark.dev and published docs.
  • Lemon Squeezy: payments, as merchant of record. We never see your card details.
  • Resend: transactional email such as invitations, password resets, two-factor authentication notices and sign-in links for readers of private docs.
  • OpenRouter: the language model behind every AI feature. When a reader uses AI search, the question and the relevant parts of your docs go through OpenRouter to the model. When someone uses AI in the editor (Ask AI, the assistant, edits across pages), the instruction, the text it works on and related pages do. If you turn on AI translations, every page is sent in full to be translated, and again after each build that changes it. We ask OpenRouter to route only to model providers that don't store or train on that data, and nothing goes to OpenRouter unless someone uses an AI feature or turns on AI translations.
  • Plausible: cookieless, privacy-friendly analytics on typemark.dev. It doesn't store IP addresses.
  • GitHub: only if you connect a repository.

Your content stays yours

Every project is a Git repository of plain MDX files and a typemark.json config. Connect it to GitHub at any time and the full history goes with it. If you leave, your docs leave with you.

What we don’t have yet

Typemark is a small team. We don't hold SOC 2 or ISO 27001 certification. If your procurement process requires them, we're not the right fit today, and we'd rather tell you now.

Enterprise does include single sign-on over SAML or OpenID Connect, with “Require SSO” for your verified domains, and an audit log of who changed what in each project, with a CSV export. Talk to us if that's what you need.

Report a vulnerability

Found something? Email [email protected] with “Security” in the subject. A person reads every report.

14-day Pro trial, no card. Your content stays in Git.