Privacy Policy

What we collect

• Session ID — a random identifier stored in your browser that links your progress to a session. It is not tied to a real-world identity unless you optionally provide an email below.
• Challenge progress — which challenges you have opened, how many times you ran checks, and whether you submitted a solution.
• Submission and check results — pass/fail outcomes and timing information for visible and hidden validation checks.
• Waitlist and feedback — if you choose to join the waitlist or submit feedback, we store the interest category, optional email, and optional message you provide.
• Basic server logs — IP address, request path, and timestamps for security monitoring and abuse prevention. Logs are not sold or shared.

Code execution

Buglyst runs checks in a controlled server-side execution environment for Buglyst-provided practice labs. When you run checks or submit a solution, the contents of your workspace (the files you have edited) are sent to that environment, which runs the validation commands defined by the challenge and returns pass/fail output. Your code is not sold, shared with third parties, or used to train machine learning models.

Do not upload private or proprietary code. Beta execution is limited, monitored, and being hardened.

What we do not do

• We do not sell your data.
• We do not serve behavioural advertising.
• We do not share personal data with third parties except as required by law.
• We do not require account registration to use the platform.

Data retention

Workspace files are automatically deleted after 24 hours of inactivity. Progress records are retained for up to 90 days from last activity and then purged. Waitlist entries are retained until you request deletion or the waitlist closes.

Your rights

You may request deletion of any data associated with your session or email address by contacting us at privacy@buglyst.com. We will respond within 30 days.

Changes to this policy

We may update this policy as the product evolves. Material changes will be announced on the site. Continued use after a change constitutes acceptance.