Secure identity sign-in is connected through Clerk. Organization provisioning, paid subscriptions, persistent creator configuration, and live TikTok connections are not operational. This document describes the software that exists now; disclosures must continue to change with product behavior.
01
Scope and current build
This Privacy Policy explains how Stream Control handles information when you use the public website, signup preview, operational demo, local browser-source features, and configured local integrations.
The current build provides optional identity creation and sign-in through Clerk and stores a pseudonymous application identity in Neon. It does not provision a Stream Control organization, workspace, subscription, persistent creator configuration, live TikTok connection, or hosted OBS connection from that identity.
02
Information handled today
A hosting or network provider may process IP address, request path, timestamp, browser information, and security logs when the site is deployed.
Deliver, protect, and diagnose the requested service.
Display name, email, and workspace name remain in the open browser dialog. They are not submitted or retained.
Validate and demonstrate the planned account flow locally.
If you choose sign-up or sign-in, Clerk processes the identifiers, contact details, credentials, verification factors, session tokens, and security data required for authentication. Stream Control stores Clerk's stable subject, lifecycle status/timestamps, last-authentication time, and any operator-granted platform-staff role in Neon. It does not copy Clerk profile/contact data, credentials, or session tokens into that database.
Create and secure an optional identity, synchronize account lifecycle, and enforce server-owned access roles.
Simulated events, rules, goals, widgets, moderation previews, and broadcast state remain in browser or server memory and reset.
Operate the requested product demonstration.
One essential-only choice is stored on your device for up to 180 days.
Remember that analytics and advertising storage remain off.
When configured, the local server may exchange bounded command and status data with software on the same machine. Secrets remain server-side.
Perform the local action you request and report a specific result.
03
Information not collected by this build
- Stream Control does not receive or store your password or multi-factor authentication secret; Clerk handles identity credentials.
- A Clerk identity creates only the bounded pseudonymous account record described above; it does not create a Stream Control organization, membership, workspace, subscription, or durable creator profile.
- No payment-card or bank information is requested or received.
- No live TikTok credential, session cookie, private endpoint, or viewer database is collected.
- No advertising identifier, behavioral profile, or cross-site tracking record is created.
- No signup-preview field is transmitted when you select “Review availability.”
04
How information is used
Information is used only to deliver a requested page or local action, verify and maintain an optional authenticated session, enforce server access boundaries, diagnose failures, remember a privacy choice, and operate the session-local demo. Stream Control does not use current-build data for advertising, automated eligibility decisions, data brokerage, or training a user-profile model.
06
Retention and device control
- Signup-preview fields last only while the client component remains mounted and are cleared when the dialog resets or page reloads.
- Clerk identity and session records follow the configured Clerk instance and provider retention controls. The pseudonymous Neon identity is retained pending the finalized account-retention schedule; a configured verified deletion webhook marks it deleted and preserves a tombstone so delayed events cannot reactivate access.
- Demo state is bounded in memory and generally resets on refresh or server restart.
- The privacy-preference record expires after 180 days and may be cleared earlier through “Privacy choices.”
- Production infrastructure-log retention is not yet configured and must be documented before public deployment.
07
Security
Current controls include verified Clerk session tokens, server-only provider keys, database-backed role and workspace-scope constraints, validated external inputs, bounded in-memory records, sanitized text rendering, signed and expiring local browser-source capabilities, loopback-only local transports, explicit desktop permissions, and redacted diagnostics. No system is perfectly secure. Do not enter secrets or sensitive personal data into the demo.
08
Your privacy rights
Depending on where you live, you may have rights to know or access personal information, correct it, delete it, restrict or object to processing, obtain a portable copy, withdraw consent, or appeal a decision. You may also have the right to complain to a local data-protection authority.
An optional identity may be durable in Clerk and as a bounded pseudonymous record in Neon even though no Stream Control workspace is provisioned. You can clear the on-device preference through “Privacy choices” and manage the active identity from the account screen. For access, correction, deletion, or another request concerning provider, server, or contact records, email Luman.Chad@outlook.com. Stream Control may need to verify the request and will respond as required by applicable law.
09
Children
The Service is intended for adults and is not directed to children. Do not use the Service or submit personal information if you are under 18. If you believe a child’s information has been provided, contact the address below.
10
International access
The public website and identity service may be accessed from different countries. Vercel, Neon, and Clerk may process service data in provider regions outside your location. The operator must finalize applicable processing regions and transfer safeguards before durable workspace data becomes operational.
11
Changes and contact
This policy will be revised when data practices change. A new effective date will be posted, and a new privacy choice will be requested before any optional device storage is activated.
Privacy questions and requests may be sent to Luman.Chad@outlook.com. See the Cookie & Storage Notice for the current device-storage inventory.