Channel Immersion Get Access
Privacy

Clear about what this website collects.

This notice covers the public Channel Immersion website, early-access and pilot-interest forms, and contact form. It does not yet serve as the final privacy notice for production app access.

Last updated: August 4, 2026

Forms and waitlist

Information you submit is stored in a private database so pilot requests can be reviewed, updated, and organized.

Necessary session

A temporary session cookie supports form security and repeated-submission controls.

No ad tracking in this package

The current website package does not include advertising pixels or third-party analytics scripts.

Pilot-stage boundary: The app’s final authentication, sync, recordings, notes, favorites, exports, data processors, storage locations, retention periods, and deletion flow must be documented before production access is offered.

1. Scope of this notice

This notice describes the website package delivered for Channel Immersion. It covers information submitted through the public forms and technical information involved in operating those forms.

A participant invited to use the app should receive a separate or expanded privacy notice that accurately describes the production app and any third-party services it uses.

2. Information collected

Early-access and pilot requests

The compact homepage forms ask only for an email address and clearly state that submission signs the person up for occasional pilot updates. The Get Early Access page asks for a first name, email address, and primary device. After the request is complete, the confirmation page offers optional questions about planned channel types and what currently gets in the way.

Contact messages

The contact form asks for a name, email address, reason for contact, and message. A privacy request may include additional information needed to identify the original submission and understand the requested action.

Information not requested

Do not submit passwords, payment-card information, government identifiers, private recordings, health information, or other sensitive personal material through these website forms.

3. How information is used

  • To respond to questions, feedback, privacy requests, and partnership enquiries
  • To assess device needs and, when optional follow-up answers are provided, likely pilot use cases and participant fit
  • To communicate availability, participation details, important pilot updates, and changes
  • To protect the forms, troubleshoot delivery, and improve the website or pilot experience

Submitting an early-access or pilot form does not create an account or guarantee access.

4. Cookies and technical information

Necessary session cookie

The current site uses a temporary PHP session cookie to create a form-security token and support session-based submission throttling. It is not used for advertising or cross-site profiling.

Submission protection

To reduce repeated submissions, the site may create a short-lived server-side record keyed with a one-way hash derived from the form and IP address. The raw IP address is not included in routine form notification emails.

Hosting logs

The hosting provider may keep routine server logs containing requested pages, timestamps, browser or device information, and IP addresses. The final launch checklist must confirm the hosting provider’s exact settings and retention practices.

5. Service providers and sharing

The website uses hosting, a private MySQL database, and authenticated email services to operate the forms, maintain the pilot waitlist, and deliver selected notifications. Access to the administrative dashboard is restricted by a password-protected session.

The current website package does not include advertising networks, social tracking pixels, or third-party analytics scripts. Personal information should not be sold.

Information may also be disclosed when reasonably necessary to protect the service, investigate misuse, comply with a valid legal obligation, or protect legal rights.

6. Retention and deletion

Early-access requests are stored as one waitlist record that may be updated when optional follow-up details are submitted. Contact messages may also be stored in the private administrative dashboard. Notification copies may remain in the receiving mailbox and related email-service systems according to mailbox practices and provider settings.

Waitlist and contact records should be reviewed and deleted when they are no longer needed for the pilot, support, legal, or security purposes described here. Short-lived rate-limit records should be removed during routine server maintenance. Server logs and failed-delivery logs follow the hosting configuration.

7. Your choices

You may ask to access, correct, or delete information previously submitted through the website. You may also stop pilot communications using the unsubscribe method provided in relevant messages or by contacting Channel Immersion.

Before fulfilling a request, enough information may be needed to locate the original submission and reduce the risk of disclosing or deleting someone else’s information.

8. Children

The public pilot-interest form is not designed to collect personal information from children. Final pilot eligibility and age requirements must be stated before invitations are sent.

9. International operation

The final site may involve hosting, email, and app services operating in more than one country. The production privacy notice should identify relevant providers and explain cross-border processing once the stack is confirmed.

10. Contact

Use the contact form for privacy questions or requests. The final public privacy email and operator identity should be added before launch.