Product privacy policy

Privacy controls are part of the product architecture.

This page describes the current product privacy design and operating controls. Final legal/commercial approval is a separate launch gate and is not claimed by this engineering checkpoint.

VeriCrawl separates authenticated customer data by authorization and Project ownership. Administrative access is permission-controlled and audited where consequential. Private runtime secrets are kept outside the public repository. Consent defaults to essential-only unless a user makes another supported choice. Privacy requests, retention operations and governed data-management workflows belong to the existing security/governance system.

Current privacy controls

Access boundaries

RBAC, customer ownership and IDOR protections remain server-side requirements.

Consent

The public shell defaults to essential-only and does not activate optional providers just because a page renders.

Auditability

Consequential administrative and privacy operations retain governance/audit evidence where the canonical engine provides it.

Secret isolation

Database credentials and provider secrets remain private runtime data rather than public CMS content.

Have a privacy question?

Use the governed contact route for a privacy or product-policy enquiry.

Direct answer · Entity: VeriCrawl

How does VeriCrawl describe privacy at this stage?

The current privacy page documents product data-handling and consent behavior supported by the implemented system. It does not claim final legal approval, market-specific compliance certification or provider behavior that has not yet been activated and verified.

Evidence & provenance

Answer is limited to implemented VeriCrawl capabilities, governed content and stored evidence. Search-engine or AI-system visibility is external and is not inferred.

Methodology & evidence standards Product Privacy