Public Data and Data Sources Notice

Monocrawl is a technical access and normalisation service. At a customer’s request it sends identifiers such as a public username, URL, post ID or search term to an official API, independent upstream API or publicly accessible page, then returns the resulting record in a documented schema.

Depending on the endpoint, a result may include a public profile identifier, biography, avatar or media URL, public post or comment, public engagement count, publication time, public company or repository information, marketplace listing, or related public metadata.

Monocrawl does not ask customers to provide a social-platform password or session cookie and does not use customer credentials to enter a private account area.

• Official or publisher-operated APIs, for example APIs made available by a platform or public body.
• Commercial independent API providers used under the applicable supplier agreements.
• Publicly accessible web pages or feeds where the endpoint documentation identifies that method.
• Monocrawl cache entries created from a prior permitted request, normally for a short documented period.

The categories of upstream supplier behind the service are described in the Privacy Notice (section 6); individual suppliers are recorded in our private supplier register and in each route’s technical metadata. The endpoint, response metadata, documentation and warnings provide the practical provenance available for a particular request. A provider name in technical metadata identifies the route used; it does not imply sponsorship or partnership.

Public availability does not place personal information outside data-protection law. For limited request-driven retrieval and short caching, NTV LTD relies where applicable on legitimate interests in operating a secure data-access service, enabling customers to access public online information efficiently, maintaining provenance and preventing abuse. We assess necessity and impact, minimise account identifiers sent upstream and provide objection and request routes.

Information is normally obtained from the source named above rather than directly from the person it concerns. Categories are the public identifiers, content and metadata listed in section 1. Recipients are the requesting customer and the infrastructure/upstream providers needed to fulfil and secure the request. The Privacy Notice explains processors, transfers, retention criteria and data-subject rights.

Customer-requested features can also save results, check a public source for changes, combine relevant sources or generate a source-based summary. Those activities may retain information longer than the response cache and may send relevant source material to a model provider. Their purpose and impact require consideration in addition to the original lookup; public availability alone does not justify every monitoring or analysis use.

For proportionate saved research and public-source change checks, our legitimate interests are helping customers revisit relevant evidence and detect the changes they request. We consider the necessity, retention and impact of that processing separately from account administration. Results may be exported or delivered to customer-configured recipients. The Privacy Notice describes the different retention periods and deletion controls.

We do not intentionally use API results to create our own sensitive-person profiles, make decisions about the person, or infer protected characteristics. A customer may not use Monocrawl for unlawful surveillance or solely automated significant decisions contrary to the Terms.

A result can be incomplete, stale, duplicated, mistranslated, misattributed or wrong. Counts change; source accounts are renamed or deleted; upstreams truncate, reorder and cache records. Null and warning fields are deliberate disclosures, not invitations to guess.

Public accessibility does not remove copyright, database rights, trade marks, confidentiality, privacy, publicity rights or restrictions binding on a customer. Monocrawl does not grant a customer ownership of third-party material or permission an upstream rightsholder has not given.

For consequential decisions or publication about a person, verify the record at the primary source and consider context, date, identity ambiguity and applicable law.

• Establish and document a lawful purpose and data-protection basis for your own collection, enrichment, storage, combination, disclosure and decision-making.
• Give privacy information where your law requires it and honour access, objection, correction, deletion and other rights for systems you control.
• Use proportionate retention and security, avoid collecting unnecessary personal information, and do not republish a raw response merely because it was technically retrievable.
• Respect platform terms and third-party intellectual-property or contractual restrictions that apply to you.
• Do not attempt to turn public endpoints into access to private, deleted, paywalled or access-controlled material.

What to send

Use the “Public-data correction or removal” category at Contact. Include the source URL or stable identifier, endpoint if known, what is inaccurate or objectionable, the relationship to the record, and the outcome requested. Do not send identity documents unless we ask for proportionate verification.

What we do

We record and assess the request, verify enough information to avoid acting on a malicious request about another person, and inspect Monocrawl-controlled caches or stored job/monitor data. We then take the action required of us and technically available to us, which may include deleting a Monocrawl-held copy, stopping a customer-controlled monitor or explaining why the request cannot be met. Where the authoritative record remains with an upstream or platform, we may direct you to that source or pass an appropriate request to the provider. We will not call an independent provider a partner.

When we accept a restriction, we record the verified source URLs or platform identifiers and withhold matching requests and results through Monocrawl, including matching cached and saved results. We review relevant retained copies and monitors before completing the request. Restrictions depend on the identifiers we can reliably match: a name alone does not establish that two records concern the same person. Please tell us about changed identifiers or additional source URLs that should be reviewed.

A restriction in Monocrawl does not remove a source record or copies already received by others. Where required, we notify recipients of a correction, erasure or restriction. We retain proportionate request, identifier and decision evidence to honour the restriction, handle the request, meet legal obligations and defend legitimate claims.

We respond without undue delay, normally within one calendar month. If a lawful extension is needed, we explain why before the applicable deadline.

A person may also object to legitimate-interest processing. We will stop unless we demonstrate compelling legitimate grounds overriding their interests, rights and freedoms, or processing is required for legal claims. Direct marketing objections are handled unconditionally.

Platform names and logos identify the subject or source of an endpoint. Unless a page expressly and accurately says otherwise, those platforms do not sponsor, endorse or partner with Monocrawl. Official API use means only that the request uses an API made available by its operator.

Coverage and upstream route can change. The live catalogue and endpoint documentation, rather than a marketing logo, determine what is currently callable.

NTV LTD is responsible for Monocrawl-controlled processing. Submit public-data or privacy requests through the recorded request form, which provides a reference and works without an account. Postal notices may be sent to the registered office shown above.