We use identity data to sign you in, project data to make your visuals, and transaction records to operate credits and billing. Uploaded tracks and renders are treated as private account content. Google sign-in asks only for basic identity scopes, and Oscillihue does not store Google access or refresh tokens.
About this policy
This Privacy Policy covers Oscillihue’s website, application, and related services (the “Service”). Oscillihue is operated by Lightbrush (“Lightbrush,” “we,” “us,” or “our”).
The Service is still being prepared for public launch. This policy describes the current account, project, rendering, and billing design as of the effective date. If those practices materially change, we will update this page.
Information we collect
Account and identity information
When you use Google sign-in, we receive a Google account identifier, your verified email address, and—when available—your name and profile image. If you use an email sign-in link, we receive your email address. We also maintain account identifiers, essential session records, verification status, and account timestamps.
Project and creative information
We process the audio files you upload, the original filename, project title, creative directions or idea text, track analysis such as duration and tempo, selected visual systems, render settings, previews, thumbnails, project state, final renders, and related technical metadata.
Billing and transaction information
We keep records needed to operate credits, purchases, subscriptions, refunds or reversals, and render settlement. Those records can include Stripe customer, Checkout, price, charge, invoice, or subscription references and transaction status. Stripe hosts Checkout and processes payment details; Oscillihue does not ask you to enter full card or wallet credentials into the Oscillihue application.
Usage, device, and security information
When the Service is operating, our servers may process IP address, browser and device details, request timestamps, feature activity, error information, rate-limit events, and other diagnostics needed to deliver, secure, and improve the Service.
Communications
If you join the Founding Loop or contact us, we receive the email address and message content you choose to send. Founding Loop records also include confirmation status, a random invitation code, referral attribution, confirmed-invitation counts, campaign source information, consent version, delivery status, and timestamps. If you submit a Launch Mission for verification, we also process the selected platform, the public post URL, your random mission proof code, the verification result and method, and related timestamps. We do not ask for or store your social-media password or social sign-in token. Invitation and proof codes do not contain your email address or account identifier.
How Google sign-in data is handled
Oscillihue requests only the openid, email, and profile scopes. We use that information to authenticate you, connect you with your account, and display basic account identity.
- We do not request Google Drive, YouTube, Google Analytics, or other Google product data through sign-in.
- We do not persist Google OAuth access tokens or refresh tokens.
- We do not use Google sign-in data for advertising.
- We share Google-derived identity data only as described under “When we share information.”
Removing Oscillihue from your Google account stops future Google authorization. It does not automatically erase account, project, or transaction records already stored by Oscillihue.
How we use information
We use information to:
- create and secure accounts, sessions, and sign-in flows;
- receive, analyze, organize, preview, render, and deliver creative projects;
- maintain private project libraries and verify access to media;
- quote render work, hold and capture credits, process purchases, and support subscriptions;
- provide support and respond to messages;
- confirm launch reservations, attribute invitations, calculate limited launch-credit eligibility, and send launch-access notices;
- detect abuse, troubleshoot failures, protect users, and enforce our Terms; and
- understand Service performance and improve the product.
We do not sell personal information or uploaded tracks. We do not use private project media in public marketing unless you direct us to publish it or separately give us permission.
When we share information
We share information only where needed for the Service or for legitimate legal and safety reasons:
- Google supports the optional sign-in flow.
- Stripe hosts Checkout, processes payments, supports the billing portal, and sends transaction events used to update credits and subscriptions.
- Infrastructure and rendering providers may process the project files, job instructions, or technical data required to host the Service and complete a render.
- Email delivery providers process addresses and delivery events needed to send confirmation and launch-access messages.
- Professional advisers and authorities may receive information when reasonably necessary to comply with law, protect rights and safety, investigate abuse, or resolve disputes.
- A successor organization may receive relevant information as part of a merger, financing, acquisition, reorganization, or sale of all or part of the Service, subject to applicable law.
Service providers are expected to use information for the work they perform for us, not for their own unrelated purposes.
Uploaded tracks and rendered media
Oscillihue is designed so project media is tied to an account and media delivery checks ownership. Authenticated uploads, previews, thumbnails, partial renders, and downloadable final videos are served as private content rather than public assets.
If Channels launches and a creator opts in, we may process the public render, creator identity, programming schedule, aggregate playback, license, royalty, payment, and tax records needed to operate the program. Private renders are not included in Channels without the account holder’s affirmative choice.
To analyze a track or complete a render, the Service copies the relevant file and job instructions to managed cloud rendering infrastructure. A worker should receive only the project material needed for that job. No internet service can promise perfect security, so do not upload material you are not authorized to use or information you do not need the Service to process.
Cookies and security
Oscillihue uses essential cookies or similar browser storage to keep a session active, protect account actions, remember necessary state, and complete sign-in. The server stores a one-way hash of the main session token rather than the raw token.
We use Google Analytics to understand visits, referral sources, device categories, page engagement, and launch-list interactions. Advertising personalization and Google signals are disabled in our configuration. We also maintain first-party aggregate counters for page views, scroll depth, engagement time, selected actions, and coarse geographic activity derived by our hosting provider. Map coordinates are rounded before aggregation. Those counters do not store IP addresses, email addresses, uploaded filenames, project content, or raw visitor identifiers.
We use technical safeguards such as access checks, expiring sign-in challenges, protected session cookies on HTTPS, request validation, and private cache controls. These measures reduce risk, but no storage or transmission system is completely secure.
Founding Loop submissions use rate limits and abuse signals. Raw IP addresses are not stored in the launch-list record; a one-way request fingerprint may be retained temporarily to enforce submission limits. Public Launch Mission URLs and a one-way fingerprint of each submitted URL may be retained to verify the post and prevent the same proof from being claimed more than once.
Retention and your requests
We keep account, project, render, security, and transaction records for as long as reasonably needed to operate the Service, maintain project access, complete and reconcile transactions, prevent abuse, meet legal obligations, and resolve disputes. Backup, fraud-prevention, financial, or minimal audit records may need to remain longer than active project data.
Pending Founding Loop confirmations may expire, while confirmed reservations are kept through launch and account activation unless you unsubscribe or request deletion. Launch Mission evidence is kept through reward reconciliation and may be retained with minimal referral and reward records where needed to prevent duplicate grants or abuse.
Oscillihue does not currently provide a self-service account deletion or data export control, and a fixed production media-retention schedule has not yet been published. Do not assume an upload will be automatically deleted after a specific number of days.
You may email us to ask what account information we hold or to request access, correction, or deletion. We will verify the request and respond as required by applicable law. Some information may be retained where needed for transactions, security, legal compliance, or backup integrity.
Send a privacy requestChildren’s privacy
The Service is not directed to children under 13, and we do not knowingly collect their personal information. If you believe a child has provided personal information through Oscillihue, contact us so we can review the situation.
Changes and contact
We may revise this policy as Oscillihue develops. We will post the current version here and change the effective date when the update takes effect. If a change materially affects how existing account data is used, we will provide additional notice where reasonably appropriate.
Questions about this policy or Oscillihue’s data practices can be sent to captain@lightbrushproject.com.