Privacy Policy for ZUVEES Operations Team App

1.1 Account and Identity Information

• Email address — used for login authentication only
• Password — transmitted securely over HTTPS and never stored locally on the device
• Full name and phone number — received from the backend after successful login

1.2 Operational Work Data

• Order picking activity — which order items and DRS (Delivery Route Sheets) you pick, mark, or scan during a shift
• QR code values scanned during the picking process for order item verification (not stored on device)
• Florist SKU assignments — items assigned to you and quantities submitted for QC
• Picker preferences such as sort order (by orders or items) and order source filter (Shopify or Marketplace), stored locally on the device
• DRS and order status updates transmitted in real time via WebSocket

1.3 Camera, Photo Library, and Order Approval Media

• Camera permission is used for QR code scanning during picking and florist workflows — frames are processed in real time on-device for code recognition only and are not stored, saved, or uploaded
• Camera permission is also used by the Video Approval feature, which lets you record a short video or photo of a fulfilled order for customer approval when enabled for that order. Videos recorded this way may include audio captured by your device's microphone
• Photo library access is requested only if you choose to select an existing video or photo from your device instead of recording a new one for the Video Approval feature
• Videos and photos captured or selected for order approval are uploaded to secure cloud storage and shared with authorised internal reviewers and, where applicable, the customer, for approval purposes (see Section 5)
• The App does not keep a persistent local copy of order approval videos or photos — the local reference is discarded once the upload completes

1.4 Push Notifications and Device Data

• Notification permission and an Expo push notification token, generated by the Expo push notification service, so we can deliver push notifications to your device
• A device identifier and device name are sent to the backend together with the push token when you log in, so the server can address notifications to your specific device
• Push tokens and device identifiers are used solely to deliver notifications — the App does not use this data for tracking, advertising, or behavioural analytics

1.5 Session and Connectivity

• Authentication token — issued by the Zuvees backend upon login and stored securely on your device using Expo SecureStore (encrypted platform keychain)
• Real-time connection status via Socket.IO to api.zuvees.ae for live order and DRS updates

1.6 Local Network and Printer Connectivity

• When you select a label printer, the App connects directly to that printer's IP address on your local network to send print jobs
• Only print-job content is transmitted to the printer — a QR code identifier and related label text. No customer name, address, or phone number is sent to the printer

4.1 Core Operations

• Authenticating your identity and maintaining your session securely
• Displaying your assigned DRS sheets, order items, and SKU tasks
• Recording picking confirmations and florist SKU submissions to the backend
• Enabling real-time status synchronisation across the operations team
• Delivering push notifications about order, DRS, or task updates to your registered device
• Enabling the Video Approval workflow — capturing, uploading, and routing order approval videos/photos to internal reviewers and, where applicable, customers

4.2 Quality and Performance

• Tracking fulfilment accuracy for QC review by operations managers
• Maintaining picker and florist activity records for operational oversight

4.3 Security and Access Control

• Verifying identity via secure token-based authentication on every API request
• Restricting access to role-specific data (picker vs. florist endpoints)
• Automatically clearing session data upon logout

5.2 We may share information with:

6.1 On-Device Storage

• Authentication token and session data are stored using Expo SecureStore — backed by the iOS Keychain and Android Keystore, which provide hardware-backed encryption
• Non-sensitive preferences (sort order, source filter) are stored in AsyncStorage and contain no personal data
• No passwords, QR codes, or order content are ever persisted on-device
• Order approval videos/photos exist only as a temporary local file during recording/preview and are uploaded to encrypted cloud storage — the App does not keep a persistent local copy after upload

6.2 Network Security

• All API communication with api.zuvees.ae is conducted over HTTPS (TLS encrypted)
• WebSocket (Socket.IO) connections are also established over secure transport
• All requests are authenticated using Bearer token authorisation headers

6.3 Access Controls

• Role-based API endpoints ensure pickers only access picker data and florists only access florist data
• Session is automatically invalidated and all local data cleared upon logout

7.1 Retention Periods

• Active operational records (picking history, SKU assignments): retained during employment and up to 3 years after termination for audit purposes
• Financial and compliance records: retained for 7 years per applicable tax and accounting regulations
• Support communications: retained for 2 years for quality assurance

7.2 Data Deletion

• Automatic deletion of expired data per retention schedules
• Manual deletion available upon valid user request, subject to legal obligations
• Secure data destruction using industry-standard methods

8.1 Access and Portability

• Request a copy of all personal data we hold about you
• Receive data in a structured, machine-readable format

8.2 Correction and Updates

• Request correction of inaccurate or incomplete personal information

8.3 Deletion and Restriction

• Request deletion of personal data (right to be forgotten), subject to legal retention obligations
• Restrict processing for specific purposes
• Object to data processing based on legitimate interests