Skip to content
Draft, pending legal review. This page has not been reviewed by a lawyer. Text in [square brackets] is a placeholder to be completed before launch.

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.

What Qunoq stores, why, and for how long
DataWhat exactlyWhyRetention
GitHub profileLogin, display name, email (if GitHub shares it), avatar URL, GitHub user idSign you in and show who you are in the appUntil you delete your account (removed within 30 days)
GitHub access tokenSealed with AES-256-GCM (envelope encryption); never logged or sent to the browserRead your repositories on your behalfUntil it expires, you revoke it, or you delete your account
SessionSHA-256 hash of a random token, browser user-agent (truncated), timestampsKeep you signed inUp to 30 days, or until you sign out
Repository metadataRepository name, owner, default branch, language, size, commit SHA of the scanBuild your inventory and show scan historyWhile the repository is imported; deleted with your account
Findings and crypto assetsFile 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 fingerprintShow what was found and where, and track remediationWhile the repository is imported; deleted with your account
Source codeNot stored. A temporary checkout is read during the scan and deleted afterwardsNot applicableDeleted at the end of each scan
Audit logWho did what and when for security-relevant actions (sign-in, import, scan, publish, delete)Security and accountability for your workspaceLife of the workspace; deleted with it
Domain claimsHost name and a random verification tokenProve you own a domain before it can be scanned or publishedUntil you remove the domain
Public scanner inputThe host you type. Not stored. Your IP address is used in memory for rate limiting onlyRun the live TLS check you asked forNot retained
Published summariesOnly if you opt in per repository: severity counts and algorithm families, never paths, lines or snippetsLet you show your status publiclyUntil you unpublish or delete the repository or account
WaitlistEmail, chosen plan, consent time, and a hash of your delete token. Stored separately from accountsTell you when Pro or Enterprise opensUntil you remove yourself with your token, or [WAITLIST RETENTION PERIOD]
Feedback and false-positive reportsYour message (up to 2000 characters), the finding and rule id if any, and your user id if signed inImprove detection rules and the productKept 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 loggedOperate and secure the service[RETENTION PERIOD]

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.

Cookies

Essential cookies only. See the cookie notice.

Changes and contact

We will post changes here and update the date above. Contact: [PRIVACY CONTACT EMAIL], [REGISTERED ADDRESS].