Privacy policy
Orbities knows where your family is. That is an unusual amount of trust, so this page is specific: what we collect, how long each thing is kept, and who can see it — including where we have not finished the job yet.
Last updated 5 November 2026Who we are
Orbities is operated by 180 Degrees IT Solutions Pty Ltd, in Queensland, Australia. We are bound by the Privacy Act 1988 (Cth) and the Australian Privacy Principles.
Your data is stored on servers in Brisbane, Queensland. Some service providers that help run Orbities are located overseas or run global networks. They are listed under “Who else touches it”, with what each one receives.
The short version
What we collect
Only what a family safety product needs to work. Each item below exists because a feature would not function without it.
What we do not collect: call content, your contacts, browsing content, or video from the camera. The microphone is used only to record sound during an SOS you press, and only if you choose it (see “Sound during an SOS” above). The camera is used for two things: to read a set-up or invitation QR code, where the image stays on your phone and only the code is used, and to take a photo you choose to send in a chat (see “Photos in chat” above), which leaves your phone only when you send it.
How long we keep it
Most kinds of data are deleted automatically by scheduled jobs, after the period shown below. Some are kept until you delete them or close your account, and a few are kept even after that; rather than quote a window nothing enforces, we say which is which. Signed-in members can see the windows we have set under Privacy → What we keep; where that screen and this page differ, this page describes what happens now.
Your plan limits how far back location history can be looked at: the last 2 days on Free, 30 days on Plus and 365 days on Premium. That is a limit on viewing, not a deletion. Older history is hidden, kept for the periods below, and shown again if you move to a plan that covers it.
Who can see it
Within your circle, what each person can see is set per viewer and per subject — not per circle. A grandparent can be given a suburb where a parent sees an exact address, and the person being viewed can see that setting from their own side.
A minor's privacy screen is theirs. A parent cannot open it, by design: a product that lets a parent read a teenager's private settings has simply moved the surveillance one level up.
A Friends & work circle, for colleagues or friends, shares three things: where you are with the trail of where you have just been, a group chat, and a shared calendar of events with who is going and what to bring. Nothing else reaches the people in it: no SOS, places, alerts, battery, medical card, safety tools, to-do lists, shopping lists, pickups or birthdays. Private messages there are allowed only between two adults whose birth dates are known, a parent and their own child, or people who share a family circle; a child's messages with anyone else stay in the group chat. Anybody can leave one at any time. A child whose parent is on Orbities cannot join one on their own say: accepting the invitation asks a parent, the child is added only if the parent says yes, and nothing is shared with that circle until then. A teenager who created their own account before 2 November 2026, without a parent, answers for themselves.
Location sharing outside the circle is always time-limited. A link to a babysitter or a friend's parent carries an expiry that cannot be removed, because temporary sharing that never expires is permanent tracking wearing a temporary name.
What people type, such as messages, Board titles and notes, addresses, poll questions and report notes, is kept on our server in Brisbane behind access controls. It is not yet encrypted at rest: the server's disks are not encrypted, and sealing these fields one by one is planned work that is not finished. Since 2 November 2026, database backups leave the server only encrypted.
Decisions made automatically
Some things Orbities decides by itself, without a person looking first. Each one is listed here with what it uses. None of them is used to profile you, for advertising, or to decide anything about you outside your circle.
You can ask for a person to review any of these decisions, or why one was or was not made, by writing to [email protected]. We will tell you what information it used and what it decided, and correct anything that was wrong.
Who else touches it
These services receive the information described below to provide the requested feature. Our servers are in Brisbane, but every company-run service in this list is based outside Australia, and the country is named against each one. Some of them may store or process what they receive in other countries too. Integrations and calendars you choose to connect are run by whoever you chose.
Google Privacy Policy · Google Maps terms
Data we use from others. Speed alerts and the driving summary after each drive need the posted limit of the road. Speed limits come from OpenStreetMap: our server keeps its own copy of Australia's roads, downloaded from an OpenStreetMap extract and refreshed about once a month, and looks the limit up in that copy. No position leaves our server for a speed limit. Road data © OpenStreetMap contributors, available under the Open Database Licence (ODbL).
Paid plans are not yet on sale. When they are, this section will name the payment provider before any payment is taken.
What you can do
All of these work in the app and on the website without contacting us.
Delete your account
In the app: You → Delete my account. On the website: sign in, then Account → Delete my account. Both ask for your password (or an authenticator code) before anything happens. The steps, with or without the app, are also at orbities.com.au/delete-account.
Deleting stops all sharing, in both directions, and signs you out everywhere straight away. Your account is then held for 30 days in case you change your mind. Signing in during that time cancels the deletion; sharing you had stays off until you choose to share again.
When the 30 days are up, your name, email address, phone number, username, date of birth, profile photo and password are removed and you leave every circle. Within a few hours after that, we erase your positions, trips, stops, device reports, messages sent to you, medical card, emergency contacts, screen time, safety records, SOS recordings and the other records listed under “Until you delete them or close your account” above.
Some records are kept, and we say so plainly:
- The audit log is append-only and hash-chained, so it cannot be edited. Its entries stay. They name the anonymised “Deleted account” placeholder rather than you, and keep the user agent and IP hash they were written with. They hold no words you typed, such as the name of a circle, place, pet or rule (see “Audit log” above). The positions in shared events are removed.
- Board lists, tasks, events and shopping items you added stay with your circle, shown as from “Deleted account”. Your answers to events, events private to you and your calendar subscribe links are erased, and you are taken out of chore rotations.
- Messages you sent to other members stay in their conversation, shown as from “Deleted account”, until they are deleted 30 days after they were sent (a board note, when its expiry passes; one you left up with no expiry, 30 days after your account is erased). Any position you attached is removed from them.
- Your memberships of circles stay as part of each circle's history, without the nickname the circle gave you or any note on your membership, and you are taken off other people's lists, such as their favourites and who a rule or a journey watches. Where you were the only person on a list whose emptying would widen it to everyone, the anonymised placeholder stays on it, which reaches nobody.
- An anonymised placeholder for the account is kept so shared history still makes sense. It is named “Deleted account” and holds no email address, phone number, username, date of birth, profile photo or password.
- Logbook entries for drives you supervised, in the learner's logbook, until their seven years are up (your own entries as a learner are erased), and the records listed under “Not deleted on a schedule, even after you close your account” above. Records of who was together, lost-item tag scans and sharing links are deleted on their usual schedule.
- Billing records, for the period Australian tax law requires.
- Our database backups. Erasure does not reach them, so erased data remains in a backup until that backup is deleted, which is within 40 days for the nightly copies (see “Up to 40 days: backups” above). If we ever restore from a backup, your account is erased again before the service is back, from an encrypted list of closed accounts that holds only identifiers and dates.
If you cannot sign in, email [email protected] from the address on the account.
Children
Orbities is built to be used by families including children, and a child's account is set up by a parent. Age changes what the product asks for: a minor is not offered features that would collect more than their age band allows, and the amount of autonomy grows as they get older rather than switching on at a birthday.
A parent or guardian sets up a child's place in the circle, and agrees to this policy on the child's behalf. Orbities uses the date of birth to place the child in an age band (under 10, 10–12, 13–15, 16–17). The band decides what can be asked of them. For example, a guardian can see per-app screen time only for members under 16. An account without a date of birth is asked for one at its next sign-in.
We collect the same kinds of information from a child as from an adult, as described above, and we do not use a child's information for advertising or share it with anyone for marketing. A child set up with a device code has no password of their own: a parent or circle administrator can remove them, which stops all sharing, and a parent can ask us to erase the child's data by writing to [email protected] from the parent's account email.
You must be 18 or older to create an Orbities account yourself, and everyone signing up gives a date of birth. Anyone under 18 is added by a parent or guardian instead. This applies from 2 November 2026 and does not affect existing accounts: a person aged 15 to 17 who created their own account before then keeps it. For anyone under 18, location is shared by default with their guardians only: live location, places, battery, phone health, SOS, and location history from the day it is switched on, at most 30 days back. A guardian is a parent the family has confirmed, never simply the person who runs a circle or sent an invitation. Every other adult in their circles, however the young person joined, is told only when they raise an SOS, unless a guardian shares more with a named person, and the young person is told when that happens. On their 18th birthday guardian links end, guardian-only sharing such as history stops, and both sides are told.
Members aged 15 to 17 can share a rough area (about 1, 5 or 20 km) instead of an exact position for up to 6 hours. Everyone, guardians included, sees only that area, and that period stays rough in their history afterwards. Guardians are told when it starts and ends and can end it early. An SOS, a crash or a fall shows the exact position at once to the people the SOS goes to.
A child can always see what is being shared about them and who is looking, and is told whenever someone new can see where they are. A tracker a child cannot inspect is something else. This follows the approach of Australia's draft Children's Online Privacy Code: private by default to people outside the family, and children told who is tracking their location.
If something goes wrong
If there is a data breach likely to cause serious harm, we will notify affected people and the Office of the Australian Information Commissioner as required by the Notifiable Data Breaches scheme.
To raise a privacy concern, write to [email protected]. If we have not resolved it to your satisfaction, you can complain to the Office of the Australian Information Commissioner at https://www.oaic.gov.au/privacy/privacy-complaints.
Changes to this policy
If we change what we collect or how long we keep it, we update this page and the date at the top, and we tell you before the change takes effect with a service notice: a banner at the top of every page of the website once you are signed in, and above the tabs in the phone app (in versions of the app from November 2026). Each change is also listed below with its date. A policy that changes quietly is not a policy.
5 November 2026: where things happened is now cleared after 400 days: the position on an arrival, departure or other activity, on a check-in, and where a journey was going and the route it took. The activity, check-in or journey itself stays. Emails to emergency contacts, which hold a position, are now deleted 400 days after they were sent. Phone health records (when a phone's health changed, daily health scores, daily battery summaries and daily screen-time totals) are now deleted after 90 days, and diagnostic reports when their 30 days are up, as this page already said of device health reports.
5 November 2026: server logs are no longer kept only on our server. Each finished day's logs are now also encrypted on the server, with a key that is not kept there, and copied to Cloudflare R2, where each copy is deleted 15 days after it was made. The copy on the server is still deleted after 14 days.
5 November 2026: sound recorded during an SOS is now stored in Cloudflare R2, in a private store of its own set to keep it in Cloudflare's Oceania region, instead of with Backblaze in the United States. Recordings already made were moved there. Every recording is still encrypted by our server, with a key made for it, before it leaves, so the store holds only data it cannot play. Backblaze now keeps only the weekly encrypted backup copy. Also removed: the website's permission for Cloudflare Web Analytics, which was never switched on; the website has no analytics.
5 November 2026: changes to this policy are now announced in the app before they take effect, with a service notice on the website and in the phone app; this section said that notice was not built yet. Nothing about what we collect has changed.
5 November 2026: the nightly encrypted backups now sit in a store of their own with a lock, so nobody, us included, can delete one in its first 35 days, and once a week the newest encrypted copy is also kept with Backblaze B2 in the United States, still deleted by day 40. They remain unreadable without a key that is not on our server.
4 November 2026: what members shared in a circle is now deleted 90 days after the circle is left empty. Words typed into audit log entries before 3 November 2026 have now been removed from those entries too, leaving only their length. The audit log now says that staff reasons and the email address a licence, gift or staff invitation was sent to are kept.
3 November 2026: added the Board and shopping lists, calendar subscribe links and calendar links, the phone calendar, requests to see or share more, the audit log and hard braking noticed by the phone, each with how long it is kept; Board content has no scheduled deletion, and that is now said. Speed limits now come from our own copy of OpenStreetMap's roads, so the Overpass service is no longer sent any position, and OpenStreetMap is credited. New audit log entries no longer hold words people typed. Backups are now paired with an encrypted list of closed accounts, which are erased again after any restore. The export now covers everything held about you, apart from what it leaves out on purpose. Corrected: background fall detection, sound during an SOS on a phone, and car connections on Android and iPhone are in released versions of the app; the Board shows the day and month of a family member's birthday; a car's parked position is sent when the phone disconnects; a Friends & work circle also shares a calendar of events; and emails include password reset links and requests to emergency contacts. Corrected too: closing your account erases your own learner logbook entries (it has done since 13 October; entries for drives you supervised stay with the learner); and it also removes your circle nicknames and membership notes, takes you off other people's lists, and ends a board note you left up with no expiry 30 days later.
2 November 2026: sound during an SOS is now off unless it is switched on, for everyone, children included; anyone who had switched it on in the phone app keeps it on, and on the website it is off until switched on again. You must now be 18 or older to create an account yourself; anyone younger is added by a parent or guardian, and existing accounts are not affected. Added photos in chat, what they hold and how long they are kept, and that the camera is also used to take a photo you choose to send. Cloudflare R2 is named as storing photos and export archives as well as backups, and database backups now leave our server only encrypted. An export leaves out a silent or duress SOS, for the safety of the person who raised it.
20 October 2026: journeys on a Premium plan are timed by Google Routes, which is sent the start and end points and how they are travelling.
20 October 2026, earlier: sound during an SOS is now on unless you switch it off, for each phone and browser. It still records only an SOS you press yourself, and only once the microphone has been allowed on that phone or browser.
15 October 2026: sound during an SOS. If you choose it, sound is recorded while an SOS you pressed is running; the people it went to can listen while it runs, only you afterwards, and it is deleted after 90 days unless you keep it as evidence, which is reviewed every year. Recordings are encrypted by our server and stored with Backblaze in the United States. The microphone is used for nothing else.
14 October 2026: corrected to match what the service does. Views of your location are recorded by the hour in a separate record you can clear, not in the audit log. The medical card can be read only by you and your family circles. Screen-time totals, places visited before, account-recovery attempts, alert feedback, learner logbook entries, records of who was together and lost-item tag scans now show the periods after which a scheduled job deletes them. Added how long backups (up to 40 days) and server logs (14 days) are kept, which records are kept until you delete them and which are kept after you close your account, Friends & work circles and a parent's approval, Suggested Places, cars and the likely driver, the wander guard, fall records, lost-pet reports, invitations, and how plans limit how far back you can look. Removed the statements that a deleted account keeps your date of birth and photo (it does not) and that Orbities can apply app limits on iPhone (it can only pause chosen apps there).
14 October 2026: location sharing for under-18s. Guardians are confirmed parents; other adults see an SOS only by default; history for guardians from the day it is switched on, at most 30 days back; rough-area mode for 15 to 17 year olds; a date of birth at every sign-up; and a notice to a young person whenever someone new can see where they are.
9 October 2026: Orbities now sends email, through SMTP2GO (New Zealand), which is named under who else touches your information, with what it receives.
6 October 2026: every service outside Australia that receives information now has its country named. Added browser notifications, the speed-limit lookup through OpenStreetMap (Germany), error reports to 180 Degrees IT (United States), and a note that email to outside contacts is not sent yet.
27 September 2026: messages are now deleted by a scheduled job 30 days after they are sent (they were hidden, not deleted), and trips, stops and coverage gaps 400 days after they ended, like the positions they are built from. Notifications are now deleted 90 days after they are sent. The hourly and daily reporting summaries are now deleted after 400 and 90 days, like the positions and health reports they summarise. The hourly ones also go when you delete that part of your history, and both go when you close your account.
24 September 2026: rewritten to describe what the service does today. Added how long positions are kept and which data has no automatic deletion yet; profile photos, messages, the medical card, emergency contacts, phone numbers and contact matching; Cloudflare, Expo and integrations as services that receive data; server logs; how account deletion works and what it keeps; and age bands for children. Removed browsing and call records, which the app does not collect, and the claim that exports need no email.