Privacy

How VeriTrust handles submitted content.

VeriTrust processes submitted images, message text, URLs, account and workspace records, scan results, profile information, and API usage metadata to operate the implemented review workflows.

Information You Submit

Web checks send the submitted image, message text, or URL string to the configured hosted inference service. Optional infrastructure enrichment also sends the image to the configured configured enrichment provider before inference.

Completed web checks can store scan metadata, result scores, model runs, indicators, and limited input previews in the active Supabase workspace. The current image route records file metadata but does not persist the original uploaded image file.

Avoid submitting secrets, unnecessary personal data, private credentials, or content you do not have permission to process.

How Data Is Used

Submitted content is used to produce the requested analysis. Web message and link history can include a preview of up to 500 characters plus a text hash; results can include extracted URLs, domains, email addresses, and phone numbers found in the text.

Developer API v1 calls record key, endpoint, scan type, status, request ID, and latency metadata for quota and usage reporting, but they do not create dashboard scan-history records in the current implementation.

API Keys

Raw API keys are shown only once. VeriTrust stores hashes, prefixes, masked values, scope metadata, timestamps, and usage limits, not the raw key value.

Access, Export, And Deletion

Users can export available scan reports as JSON or through the browser print flow. The current interface does not provide complete self-service account, workspace, or scan deletion; contact the platform operator for requests that are not exposed in the product.

Do not submit passwords, one-time codes, payment data, private credentials, or content you are not authorized to send to the configured service providers.