SymLab.
SymLab Studio

Privacy Policy

How SymLab handles account information, support requests, and engineering scenarios.

Effective September 29, 2026

1. Scope and contact

This policy applies to the SymLab Studio website and application at www.symlab.studio. The application owner operates the service under the SymLab Studio name. Use Support Contact and select Privacy request to contact the owner about your information.

2. Information we process

3. Purposes

We use account information to authenticate invited users and enforce access; support information to respond to requests; and operational data to maintain availability, investigate errors, and prevent abuse. We do not use support submissions to enroll you in marketing.

4. Cookies and analytics

Essential cookies support sign-in and bot protection. A device-local preference remembers dismissal of the cookie notice. The application does not add advertising pixels, marketing cookies, or an optional third-party analytics SDK. The hosting platform records traffic statistics and may process operational telemetry. This is not a promise that visiting the site generates no logs. See the Cookie Notice for the names, purposes, and durations we can identify.

5. Service providers and access

Supabase provides authentication and database processing for the dedicated SymLab App project. OpenAI Sites provides hosting and traffic analytics, and Cloudflare provides network delivery and security. The SymLab owner can review membership and support information. Providers may process data where their services operate, including outside your country; this application does not promise a particular data-residency location.

We do not sell personal information or share it for targeted advertising. Information may be disclosed to service providers for the purposes above, when required by applicable law, or when reasonably necessary to address abuse or protect the service.

6. Retention and removal

Account records remain until the owner removes them; revoking access does not itself delete an account. Support requests remain until deleted by the owner. You may request access, correction, or deletion through Support Contact; we may need to verify your identity before acting. Provider logs and backups follow the providers' retention practices and may not be immediately removed with an application record.

Local scenarios remain on your device until you reset the relevant tool or clear the site's browser storage. Signing out does not erase local scenarios or downloaded files. Back up wanted scenarios before clearing site data.

7. Security and your choices

We use HTTPS, server-side access checks, secure session cookies, and restricted database access. No service can guarantee absolute security. Keep invitation links and passwords private, sign out on shared devices, and do not submit passwords, invitation tokens, regulated personal information, or confidential project files in support messages.

You can block cookies in your browser, but sign-in or bot protection may stop working. Rights and exceptions vary by location; nothing in this policy limits rights available under applicable law.

8. Intended audience and changes

SymLab is intended for professional engineering use, not for children. We may update this policy as the service changes and will publish the effective date here. Material changes to data use will be communicated through the application or another appropriate channel.

Contact SymLab

Questions about this page? Contact SymLab support. Requests are saved in the SymLab App project within the SymLab Studio Supabase organization for review by the application owner.