1. Overview
CompileBytes is an account-free developer-tool service. We limit the information we collect to what is needed to run, secure, understand, and improve the Service. We do not sell personal information or use it for targeted advertising. Use of the Service is also governed by our Terms of Service.
2. Data we handle
Data stored in your browser
Editors and utilities may save code, files, input, command-line arguments, layout, theme, and editor settings in your browser’s local storage. This normally stays on your device until you clear it.
Hosted execution
When you run a hosted compiler or database playground, the code, files, input, and arguments required for the run are sent to our execution API. Do not submit passwords, API keys, confidential information, or sensitive personal data.
Share links
When you create a share link, the included code, files, input, arguments, and relevant settings are stored in encrypted form. Anyone with the link can view and copy that snapshot.
Technical and analytics data
Like most online services, we process IP addresses, request routes, browser and device information, response times, security signals, and error details. Where Google Analytics is configured, it also measures page and feature usage and may set analytics cookies.
3. How we use data
We use this information to:
- provide code execution, sharing, downloads, and other requested features;
- protect the Service, enforce rate limits, and prevent abuse;
- find errors, monitor performance, and improve useful features; and
- comply with legal obligations and protect our rights.
4. Service providers
We use DigitalOcean for hosting, Cloudflare for delivery, security, and Turnstile verification, Sentry for error and performance monitoring, and Google Analytics for site analytics. Some browser playgrounds also request packages or runtime files from package registries and content delivery networks. These providers receive the technical information needed to handle those requests.
5. How long data is kept
- Execution workspaces are temporary and are normally removed after each run.
- Share snapshots expire 30 days after their most recent successful view.
- The compiler security cookie and its server-side session record expire after 12 hours.
- Locally saved editor and tool data remains until you or the feature clears it.
- Security, error, server-log, and analytics records are kept for the configured operational or provider retention period, then deleted or anonymised when no longer needed.
6. Your choices and rights
You can clear locally stored data and cookies through your browser. Depending on where you live, you may also have rights to access, correct, or delete your personal data. Because the Service has no accounts, we may need details such as a share URL to identify the information involved.
7. Contact and changes
Contact [email protected] with privacy questions or requests. We may update this policy when the Service or legal requirements change; the date above shows the latest version.