Security and reporting.

Updated 1 November 2026. We use access controls, separate private and public content, secure sign-in and server-side checks to protect the site. Security is ongoing work. We do not claim independent penetration-test certification, ISO 27001 certification or SOC 2 assurance.

Report a concern

Send a private security report. Include the affected page, what you expected to happen, and the smallest safe reproduction. Avoid sending secrets or other people’s data. If the form is unavailable, email security@aigamecollective.com in plain text. Attachments are not imported.

This reporting route does not authorise testing other accounts, accessing private data, social engineering, disrupting the service or running automated attacks. No bounty or reward is promised.

Private content and files

Saving a creator draft does not make it public. Review and publication use separately approved copies. Private application files require the correct workspace access. File checks and human review do not amount to a guarantee that an uploaded document is malware-free.

Recovery and incident handling

We maintain release and recovery procedures and test restoration in isolated resources. Same-account recovery testing is separate from independently held backups. We continue to verify original-media recovery and recovery-key custody. A local draft recovery feature is not a backup of your account or media.

When investigating an incident we assess containment, affected information, recovery and any required notifications. Do not publish a suspected private-data exposure while it is being investigated.