Encrypted delivery
The live site is delivered over HTTPS through Cloudflare. Browser requests and responses are encrypted in transit.
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
Delivered controls and future intentions are kept visibly separate.
The public site requests information only when a visitor chooses to engage.
The assistant explains public information; it cannot approve access or make commitments.
Formal controls will be published as they are implemented and verified.
These statements describe the website running today—not the unreleased CinemaBrain production application.
The live site is delivered over HTTPS through Cloudflare. Browser requests and responses are encrypted in transit.
Contact and assistant endpoints use request limits, same-origin checks, payload limits and input validation. The enquiry form also contains a bot trap.
Site policy disables camera, microphone and geolocation access. Pages cannot be embedded cross-origin, and content-type sniffing is disabled.
The website assistant is instructed to use public CinemaBrain facts only, disclose uncertainty and avoid promises, private figures or invented milestones.
The public website currently has no visitor login, product account, payment flow or upload area. Product access remains selective and private.
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.
A plain-language map of the current public experience. Product data handling will be documented separately before wider onboarding.
CinemaBrain does not currently claim external security certification, regulatory compliance certification, enterprise identity controls or audited service availability.
These are preparation commitments, not completed controls. Progress will move to the Build Log only after it is verifiable.
Document how scripts, references, generated media, provider requests and production metadata move through the application.
Define practical controls for project removal, account closure, backups and third-party processing.
Establish role boundaries, security review, incident response and responsible vulnerability reporting.
Create clear product terms, privacy terms, provider disclosures and appropriate contractual materials before enterprise onboarding.
How the current public website handles information.
Read privacy →LEGAL NOTICEWebsite TermsCurrent terms and forward-looking information notice.
Read terms →VERIFIED PROGRESSBuild LogDelivered work, separated from roadmap intent.
View releases →CONTACTPrivacy or security questionSend a focused enquiry to the CinemaBrain team.
Ask a question →As product controls become real and verifiable, this Trust Centre and the Build Log will be updated together.