Use Cases

Version Phase 7 draft

Datorus is built for teams that collect openly available web information at scale. This page lists the customer scenarios we actively support, as well as the restricted scenarios that fall outside our Acceptable Use Policy. Pair this catalogue with our AUP for the full conduct expectations.

Permitted use cases

Representative scenarios that Datorus is built to serve. Each entry is permitted on the standard plan, in line with our Acceptable Use Policy and the published terms of any target site.

  • Public price monitoring

    Observe openly listed catalogue prices, availability, and promotion banners on retailer and marketplace sites that publish that information to any visitor. Customers respect declared rate limits and operator terms.

  • Search-engine result observation

    Sample the organic, openly returned SERP layout for a query set — ranking, snippets, knowledge cards — for SEO research, brand observation, and visibility tracking. No interaction with authenticated surfaces.

  • Public market intelligence

    Aggregate openly published market signals — press releases, regulatory filings, public statements — for competitive analysis, sector research, and journalist-grade investigation of publicly available material.

  • Public-web data collection

    Collect openly published web content (catalogues, directories, encyclopaedic references, public datasets) that the operator has elected to make freely available, subject to the target site's published terms and rate limits.

Restricted use cases

Datorus will not support the following scenarios. The list mirrors the Restricted Use section of our Acceptable Use Policy and is enforced through onboarding review, ongoing account oversight, and the reporting channels listed below.

  • Account-takeover or manipulation activity

    Activity intended to operate, register, or impersonate user accounts on a target site in a manner that misrepresents the requester or contravenes the operator's identity controls.

  • Restricted or authenticated content

    Interaction with content that the operator has placed behind authentication, paywalls, or other access controls, or that is otherwise not openly available to a typical visitor.

  • Personal data subject to privacy law

    Collection of personal information that is governed by applicable privacy regulation (such as identifiers, contact data, or sensitive attributes) outside of a documented lawful basis.

  • Violation of published target-site terms

    Conduct that contravenes the published terms of service, robots directives, or operational rate limits of a target site, including activity that the operator has explicitly indicated is not permitted.

  • Unauthorised data access

    Access to data, systems, or interfaces that the operator has not made openly available, including activity that would require credentials, tokens, or other authorisation not granted to the customer.

Questions about whether your scenario fits this policy, or a concern about another customer's activity? Reach our policy team atpolicy@datorus.com (contact form coming)abuse@datorus.com (contact form coming)support@datorus.com

Both policy@ and abuse@ are placeholders pending Phase 7 mailbox setup; until those inboxes are live, please direct correspondence to support@datorus.com with the topic in the subject line.

For the full conduct framework, see our Acceptable Use Policy. The AUP is the binding policy document; this page is the navigable use-case catalogue.