Security.

How Nuntex is designed

• Work modes set how far it may go. Start with Ask first.
• It writes only in the project folders you pick, on a branch per task, with commits under its own name.
• Every step that reaches other people needs your yes, one step per tap.
• Website changes wait for you to read the diff, are read back from the server after they go live, and roll back on their own if the home page breaks. About Put it live
• Checks are recorded from what actually ran, not from what it says. About proof
• A run has an hour. If it needs longer, it stops and says so.

How the waitlist is protected

• Sign-ups are kept outside the part of the server shown on the web.
• Internet addresses are kept only as scrambled codes, used to stop floods.
• Bots are ignored quietly, and one place can only sign up so often.
• Only Commoner Apps can read the list.

Reporting an issue

If you believe you have found a security issue in nuntex.com or Nuntex, tell us in a note on the waitlist that starts with the word Security, and we will reply by email. Please give us a reasonable time to fix it before sharing it.