Privacy Policy & Telemetry Notice
BytesLab is engineered with cybersecurity principles at its core. We believe in absolute transparency regarding the code telemetry, sandbox compute buffers, and network metadata we record to defend the platform against exploitation.
- • Code snippets submitted to interactive compilers.
- • Latency, RAM consumption, and process exit codes.
- • Originating client IP addresses for network defense.
- • Account credentials encrypted via salted bcrypt hashes.
- • We never sell or license your source code to brokers.
- • We never inject third-party ad tracking pixels or trackers.
- • We never train commercial third-party LLMs on private code.
- • We never expose raw telemetry logs to unverified parties.
Information We Collect
When you access BytesLab, our infrastructure collects specific categories of technical information necessary to provide sandboxed runtime execution, maintain account continuity, and safeguard our server clusters:
Account Credentials
Username, email address, salted password hashes (bcrypt), full name, profile bio, and connected social links. Passwords are never stored in plaintext format.
Execution Telemetry
Source code submitted to the editor, compiler output streams (stdout/stderr), process execution latency (ms), RAM allocation (MB), and POSIX exit status.
Client IP Address Auditing & Security Forensics
BytesLab operates high-performance compiler runtimes (including Docker GCC containers and WebAssembly virtual machines). To defend these compute nodes against denial-of-service floods, malicious payloads, and unauthorized network egress, we capture the originating client IP address for all code executions.
You are permitted to execute code in our public labs without creating an account or logging in. However, unauthenticated runs remain fully subject to automated security logging. The originating IP address (X-Forwarded-For / remote socket) is attached to each run to prevent anonymous abuse, automated bot loops, and container breakout attempts.
SHA-256 Cryptographic Audit Ledger
Unlike traditional cloud applications that maintain mutable database rows, BytesLab commits execution and system security events to an immutable JSONL audit ledger. Each event record is cryptographically linked to the preceding event through a SHA-256 hash digest:
Hash(N) = SHA256( Hash(N-1) + Timestamp + EventType + TaskID + PayloadDigest )This mathematical chain prevents retrofitting, log tampering, or unauthorized audit deletion. Administrators can continuously verify ledger integrity across thousands of execution cycles.
How We Utilize Platform Information
Information collected by BytesLab is deployed strictly for core operational, computational, and defense objectives:
- Compiler Dispatch: Passing user code into the target compiler container and streaming standard output buffers back to your browser in real-time.
- Gamification & Progress: Computing solved challenges, calculating experience points (XP), awarding lab badges, and calculating learning streaks.
- Abuse Mitigation: Identifying coordinated DDoS attempts, brute force login attacks, and malicious memory manipulation.
- Infrastructure Tuning: Analyzing compilation latency across CPU architectures to optimize Docker MicroVM warm-pooling and Pyodide caching.
Sandbox Isolation Runtimes
BytesLab utilizes multi-tiered sandbox containment to isolate submitted code from neighboring sessions and host operating systems:
Pyodide WebAssembly
Python code runs directly within your client browser environment inside an isolated WebAssembly memory sandbox.
GCC C / C++ Engine
Compiled languages execute within ephemeral, network-disabled containers with strict CPU quotas and 128 MB RAM ceilings.
JavaScript Sandboxes
JavaScript operates in restricted worker contexts isolated from DOM manipulation and host socket access.
Storage & Retention Lifecycle
We enforce data minimization practices. Information is retained only as long as required to maintain service availability and fulfill our cybersecurity auditing duties:
| Data Category | Storage Location | Retention Period |
|---|---|---|
| User Profile & XP | PostgreSQL Primary DB | Duration of active account membership |
| Execution Logs | PostgreSQL (code_executions) | 90 rolling days (auto-pruned) |
| Security Audit Ledger | Append-only JSONL Volume | 365 days for cryptographic forensic continuity |
| Ephemeral Temp Files | Docker Container Memory | Immediately purged upon container termination |
User Rights & Data Deletion
Regardless of your jurisdiction, BytesLab honors fundamental privacy rights aligned with GDPR and CCPA standards:
Privacy & Cybersecurity Inquiries
Direct communication line to BytesLab compliance team
If you have questions regarding our telemetry architecture, data processing agreements, or wish to submit a vulnerability disclosure report, reach out directly to our official address: