We practice data minimization by design. Successful structural compilations remain entirely ephemeral and unrecorded. We only capture telemetry and technical artifacts when compilation encounters a failure or structural error state.
| Data Category | Capture Initiation Point | Operational Purpose & Processing Scope | Lifecycle Retention Period |
|---|---|---|---|
| Structural Textual Payloads & Asset Bundles | The precise instantaneous event wherein an interactive compilation directive fails or results in an exception status upon dispatch. | When a compilation error occurs, the offending payload artifact is registered within a managed logging repository exclusively to diagnose syntax anomalies, isolate parser edge-cases, and safeguard platform utility. Successful compilations generate zero persistent logging records. | Managed according to operational diagnostic necessity and maintenance cycles. |
| Network Connection Metadata | Every inbound HTTP/HTTPS request sent to our web and API routing layers. | Standard reverse-proxy stream logging utilized exclusively for structural routing optimization, volumetric load assessment, and rate-limiting enforcement. | Volatile server execution memory buffers only; never written to persistent disk volumes. |
| Analytics Telemetry Identifiers | Initial DOM document load and subsequent client-side view navigation. | Google Analytics 4 event tracking measuring aggregate engagement metrics, browser capabilities, and regional page-load performance. | 14 months, complying with Google Analytics default rolling expiration parameters. |
| Local Client State Cache | Active browser session usage and tool configuration adjustments. | Maintains workspace continuity (active zoom scale, pan coordinates, syntax editor buffers, cached file arrays) during deep multi-page navigation contexts. | Instantly wiped upon termination or closure of the browser tab/window. |
To provide absolute clarity on our boundaries, RTL Bench architecture ensures zero ingestion of the following data types:
When you push code into our compilation pipeline via text paste or directory tree upload, the transmission travels exclusively over TLS 1.3 encrypted channels. Once received by our FastAPI backend framework:
RTL Bench relies on industry-standard, high-reliability cloud subprocessors to maintain availability, high-speed asset distribution, and deep logic analytics:
Our cookie footprint is strictly limited to core operational measurements and analytics validation:
| Cookie Identifier | Originating Provider | Functional Description | Expiration Span |
|---|---|---|---|
_ga |
Google Analytics | Computes unique visitor tallies by generating a randomly seeded client instance identifier. | 2 years from initialization |
_ga_LT20GTPEL1 |
Google Analytics | Maintains session continuity and activity state across page hits for this specific property container. | 2 years from initialization |
Visitors retain complete autonomy over tracking cookies. You may configure your browser software to block or purge all third-party cookies. Doing so will restrict none of RTL Bench's core EDA, simulation, or schematic visualization capabilities.
For individuals accessing RTL Bench from within the European Economic Area (EEA) or United Kingdom, processing of technical request metadata is executed under the lawful basis of legitimate interests (ensuring software stability, preventing service abuse, and providing real-time hardware design compilation). Because we maintain no user profiles or account repositories:
Under the California Consumer Privacy Act (CCPA) and California Privacy Rights Act (CPRA), users are entitled to know what categories of personal data are gathered. Because RTL Bench collects zero consumer personal data, sells no user information to third-party data brokers, and engages in no cross-context behavioral tracking for monetary consideration, we naturally maintain full operational compliance. We do not honor "Do Not Track" (DNT) browser header flags differently than standard operations because our baseline analytics already run without persistent cross-site behavioral tracking profiles.
We implement stringent defense-in-depth measures to protect runtime infrastructure:
RTL Bench is structured as an engineering utility tool intended for academic, professional, and experimental hardware design. We do not target, market to, or knowingly solicit data interaction from minors under the age of 13. If you believe a minor has improperly transmitted code artifacts containing identifying metadata, please reach out via our repository channels for immediate removal.
We reserve the right to amend this Privacy Policy dynamically as platform features, subprocessors, or regulatory landscapes evolve. Substantive modifications will be indicated by adjusting the "Last updated" timestamp stamped at the head of this document. Continued engagement with RTL Bench subsequent to any modification confirms your ongoing acknowledgment of the revised governance terms.
Inquiries, clarification requests, or statutory compliance notices regarding this privacy framework should be directed to our active engineering maintainers via public or private communication paths on our primary repository interface: github.com/Raghavan-04/rtlbench/issues .