Where your crew went. Only the right people know.
TetherLogix holds where people work alone, when they should be back, and who to call if they aren't. Here is how it is protected, said plainly. Every line on this page is true today.
Six things that are true today
One company, one set of records
Every request is checked on the server against the company of the person who sent it. One company never sees another's people, trips or places.
Roles that the server enforces
Workers see their own trips. Crew leads and admins see the board. Only admins change people, alert steps and billing. The server checks the role on every request, not the screen.
A trip record nobody can rewrite
Every check-in, alert and answer is written to a record that the database itself refuses to change or delete. Not even our own code can edit it.
Location only during a trip
The app uses location only while a trip is open, and stops when you tap I'm back. Your admin picks how long locations are kept, from 30 days to a year. Then they are deleted.
Sign-in that locks itself
Passwords are at least 10 characters and stored only as a hash. After 8 wrong passwords the account locks for 5 minutes, and sign-in attempts are limited per visitor.
Encrypted and backed up every day
Every connection uses HTTPS. The database is encrypted at rest by Google Cloud and backed up every day, with the last 7 days kept.
The server decides. The screen only shows it.
Every rule that matters runs on our server: who can see a trip, when an alert goes out, who it goes to next. A changed app, a stale screen or a lost phone can't skip a step. The alert timer runs on the server too, so a phone that is off or out of signal still gets someone looking.
What we look after. What you look after.
We handle
- The servers, the database, the backups and the restore.
- Keeping companies apart, and checking roles on every request.
- Encryption, sign-in rules and lockouts.
- Sending texts, calls and push alerts, and checking that they arrived.
You handle
- Who gets a login, and whether they are a worker, lead or admin.
- Turning a person off the day they leave. It signs them out everywhere.
- The alert steps: who is called, and after how many minutes.
- Keeping phone numbers and emergency contacts up to date.
Your data stays yours
The trips and records your crew creates belong to your company. We use them only to run the service, and the terms say so in writing. We don't sell them and never use them for advertising.
- Take it with you. Admins export trips and the full record as a spreadsheet file at any time, on every plan.
- Delete a person. Anyone can delete their own account in the app or on the web. Their details and trip locations are deleted at once. How it works.
- Delete a company. An admin emails support@tetherlogix.com and we delete the company's records.
What we have not built
We would rather tell you here than have you find out after signing up.
Two-step sign-in
Not offered in the app yet. Today an account is protected by its password, the lockout and the attempt limits.
SOC 2 or ISO 27001 report
We have not been audited. The six items above are what an auditor would look at.
Company single sign-on
No SAML single sign-on, so a company can't require its own identity provider for everyone.
Hosting outside the United States
One region, in the central US. Storage in Canada for Canadian companies is planned. We'll tell those companies before any move.
A second text provider
Built and set to take over if the main one fails. It is waiting for the phone carriers' approval. Push alerts and calls already go out on their own routes.
Questions? Ask a person.
Security questions, questionnaires and reports of a problem: security@tetherlogix.com. Everything else: support@tetherlogix.com.
Found a weakness? Tell us privately at the address above, give us time to fix it, and don't access other people's data to prove it. We'll answer, and we'll tell you when it is fixed.