Security & Trust

1. Customer Data Boundaries

Customer operational data is scoped to each organization. Each organization's data is stored and accessed separately. One organization's data is not accessible to another organization through the application.

The public demo environment uses a separate set of designed sample operating data. Real customer data from paying or early-access organizations is not used in public demo pages.

Customer operational data — including datasets, KPI configurations, targets, alerts, improvements, and reports — belongs to the customer. Detegere processes this data to deliver the service.

2. Data Detegere May Handle

Depending on your use of the platform, Detegere may handle the following types of data:

• Account information: email address, name, and authentication credentials
• Organization profile and membership records
• Operational datasets uploaded by your organization
• KPI definitions, values, targets, and threshold configurations
• Alerts and alert trigger history
• Operational events and annotations
• Improvement and action records
• Reports and analysis outputs generated from your data
• Public contact and interest submissions from the public site
• Security logs: login events, IP addresses, and security-relevant actions

3. Access and Organization Isolation

All data access in the Detegere backend is checked against the requesting user's organization. The backend is the authoritative enforcement point for access control — the frontend enforces user experience constraints but does not act as the security boundary.

Role-based access control is in place within organizations. Certain actions are restricted to users with appropriate roles (for example, admin-only configuration changes).

Org-scoped access enforcement means that API calls that attempt to read or write data outside a user's own organization are rejected by the backend, regardless of what the frontend sends.

4. Public Demo and Sample Data

Detegere's public demo uses purpose-built sample operating data designed to illustrate the product's capabilities. This sample data does not represent any real customer, facility, or operational dataset.

The demo environment is a separate access path with its own authentication logic. It is not connected to customer organizations or real operational data.

5. Security Safeguards

The following safeguards are implemented in the current product:

• HTTPS (TLS) enforced for all connections to the platform — data in transit is encrypted
• JWT-based authentication with token expiry
• Passwords stored using bcrypt one-way hashing — not readable in plain text
• Login security tracking: failed attempts and suspicious activity are logged
• Rate limiting applied on sensitive flows including login and public form submissions
• Organization-scoped access enforced at the API layer
• Generic error responses on auth failures — no enumeration of valid accounts
• Upload size limits to prevent resource abuse
• Security headers configured on API responses
• CORS configured to restrict cross-origin access
• Optional Sentry error tracking — not configured in production by default
• Secrets and credentials are not stored in source control

No system can eliminate all risk. We are continuing to develop our security practices, incident response procedures, and operational monitoring as the product matures.

6. Privacy and Communication Controls

Detegere does not currently operate an active automated email program. If you submit your email through a public form, a team member may follow up with you directly.

A consent data layer is in place for future communications — any future email program will be built on explicit opt-in consent with version-tracked consent text and suppression support.

For full details on how we collect, use, and handle your information, see our Privacy Notice. The terms governing your use of the platform are in our Terms of Use.

7. Product and Analytics Boundaries

Detegere is a decision-support tool for operational intelligence. It surfaces patterns, signals, and anomalies from operational data to inform human judgment — it does not make autonomous operational decisions or control physical equipment.

Detegere is not a safety-critical control system. Outputs — including alerts, root cause views, reports, and operational summaries — are meant to inform human review, not replace it. Customers remain responsible for evaluating platform outputs and for the operational decisions and actions they take.

Statistical patterns and correlations in the platform do not constitute guaranteed causal proof. See our Terms of Use for the full scope of analytics disclaimers.

8. Current Readiness Status

The table below reflects our honest assessment of current readiness for key areas. Items marked "pending" or "not launched" are known gaps we are actively working to address.

9. Contact

If you have questions about how Detegere handles data, security practices, or the content of this page, please reach out through the Contact page or email us directly at [email protected].