CINEMABRAIN TRUST CENTRE

Trust is part of the production system.

CinemaBrain is still in private development. This page states what protects the public website today, what data moves through it, and what must be completed before broader product access.

Last reviewed

01Say what is true now

Delivered controls and future intentions are kept visibly separate.

02Collect with purpose

The public site requests information only when a visitor chooses to engage.

03Keep humans in control

The assistant explains public information; it cannot approve access or make commitments.

04Earn enterprise trust

Formal controls will be published as they are implemented and verified.

CURRENT WEBSITE CONTROLS

Safeguards already in the public stack.

These statements describe the website running today—not the unreleased CinemaBrain production application.

ACTIVE

Encrypted delivery

The live site is delivered over HTTPS through Cloudflare. Browser requests and responses are encrypted in transit.

ACTIVE

Abuse resistance

Contact and assistant endpoints use request limits, same-origin checks, payload limits and input validation. The enquiry form also contains a bot trap.

ACTIVE

Restricted browser access

Site policy disables camera, microphone and geolocation access. Pages cannot be embedded cross-origin, and content-type sniffing is disabled.

ACTIVE

Bounded assistant

The website assistant is instructed to use public CinemaBrain facts only, disclose uncertainty and avoid promises, private figures or invented milestones.

ACTIVE

No public accounts

The public website currently has no visitor login, product account, payment flow or upload area. Product access remains selective and private.

ACTIVE

Aggregate measurement

CinemaBrain records a small allow-listed set of page and interaction counts without storing form contents, chat text, names, email addresses or a visitor identifier in its metrics dataset.

PUBLIC WEBSITE DATA MAP

What moves, and why.

A plain-language map of the current public experience. Product data handling will be documented separately before wider onboarding.

InteractionInformation involvedPurpose and destination
Browse the websiteNormal request metadata handled by hosting infrastructureDeliver and protect the site. CinemaBrain's aggregate metrics dataset does not receive an IP address or visitor ID.
Use the contact formTopic, name, optional company, mobile number, email and messageValidated by the website and delivered by email so CinemaBrain can respond to the enquiry.
Ask the assistantThe question and up to six recent conversation turnsSent to the configured AI service to generate the answer. The current website code does not save the conversation to a CinemaBrain database.
Play a technique clipThe requested public media fileDelivered as public learning content. No upload or account is required.
Site measurementAllow-listed event name, page path, coarse viewport group and generic target labelWritten as aggregate operational counts. Form values, chat text, referrer URLs and persistent identifiers are excluded.
NOT CLAIMED YET

Clarity before credentials.

CinemaBrain does not currently claim external security certification, regulatory compliance certification, enterprise identity controls or audited service availability.

  • Not claimedSOC 2 or ISO 27001 certification
  • Not offered publiclySingle sign-on, SCIM or role administration
  • Not published yetProduct data-retention and deletion schedule
  • Not contracted yetData-processing agreement or service-level agreement
  • Not represented completeEnterprise security review
BEFORE BROADER ONBOARDING

The trust work still ahead.

These are preparation commitments, not completed controls. Progress will move to the Build Log only after it is verifiable.

  1. 01
    Map the full production data lifecycle

    Document how scripts, references, generated media, provider requests and production metadata move through the application.

  2. 02
    Publish retention and deletion rules

    Define practical controls for project removal, account closure, backups and third-party processing.

  3. 03
    Formalise access and incident controls

    Establish role boundaries, security review, incident response and responsible vulnerability reporting.

  4. 04
    Prepare enterprise documentation

    Create clear product terms, privacy terms, provider disclosures and appropriate contractual materials before enterprise onboarding.

TRUST, BUILT IN PUBLIC

No inflated badges.
Just a clear record of progress.

As product controls become real and verifiable, this Trust Centre and the Build Log will be updated together.