Trust
Know what you’re deploying.
DataSitr is preparing a focused pilot for employees using AI in company-managed browsers. Here is the scope, the data flow, and the work required before employee use.
Start with a defined boundary.
The first Browser Guard pilot covers one managed desktop browser, one operating system and one agreed AI website. Its two checks look for personal data and match text against protected content enrolled by your organization. Each selected site needs its own send and paste checks. A second site joins the pilot only after those checks pass in the agreed browser.
Whole-device protection, native AI applications and selective inspection of uploaded files are outside this scope. An allowed message means it passed the configured checks; it is not a guarantee that every sensitive detail was found.
Some unavailable checks warn instead of blocking. The pilot must verify the selected failure policy before employees rely on it.
Know where the text goes.
In the intended pilot setup, full personal-data detection sends prompt text to the agreed DataSitr detection service. The protected-content check matches enrolled content locally in the browser; policy and event reporting can still use the service.
Before real records are used, agree the service location, permitted data, employee notice, reporting and retention with your privacy and IT owners. The public website uses separate AWS hosting and content delivery.
What the evidence establishes.
Earlier gateway benchmarks are dated technical records. They do not establish current browser accuracy or independent product validation.
- Implemented
- Browser checks, warning and blocking paths, tenant enrollment, signed policy delivery and local protected-content matching exist in the implementation.
- Tested locally
- Local browser exercises cover send, paste, warnings and blocks using synthetic content. They do not establish compatibility with every live AI site or customer-managed device.
- To prove in your pilot
- The chosen website, managed installation, policy changes, session renewal and rollback need verification in your environment. Current sessions last 24 hours and require deliberate re-enrollment.
- Live today
- The website is live. As of 27 September 2026, public product access is unavailable. A pilot environment must be arranged and verified before employee use.
Agree the review and the decision.
Start with synthetic Arabic and English examples. Measure missed sensitive content, unnecessary interruptions, completed tasks and the time added to the workflow. Review warning, block and unavailable states with the people who will use them.
The closeout should identify what passed, what failed and whether to expand, adjust or stop. Installation and recovery evidence belongs alongside detection results.
DataSitr does not claim regulatory accreditation, independent security certification or guaranteed prevention. Contractual service levels, support, retention and responsibilities belong in the agreed pilot terms. Ask for the evidence relevant to your scope rather than relying on an older document’s title or score.