Privacy Policy

Effective date: 2026-10-01
Last updated: 2026-11-01

WorkProof is an offline-first mobile application for recording work, time, pay, expenses, customers, employers, evidence, and related documents.

This Privacy Policy explains how personal information is processed when someone uses the WorkProof mobile application or the informational website at workproof-tracker.web.app. "WorkProof," "we," "us," and "our" mean WorkProof, of High Street North, E12 6QN, London.

1 Scope

This Policy applies to:

• The WorkProof mobile application
• The informational website at workproof-tracker.web.app
• Communications a person chooses to send to us, including through email or WhatsApp
• Limited online services used by the app for Firebase Crashlytics and Analytics in the reviewed Android configuration, Android barcode-scanner diagnostics, advertising consent and delivery, updates, and store reviews

It does not govern third-party apps or services selected when exporting, saving, or sharing information. Those services apply their own privacy policies.

This website is an informational site without accounts, contact-form storage, advertising pixels, or non-essential cookies. Its hosting provider may still process ordinary request logs such as IP address, browser or device type, requested page, referring page, and date and time for security and delivery. If the website implementation changes, this Policy and any required consent controls will be updated before the new processing begins.

2 Offline-First Design

WorkProof does not require a WorkProof account or sign-in. The current version has no active WorkProof-operated cloud synchronisation or application backend. The local database contains fields designed for possible future synchronisation, but the current app does not send the work database to a WorkProof server.

Offline-first does not mean that the app never communicates over the internet. The app uses or may use Google Firebase, Google ML Kit on Android, Google Mobile Ads, consent services, app-store services, WhatsApp, website hosting, and apps selected by the user, as explained below.

3 Data Controller and User Responsibilities

For personal information transmitted for diagnostics, analytics, advertising, website delivery, or support, the data controller or equivalent business is:

Controller: WorkProof
Address: High Street North, E12 6QN, London
Privacy email: swe.jamirulinfo@gmail.com

WorkProof normally cannot access records held only in the app's local storage.

When a user records information about customers, workers, employers, suppliers, or signers, that user decides why the information is recorded and shared. The user may therefore be a separate controller or business under applicable privacy law and is responsible for having an appropriate lawful basis, providing any required notices, limiting what is recorded, and responding to the rights of those individuals.

Google and other third parties may act as processors, service providers, or independent controllers depending on the service, configuration, and purpose. Their own notices and terms describe their roles.

4 Information Processed Locally

Depending on how the app is used, WorkProof may process the following information on the device:

• Profile and preferences: language, country, currency, profession, work mode, pay method, default rate, theme, onboarding status, and demo-data choice.
• Customer and business contacts: names, phone numbers, email addresses, physical addresses, billing currency, official references, pay schedules, contract information, service details, and notes.
• Work records: job and shift titles, descriptions, locations, dates, schedules, time zones, priorities, status, rates, reminders, clock-in and clock-out times, breaks, calculations, corrections, and notes.
• Financial records: quotes, invoices, line items, tax or VAT inputs, expenses, payments, payment methods and references, receipts, pay periods, payslips, gross and net pay, deductions, adjustments, overtime, premiums, and calculated differences.
• Evidence and documents: selected photos, files, payslips, file names, types, sizes, paths, descriptions, signatures, timestamps, hashes, and resized, re-encoded image copies with metadata removed.
• Marketing content: name, headline, offer, services, phone number, email address, website, address, logo, cover image, and design choice.
• Notification information: reminder settings, notification text, scheduled times, time zone, permission status, quiet hours, delivery state, and custom motivation messages.
• Security and backup information: a salted app-lock PIN verifier, biometric setting, encryption keys held through operating-system secure storage, backup history, file names, sizes, checksums, and restore state.
• Operational records: local identifiers, drafts, audit events, deletion markers, pending-operation records, export paths, checksums, and calculation snapshots.

Some of this information may be sensitive, especially pay records, signatures, identity-related documents, and free-text notes. Users should record only information they are entitled to process.

5 Camera, Scanner Diagnostics, Files, Clipboard, and Biometrics

The camera is used to scan QR codes and barcodes. Camera frames and decoded values are processed on the device and are not intentionally uploaded by WorkProof. A detected value remains on the current screen and may be copied to the clipboard if the user chooses. Clipboard contents may be accessible to the operating system or other apps under their applicable rules.

On Android, the scanner includes the bundled Google ML Kit barcode-scanning library. Google states that barcode input and decoded values remain on the device, but ML Kit may send Google device and app information, per-installation identifiers, performance metrics, API configuration, feature version, feature input and output sizes, and event or error data for diagnostics and usage analytics. Google states that this data is encrypted in transit and is not shared with third parties. The iOS scanner uses Apple's on-device Vision technology rather than the Android ML Kit library. See Google's ML Kit Android data disclosure.

WorkProof uses operating-system file pickers so the user can choose evidence, payslips, logos, cover photos, or backup files. It does not request access to every file on the device. If a selected file comes from a cloud provider exposed through the picker, that provider handles the request under its own terms.

When biometric App Lock is enabled, WorkProof asks the operating system to authenticate the user. WorkProof receives a success or failure result and does not receive or store the user's fingerprint, face template, or other raw biometric data.

6 Crash and Diagnostic Information

In the reviewed Android configuration, WorkProof initialises Firebase Crashlytics when the app starts and explicitly reports unhandled Flutter framework and Dart errors as fatal. The native Crashlytics SDK may also collect native crash reports. Crashlytics may process:

• Crash traces and exception messages
• Crashlytics installation identifiers and Firebase installation identifiers
• Firebase session identifiers and relevant application state
• App identifier, version, and crash timestamp
• Device model, operating system, CPU architecture, memory, and storage information
• Whether the app was in the background
• Root or jailbreak indicators
• Automatic Analytics breadcrumb logs or user-action context where the enabled Analytics integration supplies them
• Other technical information needed to diagnose a failure

WorkProof does not intentionally attach work records to crash reports. An exception message, breadcrumb, application state, or technical context could nevertheless contain incidental information such as a file name, path, action, or operation that was underway. No custom Analytics event calls were found in the reviewed source.

The iOS Firebase configuration and dependency lockfile are incomplete or stale, so iOS Crashlytics behaviour must be verified from a successful production archive before iOS availability is claimed.

Google describes Crashlytics processing and retention in its Firebase Privacy and Security documentation.

7 Firebase Analytics

The reviewed Android source includes and configures Firebase Analytics, initialises Firebase at startup, and contains no explicit runtime or native setting that disables automatic Analytics collection. The current Android configuration must therefore be treated as Analytics-enabled. No explicit custom Analytics event calls were found. The iOS production Firebase configuration is incomplete, so no iOS availability or Analytics-status claim is made until a production archive and network behaviour are verified.

In the current Android configuration, Analytics may process an app-instance identifier, app opens and sessions, automatically collected events, app version, device information, approximate location derived from network information, and advertising identifiers where available under platform settings.

The app does not intentionally include customer names, pay records, evidence, or free-text work notes in custom Analytics events.

Google describes automatically collected events and data collection configuration.

8 Advertising and Consent Information

After onboarding, WorkProof uses Google's User Messaging Platform to determine whether a privacy message or consent choice is required. The Google Mobile Ads SDK is initialised only after Google's consent service reports that ad requests may be made.

Depending on region, choices, device, and configuration, Google and participating advertising partners may process:

• IP address and approximate location
• Consent status and privacy choices
• Advertising, app-set, app-instance, signed-in account, or other device identifiers where available
• App launches and interactions
• Ad requests, impressions, ads viewed, and ad interactions
• Device, app, and operating-system information
• Performance and diagnostic information
• Information used for advertising, measurement, security, and fraud prevention

WorkProof does not intentionally send the contents of the work database, evidence files, contact directory, or pay records to the advertising SDK.

Google describes the Mobile Ads SDK's Android data disclosure, iOS data disclosure, and UMP privacy flow for Flutter.

9 Updates, Reviews, Feedback, and Sharing

WorkProof may check Google Play or Apple's App Store for updates and may request a store review after eligibility conditions are calculated locally. Store services may receive ordinary request information such as IP address, app identifier, installed version, store country, and device or store information. Any rating or review is submitted directly to the store.

When a user selects Send Feedback on WhatsApp, WorkProof opens an external WhatsApp link with an editable draft. WhatsApp may receive the destination number, draft content included in the link, network information, and anything the user chooses to add or send. WhatsApp applies its Privacy Policy.

When a user shares a backup, report, document, evidence pack, marketing file, or generated code, WorkProof gives the selected item to the operating system's share interface. Depending on the workflow, the payload may also contain plain subject or message text, for example a job title or reference, a marketing display name, headline, offer, phone number, email, website or address, or a generated code's raw source text. The recipient app or service then processes the supplied item and text under its own policy. WorkProof cannot control or retrieve copies held by recipients.

10 Purposes and Legal Bases

Where the GDPR, UK GDPR, or similar law requires a legal basis, the anticipated bases are set out below.

Where processing relies on consent, it may be withdrawn prospectively. Withdrawal does not affect processing that was lawful before withdrawal.

11 Disclosure to Other Organisations

Information may be disclosed to:

• Google LLC and its affiliates through Firebase Crashlytics and Firebase Analytics in the reviewed Android configuration, bundled Google ML Kit barcode scanning on Android, Google Mobile Ads, UMP, Google Play updates, and Google Play review services. Google states that ML Kit scanner telemetry is not shared by ML Kit with third parties. See Google's Privacy Policy, Firebase privacy information, and ML Kit Android data disclosure.
• Advertising partners where enabled and permitted by consent and other applicable choices. The current vendor list and purposes should be available through the UMP consent interface.
• Apple Inc. for App Store lookup, update, review, and operating-system services. See Apple's Privacy Policy.
• WhatsApp and Meta when a user opens or sends feedback using WhatsApp.
• The user's selected email service and our email provider Google (Gmail) when a user addresses or sends support, legal, or privacy email, including any message and attachment supplied by the user.
• The website hosting provider Google Firebase Hosting for delivery and security logs.
• Apps, people, and storage providers selected by the user when information is exported, saved, printed, or shared.
• Professional advisers, authorities, or courts when disclosure of information actually held by us is reasonably necessary to comply with law, protect rights or safety, or establish or defend legal claims.
• A successor or transaction counterparty if the WorkProof business is reorganised, sold, or transferred, subject to applicable law and appropriate safeguards.

Additional production vendors: {{ADDITIONAL_VENDORS}}

We do not operate a data marketplace for the local contents of a user's WorkProof database. Disclosure of identifiers and interaction information for personalised or targeted advertising may nevertheless be treated as a sale, sharing, or targeted-advertising disclosure under some United States state laws even when no money is exchanged.

No

12 Advertising Choices

When UMP determines that a consent form is required, it presents relevant choices before WorkProof requests ads. When UMP requires an ongoing privacy-options entry point, WorkProof displays Privacy Choices in Settings.

Changing or refusing advertising consent does not necessarily make the app ad-free. Refusal may still permit non-personalised, limited, or technical ad delivery where lawful. Personalised advertising is used only when the necessary consent or another valid permission exists. Non-personalised advertising can still use local storage or identifiers for functions such as frequency control, fraud prevention, and aggregated reporting.

Users may also use device settings to limit or reset advertising identifiers and, where available, restrict app tracking. Availability and effect vary by platform and region.

No

Advertising choices do not automatically control Crashlytics, Analytics, ML Kit scanner telemetry, store services, or information a user chooses to share.

13 Device Permissions

WorkProof may request or use:

• Camera: to scan QR codes and barcodes on the device. On Android, ML Kit may separately transmit the limited scanner telemetry described in Section 5, but not camera input or decoded values according to Google.
• Notifications: to show locally scheduled work, shift, break, finish, and motivation reminders. Text may appear on the lock screen depending on app and operating-system settings.
• Boot completed on Android: to restore or reconcile scheduled local notifications after a restart or app update.
• Biometrics: to ask the operating system to authenticate the user for App Lock.
• Files or photos selected by the user: to import evidence, payslips, logos, cover images, or backups and to save or share generated files.

Permissions can be denied or revoked through device settings. The related feature may then be unavailable or limited.

The current app does not request precise location, microphone, contacts-address-book, or SMS permissions.

14 Local Storage, Encryption, and Backups

The main SQLite database and app preferences remain on the device while the app's storage remains available. WorkProof does not currently apply app-level encryption to the complete SQLite database.

Protected evidence files handled through the Pay Review evidence feature use authenticated AES-256-GCM encryption. WorkProof attempts to migrate older evidence to protected storage, but every legacy or separately generated artifact cannot be described as encrypted without verifying the final release and data state.

Generated reports, PDFs, CSV files, ordinary ZIP evidence packs, work documents, invoices, receipts, marketing images, QR or barcode images, and other exports are not automatically encrypted by WorkProof. Some signature or derived files may also exist without independent app-level encryption. Device-level encryption depends on the operating system, device, and passcode configuration.

Android cloud backup is disabled by the current manifest. On Android 12 or later, some device manufacturers may still permit device-to-device transfer despite that setting because explicit data-extraction rules have not been verified. Apple device-backup behaviour depends on operating-system and user settings. No

Password-protected .workproof backups use AES-256-GCM authenticated encryption. The key is derived from the password entered by the user. WorkProof does not know or recover that password.

A manual backup contains the local database, evidence files, the evidence-encryption key, and source-device documents-directory path metadata inside the encrypted backup. Anyone who obtains the backup and its password may be able to restore its contents.

WorkProof also attempts to create an encrypted on-device recovery snapshot when one has not been created within the previous 24 hours. It keeps up to three recovery snapshots and removes older snapshots during successful rotation.

15 Retention and Deletion

Many delete actions in WorkProof are soft deletions. The active interface hides the record, but a database row may remain with a deletion timestamp. Audit logs, deletion markers, pending-operation records, and related metadata may also remain. The current version does not automatically purge all such records after a fixed period.

Deleting an active record does not remove copies already included in recovery snapshots, manual backups, reports, evidence packs, externally saved files, or third-party records.

The current version does not provide one in-app Erase All Data action. To remove the active local workspace, a user may need to clear the app's storage through Android settings or delete the app on iOS. Offloading an iOS app may preserve its data. Operating-system actions may not remove secure-storage entries, device or cloud backups, externally saved files, or information previously transmitted to service providers.

16 Security

Security measures implemented in the current app include:

• AES-256-GCM authenticated encryption for protected Pay Review attachment files and encrypted backup files
• Password-based key derivation for manual backups
• Operating-system secure storage for evidence keys, recovery secrets, and App Lock information
• A salted, iterated verifier instead of storing the App Lock PIN as plain text
• Operating-system biometric authentication
• SHA-256 checksums and manifest verification for evidence, reports, and backups
• App sandbox storage and an Android manifest setting that disables cloud backup; device-to-device transfer may still occur on some Android 12-or-later devices, and iOS device or cloud-backup behaviour remains subject to the confirmed production configuration and user settings
• Integrity checks and recovery snapshots during backup restoration

App Lock controls access through the WorkProof interface. It does not encrypt the complete SQLite database or every generated file.

No storage or transmission method is completely secure. Users should use a strong device passcode, keep the operating system updated, choose a unique backup password, protect exported files, and verify recipients before sharing. A user should never send us an App Lock PIN or backup password.

17 International Transfers

Core local records are not transferred internationally merely because they are stored in WorkProof.

When Crashlytics, Analytics, Android ML Kit scanner telemetry, advertising, app-store, operating-system or cloud backup, website-hosting, communication, or user-selected sharing and storage services are used, information may be processed in countries other than the user's own, including the United States. Firebase states that global services such as Crashlytics may process information wherever Google or its subprocessors maintain facilities.

Where European transfer rules apply, transfers may rely on adequacy decisions, the EU–US Data Privacy Framework where applicable, Standard Contractual Clauses, UK or Swiss equivalents, or another lawful mechanism. See the Firebase Data Processing and Security Terms and Google Privacy Policy.

Team

18 Privacy Rights

Depending on location, a person may have rights to:

• Know whether and how personal information is processed
• Request access to or a copy of personal information
• Correct inaccurate information
• Request deletion
• Restrict or object to processing
• Receive portable information
• Withdraw consent
• Opt out of targeted advertising or qualifying sale or sharing
• Limit certain uses of sensitive information
• Appeal a denied request
• Complain to a data-protection authority

Because WorkProof does not maintain user accounts and normally cannot access local records, we may be unable to retrieve, correct, or delete content held only on the user's device. Active records can be viewed and edited in the app, available exports can provide copies, and device controls can remove local app storage. An in-app record deletion may remain as a soft deletion in local history.

For information processed through Crashlytics, Analytics, ML Kit, advertising, website hosting, or support, contact us using the details below. We may need enough information to locate and verify the relevant record. Some pseudonymous SDK information may not be reasonably linkable to a real-world identity.

We will not discriminate against a person for exercising an applicable privacy right. Authorised-agent and appeal requests will be handled where required by law.

Supervisory authority: Team
Request response period: Team

WorkProof does not use locally stored work or pay records to make decisions that produce legal or similarly significant effects about a user. Google and advertising partners may perform profiling for personalised advertising when permitted by the user's choices and applicable law.

19 Children

WorkProof is intended for users aged {{MINIMUM_USER_AGE}} or older and is not directed to younger children.

We do not knowingly request children's information through a WorkProof account because the app has no account system. Advertising and diagnostic SDKs may process device data as described above, and a user could enter information about another person into a local record.

Yes

If a person believes information relating to a child has been transmitted to us contrary to this Policy, they should contact us. We will take reasonable steps available to us, recognising that we cannot access content held only on another person's device.

20 Changes to This Policy

We may update this Policy when WorkProof's features, vendors, legal obligations, or data practices change. The revised Policy will show a new Last updated date and will be available at https://workproof-tracker.web.app/privacy-policy.html and https://workproof-tracker.web.app/privacy-policy.html.

Where required, we will provide additional notice or seek consent before a material change takes effect. If a future version introduces accounts, cloud synchronisation, or a WorkProof backend, this Policy and applicable store disclosures will be updated before that processing begins.

21 Contact Us

For privacy questions or requests:

Controller: WorkProof
Address: High Street North, E12 6QN, London
Privacy email: swe.jamirulinfo@gmail.com
General support: swe.jamirulinfo@gmail.com
Data Protection Officer: +8801783109748
EU representative: +8801783109748
UK representative: +8801783109748