Current preview
The website does not run collection jobs or store customer API results. Its examples contain illustrative data. Website traffic, optional analytics and email inquiries are described in the privacy notice. The provider list identifies the services used for those purposes.
Collection boundaries
The API design targets supported web sources with an explicit input and output contract. Source names in the catalog are candidates, not confirmation of live access or endorsement. Capabilities requiring an end user’s personal source-site password or session token are outside the selected product boundary.
Availability, permitted use and technical limits must be reviewed for each source before opening a capability. Describing a source as public does not establish unrestricted rights to every use of its data.
Freshness and caching
The planned contract distinguishes retrieval time from the source’s own update time. source.fetchedAt records when TrueFetch fetched data; it does not promise the source itself was current. source.cacheHit identifies reuse. Requesting maxAgeS=0 means fetching again rather than using TrueFetch’s cache, not a guarantee of real-time source data.
Cross-tenant reuse is limited to public data permitted for reuse. Tenant results, private parameters and authorization contexts remain isolated. Reading an existing result and creating a new collection are different actions.
Retention and deletion
The design defaults to seven-day result retention and 30-day request-log retention, with shorter result retention available. These defaults are not evidence of a deployed API configuration. Necessary accounting records require separate retention rules before billing opens.
Deletion and suppression must take priority over ordinary expiry, including after restoring backups. A result URL does not promise permanent storage. Deleting a TrueFetch copy cannot recall copies already downloaded by a recipient.
Questions, removal and abuse reports
Email [email protected] with the relevant public URL, the concern and enough information to identify the material. Do not send identity documents or sensitive records in an initial report. We will use the inquiry to assess the request and any necessary follow-up; this preview does not promise an automated removal service or a fixed response deadline.
For vulnerabilities, use the security reporting guidance.