What stays local
Pasted rows, review text, generated drafts, and downloaded text files are handled by code running in your browser. The V0 tools do not create accounts, upload files, call an application API, or send tool input to ComplyEaze.
Browser-local by design.
Tool files are processed in your browser and are not uploaded by the tool. The site may still receive ordinary request metadata while serving static pages and assets.
What hosting may see
Static hosting, ingress, certificate, and security systems may process ordinary web request metadata such as IP address, user agent, request path, timestamp, and TLS details while serving pages and assets.
Cloudflare security checks
The public host may use Cloudflare security features, including JavaScript Detections or challenge scripts served from /cdn-cgi/challenge-platform, to evaluate automated traffic. Those systems may set Cloudflare cookies such as cf_clearance and process browser/security signals. They are not part of the tool workbench; the tool code must not intentionally send pasted tool rows or generated drafts to ComplyEaze or Cloudflare.
What not to paste
Do not paste real credentials, OTPs, CAPTCHA answers, Aadhaar numbers, bank details, portal cookies, full notices, ledgers, or taxpayer documents into public issues, screenshots, fixtures, or support threads.
Professional review
Outputs are drafts for review. Verify source documents, dates, amounts, identities, and statutory positions before sending anything to a client, counterparty, portal, authority, or auditor.