← Back to GitDoc1. Data controller
The data controller for GitDoc (and the broader CleverAI product family) is AZINOVE SAS, a French société par actions simplifiée registered with the Strasbourg RCS under SIREN 897 432 324, whose registered office is at 13 Rue de Dahlenheim, 67200 Strasbourg, France. Patrick Eiermann is the legal representative (Président).
Privacy contact: privacy@cleverai.ai. We have not formally appointed a Data Protection Officer (DPO) at this stage; we will do so as soon as the scope of our processing activities triggers GDPR Article 37(1).
2. What personal data we collect
We process the following categories of personal data:
- Account information: name, email address, profile picture, organization membership — provided directly by you or retrieved from your identity provider (Google, GitHub, Microsoft). Authentication is delegated to Clerk.
- Usage and telemetry: request timestamps, feature interactions, IP address truncated for anti-abuse purposes.
- Technical data: browser user agent, device type, language preference, server-side error logs (no third-party error-tracking processor).
3. Purposes and legal bases
| Purpose | Legal basis (GDPR Art. 6) |
|---|---|
| Provision of the CleverAI services to you | (b) Performance of a contract |
| Security, fraud prevention, abuse detection | (f) Legitimate interest |
| Product improvement (aggregated, non-identifying) | (f) Legitimate interest |
| Marketing emails (newsletters, feature announcements) | (a) Consent — opt-in required |
| Customer support requests you initiate | (b) Performance of a contract |
4. Recipients and subprocessors
We share personal data with the following subprocessors, each acting under a contract that incorporates GDPR Article 28 obligations:
| Subprocessor | Purpose | Location | Transfer mechanism |
|---|---|---|---|
| Clerk Inc. | User authentication, session management, organization management | US | Standard Contractual Clauses (SCCs) |
| Vercel Inc. | Application hosting, edge runtime, CDN | US | Standard Contractual Clauses (SCCs) |
| Neon Inc. | Managed PostgreSQL database hosting | US/EU (Frankfurt) | Standard Contractual Clauses (SCCs) |
| GitHub, Inc. (a Microsoft company) | Source-code and repository access on the user's behalf — OAuth sign-in, and reading repository content for products that import documentation from a repository (GitDoc). Only reached with a token the user has explicitly authorized. | US | Standard Contractual Clauses (SCCs) |
| Postmark / ActiveCampaign LLC | Delivering the collaborator invitation emails you send from GitDoc | US | Standard Contractual Clauses (SCCs) |
| Google LLC (Google Analytics 4) | Audience measurement — loaded only after you accept the Analytics cookie category | US | EU-US Data Privacy Framework |
5. International data transfers
Some of our subprocessors are based in the United States. Where data is transferred outside the European Economic Area, we rely on either the EU-US Data Privacy Framework (for certified recipients such as Google) or the European Commission's Standard Contractual Clauses (Decision 2021/914) for all other US recipients, supplemented by appropriate technical and organizational measures.
For customers seeking strict EU jurisdiction, our CleverAI Vault product offers a private deployment in EU regions with no third-country transfer.
6. Retention
- Account data — retained while your account is active, deleted within 30 days of account closure (90 days for encrypted backups).
- Usage logs — 12 months for security and abuse detection.
7. Your rights under GDPR
You have the right to:
- Access your personal data (Art. 15)
- Request rectification of inaccurate data (Art. 16)
- Request erasure (Art. 17) — "right to be forgotten"
- Restrict processing (Art. 18)
- Receive your data in a portable format (Art. 20)
- Object to processing based on legitimate interest (Art. 21)
- Withdraw consent at any time (Art. 7(3))
- Lodge a complaint with a supervisory authority — for France, the CNIL
To exercise any of these rights, contact privacy@cleverai.ai. We will respond within one month, extendable by two months for complex requests (GDPR Art. 12(3)).
8. Access by AZINOVE personnel
Authorized AZINOVE staff bound by written confidentiality obligations may access your personal data when strictly necessary for: (a) responding to a support request you initiate; (b) investigating suspected abuse, fraud, or security incidents; (c) legal compliance (subpoena, court order, regulatory request — where lawful, we will notify you); (d) operating, debugging, or maintaining the service. All such accesses are minimized to the data needed for the purpose and logged for audit.
9. Security
We implement appropriate technical and organizational measures to protect personal data, including encryption in transit (TLS 1.3), encryption at rest (database-level), Clerk-managed authentication with MFA support, audit logging, and segregation of duties for production access. Despite these measures, no system is perfectly secure; if we become aware of a personal-data breach affecting you we will notify you and the CNIL within 72 hours as required by GDPR Art. 33-34.
10. Cookies
See our dedicated Cookie Policy for the complete cookie inventory and consent mechanism.
11. Changes to this policy
We may update this Privacy Policy from time to time. Material changes will be communicated via email and/or in-product notice at least 30 days before they take effect. The "Last updated" date at the top of this page reflects the most recent revision.
GitDoc-specific provisions
GitDoc — What We Store, and What We Do Not
GitDoc hosts documentation and exposes it over the Model Context Protocol (MCP). It stores:
- Your account — email address, name and avatar, held by Clerk. When you connect GitHub, Clerk also stores the GitHub OAuth token issued to you.
- Documentation content — the
.mdand.mdxfiles read from the repository you connect, stored as pages in our database so they can be served and searched. - Documentation metadata — name, URL slug, repository, branch, subdirectory, and the timestamp of the last sync.
- Collaborator invitations — the email address you type when inviting someone, their role, and a hash of the single-use invitation token. The invitation email itself is delivered by Postmark.
- Personal MCP tokens — only a SHA-256 hash and the first few characters of the token. The secret is shown once, at creation, and cannot be recovered from our database afterwards.
- Waitlist entries — if you submit the form on the GitDoc marketing page, the name, email, company, phone number and use-case description you typed are forwarded to the Azinove CRM so we can reply. GitDoc itself stores no copy.
The application runs on Vercel and the database is Neon (PostgreSQL). Audience measurement uses Vercel Web Analytics, which sets no cookie, and Google Analytics 4, which is loaded only if you accept the Analytics category in the cookie banner — see the Cookie Policy.
No AI processing of your documentation
GitDoc performs no AI processing and sends your documentation to no model provider. There is no model call anywhere in the product: no summarization, no embeddings, no generation, no classification. The subprocessor table above is the complete list of who receives data, and no model vendor appears in it.
GitDoc is the MCP server: an AI agent you connect yourself — in your editor, your terminal, or your own tooling — reads your documentation through it, authenticated with a token you minted. That agent, and the model behind it, are governed by whatever agreement you have with its vendor, not by us. Deleting the token ends that access.
Repository access uses your own GitHub credential
When you connect a repository, GitDoc calls the GitHub API with your OAuth token, so it can reach exactly the repositories GitHub grants you and nothing else. Another customer's credential is never used to read your repository, and yours is never used to read theirs. A server-side token exists only for public Azinove-owned repositories and is restricted by an owner allowlist; it cannot reach a customer's private repository.
GitDoc reads repository content; it does not write to your repository. The files it copies are the Markdown pages under the branch and subdirectory you selected.
Inviting collaborators
When you invite someone, you provide us with a third party's email address. We process it for one purpose — delivering the invitation and matching the person to the invitation when they accept — and we keep the row afterwards as an audit trail of who was invited, by whom, and whether they accepted. Invite only people who expect to hear from you about your documentation. You may revoke a pending invitation at any time; ask us at privacy@cleverai.ai to erase an invitation record entirely.
Draft and published documentation
A documentation is a draft until you publish it. Drafts are readable only by the owner and the collaborators they invited — the same rule applies to the web viewer and to the MCP server. Publishing makes it readable by anyone with the link, which is what publishing means; do not publish documentation built from a private repository unless you intend that content to be public.
Deleting your documentation
Pages are kept for as long as the documentation exists. Deleting a documentation deletes its pages, its collaborator list and its invitations from our database; deleting your account removes your documentation along with it, within 30 days (90 days for encrypted backups). A deleted MCP token stops working immediately. Your repository is untouched throughout: GitHub remains the source of truth, and the copy we held is simply gone.