Terms of Service
01 Acceptance of Terms
By initializing custom context keys or prompt builds within this playground, you agree to comply with and be bound by these local configuration terms. If you do not agree to these adjustments, you may destroy your session variables immediately.
02 API Routing & Key Operations
This workspace operates entirely as a local static canvas container. Any third-party tokens or endpoints passed through the configuration panel are processed in memory through rotation filters:
- You retain co-ownership and responsibility over the volume of requests submitted to infrastructure handlers.
- Automated failover controls will block local nodes temporarily when servers report status 429 or 401 exceptions.
- You agree not to bypass server rotation configurations using external parallel spam arrays.
Strict Rate Limit Disclaimer: Repeated generation loops designed to lock system nodes or simulate artificial interface execution tasks are restricted automatically at the network layer.
03 Generated Code Ownership
All single-file web applications compiled inside the code architecture view tab belong mostly to you. No structural tracking attributes, deployment anchors, or design scripts are monitored or commercialized by the developer platform layer.
04 Limitation of Liability
This dynamic interface is provided on an "as-is" structural configuration layout. The platform is not responsible for localized browser storage corruption, token deployment blocks, or API token expirations occurring mid-build.
Privacy Policy
01 Local-First Architecture
Your workspace data safety is built directly into our layout framework. We do not maintain offsite centralized databases, identity tracking matrices, or dynamic behavioral tracking engines.
02 LocalStorage Memory Scope
The application stores state objects directly within your local hardware browser environment. This scope includes:
- API Key configurations, string fragments, and custom fallback server labels.
- Active provider targets and selected model indices.
- Your last 4 saved project layouts, prompt targets, and generated HTML builds.
Executing a localStorage.clear(); call inside your browser console instantly wipes all traces of this telemetry data forever.
Token Security Check: Your secret tokens (`ghp_` and `gsk_` parameters) are only dispatched across CORS proxies to hit official model validation paths. They are never transmitted back to an unverified storage pipeline.
03 Third-Party Data Transmission
When running prompt modifications, content text blocks are sent directly to the routing targets selected in your dropdown menu (GitHub Models or Groq Cloud). This processing is bound directly by the operational policies of those external services.
04 Changes to This Policy
We reserve the right to modify this interface structure to add security features. Updates will follow code architecture structural builds and will automatically reset localized caches when critical layout blocks alter.