Help us understand the issue safely.

What to include

• The affected page or feature and the steps needed to reproduce the behavior.
• The impact you observed, including what data or permission boundary may be affected.
• A minimal proof that avoids collecting, changing or sharing another person’s data.
• A way to contact you if we need to clarify the report.

Keep testing bounded

Do not access another person’s files, disrupt service, persist access, publish a working exploit, or send live malware. Stop if a test exposes information that does not belong to you. Do not attach passwords, secret keys or private user files.

Security reports are reviewed as the independent service is prepared. Hosting, authentication and billing are not yet provisioned, so not every planned production control is active today.