Skip to content
NYNZ

NYNZ · Policies & trust

Security

How private projects are protected, and what remains your responsibility.

Effective and last updated: 4 November 2026

Account and project access

NYNZ checks authentication and project ownership on protected requests. Staff access is role-based, with an audit history for administrative changes. Keep your password private, enable the available account security options and report unexpected access promptly.

Isolated previews

Projects use separate HTTPS preview hostnames and host-bound access sessions. Build environments are separate from the NYNZ web server. These controls protect access boundaries; they do not certify generated code as secure or make a private preview suitable for production use.

Secrets and generated applications

Do not paste production credentials into prompts, files intended for the browser, screenshots or support messages. Rotate any credential you expose. Review dependencies, authentication, database permissions, input handling and data collection in your generated app before deployment. Connected customer databases remain your responsibility.

Report a concern

Send a security report to support@nynz.in with the affected feature, a description and safe reproduction steps. Do not access another person’s information or disrupt a system to demonstrate an issue. NYNZ does not currently advertise an independent security certification, a bug-bounty reward or a guaranteed response time.

Need help?

Write to support@nynz.in, or visit our contact directory.