Privacy Policy
Last updated: [DATE]
[LEGAL ENTITY NAME] ("we") runs Qunoq. This page says what we collect, why, and for how long. The short version: we do not store your source code.
What we promise
- We never store your source code. We keep file paths, line ranges, rule ids and short redacted evidence.
- Repository access is read-only.
- We do not sell your data and run no advertising or third-party tracking scripts.
- You can delete your account and all your data; it is removed within 30 days. You can export your data.
Data map
Everything we store, why, and how long. The same table is kept in the repository as docs/data-map.md.
| Data | What exactly | Why | Retention |
|---|---|---|---|
| GitHub profile | Login, display name, email (if GitHub shares it), avatar URL, GitHub user id | Sign you in and show who you are in the app | Until you delete your account (removed within 30 days) |
| GitHub access token | Sealed with AES-256-GCM (envelope encryption); never logged or sent to the browser | Read your repositories on your behalf | Until it expires, you revoke it, or you delete your account |
| Session | SHA-256 hash of a random token, browser user-agent (truncated), timestamps | Keep you signed in | Up to 30 days, or until you sign out |
| Repository metadata | Repository name, owner, default branch, language, size, commit SHA of the scan | Build your inventory and show scan history | While the repository is imported; deleted with your account |
| Findings and crypto assets | File path, line, algorithm, rule id, severity, and an evidence snippet of at most 240 characters with secrets redacted. Key material is never stored, only a fingerprint | Show what was found and where, and track remediation | While the repository is imported; deleted with your account |
| Source code | Not stored. A temporary checkout is read during the scan and deleted afterwards | Not applicable | Deleted at the end of each scan |
| Audit log | Who did what and when for security-relevant actions (sign-in, import, scan, publish, delete) | Security and accountability for your workspace | Life of the workspace; deleted with it |
| Domain claims | Host name and a random verification token | Prove you own a domain before it can be scanned or published | Until you remove the domain |
| Public scanner input | The host you type. Not stored. Your IP address is used in memory for rate limiting only | Run the live TLS check you asked for | Not retained |
| Published summaries | Only if you opt in per repository: severity counts and algorithm families, never paths, lines or snippets | Let you show your status publicly | Until you unpublish or delete the repository or account |
| Waitlist | Email, chosen plan, consent time, and a hash of your delete token. Stored separately from accounts | Tell you when Pro or Enterprise opens | Until you remove yourself with your token, or [WAITLIST RETENTION PERIOD] |
| Feedback and false-positive reports | Your message (up to 2000 characters), the finding and rule id if any, and your user id if signed in | Improve detection rules and the product | Kept with your workspace; your user link is cleared when your account is deleted. Anonymous feedback: [FEEDBACK RETENTION PERIOD] |
| Server logs | [TO BE CONFIRMED BY OPERATOR: request metadata, retention]. Tokens, cookies and source snippets are never logged | Operate and secure the service | [RETENTION PERIOD] |
Legal basis and your rights
[TO BE COMPLETED BY COUNSEL: legal bases (contract, legitimate interests, consent for the waitlist), controller details, international transfers, and a data protection contact.]
Depending on where you live you may have rights to access, correct, export, and delete your data, and to object to processing. Use the export and delete options in your account settings, or contact [PRIVACY CONTACT EMAIL]. To leave the waitlist use the delete token shown when you joined.
Who else sees data
GitHub (sign-in and repository access under the permissions you grant). Hosting, database and email providers: [LIST OF SUBPROCESSORS]. We do not send repository contents to analytics or AI providers.
Security
See Security. Tokens are encrypted at rest; sessions are stored hashed; security-relevant actions are audit logged.
Changes and contact
We will post changes here and update the date above. Contact: [PRIVACY CONTACT EMAIL], [REGISTERED ADDRESS].