Data Requests and Deactivation
Request a review
Contact the company administrator who authorized access. State whether you need access, correction, restriction, user disablement, or deletion review. Include your name, organization, relevant location and inventory date. For a device request, include its model, company label and app version/build. Legacy users may be asked for the attribution phone number through an approved protected process.
The administrator may verify your identity and authority before changing or disclosing records. This is workplace-managed access, not public self-registration.
Do not send an activation code, employee or administrator PIN, session token, or device credential as proof of identity.
Disable access or deactivate a device
Ask the administrator to disable the managed user to revoke user sessions, or revoke the device separately. Server-side revocation is the reliable server-side step that stops future device access. Reactivation or a new device code is required to restore the relevant access.
Operating-system app-storage controls or uninstalling can remove ordinary local drafts and preferences. Secure credential behavior differs by platform: local removal is not a substitute for server-side revocation. Do not remove app data to troubleshoot an unsynchronized draft.
Records that remain
Deactivation does not automatically erase workplace profiles, prior sessions, submitted quantities, exports or immutable security and access audits. Deleted submissions leave tombstones, original lines and audit evidence. Your organization reviews historical-record requests against operational and legal retention duties.
Email privacy support. The company administrator who authorized the device remains the contact for company records and access decisions.
Never include an activation code, employee or administrator PIN, session token, or device credential in an ordinary support message.
Last updated: October 15, 2026