Privacy notice

01 / Information collected

For a submitted contribution, the project stores the text and selected original files, file names, file types, sizes and duration, embedded metadata, any speech transcript, generated text and images, submission time, record number and identifiers linking the materials and task. It also stores applicable project and model versions, processing status, moderation results and the confirmations and agreement evidence for that submission.

No public participant profile, legal name or email is required. The service uses a signed anonymous session cookie, short-lived request credentials, secret-derived hashes of a trusted connection address or session, and usage records for abuse prevention, ownership checks, limits and recovery. The application stores hashes rather than publishing connection addresses. Hosting and service providers may separately process connection addresses and technical logs under their own policies.

Files selected for local preview remain in your device’s browser until you submit with the required confirmations. Your device may retain draft text, file references, language settings and private ownership credentials in session or local browser storage. Unfinished file bytes cannot be restored after a full refresh; you may need to select them again. Protect a shared device and its recovery credentials.

02 / What is public

After your separate publication confirmation and the required checks, the public record contains the submitted text and original media, generated responses and images, available transcripts or clearly identified translations, time, record number, and project or model provenance. File names and embedded metadata can reveal identities, location or other private information; remove such information before submission. Original material is not replaced by translation.

Audio and video records are held for administrator review before publication. A connection to an earlier public contribution is displayed only if you separately choose it; other conversations are not automatically disclosed. Ownership credentials, connection hashes, private agreement evidence, unpublished moderation details and private Contact messages are not part of the public canvas.

Anyone may view, download, screenshot or further share public material, including outside this website. The operator cannot guarantee control over copies made by others. Do not submit content that must remain confidential.

03 / AI, hosting and storage services

Vercel serves the website and server interfaces. Cloudflare D1 stores records and technical ledgers; a private Cloudflare R2 bucket stores original and generated files. Larger media upload directly to authorized private storage. Original files and database records are processed by these providers as necessary for hosting, validation, storage and access.

OpenAI receives submitted text and images for safety checks, visual understanding, written responses and abstract image generation. Audio you mark as spoken voice is sent for speech transcription; its transcript can then be used in the written and visual response. The selected previous public contribution is used as context when you choose to continue it. Project instructions are sent separately from participant material.

In this phase, original video, music and environmental recordings are stored and played in the archive; they are not sent to OpenAI for video, music or sound analysis. Their labels and any description you provide may still inform the response. No new music or video is generated. Do not label music or private conversations as spoken voice simply to obtain transcription.

Service providers may process data across borders. OpenAI API data is not used for model training by default under its published API data controls; provider security or abuse-monitoring retention and any feature-specific storage can still apply. This notice does not promise zero retention or one universal deletion period for every service. The project does not authorize unrelated model training; changes in service or processing purpose require appropriate notice and any legally required consent.

04 / Retention and backups

Public project records are intended for continuing preservation and remain until withdrawn, deleted or otherwise removed by an administrator. Hidden records and pending-review submissions are not public but may remain in restricted live storage while reviewed. Failed tasks, confirmation evidence and technical usage ledgers may remain for recovery, fraud prevention, accounting or dispute handling; the service does not automatically erase every database record when public display stops.

Expired or failed unattached uploads are periodically cleaned up. Cleanup can be delayed by a failed storage operation, and a durable deletion request is retried. A hidden record can be restored; deletion and withdrawal are separate actions. Restricted evidence should be retained only as needed for the stated purpose or an applicable legal obligation.

Restricted local database and media exports currently exist for recovery. Their retention is administrator-managed, rather than automatically limited to a published daily schedule. Backblaze B2 offsite backup is planned but not enabled. The proposed future encrypted backup policy is 30 daily versions and 12 monthly versions, copying only new media. Before activation, its account, access restrictions, deletion handling and retention must be configured and disclosed. Removed materials must not be republished during restoration.

05 / Requests and practical limits

Use a record’s private Report control or the currently available channels on Contact to ask about access, correction, cessation of public display or deletion of personal data, or to raise a rights concern. Provide the record number or link and only information necessary to verify the request. You may use the browser’s ownership credentials for self-service withdrawal. Losing those credentials does not prevent a private request, but verification may be necessary.

Stopping public display is different from deleting personal data or ending permission. Deletion from live project storage does not promise instantaneous removal from every provider log, restricted export or third-party download. Applicable law may require limited evidence retention. Requests are reviewed proportionately; the operator does not claim absolute immunity from responsibility.

The private Contact form is separate from the public artwork and is currently unconfigured. Once configured, its name, reply email and message are sent privately through Resend; they are not added to the canvas or used as project inputs. A configuration or sending error is disclosed and is not a delivery confirmation. Until connected, use the private record report or the social channels linked on Contact. Do not send sensitive identification documents unless requested through an appropriate private verification channel.

06 / Updates and contact

This notice describes the implemented services and records the version shown for each new submission. Material changes to public scope, processors, retention or purpose must be explained before new consent is sought. A past contribution’s original agreement snapshot is retained rather than silently rewritten.

The project is maintained by Liu Qiming. Private record reports and the currently available Contact channels are the rights and privacy routes. Any change to the operator or contact details will be noted here. Jurisdiction-specific privacy obligations and future organizational arrangements require legal review.