Privacy Policy
Effective 6 November 2026
This Privacy Policy explains how DeepGraph collects, uses, and protects personal data when you visit deepgraph.app, use the DeepGraph web app, or contact us. It also explains how we handle information about the contributors whose Git activity appears in the repositories you analyze.
In short:
- we collect only what we need to run DeepGraph and bill for it;
- we do not sell personal data or use it for advertising;
- we use no advertising or cross-site tracking cookies, and analytics cookies only if you allow them; and
- you can delete your account and its data yourself at any time.
Who we are
DeepGraph is operated by A.I. Victor Chicu, a sole proprietorship registered in the Republic of Moldova under IDNO 1026023023591, with its registered address at Bulevardul Moscova 9/5, Chișinău, Republic of Moldova (“DeepGraph”, “we”, “us”).
For your account, billing, and website data, we are the data controller. For contributor information inside the repositories you analyze, we process personal data on your behalf, as described in section 4.
Privacy questions and requests: support@deepgraph.app.
Data we collect
Account data
Your name, email address, and profile picture, the display name you choose, and, if you sign in with email, a securely hashed password. When you sign in with GitHub, GitLab, or Bitbucket, we receive your profile from that provider and store the connection so we can access the repositories you authorize. Provider access tokens are stored encrypted.
Repository data
The repositories you analyze, their Git history, and the reports we generate from them. This includes the contributor names and email addresses recorded in commits. For local analysis, your browser uploads the Git history (the .git directory) of the repositories you select, not your working files.
For GitHub repositories you connect through the DeepGraph GitHub App, we also read their delivery data to show DORA numbers: pull requests, deployments, workflow runs, releases, and tags. This includes each pull request’s title and the GitHub username of its author.
Billing data
Your plan, trial dates, billing status, and a history of plan changes and transactions. Payments are processed by Paddle, our merchant of record. We do not receive or store your card details.
To give each person only one free trial, we also keep a record that an email address or a GitHub, GitLab, or Bitbucket account has already had a trial. The record is a one-way, salted hash: it does not contain your email address, your account, or your name, and we cannot turn it back into them. We can only check whether an email address or provider account signing up matches one that already had a trial. Addresses that reach the same inbox count as one, for example name+anything@example.com and name@example.com, or Gmail addresses that differ only in dots.
Session and security data
For each signed-in session, we record when it started and was last used and the browser and device type reported by your browser, so you can review your sessions in Settings → Security. We use IP addresses temporarily to limit request rates and protect sign-in against abuse.
Usage analytics data
Only if you accept analytics cookies, Microsoft Clarity records how you use DeepGraph, on our public pages, such as the home page, pricing, features, blog, help, legal pages, and sample reports, and in the app, such as your projects, reports, and settings: the pages you view, the layout of each page, clicks, scrolling, and mouse movement, and your browser, device, and approximate location.
Clarity receives no text from these pages. Your browser replaces every word on screen with placeholder characters before anything is sent, including project and repository names, contributor names and email addresses, numbers, and code. Images, links, and what you type in form fields are left out, and clicks on links to other websites are not recorded. In page addresses, the parts that name a project, deploy stream, contributor, or team are replaced before they are sent, so a report appears only under a random identifier, and app pages always show the same page title. We do not link this data to your account.
If you accepted analytics cookies before November 6, 2026, Clarity records only our public pages until you accept again.
Messages you send us
The name, email address, and message you send through the contact support form or by email.
We do not intentionally collect special categories of personal data, such as health or political opinions.
How and why we use it
- To provide DeepGraph: creating your account, running analyses, showing reports, and keeping your sessions secure. Legal basis: our contract with you.
- To bill for plans: managing trials, plans, and cancellations, and keeping records required by accounting and tax law. Legal basis: our contract with you and our legal obligations.
- To send service emails: sign-in codes, security notices, and important changes to DeepGraph or these policies. Legal basis: our contract with you.
- To improve and protect DeepGraph: fixing problems and preventing abuse. Legal basis: our legitimate interest in running a reliable and secure service.
- To give one free trial per person: keeping the hashed trial record described in section 2, so deleting an account and signing up again with the same email address or provider account does not start another trial. Legal basis: our legitimate interest in preventing abuse of free trials.
- To understand how DeepGraph is used: usage analytics with Microsoft Clarity, which helps us improve our public pages and the app. Legal basis: your consent, which you can withdraw at any time in Cookie settings.
- To answer you: replying to support messages. Legal basis: our legitimate interest in responding to people who contact us, or steps you ask us to take before entering a contract.
We do not send marketing emails today. If we start, we will ask for your consent where the law requires it, and every such email will include a way to unsubscribe.
Contributor information in your repositories
Commits contain the names and email addresses of the people who made them, and pull requests contain the GitHub usernames of their authors. When you analyze a repository, DeepGraph processes this information on your behalf and according to your instructions: to build contributor profiles, link identities, and show activity and delivery numbers. You decide which repositories to analyze, can link or exclude contributor identities, and can delete analyses at any time.
If you are a contributor and want to know about or object to how your information is used in someone’s DeepGraph reports, please contact the person or organization that analyzed the repository. You can also write to us at support@deepgraph.app, and we will help direct your request.
Who we share it with
We share personal data only with the service providers that help us run DeepGraph, each limited to what it needs:
- Hosting and infrastructure: Cloudflare, which delivers the website and protects traffic to our API, and the provider of the server where the API and database run.
- Payments: Paddle, which processes purchases as merchant of record under its own privacy notice.
- Repository providers: GitHub, GitLab, and Bitbucket, when you sign in with them or connect repositories.
- Email delivery: our email service provider, which sends sign-in codes and service emails.
- Usage analytics: Microsoft, through Microsoft Clarity, only if you accept analytics cookies, under its own privacy statement. It receives no text from your projects or reports, as described in section 2.
We may also disclose personal data:
- when the law requires it, such as a valid request from a court or public authority;
- to protect our rights, the safety of our users, or to investigate fraud or abuse; and
- to a buyer or successor if DeepGraph is sold or merged, under this Policy.
We never sell personal data.
International transfers
DeepGraph is operated from the Republic of Moldova, and some of our service providers process data in other countries, including the United States. Where the law requires it, we rely on appropriate safeguards for these transfers, such as the European Commission’s Standard Contractual Clauses offered by our providers.
How long we keep it
- Account, repository, and report data: until you delete the analysis or your account. Deleting your account in Settings permanently removes your analyses, reports, sessions, and account data, except the hashed trial record.
- Delivery data from GitHub: until you remove the repository from DeepGraph, disconnect GitHub, or delete your account.
- Sessions: signed-in and guest sessions expire after thirty (30) days, or earlier when you sign out.
- Local uploads: uploaded Git history is used to build your analysis and is deleted when the analysis is rebuilt or deleted, or when you delete your account; an upload that does not finish is deleted seven days after it last received data, and temporary copies used to build an analysis are removed.
- Hashed trial record: kept after you delete your account, so the same email address or provider account does not get a second free trial. It holds no email address, name, or account.
- Billing records: Paddle, as merchant of record, keeps payment and invoice records under its own legal obligations. Our copy of your plan and transaction history is deleted with your account.
- Messages you send us: for as long as needed to handle your request and any resulting relationship.
- Usage analytics data: Microsoft keeps Clarity data for a limited period under its own retention rules.
Your rights
Depending on where you live, you may have the right to:
- access the personal data we hold about you;
- correct inaccurate data, or delete your data;
- restrict or object to processing based on legitimate interest;
- receive your data in a portable format, where processing is based on contract or consent; and
- withdraw consent at any time, where processing is based on it.
You can update your name and delete your account yourself in Settings. For other requests, write to us at support@deepgraph.app. We will answer within the time required by law, usually within one month. We may need to verify your identity first.
If you believe we handle your data unlawfully, you can complain to the National Center for Personal Data Protection of the Republic of Moldova or, if you are in the European Union or European Economic Area, to the data protection authority where you live or work.
Cookies and browser storage
DeepGraph uses essential cookies, which the service needs to work and which are always on, and optional analytics cookies, which are set only if you accept them. We do not use advertising or cross-site tracking cookies.
Essential cookies:
- Session cookies: keep you signed in, or keep your guest session, for up to thirty (30) days.
- Sign-in cookies: short-lived cookies that protect the sign-in flow with GitHub, GitLab, Bitbucket, or email.
- Security cookies: Cloudflare may set cookies that protect the website against bots and attacks.
Optional analytics cookies:
- Microsoft Clarity: cookies that let Clarity recognize your visits to DeepGraph and group the pages you view, as described in section 2.
When you first visit, a cookie notice lets you accept or reject analytics cookies, or choose them in Cookie settings. If you accepted analytics cookies before they covered the app, the notice asks again, and your earlier choice applies until you choose. Analytics cookies stay off until you choose; closing the notice only hides it, and it appears again the next time you load DeepGraph. You can change your choice at any time with Cookie settings at the bottom of every public page; if you reject analytics cookies after accepting them, Clarity stops and its cookies are removed.
DeepGraph also uses your browser’s local storage to remember your cookie choice and preferences, such as your theme and report views, and to restore your last project after a reload. This data stays in your browser. You can clear it, and your cookies, in your browser settings; you will then be signed out and your preferences reset.
Security
We protect personal data with measures such as encrypted connections, encrypted provider tokens, hashed passwords and session tokens, and access limited to the data each part of the service needs. No system is perfectly secure, but we work to protect your data and will notify you and the authorities of a breach where the law requires it.
Children
DeepGraph is not intended for children under sixteen (16), and we do not knowingly collect their personal data.
Changes to this Policy
We may update this Policy. We will post the new version on this page with a new date, and notify you by email or in the app about material changes.
Contact
For any question about this Policy or your personal data, write to support@deepgraph.app, or by post to A.I. Victor Chicu, Bulevardul Moscova 9/5, Chișinău, Republic of Moldova.