CineEnnyd Drive privacy notice

CineEnnyd Drive privacy notice

Updated 9 November 2026. CineEnnyd is operated by Peter J. Knight trading as MCP | Media | Cinema | Projection. Contact hello@media-cinema-projection.com for privacy, access, correction or deletion requests.

Service status

The new Google Drive workflow is in controlled testing. Public customer rollout has not been approved. Google verification and release checks must finish before the new LIVE workflow is enabled. Test evidence is not a claim that the production service has been deployed.

Information and purposes

CineEnnyd prepares Digital Cinema Packages for cinema playback. It handles account and organisation details, job titles and status, filenames, source media, completed packages and operational reports. Personal information may be present in images, sound and documents supplied for conversion. Account and service information is used to administer requested work, support users and protect the service. Customer media is processed to carry out the submitting customer’s instructions. Customers must have the necessary rights and authority to supply their media.

Google Drive access

The Drive owner authorises the connection separately from a CineEnnyd login. The service lists configured folders, reads selected source files, stores queue manifests and returns DCP packages and reports. A worker downloads the source into server working storage, prepares the DCP and uploads the result. The application keeps job status and operational metadata. Authorisation is retained so the agreed job can run while the operator is away from the browser.

The current connector requests the full Google Drive scope. Configured CineEnnyd folders limit the intended workflow; they do not narrow the permission granted by Google. CineEnnyd does not use Drive information for advertising or generative AI model training. Use and transfer of information received from Google APIs will comply with the Google API Services User Data Policy, including its Limited Use requirements.

You can revoke the connection through your Google Account connections. This stops future authorised access but does not remove files already delivered to Drive or erase copies retained for the purposes below. Contact MCP for deletion of service-held information.

Access and storage

Processing uses MCP-operated application and worker infrastructure and the Drive account chosen by its owner. Access is limited to authorised operators and service processes. Secure web connections protect transfers. Database backups are encrypted. Necessary hosting and storage providers support operation of the service; Google handles Drive under its applicable terms and privacy information. The new LIVE Drive release uses the standard worker. AWS conversion testing is a separate DEV workflow and is not enabled by connecting Drive.

Approved release retention schedule

The following schedule is approved for the release. A documented hold or approved retry can defer deletion. Peter J. Knight owns deletion requests and holds, records their reason and scope, and reviews holds at least every 30 days.

• Source media and delivered DCPs in the Drive owner’s folders remain owner-managed. CineEnnyd does not routinely remove them.
• Worker copies of media, temporary files and DCPs have a target of removal within 24 hours after verified delivery, or seven days after a failed or cancelled job ends. Active work and approved retries are protected.
• Service logs, reports and queue manifests have a 30-day period after the job ends. Removal from active Drive storage may use Drive Trash, where files remain recoverable until Google or the owner removes them permanently.
• Job history is redacted after 90 days. Required billing records are kept separately under the applicable accounting rules.
• Closed account profiles are removed or anonymised within 30 days of verified closure, subject to a documented hold or legal obligation. Disabling an account is not treated as verified closure.
• Nightly encrypted database backups use a rolling 30-day cycle. They include account authentication data such as password hashes needed for recovery, but exclude source media, DCP packages, Drive OAuth credentials and deployment secrets. Supported deletions must be replayed before a restored database returns to service.

Current testing limitations

The complete release schedule is not yet a blanket automatic control. STAGE runs scheduled cleanup of verified successful DCP and project copies and a bounded hourly sweep for supported failed and cancelled jobs. Newly owned standard-worker source and temporary copies are included where an exact receipt can be verified. The 30-day service-record, 90-day history and closed-account processes still require operator action. Shared or historical files without reliable job ownership, unsupported history records and dependent workflows require individual reconciliation. Cleanup is held if job identity, delivery, retry status, ownership or storage availability cannot be verified. The operator laptop receives encrypted backups and authenticated deletion records while its user session is available. These limitations must be resolved or accurately reflected in the release notice before customer rollout.

Your requests

Contact MCP to ask what information is held, correct inaccurate information, request deletion or restriction, or raise a privacy concern. The applicable rights depend on the information and the reason it is processed. Where MCP processes media for a customer, requests may need to be handled with that customer. You may also complain to the UK Information Commissioner’s Office. This notice will be updated when the service or its processing arrangements change.