PRIVACY · BETA POLICY

Collect only what the loop needs.

This beta stores account, project, support and engineering records to provide the platform.

01

What is stored

GitHub identity and OAuth credentials, workspace membership, project settings, support messages, issue details, approved documentation, generated code proposals, usage and audit events are stored in PostgreSQL. Widget identifiers are random and stored server-side as keyed hashes.

02

Optional diagnostics

Page path and browser information are collected only when the owner enables diagnostics and the customer consents. The widget omits query strings and fragments. Avoid including secrets or sensitive personal data in messages.

03

Hosted processing

When an owner enables Groq, focused message/context data is sent to Groq. Repository operations use GitHub. Review their provider terms before use. No advertising trackers are included.

04

Retention and deletion

Projects configure customer-data retention from 1 to 365 days. Run the maintenance script regularly to apply it. Owners can purge customer data or delete projects from Settings. Account deletion is available for accounts without shared workspace ownership.

05

Before a public launch

Operators must replace this draft policy with their business identity, jurisdiction, legal basis, contact details and final retention policy. This beta document is not a claim of regulatory compliance.