# Privacy Policy > How TrackForge handles your data, cookies, and music catalogue information. *Published by [TrackForge](https://trackforge.studio)* Effective Date: 2 October 2026 | Last Updated: 2 October 2026 --- Adaptive Intelligence, trading as **TrackForge**, is committed to protecting your privacy. This Privacy Policy explains how we collect, use, store, and share your personal data when you use the TrackForge platform (the "Service"). We are the data controller. Our registered office is in England and Wales. For questions about this policy, contact us at privacy@trackforge.studio. ## 1. Data We Collect ### Account Data - Name and email address (provided at registration) - Organisation name (if applicable) - Authentication credentials (managed by our authentication provider, Zitadel) ### Catalogue Metadata - Track metadata: ISRCs, titles, artists, durations, album information - Rights metadata: writer names, IPI numbers, publisher names, splits - Registration data: PRO registrations, MLC status, territory coverage ### Usage Data - Service usage patterns (pages visited, features used) - Device and browser information - IP address (for security and rate limiting) ### Free Public Tools and API When you, or software acting for you such as an AI assistant, use the free ISRC Lookup, the CWR tool or the public API, we record each request: the ISRCs requested or found, the kind of input, the outcome, the user agent, the origin and referring site, and a keyed one-way hash of the IP address. The IP address itself is not stored in this log. When a request comes through our MCP server, we also record the name and version the AI assistant reports and a pseudonymous session key. ### Report Requests If you ask for a follow-up review, directly or through an AI assistant using our MCP server, we store your name, email address, optional organisation, the ISRCs or catalogue description you give, the consent you confirmed, the AI assistant's name and version, and a keyed hash of the IP address. We use them only to contact you about that request. A person at TrackForge reviews the catalogue before anything is sent to you. ## 2. How We Use Your Data | Purpose | Legal Basis | |---------|------------| | Provide and operate the Service | Contract performance | | Enrich metadata via external sources | Contract performance | | Generate and anchor certifications | Contract performance | | Process writer/IPI data for certification | Legitimate interest | | Security, fraud prevention, rate limiting | Legitimate interest | | Service communications | Legitimate interest | | Measure use of the free public tools and API, and prevent abuse | Legitimate interest | | Analytics on the public website | Consent | | Follow up on a report request you asked for | Consent | ## 3. Certification & Blockchain Privacy > **Privacy by Design:** No personal data is ever written to the Bitcoin blockchain. The blockchain anchor contains only a Merkle Root hash -- a 64-character hexadecimal cryptographic digest from which no personal data can be derived. ### Personal Data in Certifications | Data | Classification | Basis | |------|---------------|-------| | Writer names | Personal data | Legitimate interest | | IPI numbers | Professional identifier | Legitimate interest | | Writer splits | Commercial data | Contractual | | SHA-256 hash | Not personal data | N/A | ### Public Verification Page The verification page at [trackforge.studio/verify](https://trackforge.studio/verify) displays only: - ISRC, certification date, hash, Merkle Root - Blockchain transaction ID, certification tier, methodology version Never displayed: writer names, IPI numbers, splits, track titles, or any commercially sensitive data. The page operates without cookies, tracking, or analytics. ## 4. Data Sharing We share data with: - **Enrichment sources** -- ISRCs are sent to external APIs (Spotify, MusicBrainz, Discogs, Last.fm, PRS, MLC) to retrieve and verify metadata. Only ISRCs and track identifiers are shared, not your account data. - **Authentication provider** -- Zitadel processes your authentication data under their privacy policy. - **Bitcoin blockchain** -- Only the Merkle Root hash is published. No personal data. - **OpenTimestamps calendars** -- Hash submitted for timestamping. No personal data. - **Analytics providers, only with your consent** -- PostHog (EU cloud) for product analytics, and Google Analytics 4 delivered through Cloudflare Zaraz, receive page and feature usage from the public website. We do not sell your personal data. We do not share it with advertisers. ## 5. Data Retention | Data Type | Retention | |-----------|-----------| | Certification records | Indefinite (the product) | | Blockchain anchors | Permanent (immutable) | | Audit trail | 6 years (regulatory) | | Account data | Duration of account + 90 days | | Working enrichment data | Per retention schedule | | Public tool and API request log | 12 months; the IP address hash is removed after 90 days | | Report requests | 24 months after the request, or sooner if you ask us to delete it | ## 6. Your Rights Under UK GDPR and the Data Protection Act 2018, you have the right to: - **Access** -- request a copy of data we hold about you - **Rectification** -- correct inaccurate data - **Erasure** -- request deletion of your data, subject to legal obligations and the blockchain exception below - **Restriction** -- limit how we process your data - **Portability** -- receive your data in a structured format - **Objection** -- object to processing based on legitimate interest > **Blockchain Exception:** The SHA-256 hash on the Bitcoin blockchain cannot be deleted or modified. However, this hash is a cryptographic digest and is not personal data. Underlying personal data (writer names, IPIs) in our databases can be deleted on request -- the hash will remain but will no longer be linkable to personal data. To exercise any right, contact privacy@trackforge.studio. We will respond within 30 days. ## 7. Data Security - Encryption in transit (TLS) and at rest - Role-based access controls - Operator audit logging on all data access - Regular security reviews ## 8. International Transfers Your data is primarily stored in the EU/EEA (Neon PostgreSQL). Some enrichment queries are sent to international APIs (e.g., Spotify, MusicBrainz), and, with your consent, analytics data may be processed by Google and Cloudflare outside the UK and EEA. These transfers rely on standard contractual clauses or adequacy decisions as appropriate. ## 9. Cookies The signed-in TrackForge application uses essential cookies for authentication and session management. We do not use advertising cookies. On the public website, analytics (PostHog and Google Analytics 4 through Cloudflare Zaraz) run only after you accept them in the cookie banner; until then nothing is captured. You can accept or decline analytics at any time on the privacy page at [trackforge.studio/privacy](https://trackforge.studio/privacy). The public verification page at /verify uses no cookies at all. ## 10. Changes to This Policy We may update this policy from time to time. Material changes will be notified via email or prominent notice on the Service at least 30 days before taking effect. ## 11. Contact & Complaints Adaptive Intelligence (trading as TrackForge) Email: privacy@trackforge.studio You have the right to lodge a complaint with the Information Commissioner's Office (ICO) at [ico.org.uk](https://ico.org.uk) if you believe your data protection rights have been violated. --- *This document is a draft prepared for legal review. See the full [data handling documentation](https://trackforge.studio/certification/for-lawyers/data-handling-gdpr) for certification-specific GDPR details.* *Copyright Adaptive Intelligence. All rights reserved.* --- Source: [https://trackforge.studio/privacy](https://trackforge.studio/privacy)