Modworks Privacy Policy

Information used to provide Modworks

Account and work information includes your name, email address, account and employee identifiers, contact details supplied by your organization, company, project memberships, roles and permissions. We use it for sign-in, account recovery, access control and attribution of work.

Work records include module and task information, inspections, incidents, notes, submitted field values, photos, documents and other evidence you or your organization provide. Uploaded files may contain embedded metadata. These records support project coordination and work history.

Device and operational information includes notification tokens, app installation identifiers, permission and tracking readiness, timestamps, diagnostic phase and error codes, and connection information used to deliver and troubleshoot the service. Servers and service providers may process network information, such as IP addresses, as part of requests.

If you send a website enquiry, we receive the name, email address, company and message you enter. We use these details to handle the enquiry and send it to the support or project-enquiry recipient.

Phone location and background sharing

With your permission, Modworks collects precise phone location for accepted transport trips and a separately enabled Driver GPS Test, including when the app is closed or not in use. Location records can include coordinates, measurement time, accuracy, speed, direction and the associated account, installation, project or trip. Authorized project and transport teams use them to view trip progress, arrival estimates and comparisons with module tracker reports.

For transport trips, you review location setup before accepting tracking. A future pickup can register pickup and delivery areas with Android; it does not record a route before pickup. Trip collection ends at delivery, expiry, sign-out or when tracking is stopped or paused.

A Driver GPS Test requires your separate consent. In the Android app, review its disclosure and choose Start sharing. An administrator enabling a test, or a location permission grant alone, does not start sharing. A consented test can continue with the screen locked and resume while that same test is active. Stop the test from the app or, on Android, its sharing notification. It also ends at its displayed expiry, sign-out or loss of access.

You can change location permission or turn off device location in system settings. Other permitted work remains available, but location-dependent features may be unavailable. Revoking permission or stopping sharing does not delete records already received by the service.

Module tracker reports come from separately attached hardware and its tracking provider. They are distinguished from phone location; stopping phone sharing does not disable a module's hardware tracker.

Camera, files, notifications and device security

Camera and file access support module-code scanning and the photos or documents you choose to attach. Notifications provide work updates and tracking status. You control these permissions in device settings.

Optional biometric quick unlock uses the device's authentication system. Modworks does not receive your fingerprint or face template. The Android app protects stored credentials with Android Keystore, separates saved data by service connection and excludes its app data from Android backup and device transfer. Cached files and offline work may remain on the device until app cleanup, device storage management or uninstall.

The app and service use HTTPS for production connections and restrict project access according to assigned permissions. These measures reduce risk but cannot guarantee absolute security.

Who receives information

Your authorized organization, project and transport teams can access information needed for their roles. Shared work and audit records can remain visible to authorized teams after an individual loses access.

Service providers support hosting, storage, authentication, email, maps and notifications. Current integrations include Amazon Web Services for the service, database, authentication and email; Vercel for web hosting; and Google Firebase Cloud Messaging for notification delivery and installation tokens.

Google Maps supplies map content. Google Routes receives the origin and destination coordinates used for driving estimates. Device and connection information is also processed when these services are used. Module tracking providers supply reports from the project's hardware trackers. Providers have their own data-handling terms and policies.

The Android app uses Google ML Kit to recognize module barcodes on the device. The barcode image is processed locally; the SDK also sends app and device metadata, installation identifiers, usage and diagnostic information to Google to operate and improve its services.

Notification delivery uses device tokens and work identifiers with generic alert text; the app retrieves detailed work information through the authenticated service. The field app's data features described here support account access, project work, notifications, maps and troubleshooting.

How long information remains

Accounts, shared project work, evidence, document revisions and audit history are retained for operational, customer and legal needs. These records do not currently have a single automatic deletion period. Suspending an account or unlinking an employee stops access; it does not erase shared history. Some records are protected from ordinary deletion to preserve evidence and attribution.

Routine trip cleanup removes phone positions received more than 90 days ago and ended or revoked trip sessions created more than 90 days ago, including associated session diagnostics. Recorded module tracker history also has a 90-day cleanup threshold. Cleanup runs during service operations, so these thresholds are not a promise of deletion at an exact time.

Standalone Driver GPS Tests whose expiry is more than seven days old, and their points, are removed when a new test is enabled. They may remain longer if that cleanup operation does not run. Website enquiry database records have a 30-day expiry and are removed by the enquiry worker; this does not remove copies delivered to an email inbox.

The current service database is configured for 14 days of automated backups. Application and migration logs are configured for 30 days, and authentication email-feedback and recipient-guard logs for 14 days. Separately retained snapshots, document versions and recipient email copies can outlast those periods. A deletion from the active service does not necessarily immediately remove every backup or copy.

Access, correction and deletion requests

Contact admin@modworks.pro for app support, privacy questions, or a request to access, correct or delete your account or personal information. Include the account email and relevant organization or project so the request can be located; do not send your password or unnecessary sensitive documents.

Requests may require identity verification and coordination with the organization that manages the project. Some shared work, evidence, audit records or other information may need to remain for operational, customer or legal requirements. There is no automatic in-app account deletion feature, and this policy does not promise immediate removal of all records or copies.

You can sign out, stop location sharing, manage device permissions and ask your organization to change or revoke project access. These actions affect access or future collection and are separate from a request to delete stored information.

Request account or data deletion

Policy updates and contact

We may update this policy as Modworks changes. The revision date identifies the version you are reading. The Android app includes a copy that is available without signing in or opening a website. For the current policy or questions about this version, contact admin@modworks.pro.