M.01
Every report is attributable
No record enters the system without a named author, shift, site and moment. Anonymous filings are not an option.
›XSECURITY & COMPLIANCE
Security is part of the
operating layer, not an appendix.
FieldOps is the authoritative system of record for operations where evidence, attribution and retention are contractual obligations. Security is not a compliance attachment — it is the structural property of a field-operations system that must survive client disputes, insurer claims, regulatory requests and legal scrutiny.
AUDIT TRAILIMMUTABLETIMESTAMPED
›X.01SECURITY POSTURE AT A GLANCE
Seven lines for procurement.
Seven structural commitments.
Operator
SenSec LLC — Wyoming, USA30 N Gould St, Ste N, Sheridan, WY 82801 · US-registered legal entity operating FieldOps globally.
Tenancy
Cloud · Private · On-premiseTenancy model chosen per contract and jurisdiction — not per price tier.
Data residency
United States by defaultHosted where the client requires — EU/UK, Middle East in-country (UAE / KSA), on-premise or sovereign.
Certification
SOC-2 Type II — audit in progress · CCPA · GDPR-readyIndependent SOC-2 Type II audit underway (observation period). Architecture aligned to ISO 27001 and NIST 800-53 control families — not certified. GDPR alignment for EU-hosted deployments.
Evidence integrity
Tamper-evident chainContent-addressed, cryptographically signed, access-audited on every retrieval.
Identity
SSO · SAML · OIDCRole-scoped access with full attribution across field, dispatch, command and client layer.
Retention
Jurisdiction-awareConfigurable per contract, legal request and evidence class — default 36 months, extendable.
›X.02WHAT THIS MEANS OPERATIONALLY
The posture, translated
into day-to-day operation.
Procurement reads certificates. Operations lives with the consequences. Six of them.
M.02
Every edit is timestamped
Amendments, corrections and retractions are versioned. Nothing is silently overwritten — the edit history is part of the evidence.
M.03
Evidence is bound to the event
Voice, photo, video and signal data are content-addressed and bound to the incident or task they belong to. Reconstruction is a query, not a forensics project.
M.04
Access is role-scoped
Guard, Supervisor, Dispatcher, Manager and Client see different views of the same record. Visibility is policy, not UI.
M.05
Retention follows the contract
Retention schedules align to client contract, regulator requirement and evidence class — not to a default setting.
M.06
Client release is filterable
What leaves the operation to the client is explicit, audited and redactable — evidence release is an operational action, not a database export.
›X.03IDENTITY AND ACCESS MODEL
X.03 · Identity
Five roles, one record,
role-scoped visibility.
Identity is bound to the five operational roles — Guard, Supervisor, Dispatcher, Manager and Client. Access is scoped by role, by site and by contract. The same record is read differently at each layer; no role sees more than its operation requires.
- Role model — Guard, Supervisor, Dispatcher, Manager, Client — enforced at the data layer, not the UI
- Enterprise SSO via SAML 2.0 and OIDC; identity provider of record on the client side
- Least-privilege default — access scope granted per contract, site and role, not per seat
- Scoped client visibility — per-site, per-contract, per-evidence-class, with filter-on-release
- Session and access audit — every read, write and export is attributable and retrievable
- De-provisioning bound to HR signal — leavers lose operational access at the source, not at the ticket
›X.04EVIDENCE INTEGRITY
X.04 · Evidence
Content-addressed, signed,
legally retrievable.
The evidence chain is where field reality becomes legally defensible. Evidence is not uploaded media — it is a cryptographic chain bound to an incident, a task or a shift, retrievable under dispute, claim or regulatory review.
- Content-addressed storage — every artefact is identified by its cryptographic digest
- Cryptographic chain — evidence items are signed and linked to the operational event
- Tamper-evident — any modification is detectable, versioned and attributable
- Export log — every retrieval, download and client release leaves an access record
- Legally relevant retention — evidence class mapped to jurisdiction and contract
- Audit access history — who read what, when, from which client and under what scope
›X.05DEPLOYMENT AND DATA RESIDENCY OPTIONS
X.05 · Residency
US-operated, globally
deployable, jurisdiction-aware.
SenSec LLC operates from Wyoming, USA. Data defaults to US residency. Where client, sector or regulator requires otherwise, FieldOps is deployed under the tenancy and residency the operation needs — not the one the vendor prefers.
- Cloud — multi-tenant, US-residency by default, SOC-2 Type II audit in progress
- Private tenancy — dedicated infrastructure, client-isolated, region of choice
- On-premise sovereign — client-hosted, air-gapped where required, audit-aligned
- Regional residency on request — EU, UK and Middle East in-country (UAE / KSA)
- GDPR-ready posture for EU-hosted deployments — DPA and SCCs available under contract
- Aligned to ISO 27001 and NIST 800-53 control families — control mapping shared under NDA; not a certification claim
- Residency is contracted, not toggled — every change is a formal deployment step
›X.06PROCUREMENT NOTE
For procurement teams
If your procurement process requires the detailed security brief — including third-party audit reports, penetration test summary, data processing addenda, sub-processor list and evidence integrity architecture — it is shared under NDA as part of the operational assessment.
This page is the public posture. The full document is how we answer procurement. We do not publish it for the same reason we do not publish client names: the operation is the client's, not ours to advertise.
›X.07RESPONSIBLE DISCLOSURE
X.07 · Disclosure
Coordinated disclosure,
safe harbor for good-faith research.
FieldOps carries operational data — incidents, patrols, evidence. We take reports of security weaknesses seriously and coordinate with researchers acting in good faith. This page is the single authoritative channel; please use it before any public disclosure.
- Primary channel — security@sensec.app; PGP key available on request
- Acknowledgement — receipt confirmed within two business days, triage typically within five
- Coordinated timeline — we aim to remediate within 90 days; extensions discussed in writing where complexity requires it
- Safe harbor — good-faith research within this scope will not trigger legal action from SenSec LLC
- Credit — public acknowledgement on request; anonymous reports equally welcome
- No bounty program at this time — we respond, fix and credit; monetary rewards are not offered
In scope
- sensec.app and its documented subdomains; the FieldOps web and mobile applications
- Authentication, authorisation and tenant-isolation flows
- Data handling of Customer Data (integrity, confidentiality, audit trail)
- Public API endpoints used by the platform
Out of scope
- Social engineering of SenSec personnel, customers or their staff
- Denial-of-service, volumetric or resource-exhaustion testing against production
- Physical attacks against SenSec or customer premises
- Findings against third-party services, vendors or customer-hosted integrations
- Reports generated purely by automated scanners without demonstrated impact
What we ask of researchers
- Do not access, modify or exfiltrate data beyond what is strictly necessary to demonstrate the issue
- Do not disclose publicly before we have had a reasonable opportunity to remediate
- Provide clear reproduction steps, affected component and, where possible, a proposed mitigation
- Use test accounts rather than real customer data; report data exposure immediately and stop
Email: security@sensec.app
PGP: available on request
Postal: SenSec LLC, 30 N Gould St Ste N, Sheridan, WY 82801, USA
NEXT STEP
Procurement-ready posture,
operational-grade evidence.
Twenty minutes is enough to understand whether our security posture matches your contractual and regulatory obligations.