Acceptable Use Policy
This policy applies to the public website and expresses baseline conditions for any future MyDataNinja pilot. A pilot may add stricter, product-specific controls.
Published and last reviewed: 11 September 2026This document reflects the website implementation reviewed on the date above. It is not a lawyer’s approval or a guarantee of compliance in every jurisdiction.
Authorized data and systems
Submit or connect only information and systems you are authorized to use for the agreed purpose. You must not connect third-party customer data, repositories, credentials, or services merely because you can technically access them.
A person cannot authorize security testing, repository changes, or agent actions against a system they do not own or control with adequate permission.
Prohibited conduct
Do not use the website or any future pilot to distribute malware, steal credentials, evade safeguards, conduct unauthorized surveillance or testing, infringe intellectual-property or privacy rights, generate deceptive impersonations, facilitate discrimination, or perform illegal or harmful activity.
Do not place secrets, production credentials, regulated data, or unrelated personal information into prompts, requirements, logs, or test fixtures unless a written pilot scope expressly allows and protects that data.
Customer feedback and connected content
You remain responsible for having appropriate rights and notices for customer feedback, business data, source code, transcripts, and third-party material supplied to a future pilot. Generated themes and requirements do not transfer ownership of source material or expand third-party licenses.
Agent and code actions
Future agent work must stay inside approved repositories, paths, credentials, budgets, and tasks. Do not attempt to bypass approval gates, branch protections, test requirements, stop controls, or audit records. Agent proposals require qualified human review before merge or deployment.
Enforcement
We may reject a request, pause evaluation, restrict a pilot, preserve relevant records, or end access when activity creates security, legal, or operational risk. Emergency action may occur before notice when needed to protect people, systems, or data.