WASID Acceptable Use Policy (AUP)

Last updated: 2026-07-28 Provider: Boldstep Productions Ltd, Accra, Ghana Contact: the access-request form

This Acceptable Use Policy governs use of WASID ("the Service") and is incorporated into the Terms of Use (Terms of Service). It applies to every tier (Signal, Watch, Analyst) and every customer worldwide. Violation may result in suspension or termination of your API key or account (Terms §8).

1. The core rule: events, not people

WASID exists to report verified events at places — not to watch people. You may not use the Service, alone or combined with any other data, tool, or model, to:

identify, locate, track, profile, or surveil a named or identifiable individual;
attempt to re-identify any person from event data, pseudonymised tokens, or scrubbed source text;
target an individual or group for harassment, retaliation, or violence;
support law-enforcement, intelligence, or military targeting of individuals. This exclusion is deliberately broad: "events-not-people" is a product boundary, not just a compliance posture.

This is the product's defining boundary. We enforce it without a grace period.

2. Lawful use

You may not use the Service in violation of applicable law in Ghana, in your own jurisdiction, or in any jurisdiction where you act on WASID data — including data-protection law (Ghana's Act 843, the GDPR/UK GDPR where they apply to you), sanctions and export-control regimes, and anti-corruption law.

3. Data handling and redistribution

No resale or redistribution of the feed, events, or alerts to third parties without our prior written consent (Terms §3). Internal use within your organisation, per your tier, is what your licence covers.
No misrepresentation: do not present unverified or dismissed candidates as verified, strip confidence scores or provenance in a way that misleads, or pass WASID data off as your own original reporting.
No corpus building: do not systematically extract, archive, or scrape the Service to build a competing dataset, train a model on our verified feed, or reconstruct our source list or verification methodology.

4. Life-safety decisions

Per Terms §2: WASID is one input to a competent risk process, not a life-safety system. You must not wire the Service as the sole automated trigger for evacuation, armed response, or any decision where being wrong means death or serious injury, without independent corroboration and human judgment in the loop.

5. API and platform integrity

You may not:

share, sublicense, or pool API keys across organisations, or use another customer's key;
circumvent or probe rate limits, plan-tier gates, or authentication;
probe, scan, penetration-test, or load-test the Service without our prior written permission;
attempt to access another customer's assets, watchlists, alerts, or account data, or any internal surface (including the verifier console) you were not granted;
attempt prompt-injection or similar attacks against the extraction/verification pipeline (e.g. crafting or planting source content designed to manipulate verification outcomes);
introduce malware or interfere with the Service's operation or other customers' use.

6. Ingestion integrity (Analyst tier)

If you hold Analyst-tier access, you additionally may not:

submit fabricated, deliberately misattributed, or personal-data-bearing candidate events;
verify or dismiss events other than through the audited verification flow;
disclose unverified queue contents outside your authorised role.

Every verification decision is recorded in an append-only audit trail; Analyst access is conditioned on that trail staying meaningful.

7. Enforcement and reporting

We may investigate suspected violations, suspend or revoke keys immediately for serious violations (especially §1, §5, and §6), and report unlawful activity to authorities. Where practicable we give notice and a chance to cure for lesser violations.

Report suspected violations to the access-request form.