Skip to content

meldoc.io › Privacy Policy

Privacy Policy

Last updated: November 8, 2026

This policy explains what personal data Meldoc collects when you use meldoc.io, the app at app.meldoc.io, public documentation at public.meldoc.io, the meldoc command-line tool and the Meldoc MCP server; what we do with it and why; who else receives it; how long we keep it; and what your rights are.

Who we are

Meldoc is operated by Eduard Balev, an entrepreneur registered in the Czech Republic, Company ID (IČO) 08180989, who is the controller of the personal data described in this policy. For anything about your data, write to [email protected].

When a business or team uses Meldoc, the content of its workspaces — documents, comments, files, and the personal data in them, including the email addresses of people it invites and the names of authors of commits in repositories it connects — is processed by us on the workspace owner's behalf. For that content the workspace owner is the controller and we are its processor; questions about it are best sent to the owner, and we pass on any request we receive. A Data Processing Agreement is available to every customer on request. This policy describes the data for which we are the controller — accounts, sign-in, billing, security logs, analytics and our emails — and, for your information, what happens to workspace content.

What we collect

What you give us

  • Account details: your email address; your first and last name, if you enter them or your GitHub or Bitbucket account shares them; a profile picture, if you upload one.
  • Sign-in with GitHub or Bitbucket: your account ID with that provider, your email address and your name.
  • Workspace content: documents, comments, uploaded files and images, glossary entries and settings; the email address and role of people you invite; when you ask a workspace's admins to let in you or a colleague, the email address concerned and the message you add.
  • Repository connections: when a project is connected to a GitHub, Bitbucket or GitLab repository, we read and write the documentation files in it, and record the name, email address and username of the authors of commits that change documentation, including people who do not use Meldoc. The command-line tool also sends the author and co-authors of the last commit of each file it uploads.
  • Billing: payments are handled by Stripe. We give Stripe the subscriber's email address and the workspace's name; Stripe collects payment details and the billing address itself, and we never see your card number. We receive your customer and subscription identifiers, the plan, amounts and payment status. Stripe also uses payment data for its own purposes, such as preventing fraud and meeting legal obligations, as a controller under Stripe's Privacy Policy.
  • Messages you send us.

You need to give us an email address to have an account, and payment details (to Stripe) to buy a paid plan; without them we cannot provide the service. Everything else, such as your name or a profile picture, is optional. No law requires you to give us any of it.

What we collect automatically

  • Sessions: when you sign in to the app or the command-line tool, we store the IP address and the browser or client identification (user agent) with that session. For each integration token we store the IP address it was last used from.
  • Server logs: our API records each request with a shortened IP address (the last part removed), the address requested, the result, how long it took and your account or token ID, and records each email we send with its recipient. Warnings and errors are also kept in a separate log store we run at our hosting provider; some of them contain a full IP address or, when an email could not be sent, the recipient's email address.
  • Error reports from the app: when the app hits an error, it sends us the error message, the page it happened on, your browser identification and your account ID.
  • Performance measurements from the app: how long a page took to load and to respond to input, with the pattern of the page's address (for example /w/:workspace/documentation). The measurements carry no account ID and no names of workspaces or documents, and they are added into totals as they arrive; the request that delivers them is recorded in the server logs like any other.
  • Activity records: each workspace keeps an audit log of who did what and when, which names you, with your email address, as the person who acted.
  • Presence: whether you are online in a workspace, when you were last active and which page you are on, so that collaborators see each other.
  • Searches that found nothing: the text of the query, without who made it, so that missing documentation can be spotted.
  • Analytics: Google Analytics, as described in our Cookie Policy.

How we use it, and on what basis

  • To provide the service you signed up for — your account and sign-in, workspaces and documents, search and the AI features you use, repository sync, and the emails that belong to the service (sign-in codes, invitations, workspace and billing notices). Basis: performing our contract with you (GDPR Art. 6(1)(b)).
  • To keep the service secure and working — session records, logs, error reports, performance measurements, rate limiting and the audit log. Basis: our legitimate interest in protecting accounts and the service and in finding and fixing problems (Art. 6(1)(f)).
  • To understand how Meldoc is used — analytics cookies only with your consent (Art. 6(1)(a)), which you can withdraw at any time.
  • To send product news — occasional emails about Meldoc's own features and plans, only to people with a Meldoc account who turned them on in their email settings; every category is off until you do. You can turn it off again there, or use the unsubscribe link in any of them. Basis: your consent (Article 6(1)(a) GDPR and Section 7(2) of Czech Act No. 480/2004 Coll.).
  • To meet legal obligations — invoices, tax and accounting records (Art. 6(1)(c)).

We do not sell personal data, and we do not use it for advertising.

Your right to object. Where we rely on our legitimate interests — security records — you can object at any time by writing to [email protected]. We then stop, unless our reasons override yours or we need the data for a legal claim. Product emails rest on your consent instead: withdraw it in your email settings or with the unsubscribe link in any of them, and they stop at once.

AI features

  • AI search. In workspaces where AI search is on, the title and text of each document are sent to OpenAI to turn them into search vectors, and so is each search query. This always uses Meldoc's own OpenAI account, even when a workspace has connected its own AI provider. The vectors and document passages are stored in our own search database on our servers in Frankfurt.
  • AI Ask, AI writing, summaries, answers above search results and duplicate detection. The question or selected text and the relevant passages of documents are sent to the workspace's own AI provider (OpenAI or Anthropic) if it has connected one, and otherwise to Meldoc's OpenAI account.
  • Documentation review of pull requests. This runs only with a workspace's own AI key, which receives the documents concerned and the changed code. To find related documents, the added lines of up to five of the most-changed files, at most 800 characters each, are also turned into search vectors, on Meldoc's OpenAI account like every search.
  • With these requests we send no name, email address or account ID of yours — only the question or text and the document passages concerned, which may themselves mention people.
  • OpenAI does not use data sent through its API to train its models, and keeps it for up to 30 days to detect abuse. A workspace's own provider handles data under the workspace's own agreement with it.
  • None of this makes decisions about you that have legal or similarly significant effects.

Who receives your data

Service providers working for us

  • Render — hosts our servers, our database, our search database and our log and metrics stores, in Frankfurt, Germany, and serves our websites.
  • Cloudflare — stores the files and images uploaded to workspaces (Cloudflare R2).
  • OpenAI — AI search and, where a workspace has not connected its own provider, the other AI features.
  • Stripe — payments, subscriptions and invoices; for some purposes Stripe is a controller in its own right, as described above.
  • Resend — sends our emails.
  • Google — Google Analytics as described in the Cookie Policy.

Services you choose

  • GitHub, Bitbucket and GitLab, when you sign in with them or connect a repository.
  • Your workspace's own AI provider (OpenAI or Anthropic), when a workspace connects one; the workspace's account with that provider is used.
  • Your own tools: MCP clients, the command-line tool and webhooks receive what you ask them to fetch, at the addresses you configure.
  • YouTube and Vimeo, when public documentation contains an embedded video: the preview image is served through public.meldoc.io, and the player loads from YouTube or Vimeo when you press play.
  • Figma, when a document embeds a Figma design in interactive mode: it loads from Figma when you open the document.

Other people

Members of your workspaces see your name, email address and activity in them. Public documentation is visible to anyone; it does not show who wrote it, but its content may name people. We disclose data to authorities when the law requires us to.

International transfers

Our servers, database and search database are in the European Union (Frankfurt). Several providers above belong to companies in the United States, which may access or process data there:

  • Render, Cloudflare, Resend, Google and Stripe are certified under the EU–US Data Privacy Framework, and their data processing terms also include the Standard Contractual Clauses adopted by the European Commission.
  • OpenAI: our contract is with OpenAI Ireland Limited; transfers to its US group companies rely on the Standard Contractual Clauses in its data processing addendum.

You can ask us at [email protected] for a copy of these safeguards.

How long we keep it

  • Your account and profile: until you delete your account.
  • Sessions, with their IP address and user agent: until the session ends, at most 90 days after your last activity; a session you sign out of is kept for 30 more days.
  • Sign-in codes: valid for 10 minutes and deleted the day after they expire.
  • Integration tokens, with the IP address last used: until the token is deleted, and 30 days more.
  • Server logs: kept by our hosting provider for up to 30 days. Warnings and errors kept in our log store, including the app's error reports: 30 days.
  • Performance totals: 90 days.
  • Audit log: shown for 7, 30 or 180 days or without limit, depending on the workspace's plan; deleted after 3 years at most.
  • Document history: shown for 7, 30 or 365 days or without limit, depending on the workspace's plan; each version is deleted 2 years after it was saved, and only the latest 500 versions of a document are kept.
  • Deleted documents and projects: erased 30 days after they were deleted, together with the earlier versions of those documents; uploaded files and images stay until a workspace admin deletes them.
  • Deleted workspaces: erased 30 days after they were deleted, except as described below.
  • Commit authors' names, email addresses and usernames: the record of each commit for 30 days; the name, email address and username a workspace links to its members for as long as the workspace exists.
  • Requests to join a workspace: 30 days after they are approved, declined or withdrawn; 90 days if no one answers them.
  • Presence: until you leave the workspace or delete your account.
  • Workspace exports: 7 days.
  • Searches that found nothing: 60 days.
  • Email unsubscribes and blocked addresses: for as long as needed to respect them.
  • Records of which product emails we sent you: until you ask us to delete them.
  • Messages you send us: as long as needed to answer them.
  • Billing records: as long as Czech tax and accounting law requires.
  • Analytics: Google Analytics keeps event data for 2 months and data linked to the analytics identifier for 14 months; for the cookies, see the Cookie Policy.

Clean-up runs every few hours, so data can remain a few hours longer than the period stated.

Deleting your account or a workspace

You can delete your account from your profile. We then delete at once your profile, your sign-in methods, your sessions and your workspace memberships. Each workspace you own is handed to another member or deleted. Some records stay:

  • entries naming you, with your email address, in the audit logs of workspaces you were active in, for up to 3 years, because a workspace's record of what happened in it must stay complete;
  • documents, comments and versions you wrote in other people's workspaces, which then no longer show your Meldoc name;
  • your name and email address as they appear in Git commits, if a workspace syncs a repository you committed to — they come from the repository, not from your Meldoc account, and stay with that workspace;
  • billing records, with us and with Stripe, for as long as the law requires.

When a workspace is deleted, its content is no longer accessible to anyone. 30 days later we erase its projects, documents and their versions, comments, glossary, teams, members, invitations, connected AI keys and integration tokens, and its search index. Its uploaded files stay until you ask us at [email protected] to erase them; its audit log is kept for up to 3 years, and billing records as the law requires.

Your rights

Under the GDPR you can ask us to:

  • give you a copy of your personal data (access), and the data you gave us in a portable format — workspace owners can also export a workspace themselves;
  • correct it — most of it you can edit in your profile;
  • delete it, or restrict how we use it;
  • stop using it where we rely on our legitimate interests (see Your right to object above);
  • and you can withdraw your consent to analytics cookies, as described in the Cookie Policy, and to product emails, in your email settings, at any time.

Write to [email protected]. We answer within one month, and may need to confirm that the request comes from you. You also have the right to complain to a data protection authority, in particular in the EU country where you live or work. Ours is the Office for Personal Data Protection (Úřad pro ochranu osobních údajů), Pplk. Sochora 27, 170 00 Praha 7, uoou.gov.cz.

Security

Sign-in codes, session tokens and integration tokens are stored only as hashes; the AI provider keys and repository access tokens that workspaces connect are stored encrypted; all our sites are served over HTTPS. No method of transmission or storage is completely secure; if a breach puts your data at risk, we will tell you as the law requires.

Changes

We update this policy when what we collect or how we use it changes. The date at the top says when it last did.

Contact us

Questions about this policy or your data: [email protected]. For anything else, see our contact page.