Privacy notice

The legal identity and contact details of the data controller.

• Controller name, registered address and privacy contact — owner to verify

The account and service data needed to operate Gitpin.

• GitHub account ID and verified primary email for owner identity
• Repository content, scoped-key metadata and operational records
• Usage, invoices and payment-provider references
• First-touch source supplied during account creation

The purposes and legal bases must be stated in the approved notice.

• Operating accounts and repositories
• Metering, billing, security and recovery
• Lawful bases and any legitimate-interest assessment — owner to verify

Explain essential session cookies and the exact analytics configuration actually deployed.

• Owner session and security cookies
• Cookieless PostHog measurement only if enabled and verified
• No repository content, secrets or private query parameters in analytics

Identify the processors actually used and the work each performs.

• Hosting, storage, identity, payment and diagnostic providers
• Current processing agreements and transfer safeguards — owner to verify

Describe actual retention, recovery and backup behavior.

• Repository deletion versus retained usage and billing records
• Backup retention and erasure limits
• Account closure and required retention periods — owner to verify

Describe applicable rights and how a person can exercise them.

• Access, correction, deletion, portability and objections where applicable
• Verified privacy contact and supervisory authority — owner to verify

Provide the approved contact and current version.

• Privacy contact — owner to supply
• Notice changes and effective dates