1. Overview

POSMWorks is a business application for point-of-sale material operations, dispatch planning, field execution, evidence collection, reporting, accounting document workflows, and role-based operational dashboards.

The app is intended for authorized business users only. Available features depend on each user's assigned organization, account, vendor, role, and permissions.

2. Data We Collect

POSMWorks collects and processes information needed to operate the platform and support field work. Depending on your role and the features you use, this may include:

  • Account and profile information: name, email address, profile details, role, permissions, assigned accounts, assigned vendors, and organization relationships.
  • Operational records: accounts, projects, stores, products, orders, tasks, dispatch runs, route plans, vehicle and crew details, work status, notes, and review decisions.
  • Field execution evidence: photos, signatures, remarks, attachments, timestamps, store execution details, and submitted completion information.
  • Location information: approximate or precise device location used for field execution, route progress, geofence checks, on-the-way tracking, and evidence context.
  • Device, app, and sync information: device identifiers used for notifications, app version, network status, sync status, offline queue state, diagnostics, and activity logs.
  • Notifications and communications: notification delivery preferences, notification events, and related delivery status information.

3. App Permissions

POSMWorks requests Android permissions only when they support app functionality. Permission availability may vary by device and Android version.

Camera and Photos

Used to capture or upload field evidence, store photos, issue documentation, and execution attachments.

Location

Used for field execution context, route progress, geofence checks, and operational verification. When enabled for field work, location may be collected while a user is actively assigned to execution activity, including background tracking needed for route or on-the-way workflows.

Notifications

Used to alert users about assignments, dispatch updates, review items, work status changes, and other operational events.

Storage and Files

Used to handle evidence attachments, cached files, generated reports, exports, and offline work data.

Network Access

Used to sign in, sync data, upload evidence, receive updates, and detect whether offline actions need to be queued.

4. How We Use Data

We use collected data to:

  • Authenticate users and enforce role-based access controls.
  • Manage orders, stores, projects, products, vendors, and tasks.
  • Plan dispatch runs and coordinate vehicle, crew, and route work.
  • Track field execution progress and collect completion evidence.
  • Support offline work and synchronize updates when connectivity returns.
  • Generate dashboards, reports, exports, and operational analytics.
  • Send operational notifications and status updates.
  • Maintain audit logs, security records, and system reliability.

POSMWorks does not sell personal or sensitive user data.

5. Data Sharing

POSMWorks data is shared only as needed to provide the service, operate business workflows, comply with legal obligations, or protect the platform. Data may be visible to authorized users based on their roles, such as internal operations users, logistics teams, field personnel, vendor administrators, client users, finance users, and system administrators.

The app may rely on service providers for hosting, authentication, storage, notifications, maps, analytics, and infrastructure. These providers process data only to support POSMWorks functionality and service operations.

6. Security

POSMWorks uses technical and organizational safeguards designed to protect user and operational data. These safeguards include authenticated access, role-based permissions, database security rules, audit logging, encrypted network transmission, and controlled access to stored evidence and operational records.

No method of transmission or storage is completely secure, but we work to limit access to authorized users and maintain appropriate protections for business and personal information.

7. Retention and Deletion

POSMWorks retains information for as long as needed to provide the service, support operational records, meet audit requirements, resolve disputes, comply with legal obligations, and maintain security.

Some records, such as dispatch history, execution evidence, accounting document references, and audit logs, may need to be kept for legitimate business, compliance, or security purposes even after a user account is deactivated.

Authorized users may request account deletion or data deletion through their POSMWorks account administrator or through the contact method listed in this policy. Requests will be reviewed according to applicable business, legal, security, and retention requirements.

8. User Choices and Controls

  • You can manage Android runtime permissions in your device settings. Some features may not work if required permissions are disabled.
  • You can control notification permissions through Android system settings and, where available, app notification preferences.
  • If you believe your assigned role, account, vendor, or access level is incorrect, contact your organization or POSMWorks administrator.
  • If you use guest execution links, only submit information that is relevant to the requested field execution or evidence workflow.

9. Children

POSMWorks is a business operations application and is not directed to children. The app is intended for authorized business users and field personnel.

10. Changes to This Policy

We may update this Privacy Policy to reflect changes to the app, operations, legal requirements, or security practices. The effective date at the top of this page indicates when the policy was last updated.

11. Contact

For privacy questions, account deletion requests, or data inquiries, contact your POSMWorks account administrator or the POSMWorks Team at digitechdept@gmail.com.

Please include your name, organization, account email, and a clear description of your request so the correct administrator can review it.