FieldOps ADMIN
Privacy Policy
FieldOps ADMIN provides Android access to the administration and client features of FieldOps. It is developed and provided by SenSec LLC, 30 N Gould St, Ste N, Sheridan, WY 82801, USA. Android package: ai.sensec.admin.
This policy covers the app’s embedded web interface, mobile notifications and optional biometric sign-in. It supplements the FieldOps Privacy & Data Processing Notice, which describes platform modules, privacy roles and our EU/EEA representative. FieldOps ADMIN is not the guard patrol-recording app.
Who is responsible for processing
The relevant customer organisation determines the purposes of processing operational data. Depending on the relationship, SenSec acts as its processor or subprocessor. SenSec acts as controller for processing whose purposes it determines, such as its own customer communications and certain security records. The FieldOps notice and contractual documentation describe the applicable allocation of roles.
SenSec LLC’s EU/EEA representative under Article 27 GDPR is Sentinel Executive Services s.r.o., company ID 23966751, Jičínská 226/17, Žižkov, 130 00 Praha 3, Czech Republic, registered at the Municipal Court in Prague, file C 436114. The representative is appointed under a written mandate. Matters within the mandate can be sent to this postal address or coordinated through privacy@sensec.ai. It is a separate company under common ownership, not a data protection officer or the product supplier; SenSec LLC remains the FieldOps provider.
Data we process
- Account and access: account identification and contact details, such as your name and work email, user identifier, organisation, role, assigned sites and information needed to authenticate access.
- Content in the modules you use: information you view or submit within your permissions, such as reports, comments, tasks, patrol records and associated attachments. Other modules may contain workforce, visitor, parcel or equipment information. The scope depends on your organisation’s services and your access. Records may contain other people’s personal data.
- Mobile device and preferences: app installation and notification delivery identifiers, app version, language, technical system and device information, phone registration and notification preferences.
- Operation and security: IP addresses, timestamps, session cookies and sign-in credentials, access records, notification delivery or opening status and technical errors.
- Support: information and content you send us when requesting assistance.
This Android app is not a tool for recording a guard’s patrol using GPS, NFC or motion sensors. Within your permissions, it can display operational information, including location data, created elsewhere in FieldOps. Processing within its web interface is part of using the app, not an exception to this policy.
AI in FieldOps workflows
FieldOps ADMIN displays FieldOps web functions, some of which may use AI when enabled for the organisation. Depending on the workflow, processing may include a question, conversation history, authorised operational records, documents, images or audio, including original content containing personal data. Scheduled or background workflows can also process records independently of whether the mobile app is open.
The protected OPS task workflows use specific minimisation and pseudonymisation controls. These controls do not make all AI processing anonymous and do not automatically cover every other workflow. External AI processing is distinct from mobile push delivery and Sentry error diagnostics. The permitted workflows, recipients, retention and international-transfer arrangements are governed by the organisation’s instructions and the applicable DPA. See the FieldOps Privacy Notice and AI Use and Human Oversight Notice for details. Contact privacy@sensec.ai for processing-scope questions.
Why we use data
We use data to authenticate users, check permissions, provide the relevant modules, process your actions, deliver selected notifications, save preferences, provide support and protect the service against misuse.
Where SenSec acts as controller, the legal basis depends on the purpose: performance of a contract where the user is a party, legitimate interests in operating and securing the service, legal obligations, or consent where required. The relevant controller determines the legal basis for customer operational data. Android notification permission does not itself replace the legal basis for all processing of operational data.
Personalised navigation
The dashboard’s Quick access feature uses account-linked records of visits to selected application sections to suggest useful shortcuts. These records include section identifiers, visit counts, active days and visit timestamps; they do not include the contents of the operational records you view. This is activity within FieldOps, not a history of websites you visit elsewhere.
Selecting your own shortcuts does not itself disable this activity recording. We use these records to provide and personalise navigation, not to target advertisements. They are within the scope of account and data deletion requests described on our account and data deletion page.
Mobile error diagnostics
FieldOps ADMIN for Android includes limited JavaScript error reporting to help us investigate faults and improve reliability. This reporting does not currently have a separate in-app opt-out.
The description below covers the bundled mobile diagnostics in Android version 0.3.9. It does not describe the diagnostic configuration of browser-only use or all earlier releases.
The mobile diagnostic payload is restricted to an error category, a redacted message, approved script identifiers and stack positions, the event time, the app version and a random identifier for that event. It does not include form contents, operational messages, account identifiers, raw page URLs, cookies, attachments, session recordings or performance traces.
Sentry processes these reports on our behalf. As with other internet requests, Sentry receives network information such as the connection IP address and browser User-Agent. The current mobile project is configured to prevent IP addresses and user-profile fields from being stored in diagnostic events. These safeguards minimise the data; they do not mean that the network connection is anonymous or that no personal data is processed.
Optional biometric sign-in
After signing in normally, you can enable biometric sign-in on a supported phone. Android performs the biometric verification. SenSec does not receive your fingerprint image or biometric template.
The phone stores a protected, time-limited sign-in credential, not your password for biometric sign-in. Using that credential requires successful system biometric verification. The server stores verification values and the technical association between the credential, account and device. You can disable biometrics; normal sign-in may then be required.
Notifications and content previews
We deliver Android notifications through Google Firebase Cloud Messaging. This uses an installation identifier, a delivery token and technical information needed to operate the service. Our delivery infrastructure and Google also process the content of each notification we send.
- Basic overview: may include an event type and site name.
- Private mode: omits the site name and operational text.
- Optional short text: if you explicitly enable it on a particular phone, a notification may include a shortened report title or comment excerpt, up to 120 characters.
- OPS Hub task titles: require an additional, separate setting and appropriate management access, and depend on the mobile notification features enabled for the service. They are not available to ordinary client accounts.
Previews are excerpts, not AI-generated summaries. Shortening text and removing formatting do not anonymise it: text and site names may contain personal or confidential information. Choose your preview settings in accordance with your organisation’s rules. A personal preference does not override the controller’s instructions or the applicable customer agreement. Full details open in the app after access is checked.
You can change the available notification filters by site, event type and, for supported reports, labels, and use quiet hours. You can also disable notifications in Android settings. Restricting lock-screen display reduces exposure but cannot guarantee confidentiality on every phone, watch or connected device. The app’s biometric lock does not retract a preview already received by the delivery service or operating system.
Providers and international processing
Our current service uses SiteGround for web and database infrastructure, Railway for the separate mobile service, and Google Cloud and Firebase for sending and delivering mobile notifications. Authorised support personnel may also have access where necessary. Additional recipients depend on the modules and customer integrations you use and are described in the FieldOps notice and applicable contractual documentation.
Sentry — mobile error diagnostics
Sentry processes the limited technical error reports described above to help SenSec identify and resolve application faults. Android version 0.3.9 and later uses SenSec LLC’s EU-region Sentry project. Regional storage does not mean that all support, service operations or subprocessor processing takes place exclusively in the EEA; the applicable data-processing terms and international-transfer safeguards also apply.
Android version 0.3.8 continues to use the earlier US diagnostic endpoint until the app is updated. The EU-region description must not be read as applying retrospectively to that version.
Mobile push and international processing
Mobile push is a separate data flow. Firebase Cloud Messaging uses global infrastructure and may involve processing outside the European Economic Area. Hosting the primary customer database in Europe therefore does not mean that all notification-related data remains exclusively within the EU. For transfers, we apply a protection mechanism appropriate to the provider and data flow, such as applicable standard contractual clauses. You can request details about recipients and applicable safeguards at privacy@sensec.ai. Further information is available in Google’s Firebase privacy documentation.
The primary FieldOps application and database are hosted in the Netherlands. This does not mean that all mobile service providers, support activities or copies remain in the EU. The FieldOps Privacy Notice describes the distinction between primary hosting and connected processing. Mobile notifications must be covered by the relevant processing instructions and provider documentation; this policy does not authorise a transfer prohibited by the customer’s executed agreement.
Security and retention
The app communicates with the service over HTTPS. Server-side permissions control access to operational data. Android’s secure storage protects mobile sign-in credentials on the phone; selected server-side credentials are stored as verification hashes or in encrypted form. No security measure eliminates every risk.
We retain account information and preferences for as long as needed to provide access, handle subsequent requests and meet any legitimate security or legal needs. Your organisation’s operational records are subject to their purposes, controller instructions, contractual retention periods and legal obligations. Deleting personal access does not automatically delete all organisational records.
- Completed notification delivery records: the mobile service’s regular cleanup removes records older than 90 days and associated events no longer required for delivery. This period does not apply to the underlying reports, comments or tasks.
- Trusted-phone sign-in authorisation: lasts no more than 30 days. Associated records enter regular cleanup after a further 60 days following expiry.
- Notification preferences and device registrations: are included when assessing and fulfilling an account deletion request, rather than being automatically erased by signing out.
- Backups: are rotated under the applicable backup cycle.
If particular data must be retained for legal or security reasons, we will explain the reason and applicable retention period or criterion. The relevant controller of operational data also determines the applicable conditions.
Diagnostic data retention
Mobile JavaScript error events are retained in Sentry’s production systems for up to 90 days from receipt. The retention period is assigned when an event is received. Applying a shorter period to new events does not automatically shorten the period already assigned to earlier events.
Backup copies follow a separate lifecycle: Sentry deletes diagnostic event-data backups within 90 days of their creation. This is measured from the creation of each backup, not from receipt of the original event, so backup copies may remain after the event has been removed from production systems. These periods concern diagnostic event data, not separate administrative account and audit records.
Your rights and account deletion
Depending on applicable law, you may request access, correction, erasure, restriction or portability of your personal data, object to processing, or withdraw consent where processing relies on it. You may also contact the competent supervisory authority.
Instructions and a direct contact are available on the FieldOps ADMIN account and data deletion page. You can submit a request without access to the app. Where your organisation or another controller is responsible for the data, we will help identify the appropriate recipient. We may reasonably verify your identity to protect your account.
Uninstalling the app, disabling biometrics or signing out does not itself delete your server-side account or operational records. This app is intended for workplace users and is not directed at children. We will provide appropriate notice of material changes and update the date of this policy.
Privacy: privacy@sensec.ai. Technical assistance: FieldOps ADMIN support.
This public information page
This app Privacy Policy, the app support page and the account deletion page do not load our optional website analytics or CRM tracking scripts, even if you previously accepted analytics elsewhere on this website. Hosting may still generate technical access and security logs. Your browser can retain essential site preference storage. See the Cookies Policy for the wider website; this does not exclude processing within the app’s embedded web interface from the policy above.
This statement concerns these public information pages. It does not mean that the app has no activity recording or diagnostics: see Quick access personalisation and mobile error diagnostics.