PRIVACY · RETENTION · DELETION
Keep only what the boundary requires.
This notice covers customer identity, organization control data, inquiries, billing records, repository metadata, jobs, and encrypted receipts. It does not authorize unrelated marketing use.
- VERSION
- privacy-v1
- EFFECTIVE
- 30 August 2026
1. What is processed
We process identity and organization identifiers, verified email details, policy acceptances, billing status, GitHub App installation and sanitized repository metadata, scan job state, reduced encrypted receipts, and messages you deliberately submit. Repository source is acquired transiently for an authorized scan and is not the durable product record.
2. Purposes and basis
Data is used to review access requests, provide and secure the contracted B2B service, enforce tenant and billing authority, answer support, prevent abuse, meet accounting obligations, and investigate incidents. Depending on the activity, processing is necessary for the contract, legitimate security interests, legal obligations, or the consent expressed on a public form.
3. Service providers
Current processors support hosting and compute, authentication, GitHub repository authorization, managed PostgreSQL, payment processing, and transactional email. In practice these include Vercel, Clerk, GitHub, Stripe, the configured database provider, and Resend. Each receives only the data needed for its role.
4. Retention
Encrypted receipts are retained for 30 days by default; job and security-audit records for 90 days; operational logs for 14 days; disconnected repository metadata for 7 days. Contact, early-access, and support messages are retained for 90 days unless a continuing customer or legal need requires a narrower record. Billing and accounting records follow mandatory legal retention.
5. Deletion and rights
Authorized organization members can use the product’s receipt deletion controls. For access, correction, export, objection, restriction, or deletion requests, use the contact form. Requests are verified against the relevant identity and organization before data is disclosed or changed. Some audit, dispute, fraud-prevention, or accounting records cannot be erased immediately.
6. International processing and security
Providers may process data outside Norway under their applicable safeguards. We use tenant-scoped authorization, short-lived repository authority, encrypted receipts, separated runtime roles, audit records, and bounded email content. No system is risk-free; incidents are handled under the published security process.
7. Contact and versioning
Seal of Sigmund is a founder-operated prelaunch service based in Norway. Use the contact page for privacy requests. Material changes create a new privacy version; organization acceptance is recorded during onboarding.