Confidentiality & Privacy
Your observation program, your taxonomy, and your data are yours. Sentinel Watch is built around strict client confidentiality — by design, not as an afterthought.
Program Confidentiality
Enterprise clients often come to Sentinel Watch with research questions, model training objectives, or competitive intelligence needs that they cannot expose publicly. We treat every engagement as confidential from the first conversation.
No Cross-Client Data Sharing
Observation data collected under your program is never aggregated with data from other clients, never used to train shared models, and never sold or transferred. Each client engagement is isolated end-to-end.
Taxonomy Confidentiality
The classification schema you define — the event types, labeling criteria, and research parameters — is yours alone. We do not publish, reference, or repurpose client taxonomies. What you define stays within your program.
Observer Confidentiality
Observers are briefed on your program parameters without being told who the client is unless operationally necessary. They are bound by confidentiality agreements covering program scope, methodology, and observed data.
Data Handling
Observation data moves through a controlled pipeline from field capture to structured delivery. At every stage, access is scoped and logged.
Scoped Access
Only the personnel directly involved in your program have access to your observation data. Internal access is role-based and auditable. No observation data is accessible to staff outside the program scope.
Structured Delivery
Your data is delivered in the format you specify, to the endpoint you control. Sentinel Watch does not retain client observation data after the agreed delivery and retention period unless explicitly requested.
Dedicated MCP Connection
Enterprise clients who integrate via the Sentinel Watch MCP server receive a dedicated, scoped connection hosted at app.sentinel-watch.org. Your connection credentials, tool access, and data are isolated from other clients at the infrastructure level.
Observer Privacy Obligations
Observation programs operate in real-world environments where third-party privacy must be respected. Sentinel Watch programs are designed to comply with applicable privacy frameworks in the jurisdictions where observations take place.
- Public environment protocols — Observations in public or semi-public spaces follow guidelines aligned with local privacy law and ethical research standards. Observers do not record individuals without lawful basis.
- Commercial environment protocols — Programs operating in retail, hospitality, or other commercial environments are scoped in coordination with the venue operator to ensure appropriate legal basis for observation activity.
- Data minimization — Observers capture what the program taxonomy requires — no more. Personal identifiers are not collected unless explicitly required by your program and covered by appropriate legal basis.
- Jurisdiction awareness — Programs operating across borders are scoped with awareness of regional privacy frameworks including GDPR, CCPA, and equivalent local requirements.
Contractual Framework
Every client engagement is governed by a dedicated service agreement that codifies confidentiality obligations, data handling requirements, retention periods, and program scope. We do not operate on generic terms of service for enterprise programs. Your agreement is specific to your engagement.
If your organization has specific contractual requirements — NDA prerequisites, security questionnaires, data processing agreements, or legal review processes — we accommodate these as standard practice, not exceptions.
Questions About Data Handling?
If you have specific privacy, security, or contractual requirements, we are happy to walk through them before any engagement begins. Reach out and we will respond directly.