- Effective date
- 9 October 2026
- Publisher
- Digisquares Technologies Private Limited, Saravanampatti, Coimbatore 641035, Tamil Nadu, India
- Contact
- sathish@digisquares.com or support@worksquares.ai
- Public policy address
- https://digisquares.com/style-to-ship/privacy
Style to Ship is an Android workplace app for staff of garment manufacturers using AGMS. It provides access to assigned approvals, business records, inventory, production, quality workflows and reports according to your company's configuration and permissions. Accounts are provided by your organization; the app does not offer self-service registration.
Version scope: this policy covers the existing app and the 0.3.2 update. The reliability reporting and Android notification features described below apply from version 0.3.2; they are not present in version 0.3.1. A policy update does not mean that an app update is already available. Check the version shown on Sign in or Profile.
Who controls your information
Digisquares builds the app. Your company controls the business records in its AGMS service. For questions about a record you enter, account access or company retention requirements, contact your AGMS administrator. For app-related questions, contact the publisher using the addresses above.
Information sent to AGMS
The app communicates with the AGMS service used by your company over HTTPS. It has no advertising integration.
- Sign-in: your work email address and password are sent to authenticate your account and obtain session credentials.
- Business activity: permitted receipts, issues, production output, inspections, challan receipts, approval decisions and comments, watchlist changes and notification read-state changes are sent to AGMS. Searches, report options, decoded barcode values and supported document QR tokens may also be sent to retrieve records.
- Request context: requests use session credentials and app-version information. The service attributes business activity to your user and company.
Reliability reporting — from version 0.3.2
The app automatically reports crashes and failures to respond to the AGMS service so the service operator can diagnose reliability problems. Reports may include the failure type, error message and stack trace, app version, Android API version, device model, language, failure time, pending-entry count, and a short trail of recent screen routes and API request paths. Received reports are associated with the authenticated user and company; they are not anonymous.
The app and server apply filters intended to remove tokens, email addresses, document-number patterns and amounts from diagnostic text. Business request and response bodies are not intended to be included. These filters are safeguards, not a guarantee that every sensitive value in free text can be recognized. There is no in-app opt-out from reliability reporting.
The server is configured to remove reports older than 90 days through scheduled cleanup. Pending reports on the phone are described below. Reliability reporting does not send reports through a third-party crash-reporting SDK.
Information stored on the phone
- Session credentials: access and refresh tokens and account details are encrypted using a non-exportable Android Keystore key. Hardware protection depends on the device. Session data is cleared on sign-out or session invalidation; the app does not save your password.
- Unsent entries: supported operational entries remain in the local queue until they can be sent or you discard them through Sync Center. Signing out does not discard that queue. Entries that have already posted are subject to your company's business-record rules.
- Preferences and searches: the app stores appearance preferences and recent searches. Recent searches are cleared on sign-out.
- Report exports: requested spreadsheet files are temporarily cached for sharing with the app you choose. Files older than a day are removed on the next export, cached exports are cleared on sign-out, and Android may clear the cache. Copies shared to another app follow that app's storage and privacy practices.
- Reliability reports, from 0.3.2: at most 20 reports are held in private, non-backed-up storage. Reports older than 14 days are removed when report cleanup runs. Reports made while signed in wait for the same account before upload; a report made before sign-in can be uploaded under the next signed-in account. Sign-out does not immediately remove these files.
The app uses private storage and opts out of Android cloud backup and device-to-device transfer. User-initiated report sharing is separate from backup.
Camera and Google ML Kit
Camera permission is requested when you open the scanner. Barcode and QR decoding happens on the device. The scanner does not take, store or upload photos or videos. Decoded values may be sent to AGMS for record lookup. You can type instead, and a device without a camera can use the app.
The bundled Google ML Kit barcode SDK has separate diagnostic and usage collection. Its provider disclosure describes device and application information, installation identifiers, performance information, scanner configuration, input/output sizes, feature versions, events and error codes. Google describes HTTPS transport for this information. The app's business requests do not send camera images or decoded lookup content to Google. See Google's ML Kit data disclosure.
Permissions and notifications
The app uses internet and network-state access and optional camera access. It does not request location, contacts, microphone, phone or broad shared-storage permissions.
From version 0.3.2, on Android 13 and later, the app asks after sign-in for permission to display notifications. Notifications use generic approval, unread-alert or failed-entry information, without amounts, counterparty names or document numbers in displayed text. Supported notifications can open records in the app. You may decline permission or disable notifications in Android settings. This version checks AGMS for updates rather than using Firebase push messaging.
Sharing and recipients
Business requests and reliability reports go to your company's AGMS service. The scanner's SDK diagnostics follow Google's disclosure. If you choose to share an export, the selected app receives that file. Do not share business records with recipients your company has not authorized.
Data deletion and account requests
- Sign-out clears session credentials, recent searches and cached exports, but does not delete queued entries or all pending reliability reports.
- Uninstalling removes the app's local storage, including unsent entries. It does not delete server records, uploaded reports or copies already shared with other apps.
- Account and server records: contact your company's AGMS administrator to request correction, removal or account closure. You can also email sathish@digisquares.com or support@worksquares.ai with your company and account email; do not include your password. We will route the request to the relevant administrator. Identity verification and applicable business-record retention requirements affect what can be removed.
Children
Style to Ship is a workplace tool, is not directed at children and does not knowingly collect information from people under 18.
Changes to this policy
Updates appear at the public policy address with a revised effective date. Material changes are also described in the app's release notes.