Privacy Notice
Draft for owner review. Not legal advice and not reviewed by a lawyer. Replace the bracketed placeholders before public launch.
Last updated: [date]. Operator: [legal name and contact address of the operator].
What we collect
- Account: your email address, used to sign you in with one-time links and to send account and billing messages. If you sign in with GitHub: your GitHub user id, username, display name, avatar address, and verified primary email. We do not store your GitHub access token and do not request repository access.
- Sessions: a one-way hash of your session token, when it was created and last used, and your browser's user-agent string. We do not store IP addresses with sessions; we use them briefly for rate limiting.
- Submissions: the
app.pyfiles you upload for grading, or fetch from a public GitHub repository (with the repository, path, and commit), with a hash, size, lab, and timestamps. - Kompile Scan: the websites you add, how you verified them, and each scan's findings. Findings describe what we observed (headers, certificate details, which well-known files were reachable) and never include the contents of exposed files.
- Results: check outcomes and short diagnostic evidence produced by grading, and your attempt history.
- Billing: subscription status and dates received from Stripe. Card details are entered on Stripe's pages and never reach our servers.
- Product events: a small set of events (for example sign-up, starter download, submission, completion, checkout started) with timestamps and lab or attempt identifiers. They never include your source code or credentials.
- Operational logs: server and worker logs used to keep the service running. We avoid logging email addresses, tokens, and source code.
How submissions are processed
Each submission runs once in a fresh isolated sandbox operated by our sandbox provider (E2B), without internet access, and the sandbox is destroyed after grading. Source content is deleted 7 days after submission by a scheduled job. Check results and history are kept while your account exists.
Your scans are never used for training
We do not use your sites, scan results or reports to train or improve any model, and we do not copy them into any dataset. Kompile Scan is improved using only test sites and practice applications that we build and run ourselves. Your scan reports are kept only so you can see them in your account, and are deleted with your account.
Service providers
- [Database and hosting provider, for example Railway]: database and application hosting.
- GitHub: sign-in, and reading public files you choose to submit.
- [Email provider, for example Resend]: delivering sign-in links.
- Stripe: payments and subscription management.
- E2B (if used): isolated code execution for grading.
Your choices
You can request access to or deletion of your account data by emailing [support email]. Deleting your account removes your profile, attempts, results, and remaining source content. Stripe retains payment records as required by law.
Changes
We will update this page when these practices change.