Privacy Policy

Scope

This policy describes the data handling in the current More Playables website and playable-brief flow. The site does not provide public customer accounts.

Information in a playable brief

The brief can collect studio name, game name, store URL, a current creative URL or one uploaded attachment, production objective, target networks, language, orientation, timing, contact name, and contact email. The server also records operational metadata used to process and protect the request: a receipt identifier, timestamps, a request fingerprint or idempotency key, and a bounded hashed IP value for abuse prevention.

Why the information is used

Receive and identify the production request.
Review the game, current creative, requested scope, target destinations, and timing.
Contact the named person about clarification or a possible written production proposal.
Prevent duplicate submissions, return the correct receipt, diagnose failures, and limit abuse.
Protect the private brief and attachment stores and maintain an operational record of the request.

Storage and access

In the deployed service, brief and contact fields are stored with Cloudflare D1. An uploaded attachment is encrypted with AES-GCM before Cloudflare R2 stores the ciphertext under a receipt-specific object key. Attachments are not published as gallery media, and the site does not provide a public attachment-download or lead-list endpoint.

Access is through authorized operational tools for reviewing or administering briefs, investigating failures or abuse, and responding to the named contact. A submission receipt is displayed only after the database record and any attachment have been stored successfully.

Files and upload limits

The form accepts one current-creative URL or one attachment no larger than 10 MB. Accepted attachment extensions are HTML or HTM, ZIP, PNG, JPG or JPEG, WebP, GIF, MP4, WebM, MOV, and PDF, with a matching allowed media type. File type and size checks reduce risk but do not guarantee that an attachment can be used in production.

Email and receipt behavior

The on-screen receipt confirms that the submitted data was stored. It does not claim that an email was sent unless the service later displays an accurate email-delivery confirmation. A receipt also does not accept a project or create a paid production agreement.

Retention and deletion requests

Submitted information is retained as needed to review and respond to the request, administer an engagement, prevent abuse, protect the service, and maintain applicable operational records. Retention depends on the status of the request and those purposes rather than a single published duration.

To ask about a submitted brief, access, correction, or deletion, use the playable brief path, begin the objective with ‘Privacy request,’ and include the earlier receipt identifier when available. Do not resend a sensitive attachment.

Playable gallery and external destinations

The public gallery contains More Playables-owned playable work. Activating a playable can run its interactive package inside a restricted frame, and its CTA may point to an external app-store or other approved destination. Generated concept illustrations are labeled and are not presented as campaign screenshots. External destinations apply their own data practices.

Security and limits

The service uses attachment encryption and scoped operational access, but no internet service can promise absolute security. Do not submit passwords, payment data, personal player data, health data, government identifiers, or other unnecessary sensitive information in a production brief or attachment.

Changes

This page uses its actual update date. Material changes to the fields collected, storage, access, sharing, retention, or communication behavior will be reflected here.