Axima Workforce Privacy Policy
This policy explains how Graxana Software Inc. handles information through Axima Workforce for Android and the connected workforce service.
Request account or data deletion · Get help with the app
Accounts and workforce information
Axima Workforce supports organizations and their authorized workers, managers and clients. The native app uses an existing account and does not offer a public registration form. Organization administrators can arrange access. Connected web pages may also offer account registration and organization setup; these do not grant access to another organization's records.
Depending on your role and organization, the service processes name, email, phone number, account identifiers, membership and permissions; shifts, sites and assignments; availability and time-off requests; attendance, breaks, timesheets, approvals and comments; and authorized team, operations, client, contract, reporting and pay-statement information. Passwords are submitted for authentication; the native app retains an access token rather than your password. Actions and security events may be logged to protect accounts and maintain records.
Care clients, credentials and some agreement functions open a separate authenticated web workspace. If you use them, records may include care or health information, credential documents, attachments and signatures. Access depends on your organization's permissions. The app does not provide diagnosis or treatment advice. Do not include unnecessary sensitive information in free-text fields.
Location during attendance actions
The app requests foreground location only when you start an attendance action for an assignment whose organization and site require location verification. It does not continuously track your movements or request background location. For assignments that do not require location, the current native punch flow does not request GPS evidence.
When permission and location services allow it, the app captures coordinates, accuracy and capture time and sends them with the attendance event. Required clock-in needs connectivity and acceptable, fresh location evidence inside the site's boundary. Denial, unavailable location or failed verification can prevent clock-in. Clock-out can still be submitted when GPS is denied or unavailable, or evidence needs review, so a manager can resolve the exception. Approximate or poor accuracy may be insufficient for required clock-in. Device capture time is evidence, not automatically verified attendance time.
Information stored on your device
Native authentication tokens, selected organization and pending punches use protected Android storage. Pending punches can include account and assignment identifiers, timestamps, location evidence and synchronization errors. Legacy plaintext punch copies are migrated when read.
Unsent and unresolved punches remain associated with their original account after sign-out; another account cannot synchronize them. Sign back into the original account to resolve and synchronize them. These records have no automatic age-based deletion in the current app. Clearing app data or uninstalling removes local unsent evidence; it does not erase attendance already submitted.
Cached native schedules are protected, scoped to account/organization/permissions, and limited to 12 ranges and 1,000 shifts. Copies older than 24 hours are removed when the cache is accessed; sign-out or revoked/changed access clears them. This is not a background deletion timer. Browser previews keep schedules in memory, while pending punches in a browser use browser storage rather than Android encryption. Basic interface preferences and last sync time may use WebView storage. Android cloud backup and device-to-device transfer are disabled for app-private data.
Notifications, providers and web analytics
When Firebase messaging is configured, Google Firebase processes installation identifiers and technical app/device information to support messaging. With notification permission, the app registers a push token with the workforce service. Messages may carry workforce notification text and record links; device settings control lock-screen display. Denying notifications does not prevent using workforce screens. Provider SDK initialization can process technical identifiers independently of whether a notification is displayed.
Your organization and its authorized users can access information allowed by their roles. Hosting, communication and operational service providers process information needed to deliver and maintain the service. Requests expose network metadata such as IP address, request time and user agent for delivery, authentication, security and troubleshooting.
The current native application includes no advertising or behavioral-analytics SDK. Connected web pages have their own analytics preferences: optional public-page analytics and aggregate click maps run after consent. This distinction does not mean operational audit logs or Firebase technical processing are disabled. Web handoffs do not include the native access token in their URL.
Retention, access and deletion
Workforce records are retained according to organization configuration, service arrangements, applicable obligations and administrator actions. Precise location can be removed separately from attendance records through configured retention processing. Local schedule expiry is not a promise that server records, backups or unsent punches are deleted after the same period.
To request access, correction, account deletion or deletion of associated data, contact your organization administrator or email privacy@graxana.com with the subject Axima Workforce privacy request. Include your registered email, organization and the request you want to make. Do not send your password, identity documents, care records or other sensitive attachments in an initial email. We may need to verify your identity and coordinate with the organization responsible for the records. If information must be retained, for example for payroll, security, legal obligations or another person's records, the response should explain that retention. Sign-out, account deactivation and uninstalling are not the same as deleting server-held data.
Security and contact
The service uses HTTPS, organization-scoped authorization and protected native storage. No system can guarantee complete security. For support use support@graxana.com. Privacy questions can be sent to privacy@graxana.com or Graxana Software Inc., 1351 Wilson Avenue, Toronto, Ontario M3M 1H7, Canada. This notice and its effective date will be updated when the described processing changes.