Security
Every claim below is a mechanism, not an intention — because “we take security seriously” is what every company says the week before it doesn’t.
Last updated 14 October 2026Staff cannot read your location
This is the difference that matters. Almost every product in this category has an internal tool that can see any customer's data, guarded by a policy and an access log. A policy is a promise; a missing grant is a fact.
Every look is written down
It covers looks by your own family. If somebody in your circle opened your location at 2am, you can see that they looked in that hour, and this was a deliberate choice: the person most likely to misuse a family tracker is in the family.
How the data is protected
Accounts and sessions
Dependencies
Packages are installed with install scripts switched off, and each one is checked against the checksum recorded in the lockfile. The checks that run on every proposed change also require every lockfile entry to carry a checksum, and fail on a known High or Critical vulnerability unless we have recorded an exception with an owner and an expiry no more than 30 days away. The job that builds the release images does not yet wait for those checks to pass. Checking how widely used a package is and whether its publisher changed recently is done by hand when a package is added, with a script we run ourselves; it is not yet part of every build.
The API takes its settings and secrets before any outside package loads, removes them from its environment, and hands each part of the code only the values it uses. Most secrets reach it as read-only files rather than environment variables. That narrows what a compromised package could pick up, but it does not stop code running inside the API from reading those files: holding secrets in a separate process is not built.
What we have not done yet
Orbities has not been through an external penetration test or a formal certification such as SOC 2 or ISO 27001. Saying so is more useful than a badge: if you are choosing between products on this basis, you now know where we are.
Reporting a problem
Write to [email protected] with enough detail to reproduce it. We will acknowledge within two business days and tell you what we are doing.
We will not pursue anybody who reports a flaw in good faith, does not access data belonging to other people, and gives us a reasonable chance to fix it before publishing.