The preview is explicit about what it does and what it does not do.
The current DiligenceFox website includes a browser-based product preview. That matters because trial users may want to test the workflow without uploading sensitive internal documents to a live external platform yet.
Browser-based preview
The free beta preview runs locally in the browser. In the current package, uploaded files stay on the user’s device and are used only for local interface simulation.
No overclaiming
DiligenceFox does not claim to provide formal legal advice, certification, or guaranteed compliance outcomes. The product is about buyer-ready documentation and diligence workflow.
Transparent beta scope
The preview is intended to show the product shape, output structure, and UX. It is not a production-hosted document processing service yet.
Safe evaluation path
Prospective users can open the sample workspace first, then personalize the trial preview with low-risk files before deciding whether they want deeper access.
What happens to trial inputs in this preview.
This page should stay conservative. Buyers evaluating trust software care as much about honest scoping as about polished claims.
| Area | Current preview behavior | Recommended production direction |
|---|---|---|
| File upload | Files are handled locally in the browser for the beta preview. | Move to secure server-side storage with access control and auditability. |
| User accounts | No production account system in the current website preview. | Add authenticated workspaces and role-based access later. |
| Generated outputs | Outputs are generated from structured local demo logic. | Add production generation with source-traceability and workspace persistence. |
| Data retention | Browser preview data stays on-device unless the user exports or emails it. | Publish explicit retention and deletion controls in the hosted product. |
| Security review | Questions can be directed to the published email addresses. | Provide a dedicated trust page and security response package for hosted plans. |
Recommended trial guidance
- Use the sample workspace first.
- In the personalized preview, prefer low-risk documents or redacted examples.
- Do not assume the current website preview is the final hosted product architecture.
- Use trust or security contact addresses for questions before sharing sensitive internal material.
Recommended messaging discipline
- Say “buyer-ready AI diligence materials,” not “instant compliance.”
- Say “system card” or “trust page draft,” not “certified documentation.”
- Say “review and refine outputs,” not “fully automated decisions.”
- Preserve clear unknowns instead of inventing polished answers.
Keep security and trust questions separate from general contact.
That helps the site feel operationally real from day one, even before the full hosted product exists.