Privacy Policy
What we collect, why we collect it, who sees it, how long we keep it, and the rights you have over it. We collect what the product needs and nothing that it does not.
Last updated 21 August 2026
1. Who is responsible
[COMPANY LEGAL NAME] Ltd ([REGISTERED OFFICE ADDRESS], United Kingdom) is the controller of the personal data described in this policy, except where section 4 says otherwise. Questions and requests go to privacy@logg.sh.
2. Who this policy covers
- Visitors to https://logg.sh and to the public changelog pages hosted on it.
- Account holders — people who sign in to logg, alone or as members of an organisation.
- Subscribers — people who give their email address to receive a logg customer’s changelog. For them the customer is the controller and we are the processor; see section 4.
- Contributors whose names or handles appear in the commits, pull requests and issues that a customer connects to logg.
3. What we collect and why
| Data | Where it comes from | Why we process it | Lawful basis |
|---|---|---|---|
| Account details: name, username, email address, avatar, the identifier of the GitHub, GitLab or Bitbucket account you sign in with, and which method you used | Your sign-in provider, or the address you type for an email link | To create and secure your account, identify you in an organisation, and contact you about the Service | Contract |
| Access tokens for the code hosts and tools you connect | The provider, when you authorise logg | To read releases and register webhooks on your behalf. Stored encrypted (AES-256-GCM) and never shown again after connection | Contract |
| Repository data: commit messages, pull and merge request titles and descriptions, tags, release notes, changed-file lists, and the names and handles of their authors; issue titles from Linear | The code host, on your instruction | To generate changelog drafts. We do not fetch the contents of your source files | Contract; our legitimate interest in providing the feature you asked for |
| Content you create: projects, changelog entries, settings, custom domains, webhook endpoints, notification channels | You | To run the product and publish what you choose to publish | Contract |
| Billing records: Polar customer and subscription identifiers, plan, status and renewal date | Polar, our merchant of record | To give your organisation the plan it paid for. Polar holds your payment details and invoices; we never see card numbers | Contract; legal obligation (tax and accounting) |
| Technical data: IP address, browser and device information, request logs, timestamps, rate-limit counters | Your browser or client | Security, abuse prevention, debugging, and keeping the Service available | Legitimate interests (security and operation of the Service) |
| Audit records of significant actions (sign-in, plan changes, publishing, deletions) | Your use of the product | Accountability and incident investigation | Legitimate interests |
| Analytics: pages viewed, approximate location, device type, via Google Analytics 4 | Your browser, only after you accept analytics cookies | To understand how the product is used | Consent |
| Emails we send you and whether they were delivered | Our email provider | Sign-in links, invitations, welcome and service notices | Contract; legitimate interests |
We do not sell personal data, and we do not use it for advertising. We do not make decisions about you by automated means that have legal or similarly significant effects.
4. Data we process on behalf of customers
When a customer enables email subscriptions on a changelog, readers give their address to that customer. We store the address, its confirmation status and preferences, send the emails the customer configures, and nothing else. The customer is the controller; we act only on their instructions under our Data Processing Addendum. The same applies to the contributor names in repository data a customer connects. If you are a subscriber or contributor and want to exercise your rights, contact the customer whose changelog it is; every subscription email carries an unsubscribe link, and we will help the customer respond.
5. AI processing
To draft an entry we send the relevant repository data to the AI providers on our Subprocessors page, which return generated text. We send only what the draft needs, the providers process it to produce a response and not for their own purposes, and we do not permit them to use it to train models.
6. Who we share data with
- Subprocessors that host, store, send email, process payments or run models for us, listed with their locations on the Subprocessors page. Each is bound by a contract that restricts what it may do with the data.
- Services you connect — your code host, issue tracker, chat tools — receive data as required to do what you asked (for example, a release notification posted to your Slack channel).
- Members of your organisation can see the projects, entries, settings and audit records of that organisation.
- The public, for anything you publish. Published pages, feeds and API responses are public and are indexed by search engines and AI agents.
- Authorities, where the law requires it or to protect our rights, our users or the public.
- A successor, if we are acquired or merge; we would tell you before your data is transferred under a different policy.
7. International transfers
We are a United Kingdom company and our servers are hosted by Oracle Cloud Infrastructure in [HOSTING REGION]. Some subprocessors are in the United States. Where personal data leaves the UK or the EEA we rely on an adequacy decision (including the UK–US Data Bridge and the EU–US Data Privacy Framework for certified providers) or on the UK International Data Transfer Addendum and the EU Standard Contractual Clauses with the provider, together with supplementary measures where appropriate.
8. How long we keep data
| Data | Kept for |
|---|---|
| Account and content | Until you delete the account or the content. Deleted records can persist in backups for up to 30 days. |
| Sign-in sessions | 30 days from sign-in, or until you sign out. |
| Email sign-in links | 15 minutes; spent or expired links are removed within a day. |
| Access tokens | Until you disconnect the integration, revoke the token at the provider, or delete the account. |
| Billing records | For the life of the subscription and then as long as tax and accounting law requires (typically six years). |
| Request logs | Up to 30 days. |
| Audit records | For as long as the organisation exists. When you delete your account they are dissociated from you. |
| Analytics | According to Google Analytics’ retention setting (14 months), and only with your consent. |
9. Security
All traffic is encrypted in transit. Access tokens are encrypted at rest with a key held outside the database; sign-in links are stored only as hashes; sessions are bound to HTTP-only cookies. Access to production systems is restricted to the people who run them, and significant actions are written to an audit log. No system is perfectly secure; if we learn of a breach affecting your data we will tell you and, where required, the regulator without undue delay.
10. Your rights
Under the UK GDPR and, where it applies, the EU GDPR, you can ask us to give you access to your personal data, correct it, erase it, restrict or object to its processing, or provide it in a portable form, and you can withdraw consent at any time without affecting what was done before. Two of these are self-service:
- Export — Settings → Account → “Download your data” gives you a JSON file of your profile, organisations, projects and entries.
- Erase — Settings → Account → “Delete account” removes your account and the organisations of which you are the sole member.
For anything else, email privacy@logg.sh. We answer within one month. If you are unhappy with our answer you can complain to the Information Commissioner’s Office (ico.org.uk) or, in the EEA, to your local supervisory authority.
If you are a California resident, the rights to know, delete, correct and not be discriminated against described above apply to you under the CCPA. We do not sell or share personal information for cross-context behavioural advertising.
11. Cookies
The cookies and similar technologies we use, and how to control them, are described in the Cookie Policy.
12. Children
The Service is not directed at children and we do not knowingly collect data from anyone under 16. If you believe we have, tell us and we will delete it.
13. Changes
We will post changes here and update the date at the top. For changes that materially affect how we use your data we will also email account holders in advance.
14. Contact
[COMPANY LEGAL NAME] Ltd, [REGISTERED OFFICE ADDRESS], United Kingdom. Privacy questions: privacy@logg.sh. General: hello@logg.sh.