Privacy Policy.
This page explains how Field Blink — the mobile Sales Force Automation app published by Field Blink — collects, uses, stores, and shares personal data. It is intended for distributors, field employees (DSRs, TSOs, ASMs), sales managers, and the administrators who deploy the app.
§ 01
Introduction
This Privacy Policy explains how Field Blink ("we", "our", or "the app") collects, uses, stores, and shares your personal data when you use our mobile application. Field Blink is a field sales and execution management tool used by distributors, field employees (DSRs, TSOs, ASMs), and sales managers to manage daily sales operations, attendance, route execution, and order booking.
Field Blink is a business-to-business (B2B) platform. users are onboarded onto the system by their organization's administrator, not directly by Field Blink. The organization that onboards you is the data controller for the operational records you capture during the course of work — orders, attendance, shop visits, shop registrations, shop photos and route GPS. Field Blink processes those records on the organization's instructions. This policy applies to your personal data user of the app; questions about operational records should be directed to your organization's administrator.
By using the app, you agree to the collection and use of information in accordance with this policy. If you do not agree, please do not use the app.
§ 02
Information We Collect
Account & Profile Information
- Name, email address, username, employee code — used to identify you within your organization's field operations.
- Position / role assignment — your job title (e.g., DSR, TSO, ASM) determines what features and data you can access.
- Org unit and distributor assignments — which territory or distributor you are assigned to for route planning and reporting.
Location Data (GPS)
Most sensitive — Location is used for:
- Attendance check-in / check-out: GPS coordinates are captured as proof when you start and end your work day.
- Background location tracking: While you are checked in ("on duty"), the app continuously collects GPS location data in the background (even when the app is closed) to track your field route, generate visit reports, and calculate distance-based allowances.
- Shop visit verification: GPS is captured when you visit a shop to confirm proximity.
- Shop onboarding: GPS coordinates are captured when you register a new outlet.
- Mock location detection: We check GPS accuracy to detect simulated locations.
Background location access is requested on iOS and Android. You can revoke this permission at any time through your device settings, but doing so will limit key app functionality (attendance check-in, route tracking).
Camera & Photo Library
- Attendance selfie proof: A selfie photo may be required as proof of presence during check-in or check-out, depending on organizational policy.
- Shop onboarding photos: Photos of new outlets are captured to support distributor verification.
- Receipt / document capture: Photos may be attached to payment collections or returns as evidence.
Order & Transaction Data
- Product catalog — products, pricing, units of measure (UOM), and availability.
- Order details — products ordered, quantities, prices, discounts, order totals, order status.
- Return records — returned items, reasons, and associated documentation.
- Payment collections — payment amounts, methods, and proof.
- Outlet / shop information — shop names, addresses, GPS coordinates, distributor assignments.
Device Identifiers
- Device binding token: A unique device key is generated and securely stored to bind your account to a specific device, preventing unauthorized access.
- Tracking device ID: A token registered with our location tracking service (Traccar) to associate GPS pings with your user account.
- Client mutation ID: A device-generated identifier to ensure idempotent data submission (prevents duplicate records from offline operations).
Attendance & Working Hours
- Check-in / check-out timestamps — start and end of your work day.
- Attendance status — full day, half day, late arrival, early departure, missed check-in/out, absent, leave, holiday, weekend.
- Late / early minutes — calculated based on your organization's attendance policy and time tracking.
- Attendance policy assignments — which policy rules apply to you (shift times, grace periods, geofence boundaries).
- Leave requests — submitted leave with dates, reason, and approval status.
Offline Data Storage
The app is designed to work offline. Data (orders, attendance events, shop registrations) is stored locally on your device using PowerSync and SQLite databases. This local data is encrypted at rest where the device OS supports it and is automatically synced to our servers when connectivity is restored.
§ 03
How We Use Your Information
| Purpose | Data Used | Legal Basis |
|---|---|---|
| Field execution management | Orders, shop visits, route data | Contractual necessity (service delivery) |
| Attendance & payroll processing | GPS, timestamps, attendance status, selfie proof | Contractual necessity / consent |
| Route & territory optimization | Background GPS location | Consent |
| Security & fraud prevention | Device binding, GPS accuracy checks, audit logs | Legitimate interest |
| Allowance & incentive calculation | Attendance records, order performance, routes | Contractual necessity |
| Reporting & analytics | Aggregated anonymized data | Legitimate interest |
§ 04
Third-Party Services & Data Sharing
We use the following third-party services to operate the app. Each processes data only as necessary to provide their service:
| Service | Purpose | Data Shared | Location |
|---|---|---|---|
| Supabase | Backend database, authentication, file storage, real-time sync | All user data (profile, orders, attendance, location, photos) | US (multi-region) |
| PowerSync | Offline-first data sync engine | Synced database rows (orders, shops, products, attendance) | US |
| Traccar | Real-time GPS location tracking & route management | GPS coordinates, device tokens, timestamps | Self-hosted / customer-configured |
| Expo | Mobile development platform, build pipeline, OTA updates | Device model, OS version, crash logs, installation ID | US |
We do not sell your personal data to third parties. Data is shared only with service providers essential to app functionality, under Data Processing Agreements (DPAs) where required.
§ 05
Data Storage & Retention
- Server-side storage: Your data is stored in Supabase PostgreSQL databases with row-level security (RLS) enforcing access control. Backups are performed regularly with point-in-time recovery (PITR).
- Local device storage: Offline data is stored on your device in PowerSync SQLite databases. This data mirrors the server data you have access to and is deleted when you sign out or the app is uninstalled.
- Secure credential storage: Authentication tokens and device binding keys are stored in platform-native secure storage (iOS Keychain / Android EncryptedSharedPreferences via SecureStore).
- Retention: We retain your data for the duration of your organization's contract with the service. Attendance records and order history may be retained longer to meet legal, tax, or payroll obligations. You may request deletion of your personal data (see Section 7).
§ 06
Permissions Requested by the App
| Permission | Why It's Needed | Can Be Revoked? |
|---|---|---|
| Location (Foreground) | Attendance check-in/out GPS proof, shop visit verification, shop onboarding location capture | Yes — but check-in will fail |
| Location (Background / "Allow all the time") | Continuous route tracking while checked in, even when app is closed | Yes — but route tracking will stop |
| Camera | Attendance selfie proof, shop onboarding photos, receipt capture | Yes |
§ 07
Your Rights & Choices
Depending on your jurisdiction (e.g., GDPR in the EEA, CCPA in California), you may have the following rights:
- Right to access — request a copy of the personal data we hold about you.
- Right to rectification — request correction of inaccurate or incomplete data.
- Right to deletion — request deletion of your personal data, subject to legal retention requirements.
- Right to restrict processing — request that we limit how we use your data.
- Right to data portability — request a machine-readable copy of your data.
- Right to withdraw consent — for location tracking and camera use, you can revoke permissions at any time in your device settings.
- Right to object — object to processing based on legitimate interests (e.g., analytics).
To exercise any of these rights, contact your organization's administrator or reach us at the contact details below. To request permanent deletion of your user account and the personal data tied to it, use our Account Deletion form. Note that Field Blink is a B2B platform — field-force users are onboarded by their organization's administrator, and the operational records they capture during the course of work (orders, attendance, shop visits, shop photos, route GPS) are the property of that organization. Your organization is the data controller for those records; requests to amend or expunge them must go to your administrator directly.
§ 08
Data Security
We implement appropriate technical and organizational measures to protect your data, including:
- Encryption in transit (TLS 1.3) for all network communication
- Row-level security (RLS) in the database to enforce data access boundaries
- Secure credential storage on device (iOS Keychain / Android EncryptedSharedPreferences)
- Device binding to prevent unauthorized account access from unknown devices
- Audit logging of data access and modification events
- Regular security reviews of dependencies and infrastructure
§ 09
Children's Privacy
Field Blink is a business-to-business (B2B) application intended for use by adults in a professional capacity. We do not knowingly collect personal data from children under the age of 16. If you believe a child has provided us with personal data, please contact us immediately.
§ 10
Changes to This Policy
We may update this Privacy Policy from time to time. We will notify you of material changes through the app or via your organization's administrator. The "Effective" date at the top of this page indicates when the policy was last revised. Continued use of the app after changes constitutes acceptance of the updated policy.
§ 11
Contact Us
If you have questions, concerns, or requests regarding this Privacy Policy or our data practices, please contact your organization's administrator who manages the Field Blink service. If you are an administrator, you may reach the development team at: