Mobile · Android & iOS

Mobile App Permissions Disclosure

This page discloses every device permission our mobile applications may request — what it does, why we need it, where the resulting data is stored, and with whom (if anyone) it is shared. Each permission is requested only when relevant to a feature you actively use, and you can review or revoke any of them at any time through your device settings.

Last updated: January 1, 2026Sigmantic Digital Technology · Khalid Aboubakr

At-a-glance summary

Permission	Required	Primary purpose
Camera	Optional · feature-specific	Used strictly for operational workflows that require visual capture — barcode scanning, QR code recognition, document capture, photographing assets, and attaching evidence to work records.
Files & Storage	Optional · feature-specific	Used so you can attach existing photos, PDFs, or documents from your device to a record, ticket, or workflow.
Internet Access	Required for app function	Required to communicate with our servers — authentication, syncing records, retrieving updates, and submitting work.
Notifications	Optional · feature-specific	Used to deliver operational alerts — work assignments, ticket updates, security notices, and other time-sensitive events.
Location (Optional)	Optional · feature-specific	Used only when an organization administrator enables a location-aware workflow — for example, geo-tagging a completed work order, locating an asset, or routing within a service area.

Permission 1

Camera

Optional · feature-specific

Android scope

android.permission.CAMERA

iOS scope

NSCameraUsageDescription

Purpose: Used strictly for operational workflows that require visual capture — barcode scanning, QR code recognition, document capture, photographing assets, and attaching evidence to work records. Camera access is invoked only during direct user interaction.
Storage behaviour: Live preview frames used for scanning are processed transiently in device memory and are not persisted. Only images you deliberately capture and upload are stored — in encrypted object storage, scoped to the workspace that received them.
Sharing behaviour: Camera data is never sold, rented, advertised against, or shared with unrelated third parties. Captured images shared via the service flow only to the destination workspace under the same access controls as other operational data.

Additional safeguards

No background recording — the camera is never activated unless you tap a scan or capture control.
No facial recognition, no biometric profiling, no identity inference.
No permanent raw-feed storage; only deliberately captured images are kept.
Permission can be revoked at any time in your device settings without losing access to the rest of the app.

Permission 2

Files & Storage

Optional · feature-specific

Android scope

android.permission.READ_MEDIA_IMAGES
android.permission.READ_MEDIA_VIDEO
android.permission.READ_EXTERNAL_STORAGE (legacy)

iOS scope

NSPhotoLibraryUsageDescription
Document Picker (UIDocumentPickerViewController)

Purpose: Used so you can attach existing photos, PDFs, or documents from your device to a record, ticket, or workflow. Newer Android versions use scoped media access; older versions fall back to limited external-storage scopes.
Storage behaviour: Selected files are uploaded over an encrypted channel and stored in encrypted object storage associated with your workspace. The app does not scan or index your device storage.
Sharing behaviour: Uploaded files are visible only to members of your workspace and to authorized personnel acting under documented procedures. They are not shared with advertisers or unrelated third parties.

Permission 3

Internet Access

Required for app function

Android scope

android.permission.INTERNET
android.permission.ACCESS_NETWORK_STATE

iOS scope

Foundation networking APIs

Purpose: Required to communicate with our servers — authentication, syncing records, retrieving updates, and submitting work. Network state is read to provide accurate offline / online indicators and resume failed uploads.
Storage behaviour: No content is stored as a result of this permission. Connection metadata (status codes, timing) is captured solely for diagnostics and is retained according to the Data Retention Policy.
Sharing behaviour: Network metadata is used internally for reliability and security monitoring. It is not sold or shared with third parties.

Permission 4

Notifications

Optional · feature-specific

Android scope

android.permission.POST_NOTIFICATIONS

iOS scope

UNUserNotificationCenter

Purpose: Used to deliver operational alerts — work assignments, ticket updates, security notices, and other time-sensitive events. Notification categories can be controlled individually inside the app.
Storage behaviour: Device push tokens are stored only to route notifications to your device and are removed when you sign out or revoke notification permission.
Sharing behaviour: Push tokens are transmitted only to Apple Push Notification service and Firebase Cloud Messaging as the operating-system-required delivery channel. They are not shared for marketing or advertising.

Permission 5

Location (Optional)

Optional · feature-specific

Android scope

android.permission.ACCESS_COARSE_LOCATION
android.permission.ACCESS_FINE_LOCATION
android.permission.ACCESS_BACKGROUND_LOCATION (only when enabled by organization)

iOS scope

NSLocationWhenInUseUsageDescription
NSLocationAlwaysAndWhenInUseUsageDescription (only when enabled by organization)

Purpose: Used only when an organization administrator enables a location-aware workflow — for example, geo-tagging a completed work order, locating an asset, or routing within a service area. The application is fully functional without this permission.
Storage behaviour: Coordinates are transmitted over an encrypted channel and stored only when associated with a deliberate user action (e.g. submitting a geo-tagged report). Continuous background tracking is not performed.
Sharing behaviour: Location data is shared only within the customer organization's workspace where required by the active workflow. It is never used for advertising, profiling, or sold to third parties.

Additional safeguards

Permission requests appear only when an organization administrator has enabled the relevant feature.
Background location is requested via a separate, explicit in-app consent step.
You may revoke location permission at any time from your device settings.

Camera disclosure — Google Play & App Store

Our mobile applications never activate the camera silently. The camera is used exclusively for barcode/QR scanning, document capture, and asset photography during direct user interaction. We do not perform facial recognition, biometric profiling, or any form of identity inference. Raw camera frames used for live scanning are not stored. Camera data is never sold, rented, advertised against, or shared with unrelated third parties.