Security

Your data, kept apart and kept in scope.

How each company’s data is separated, who can see what inside it, and what the phone records. Written from how the product works today.

Another company

Its own data

Your company20 people

Company scope

Telangana15 people

Region scope

Hyderabad West team5 people

Team scope

One rep1 person

Own

Illustration. Sample organisation.

Separated by company.

Every record carries its company.: The database filters every request to the caller’s company before anything else happens. It is enforced in the database, not only hidden on screen.
Scope is enforced the same way.: Own, team, territory, region or company. A login sees the people its scope allows and no one else. Try the scopes on the Console page
A suspended company is closed.: When a company’s account is suspended, its logins stop seeing its data.

Invite only.: There is no public sign-up. We create each company and invite its owner by email.
Nobody at Mr Sales knows your password.: Owners and office colleagues set their own. Field staff are emailed a link to choose theirs, and must change any starting password on first sign-in.
A reset needs the inbox.: Knowing someone’s employee ID is not enough to reset their password. The link goes to the email on record.
Pay stays private.: Payslips are visible to the employee and to the owner, admin, HR and finance roles only.

Location, files and decisions, in the order a working day produces them.

Day plan sent
Location recorded.
The phone records where it is when the day plan is sent.
At each visit
Location recorded, and checked.
A phone that reports a mocked GPS position is raised to the manager as a compliance event.
Between visits
Nothing recorded.
There is no background tracking. Location is taken at moments, not all day.
Receipts and visit photos
Kept private to the person.
They are stored privately. A rep cannot open a colleague’s receipt or photo.
Files from the office
Private unless published.
Only files the office publishes to the field force, such as visual aids, are shared across the company. Anything else defaults to office only.
Each approval
A name and a time.
Every approval records who decided and when.
Each change in the console
Logged.
The audit log records who changed what in the console.

Illustration of one working day.

Said plainly, so nothing on this page overstates where we are.

What you might expect	Today	What changes it
ISO 27001 or SOC 2	Not held	We do not hold either today, and we will not show a badge until we do.
An uptime figure	Not published	We will publish one when we have a track record to base it on.
Your security questionnaire	Ask us	Send it with your demo request and we will answer it in writing.

Book a demo and bring whoever signs off on security. We will walk through all of this on your own data.