MCE Field Services (“the App”) is an internal workforce application operated by MidCentral Energy (“MidCentral”, “we”, “us”). It is used by our employees and authorized contractors to record field work — forms, job and crew records, photos, and signatures. It is not a consumer application: accounts are provisioned by MidCentral and there is no public sign-up.
This policy describes what the App actually collects, why, where it goes, and what we currently can and cannot do about deletion. Where a process is not yet finalized, we say so plainly rather than describing something we do not do.
You sign in with your MidCentral-issued Microsoft Entra ID (Azure AD) account using OpenID Connect. We store your display name, work email address, and your Entra object identifier. When you sign in, a server-side session record is created holding that object identifier and a snapshot of your permissions; the session expires after 8 hours. We also read your directory profile (identifier, display name, mail, user principal name) and your group memberships from Microsoft Entra ID to determine what you are allowed to see and do. We never receive or store your password — authentication happens entirely with Microsoft.
Every request the App sends to our servers also carries a per-install device id — a random identifier generated on your device, not derived from any hardware serial number or advertising id. It is used for app functionality and diagnostics: attributing requests and errors to the installation that made them (including unauthenticated requests, which have no account to attribute to) and enforcing minimum supported app versions. It is not used for advertising or cross-app tracking.
Form submissions, job and work-order details, crew and time entries, inspection results, notes, asset and location references, approval decisions, uploaded documents and photos, and captured signatures. Submissions and documents are attributed to the Entra object identifier of the person who created them.
When a form contains a location field, tapping its capture button asks your device for your current position and stores the resulting latitude and longitude with that submission. On the mobile app this uses a balanced accuracy setting (roughly 100 meters), not the highest accuracy your device is capable of — it is precise enough to identify the site or asset you are recording without pulling the most exact fix your GPS can produce. This happens only in response to that explicit tap.
When you attach a file or photo to a record, or draw a signature, that file is uploaded to private Microsoft Azure Blob Storage. Uploads and downloads use short-lived, single-purpose access links (15 minutes for uploads and for signature downloads; 60 minutes for image and document downloads). The storage container is not publicly readable.
On the mobile app, attaching a photo can ask for permission to use your camera (to take a new photo of a site, asset, or defect) or your photo library (to attach an existing picture). The app only ever captures still images — it does not record audio or video, and does not ask for microphone permission. On the web version of the App, choosing a photo instead opens your device camera through the standard browser file picker, which is governed by your browser’s own permission prompt rather than the App. The App does not request access to your contacts.
The mobile app stores your sign-in session in your device’s secure, encrypted storage (the iOS Keychain or Android Keystore) so you do not have to sign in with your work account every time you open the App.
If you enable browser notifications, we store the push subscription your browser issues — its endpoint address, its encryption keys, and your browser’s user-agent string — so we can deliver approval and assignment alerts. We also send email notifications; recipients are resolved from Microsoft Entra ID, and those messages can contain form and submission details.
The App works offline. Unsent submissions, cached records, and pending photo and signature files are stored locally on your device (in the browser’s origin-private file system or IndexedDB) until they sync. Signing out or clearing site data removes this local copy.
If you use the App’s in-app feedback tool, we store your message, category, and an optional screenshot, along with non-personal technical context (app version, build, platform, route, and similar diagnostic detail) and an internal feedback record ID. We forward that feedback — message, category, screenshot link, and technical context — to an internal GitHub issue for triage, but we do not forward your name, email address, or Entra object identifier to GitHub; only the internal feedback record ID travels with it, so triage can be correlated back to your submission without exposing your identity in GitHub.
The App can report crashes and performance traces to Sentry to help us fix defects. These reports include technical context such as app version, build, environment, and device/runtime information, along with your Entra object identifier — an opaque, tenant-scoped ID number, not your name or a readable account name — your role labels within the App (for example, which portal role you were using), and your per-install device id (the same non-advertising identifier described in “Identity and account information” above), so we can tell how many people a defect affects and reproduce role- and device-specific bugs. We do not send your name, email address, username, or IP address to Sentry, and Sentry’s automatic personal-data collection is turned off. Diagnostics are disabled entirely unless a reporting endpoint is configured for the build.
Session replay, on error only, production only. In the production build only, when the App detects an error it uploads a short (roughly the preceding 60 seconds) screen recording of what led up to it, to help us see what you were doing when it failed. We do not record ordinary sessions — only the session that experienced the error. Before upload, the recording masks all text, images, and embedded web content by default (form fields, free-text notes, photos, and signatures all render as blocked-out placeholders), so field content you entered is not visible in the recording. Taps, navigation, and the sequence of screens are visible. Network request bodies and headers are never captured.
We do not use your information for advertising or marketing, and we do not profile you for any purpose unrelated to your work.
We do not sell your personal information, and we do not share it with advertisers or data brokers. The App contains no advertising, analytics, or cross-app tracking software, and does not ask for permission to track you across other companies’ apps or websites.
Your information is shared only with the following, and only for the purposes shown:
| Recipient | What is shared | Why |
|---|---|---|
| Microsoft Azure (cloud hosting) | All application data and files | Hosting, database, and file storage |
| Microsoft Entra ID (identity) | Sign-in, directory profile, group membership | Authentication and authorization |
| UKG (workforce management) | Your UKG account identifier, work dates, hours worked, and per-diem amounts when applicable | Time and attendance / payroll processing |
| NetSuite (accounting / ERP) | Your work email address (used as the cross-system employee key), employee identifiers, hours, per-diem and cost amounts, and the job or task the work is charged to | Job costing, project accounting, and payroll-related entries |
| Sentry (error monitoring) | Crash and performance diagnostics, including your Entra object identifier, role labels, and your per-install device id, but never your name, email, or IP address; and, in production only, a masked screen-recording of the ~60 seconds preceding an error | Defect detection |
| Google (Maps SDK, Android only) | On the Android app only, the map screens (the locations map and a location’s detail map) render using Google’s Maps SDK for Android, which runs through Google Play Services on your device. iOS uses Apple Maps instead. Our own code does not send Google any of your work data or location readings beyond what the SDK needs to draw the map | Displaying location maps in the Android app |
| Expo / EAS (mobile build and update service) | Application builds and over-the-air update delivery | Distributing the mobile app |
| GitHub (issue tracking) | In-app feedback text and an optional screenshot, plus non-personal build/version and correlation details; not your name, email, or object identifier | Triaging bugs and feature feedback you submit through the App |
| Authorized MidCentral personnel | Work records within their role’s scope | Supervision, approval, payroll, and administration |
Because hours, per-diem amounts, and employee identifiers flow into payroll and accounting systems, we treat that information as sensitive employment data and restrict access to personnel with a business need. We may also disclose information where required by law, or to protect the rights and safety of MidCentral, its personnel, or others.
Business records — form submissions, approvals, crew and time records, attachments, and audit history — are retained as company records for as long as they are needed for operational, legal, and compliance purposes, in line with MidCentral's records-retention practices. Records are not deleted automatically; removal is an administrator action.
Location is collected only as described in section 1: a single reading, at a balanced accuracy of roughly 100 meters, taken when you tap a form’s location capture button, stored with that submission so the work can be tied to the correct site. It is used for operational and record-keeping purposes only. It is not used to monitor your movements, is not collected in the background, and is not shared outside the recipients listed in section 3.
All traffic between the App and our servers is encrypted with TLS; unencrypted connections are rejected at the ingress. Data is stored in Microsoft Azure with access enforced by role- and capability-based permissions. File storage is private and reachable only through short-lived, scoped access links. Sessions expire after 8 hours and can be revoked by an administrator. No system is perfectly secure, but we apply industry-standard controls and review them as the App evolves.
If you have a question about your personal information or about this policy, contact us using the details in section 10.
Accounts are employer-managed Microsoft Entra ID (Azure AD) work accounts, provisioned and de-provisioned entirely by MidCentral IT. There is no in-app sign-up and no in-app account deletion — the App does not provide a self-service way to create, close, or delete your account or your data from within the App. Onboarding and offboarding are both handled by the employer, outside the App: an administrator provisions your Entra account when you join, and deactivates it and revokes active sessions when you leave. Work records created before that remain retained as company business records (see section 4).
Because the App creates no accounts and holds no data of its own outside your work account, there is no separate in-app data-request process. Access ends, and your account is removed, through MidCentral IT offboarding under company hiring and IT policy. Records you created while employed are retained as company business records (see section 4). Questions about this policy or about information connected to your work account go to MidCentral's IT department at AISupport@midcentralenergy.com.
The App is a workplace tool for adults. It is not directed to children, and we do not knowingly collect information from anyone under 18.
We may update this policy as the App changes or as the law requires. The current version is always available at the public address where you are reading it, and from the sign-in screen and account menu inside the App. We will update the effective date above when we make a change, and will notify personnel of material changes through normal company channels.
Questions, concerns, or requests regarding this policy:
MidCentral Energy Partners LLC — IT & Compliance
AISupport@midcentralenergy.com
914 N. Broadway Avenue, Suite 230
Oklahoma City, OK 73102
(405) 664-4242