Security

Location data is sensitive. We treat it that way.

You are asking staff to carry a tracker. That only works if the data is tightly scoped, access is controlled, and every sensitive action leaves a trail. Here is how that is enforced.

  • Organisation-scoped isolation
  • Role-based access
  • Audit logging on sensitive actions
The agent's own profile screen, showing their performance figures and the app permissions they control, including location tracking.

Access & audit

Role-based access and audit-ready logs.

Different roles see different data, and every sensitive action is written down.

Who can see what

Roles inside a customer organisation.

  1. AgentTheir own work only

    Own routes, the customers assigned to them, their own orders and visit history. Cannot reassign work to anyone else.

  2. ManagerTheir team

    Everything an agent sees, across the team they manage, plus assignment of leads and customers, and reporting on team performance.

  3. Company adminThe whole organisation

    All team routes, detailed GPS tracks, customer approvals and full visit history, for their own organisation and no other.

Audit log

An example of what an admin sees.

  1. Admin login
    admin@gupta-dist.com · IP 103.x.x.x · Mumbai, India
    2 min ago
  2. Customer approved
    admin@sharma-fmcg.com approved "New Store Mumbai"
    2 hours ago
  3. Geofence radius changed
    admin@gupta-dist.com changed 50m to 100m
    1 day ago
  4. Lead reassigned
    manager@gupta-dist.com moved 4 customers to a new agent
    2 days ago
  • Organisation-scoped isolation

    Data is partitioned by organisation at the database rules layer, not filtered in the client.

  • Role-based access control

    Agent, manager and company admin roles, enforced by signed custom claims rather than UI state.

  • Audit trail on sensitive actions

    Logins, approvals, geofence changes and reassignments are written to an append-only log.

  • Encrypted in transit and at rest

    Served over TLS and stored on Google Cloud infrastructure, which encrypts data at rest by default.

See it on your own routes.

A 30-minute demo, then a pilot with a few of your agents, so you can judge FieldFlowSales on your own data.

Offline-first
No data lost when the signal drops
Native GPS
Survives app kill and battery saver
Android · iOS · Web
Every device your team already uses
  • Built on Google Cloud
  • Role-based access and audit logs
  • Direct founder support