Site Rep Trust and Data Handling

Last updated: 2026-08-11.

This page explains what Site Rep does today, how customer and visitor data is handled, and which larger capabilities are not included today.

What is working now

• Source-backed answer behavior: the public bot answers from approved sources and asks for follow-up when source backing is missing.
• Customer dashboard: leads, conversations, unknown questions, source gaps, install health, exports, notifications, and deletion-review requests are visible in the private dashboard.
• Visitor data minimization: visitor records store only the question and any name, email, or need the visitor chooses to submit. Visitor IP addresses are used only transiently in memory for rate limiting and are not written to conversations or leads.
• No tracking cookies: the chat widget sets no cookies and no persistent local storage; it uses session-only storage (cleared when the tab closes) for a random session id.
• Access control: admin routes require server-side admin access, customer routes use scoped session access, and public widget routes do not return private access material.
• Paid unlock: Dodo and Razorpay paths unlock customer access only after server-side payment verification.
• Data exports: private bot backup, leads, conversations, follow-up queue, action queue, and answer report exports exist.
• Abuse and browser safety: public signup/chat/lead/install/feedback routes are rate limited and Worker responses include security headers.
• Storage separation: Durable Objects coordinate writes, D1 stores high-volume ledgers, and private R2 stores large source content server-side.

Sub-processors

Data is processed by Cloudflare (Workers, Workers AI, D1, R2, KV), Dodo Payments for billing, and the configured email provider. Cloudflare's Workers AI terms say customer content is not made available to other customers and is not used to train or improve services unless explicit consent is given; Site Rep storage services still keep the app data disclosed here.

What is not included today

• Site Rep does not currently include SOC 2 Type II, HIPAA, BAA, zero-retention, or no-training-on-data certification.
• Site Rep focuses on source-backed website chat, lead capture, and private follow-up queues. Full helpdesk replacement, native CRM sync, and automated execution are not included in the public self-serve product.
• Site Rep does not promise guaranteed conversion lift, guaranteed setup time, or enterprise omnichannel coverage.
• Larger legal, regional privacy, retention, and enterprise compliance requests need written review before purchase.

Data map

• Approved website sources: used to answer visitors with citations; customers can edit, replace, audit, export, and roll back supported snapshots.
• Visitor conversations and feedback: used for team follow-up, source repair, lead follow-up, and quality checks.
• Lead details: submitted by visitors for human follow-up; exported privately for the customer.
• Payment records: used only to verify checkout, activation, billing portal access, renewals, and plan status.
• Operational events: install checks, source health, quota warnings, notification receipts, and error visibility for reliability work.

Technical details

Structured trust details remain available for technical review and monitoring without making raw endpoints the main trust story.

The machine-readable trust status reports the same confirmed controls, not-claimed boundaries, and data map as this page, so the human story and the verifiable endpoint always match. Release identity and freshness live at release status.

Contact

Questions: hello@siterep.net