PRIVACY & SUPPORT
Modworks Privacy Policy
Updated November 18, 2026
This policy explains how Modworks handles information in its field apps, project workspaces and public website. Modworks is intended for construction professionals aged 18 and over. Your organization manages your account access and the projects, companies and work you can see.
Contact: admin@modworks.pro
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 in the background or with the screen locked, subject to operating-system permissions and execution limits. 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 supported Android and iOS trips, you review location setup and choose Start. This begins phone route collection immediately, which can be before physical pickup. Opening a queue, signing in or granting location permission alone does not start it. Start does not confirm hardware pickup or departure. Phone arrival alone does not end an explicit Start trip: collection continues until the currently selected module's hardware arrival is confirmed, or until expiry, sign-out, loss of permission or access, or an explicit Stop. Older services may register pickup and delivery areas and begin route collection on pickup-area entry.
A Driver GPS Test requires your separate consent. In the Android and iOS apps, 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 iOS app stores credentials in the device-only Keychain and separates protected local drafts, evidence and diagnostic recordings by account and service connection. Protected local files are excluded from device backups. Optional Face ID or Touch ID unlock is handled by iOS. Cached files and unsent work may remain until their feature cleanup, your deletion or uninstall; signing out is not a request to delete shared project records.
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.
Troubleshooting recordings and lifecycle walkthroughs
Detailed Android troubleshooting recording is off by default. Choose Start recording to collect timings, request outcomes, app and photo-processing phases, tracking-queue status and limited device context such as app version, network type, battery and memory. An active recording continues through camera use and app switching and can resume after the app process restarts, for up to 24 hours from its start. Stop recording, sign-out or authentication expiry stops it. Saved detailed recordings remain on the device after sign-out until you delete them or app cleanup removes them.
A separate small Android basic health history is enabled by default. It automatically keeps local failure and established tracking-warning summaries even when detailed recording is off. In Troubleshooting, turn off Keep basic health history to prevent new summaries, or choose Clear basic health history to delete the current history. Turning it off does not itself delete existing history. Sign-out or an account change clears this health history. It is not uploaded automatically; an Android report you choose to save or share includes the retained recent health history.
In iOS 1.4, detailed Diagnostics recording is also off by default and requires explicit consent. It records restricted request timings and outcomes and recording state. It can continue while using the camera or switching apps, subject to iOS execution limits, but an app restart requires fresh recording consent. Stop, sign-out, an account or service change, or the 24-hour limit ends active recording. Saved detailed recordings remain protected on the device for the same account and service connection until deletion or cleanup. Basic app health is on by default and stores only a small local buffer of request-failure summaries. On iOS, turning it off or choosing Clear basic health deletes that buffer and cached reports that may contain it; sign-out and account or service changes also clear them. No basic health history is uploaded automatically.
Creating or joining a lifecycle walkthrough requires sign-in and current access to its selected project and module. It enables automatic collection, correlation and storage by the service of new operational timings for eligible requests about that module and relevant background operations, such as tracking-provider polling. These records include timings and outcomes, database and lock timings, and bounded service resource measurements. The run-management requests themselves are excluded from this walkthrough tracing. Stopping or leaving a device recording ends that device's request correlation; the shared run and relevant server background tracing can continue for other participants until an authorized project manager ends it or its 24-hour active window expires.
During active Android detailed recording, API or socket requests carry random diagnostic request and action identifiers. Joining a walkthrough adds its run and capture identifiers. Related identifiers link events across devices and the service. Local resource identifiers are salted for each recording, and server reports use aliases scoped to the run. The service retains the authenticated account association and authorized review includes project, module, stage, task and role context. These records are pseudonymous, not guaranteed anonymous; a run ID is a reference and does not grant access.
On iOS, joining a walkthrough reports the app version, starts a new consented local recording and adds random request, run and capture identifiers only to eligible requests to the configured authenticated service. Diagnostic management requests are excluded. Local event fields exclude account and module identifiers rather than retaining salted copies. Joining never grants project or module access. Leaving the walkthrough stops new request correlation on that device; local recording continues until it is stopped.
Dedicated diagnostic event payloads use restricted event names and scalar fields. They exclude credentials, cookies, raw URLs, request or response bodies, exception messages or stacks, image bytes and precise coordinates. Protected walkthrough reports also contain the selected project/module labels, configured stage and task labels, and the troubleshooting label supplied by the run creator. Use a label without personal or sensitive information. Normal work records and permitted location transfers remain governed by their separate features.
Android and iOS local recordings are sent only when you choose Add stopped recording to walkthrough, or explicitly prepare and save or share a report and select a destination or recipient. Joining does not upload old saved recordings or health history. Add stopped recording sends a restricted version of the selected recording to the protected server report and excludes the basic health history. Browser walkthrough recording requires an explicit create/join choice; its local events remain in browser memory until you choose Add browser recording to report. Reloading or changing the signed-in account clears that local browser recording. Automatic backend tracing while a run is active is separate from these manual local-recording uploads.
Project managers with current project management access can review, export, end and delete a combined walkthrough report. Field participants need current access to the module and can add only captures registered to their own authenticated account; their participation does not grant combined-report review. Your organization or other recipients may receive a copy through authorized review or your explicit sharing. Deleting a device recording or clearing health history does not delete a server report, a downloaded report or a copy already saved or shared outside the app.
These troubleshooting controls do not disable normal authenticated work requests, installation-linked trip diagnostics, separately consented phone-location sharing, maps, notifications or SDK transfers described elsewhere in this policy. Further automatic upload of local recordings would require a fresh review of the data flow, disclosure, consent and retention controls.
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, together with Apple Push Notification service for iOS delivery. Firebase SDKs also process app, device and operating-system metadata and operational SDK telemetry to deliver notifications and monitor or improve their services. These provider transfers are separate from the optional Modworks diagnostic recordings.
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. The iOS app uses Apple VisionKit to recognize module codes on the device; it does not use the Android ML Kit scanner.
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.
Android detailed troubleshooting recordings expire seven days after their start. At most eight sessions, at most 32 MiB per session, and a combined 64 MiB allowance for detailed history, health history and app-cached exports limit local storage. The basic health history retains at most 512 KiB of summaries for up to seven days, with another 512 KiB reserved for file rewriting. Older events or sessions can be removed sooner when a limit is reached. App-cached ZIP reports have a lease of at most 24 hours, shortened by the source recording's expiry. Deleting a local session also removes its app-cached exports. Cleanup occurs while the app runs; it is not a promise of deletion while the device or app is inactive.
In iOS 1.4, detailed recordings are limited to eight sessions per account and service connection, 100,000 events and 32 MiB per session, and seven days from their start. Detailed recordings and app-cached ZIP exports share a 64 MiB allowance. The separate basic health buffer is limited to 1,500 events, 512 KiB and seven days. Limits can remove older events or recordings sooner. Deleting or expiring a local recording removes its cached exports; clearing or disabling basic health also clears cached exports that may include it. The iOS app does not use the Android 24-hour ZIP lease. Cleanup occurs while the app runs, not necessarily while the app or device is inactive. Copies you save or share outside the app remain with their recipients or destinations.
Browser walkthrough recordings are limited to 1,500 events and 512 KiB of event data in memory, plus small bookkeeping and dropped-event summaries, and are cleared on reload or account change. A server walkthrough is active for at most 24 hours and its controlled records have a retention window of seven days from run creation, limited to 80,000 events and 64 MiB per run across all participants and service timings. Each stopped Android or iOS recording can add at most 19,999 normalized events plus one completeness summary, within a separate 16 MiB upload budget with 4 KiB reserved for the summary; additional local events remain available in the original report. Stop and Add before changing accounts, and use separate recordings for later handoffs. These per-recording limits do not increase with the shared run capacity. Routine automatic timings use bounded five-minute counters and representative detail; essential outcomes have reserved capacity. A run may be active but full: new server work is then unobserved. Add keeps unacknowledged browser rows and stopped Android and iOS originals for retry or export, and reports a failed or partial import rather than claiming success. Expired server runs are excluded from ordinary access and scheduled or subsequent service cleanup removes their stored records. An authorized project manager can delete the controlled server run/report earlier. Operational application logs have their separate retention described below. Downloaded, saved or shared report copies are controlled by their recipients and destinations and are not removed by these app or server controls.
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.
Policy updates and contact
We may update this policy as Modworks changes. The revision date identifies the version you are reading. The Android and iOS apps include 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.