Privacy Policy

Gitmayo (“we”, “us”) turns activity from repositories you select into plain-English summaries. This policy explains how we handle personal data. We read activity metadata and which files changed; we never store source code or diffs.

Information we collect

• Account details: your GitHub username, user ID, email address, avatar, and details for any additional GitHub accounts you connect.
• Terms agreement: the Terms of Service version you accepted and the time of acceptance, linked to your account. This is separate from optional analytics or marketing choices.
• Repository discovery metadata: GitHub repository ID, full name, public/private visibility, default branch, and your selection choices.
• Activity metadata: commit subjects; pull-request and issue titles, bounded descriptions, labels, assignees, milestones, linked issue numbers and review timestamps; release titles and bounded notes; deployment and workflow status; branch and repository names; and timestamps, only for repositories you select.
• Reporting context: the product description, target customer, roadmap initiatives, reporting priorities, and known risks that you choose to save for a repository.
• Owner-provided report context: generated summaries and optional context you add, such as milestones, business meaning, blockers, decisions, risks, and next steps.
• External delivery settings and review records: names, email addresses and roles for up to ten external recipients, delivery preferences, approvals, attachments, and delivery outcomes. Emails are separately addressed.
• Investor sharing: email addresses and a company name for investors you invite, their acceptance, and the approved investor reports you choose to share with them. Invited investors sign in with a one-time email link; we store their email address and which companies share with them. Investors see only the report text you shared, never your repositories, evidence or drafts.
• Credentials: GitHub access tokens, encrypted at rest and used only on our servers.
• Settings: cadence, timezone, tone, email choices, and other account preferences.
• Technical data: restricted security and diagnostic logs; aggregate report-generation outcomes, missing-context counts, and deterministic prose-quality scores that contain no report text or account, repository, report, recipient, or prompt identifier; and, only with your consent, limited public-page usage and performance measurements.
• Messages: information you send through our contact form.

Information we do not collect

• Source-code or file contents, diffs and patches. To see which parts of the product changed, we read each commit's changed-file list and line counts from GitHub; GitHub returns the change text in the same response, which we discard immediately without storing it or sending it to AI. We keep only derived facts such as product-area names, never file paths.
• Workflow logs, generated files, and commit bodies.
• Payment-card details; there is no paid billing at this time.

Why we use information

We use it to authenticate you; retrieve and categorise selected activity; generate, display, export, and deliver reports; provide support; prevent abuse; and maintain the security, reliability, and performance of Gitmayo. We do not sell personal data or use it for third-party advertising.

Where UK or EU data-protection law applies, we rely on performance of our contract with you, consent for optional processing such as analytics, compliance with legal obligations, and our legitimate interests in operating and securing the Service. You may withdraw consent at any time without affecting earlier lawful processing.

Who we share information with

We share only the information needed with:

• GitHub, when you sign in or ask us to retrieve activity from repositories you select;
• hosting, database, authentication, security, and monitoring providers that operate and protect the Service;
• Cloudflare Turnstile, when email registration is enabled, which processes browser and technical security information to check for automated abuse; we do not include your password, report text or repository data in the verification request;
• an AI processing provider that receives categorised activity metadata and context needed to generate a report, excluding source files, diffs, access tokens, and recipient details;
• email delivery providers that receive the address and approved content needed to send each message;
• an analytics provider hosted in the EU that receives only counts of product events, such as how many reports were generated or approved, with no account, repository, report, email or IP address attached; and
• professional advisers, regulators, courts, or law-enforcement bodies where reasonably necessary or legally required.

Providers act under contracts and may use subprocessors. Ask privacy@gitmayo.com for current recipient categories and applicable international-transfer information.

International transfers

Some providers may process information outside your country. Where required, we use recognised safeguards such as adequacy regulations or approved contractual clauses. You may contact us for information about safeguards relevant to your data.

How reports reach other people

Reviewing before sending is the default. A report is generated for you first, and each external recipient draft waits for your approval of that exact version before it can be sent. Nothing goes to a recipient because a report was generated.

You can turn on scheduled automatic sending in Settings instead. That is a separate, explicit choice and it applies only to a report that has already passed validation and is bound to the exact version, recipients and consent you approved. It never widens who receives a report, and it never sends a report that failed validation.

Changing the report, its owner-provided context, or your recipient settings withdraws that authorisation: the affected draft stops being approved, must be regenerated, and needs your approval again before any send. You can cancel or delay a pending delivery at any time before it is claimed for sending.

If the email provider’s response is ambiguous, we treat the outcome as unresolved rather than guessing. The delivery stays in a sending state for manual reconciliation and is never retried automatically, so an uncertain result cannot become a duplicate message. We record a non-personal audit and idempotency fact for that attempt.

Retention and deletion

We keep account details, settings, selected activity metadata, and reports while your account is active. Delivery records and logs are kept only while needed to deliver reports, prevent duplicate sends, secure the Service, resolve disputes, or comply with law. When you delete your account, we delete or anonymise associated personal data unless a limited record must be retained for legal or security reasons. Backups expire through their normal cycle.

A successful repository refresh removes discovery rows that are no longer available unless an older summary still needs the repository identity to remain readable. We deselect such a repository from future activity pulls. Completed delivery records may preserve non-personal audit and idempotency history to prevent duplicate sends after recipient and message details are removed.

Security

We use encryption in transit and at rest where appropriate, server-side token handling, access controls, monitoring, and other technical and organisational safeguards. No system is completely secure, so we also minimise the data we hold and restrict access.

Your rights

Depending on applicable law, you may ask to access, correct, delete, restrict, or export your personal data; withdraw consent; or object to processing based on legitimate interests. You may also complain to your local data-protection regulator. You can manage some data in Settings or email privacy@gitmayo.com. We may need to verify your identity before acting.

Cookies and optional analytics

Necessary cookies keep you signed in and protect the Service. A first-party preference remembers your privacy choice for up to 180 days. We do not use advertising or cross-site tracking cookies.

Optional public-page analytics and performance measurement are off until you choose “Accept optional analytics”. Rejecting leaves every Gitmayo feature available. Measurement is limited to public information pages and excludes signed-in routes, report content, repository details, account identifiers, form contents, query parameters, session replay, profiling, and screenshots. Use Privacy choices on this privacy page to change or withdraw your choice. Withdrawal stops future optional collection but cannot recall measurements already sent. A material new provider category or purpose requires a new disclosure and choice.

Children

Gitmayo is not directed to children and is not intended for anyone under 16.

Changes

We will update the date above and give reasonable notice before a material new use of personal data begins.

Contact

Questions or rights requests: privacy@gitmayo.com.