Lawful Use Policy

This policy applies to every order placed with DataRiver New Zealand Limited, NZBN 9429050155972, trading as OvernightOps. It forms part of the Statement of Work you accept at checkout and is linked from the consent you affirm before payment.

Policy version: LU_v1.0. The version in force is the one published at the time of checkout and recorded against your order.

1. Our position

Legitimate engineering regularly touches sensitive areas: AML and KYC compliance tooling, fraud detection, authorised penetration testing, security research, content moderation, licensed gambling platforms, and pharmaceutical compliance. We support that work. What we refuse is work that exists to commit, enable or conceal an unlawful activity. Our screening is therefore designed to read intent, not to block keywords.

You confirm that the work you order — and every output we deliver — will not be used, directly or indirectly, for any of the activities below. This representation is a condition of the agreement and is repeated in Clause 11 of the Statement of Work.

2. Activities we do not support

The 55 unlawful-activity classes we screen for are grouped into the eleven categories below. This list is illustrative, not exhaustive: we may decline any order on reasonable compliance grounds.

3. The standards our practices are informed by

Our screening, review and delivery practices are informed by the frameworks below. This is an alignment statement only: it is not a certification, accreditation or attestation, and we do not claim to hold any certification we have not formally obtained.

4. How pre-payment screening works

1. Deterministic scan. Before payment can be authorised, the order details — the current state, target state, constraints and access notes you type, plus repository names and any documentation branch — are screened against all eleven categories. The scan is instant, repeatable and runs both in your browser (for live feedback) and on our servers (authoritatively).
2. Sentence-level context. A compliance or counter-abuse phrase in the same sentence (for example “AML”, “KYC”, “fraud detection”, “authorised penetration test”, “our own systems”, “content moderation”) clears that match. A phrase elsewhere does not.
3. Clear, flagged or blocked. A clear scan unlocks payment once the other gates are met. A flagged result keeps payment off: you can revise your answers to make the lawful purpose explicit, or request a manual review. A blocked result — child sexual abuse material, ransomware/botnet/DDoS builders, counterfeit operations, sanctions or OFAC evasion, weapons or ghost guns, no-prescription pharmaceuticals, or trafficking — keeps payment off and can only be resolved by revising the order; if you believe it is an error, contact [email protected].
4. You always see the reason. When we cannot clear an order automatically, we show exactly which passage our review flagged, in your own words. There is never a silent gate.

5. Manual review

If you request a manual review, your order enters our compliance queue and we typically respond within two business hours. You can also revise your answers at any time and re-run the scan. Payment only unlocks after a reviewer records an approval for that specific order. If a review is rejected, we explain the decision and invite you to revise the order.

6. Delivery-team re-verification

Screening does not end at payment. Before work proceeds, our delivery team re-checks the materials you provide — including documentation converted from your repository — against this policy. If a concern appears once work has started, the team pauses, records the concern and follows up through your delivery dashboard. Illegal use may result in the order being held or cancelled in line with Clause 11 of the Statement of Work.

7. What we may do

• Refuse, hold or cancel any order on reasonable compliance grounds.
• Provide a full refund where we cancel an order and no work has been delivered.
• Report suspected unlawful activity to the appropriate authorities where we are legally required or permitted to do so.

8. Contact

Questions about this policy, or a belief that an automated flag is in error, can be sent to [email protected]. The full contractual terms are in the Statement of Work (Clause 11) and the Terms of Service.