Acceptable use policy

Last updated: 30 September 2026

This Acceptable Use Policy (AUP) forms part of the Rabona Intel Terms of Service. It applies to every user, API client, integration, agent and other system accessing the Service through a customer account. Customer is responsible for ensuring its users and systems comply.

1. Lawful and authorised use

You may use the Service only for lawful business purposes and within your plan, documentation and permissions. You must not use the Service to:

• violate intellectual-property, database, privacy, publicity, confidentiality, contractual or other rights;
• copy, store, display, redistribute, syndicate or monetise publisher material without the rights required for that use;
• defame, harass, threaten, discriminate against, dox, stalk or unlawfully profile a person;
• facilitate illegal gambling, market manipulation, fraud, match fixing, insider dealing or evasion of sanctions or regulation;
• make employment, credit, insurance, housing, legal, health, safety or other high-impact decisions about a person based on automated output;
• collect or process children’s data, special-category data, government identifiers, payment-card data or other regulated data unless Rabona has expressly approved the use in writing;
• publish an automated allegation, rumour, sensitivity label or identity match as fact without proportionate human review and source verification; or
• misrepresent Service output as Rabona’s independent reporting, endorsement or verification.

2. Protect publishers, sources and individuals

• Use source links and provenance to verify material before acting or publishing.
• Respect publisher access controls, terms, copyright notices and lawful takedown or correction requests applicable to your use.
• Do not use Rabona source URLs, metadata or timing to overload, probe, circumvent or retaliate against a publisher or source.
• Do not reconstruct or distribute a substitute archive from summaries, blocks, Facts or repeated API calls.
• Do not use entity resolution or story grouping to identify a private person who is not reasonably identified in the underlying public reporting.

3. Protect the Service

You must not, and must not help another person to:

• probe, scan or test vulnerabilities without Rabona’s prior written authorisation;
• introduce malware, destructive code, abusive payloads or data intended to manipulate extraction or automated models;
• bypass authentication, authorisation, plan limits, rate limits, source restrictions, robots controls or safety mechanisms;
• share, sell or expose account credentials or API keys, or use credentials belonging to another organisation;
• distribute requests across accounts, keys, IP addresses or systems to evade technical limits;
• reverse engineer non-public components except to the limited extent a restriction is prohibited by law;
• access the Service in a way that degrades availability, creates disproportionate load or interferes with another customer;
• use the Service to benchmark or build a competing news-intelligence database or general-purpose training corpus without written permission; or
• remove provenance, rights notices, source links or technical measures attached to output.

4. API, agents and automated publication

• Use documented endpoints, bounded concurrency and retry with backoff. Honour HTTP status codes, cursors and cache guidance.
• Deduplicate and verify updates; a story may merge, split, be corrected or disappear from a result set.
• Do not treat summaries, Facts, classifications or sensitivity fields as infallible.
• Do not allow an autonomous agent to publish, accuse, place a wager, execute a trade or take another material action solely from Service output without safeguards appropriate to the risk.
• Maintain logs and controls sufficient to identify the integration and stop it promptly if it behaves unsafely.

5. Security and incident duties

Use least privilege, keep credentials out of client-side code and public repositories, rotate exposed keys, and request removal of former users through available controls or Rabona support. Notify Rabona without undue delay through the designated security contact if you suspect compromise, unauthorised access, material abuse or a vulnerability.

Rabona will not treat good-faith security research as a violation solely because it reports a vulnerability, provided the researcher avoids privacy violations, data access beyond the minimum needed to demonstrate the issue, disruption, extortion and public disclosure before Rabona has had a reasonable opportunity to investigate and remediate. This limited safe harbour does not authorise testing that applicable law prohibits.

6. Enforcement

Rabona may investigate suspected violations; preserve relevant records; rate-limit, quarantine or disable a key; remove or restrict data; suspend features or accounts; require remediation; notify an affected customer, publisher, provider or authority where lawful and appropriate; and terminate access for material or repeated violations. We may act immediately where delay could create security, legal, infrastructure or third-party harm.

Rabona will consider context, severity, intent, recurrence, cooperation and risk when deciding action. Customer must cooperate with reasonable investigations and remediation. Enforcement does not limit other contractual or legal remedies, and Customer remains responsible for fees incurred before suspension.

7. Reporting concerns

Reports should identify the account or integration, relevant URLs or request identifiers, timestamps, the suspected violation and supporting evidence. Before publication, Rabona must establish and publish monitored abuse and security contact routes; draft addresses must not be advertised until they can receive mail.