Legal

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 2026

Who 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

We do not sell your data, and there is no arrangement under which we could.
We have no advertising product, no data-broker relationship and no analytics partner with access to location. Our business model is subscriptions. Selling location data would require building something we have not built.
Orbities staff tools cannot read your family's location.
Staff accounts connect through a database role that has no permission on the location tables, so the query fails rather than relying on staff not looking. Direct access to the servers and backups is limited to the engineers who operate them, and is used only to keep the service running.
When somebody in your circles looks at your location, you can see that they did.
Each time a member of your circles, your own family included, opens your location on the map, on your card or in your history, that hour is recorded against their name. The record is kept for 120 days, Privacy → Who checked on me shows it to you, and only you can clear it early. Opens of a sharing link are counted, and reads by a connected integration are logged for 90 days. Sign-ins, removals and permission changes go in a separate audit log that is append-only and hash-chained.

What we collect

Only what a family safety product needs to work. Each item below exists because a feature would not function without it.

Account
Email address or username, display name, optional phone number, optional date of birth, time zone and language.
Date of birth is used for an age band, which changes what a minor can be asked to share. The full date is not shown to other members. In a family circle, the Board calendar shows the day and month as your birthday, never the year.
Profile photo (optional)
If you choose one, it is resized on your phone and stored so your circle can see it: on our servers, or in Cloudflare R2 storage (see “Who else touches it”). You can remove it at any time.
Location
Position, accuracy, altitude, speed and heading, whether you appear to be moving, and battery level, recorded in the foreground and in the background while sharing is on.
Accuracy and confidence are stored with every position because a location without them is a claim without evidence. From these positions the service also builds your trips, stops, daily summaries and place arrivals.
Places
Places your circle saves, such as Home or School, with their names and addresses.
Device health
Which permissions are granted, battery level and charging state, whether power saving or airplane mode is on, location accuracy, network type, the phone's manufacturer and its background-app setting, which app version and update is running, and the error message from the last time the app crashed.
This is what lets Orbities say why a phone stopped reporting instead of showing a stale dot. From the app updates after 4 November 2026 it also includes how the app last ended, as the phone's own system reports it: a reason code (such as low memory, force stopped or crashed), when, how much memory it used, and for an iPhone crash a short technical code and up to five positions inside the Orbities app itself. None of it holds anything you typed, saw or did in the app. Our staff see it only as counts across all phones.
Devices and sessions
Platform, model, OS version, app version, an installation identifier and a notification token.
So Sessions & devices can say “Pixel 9” rather than “a device”, so notifications reach the right phone, and so you can end a session you do not recognise.
Messages you send in Orbities
The text, and a position only if you choose to attach one. Messages are deleted 30 days after they are sent. A note pinned to the circle board is deleted when the expiry its author set passes; one with no expiry stays until its author removes it.
Photos in chat (optional)
Photos you choose to send in a chat, taken with your phone's camera, picked from its photo library, or chosen on your computer. Before a photo is stored, the details saved inside the picture, such as where and when it was taken, are removed. It is stored in Cloudflare R2, Cloudflare's storage service, which may hold it outside Australia (see “Who else touches it”), and only people who can see that message can open it. Children can send photos too: there is no age limit on photos in a family circle's chat or in the group chat of a Friends & work circle.
A photo is deleted with its message, 30 days after it was sent. The stored picture is removed by a clean-up that runs once a day, so it can take up to a day longer. Unsending a message deletes its photos straight away. A photo you chose but did not send is removed by that clean-up once it is an hour old. If a message is reported, a copy of its photos is kept for our staff to review until the same 30-day mark.
Safety features
SOS alerts, safety timers, check-ins, journeys, pickup requests and requests for help (such as roadside or travel help) that you start, with the position they relate to. Possible crashes the phone detects, and possible falls if you switch fall detection on.
Fall detection works while Orbities is open on screen. It also notices a fall with the app in the background: on Android from app version 0.8.0, and on iPhone from app version 0.9.0 while iOS keeps Orbities running. Older versions notice a fall only while Orbities is open on screen. A fall record can be read by you and, once your family has been told about it, by the people in your family circles; never by a Friends & work circle.
Sound during an SOS (off unless you switch it on)
Sound from your phone's or browser's microphone while an SOS you pressed is running. Recording starts only when you press SOS yourself, while “Record sound when I press SOS” is on for that phone or browser and the microphone has already been allowed, or when you press Record sound during the SOS. The setting is off for everyone, children included, unless it is switched on: you can switch it on for yourself, and a parent or guardian can switch it on for a child on the child's own phone or sign-in. An SOS never stops to ask for the microphone. It is never recorded for a crash, a fall, a safety timer, a missed arrival or a discreet SOS, and nobody else can start it. It shows on your screen the whole time with a Stop button, and stops when the SOS ends or after 15 minutes.
While the SOS is running, the people it was sent to can listen, about 5 to 10 seconds behind. Once it has ended, only you can play, download or delete it. Orbities staff cannot play it, and it is used for nothing else. On a phone it works from app version 0.8.0; older versions cannot record. On the website it works in a browser that allows the microphone.
Wander guard (optional)
An alert a family sets up so that they are told when somebody leaves a saved Place during the hours they chose, for example at night. It is an ordinary place alert, and uses the same arrivals and departures as any other.
Suggested Places
Orbities suggests somewhere to save as a Place when a person keeps stopping there: at least three visits on at least two different days. Suggestions are worked out from their recent stops each time the list is opened, and are not stored. They are shown only to people who can already see that person's location history, and only as far back as the plan allows.
If somebody chooses “Not a place”, that spot and its size are kept so it is not suggested again.
Cars (optional)
If your family pairs a car with a phone, the phone records when it connects to and disconnects from that car's Bluetooth, and its position when it disconnects. Only the car, the times and that position are sent: no Bluetooth address or device name. Orbities uses them to say which car a drive was in, to mark the likely driver when only one adult's phone was connected (the person can correct it), and to show where the car was left.
Android phones report car connections from app version 0.8.0. iPhones report them from app version 0.9.0, and only while iOS keeps Orbities running; older iPhone versions do not report them. The connection times are deleted after 90 days; a drive keeps its car and driver after that, and the parked spot is replaced the next time the car is parked.
Medical card (optional)
Blood type, allergies, conditions, medications and notes that you enter for use in an emergency. This is health information. We collect it only because you type it in, and you can clear it at any time. Only you and the people in a family circle with you can read it. Somebody who shares only a Friends & work circle with you cannot.
The card has a “Show on my lock screen” setting. It is saved with the card, but Orbities does not currently put the card on your phone's lock screen.
Emergency contacts
Names and phone numbers or email addresses of the people you list. Please tell them you have added them. They are deleted when you remove them or close your account.
Lost-pet reports
If a pet in your circle is lost, somebody who finds it can report a sighting from the pet's tag page without an account. A report holds where the pet was seen if the finder shares it, their note, any name and contact details they choose to give, and a one-way hash of their internet address, which is enough to stop abuse and not enough to identify them.
Invitations to a circle
When you invite somebody by email or username, we keep who invited whom, to which circle, and whether it was accepted or declined. We do not keep the email address you typed, only a hint such as jo***@example.com for your own list.
The Board and shopping lists
What your circle puts on its Board: to-do lists and tasks (with who they are for, who did them and when, and chore rotations naming who takes turns), events with their times, place or address and notes, who is going (yes, maybe or no, with an optional note), what to bring and who is bringing it, pickups (the child a pickup is for, who is taking it and, in a family circle, whether it was confirmed when they arrived), reminders, and shopping lists with their items, who added and ticked each one, and the usual items, learned from what is bought or pinned. Anyone in the circle can see the circle's Board. An event marked private is seen only by the person it is private to. How a pickup was confirmed is seen only by the child, the person taking it and the child's guardians.
A Friends & work circle has events, who is going and what to bring, but no to-do lists, shopping lists, pickups or birthdays. Board reminders are sent as notifications. How long the Board is kept is under “Kept while your family uses its circle” below.
Calendar subscribe links and calendar links (optional, adults only)
A subscribe link lets an adult add their circle's Board events to a calendar app such as Google Calendar, Apple Calendar or Outlook. We keep only a one-way hash of the link, when it was made and when it was last used. The calendar app fetches the link and receives the Board events that person can see, from a month back to a year ahead: titles and times, and addresses only if they chose to include them; never notes or who is going. A calendar link works the other way: an adult adds the address of an outside calendar, such as a club's fixtures or a school calendar, and every six hours our server fetches it and puts its events on the Board for the circle to see. Only the adult who added it can see the whole address; the rest of the circle sees the website's name.
Anyone who has a subscribe link can read the calendar it gives, so making a new one, turning it off, leaving the circle or closing your account stops the old one working. What the calendar app has already fetched is kept by that app under its own terms. Fetching a calendar link sends the outside website nothing about your family: only the request for its calendar, from our server.
Phone calendar (optional, on your phone)
On a phone, you can add a Board event to your phone's own calendar. The copy holds the title, the time, the address and a link back to Orbities, not the note or who is going, and Orbities keeps it up to date. You can also turn on calendars from your phone so their events show on your own Board view. Orbities then reads the title, time and place of events in the calendars you turned on, and shows them on that phone only. Nothing from your phone's calendar is uploaded, unless you choose to share one event to the Board, which adds it there like any other Board event.
Which phone events were copied where is remembered on the phone, not on our server. A copy in your phone's calendar is then held wherever that calendar is kept, such as your Google or iCloud account. This needs app version 1.0.0 or later on Android, and version 1.1.0 (38) or later on iPhone and iPad; the website has no phone calendar.
Requests to see or share more
If a member cannot see somebody, they can ask to see them (“Ask to see”), and a teenager can ask to share more with a person. A request records who asked, who it is about, who would see more, in which circle, what would be shared (such as live location or history), and whether it was approved, declined, withdrawn or lapsed, by whom and when. It is seen by the person who asked, the person it is about and, for someone under 18, their guardians, who decide it. An adult decides for themselves.
A request nobody answers lapses after 7 days. How long requests are kept is under “Until either person closes their account” below.
Driving
Trip start and end, speed, harsh events, crash detection and learner-driver logbook entries, when driving features are switched on.
Screen time (Android only, optional)
Per-app daily totals, meaning app names and minutes, never the content, when the phone's holder turns on Usage Access. A parent or guardian in the circle can see these totals only for members under 16. Adults' totals are visible only to themselves.
On iPhone, Orbities receives no usage information at all. It cannot set app schedules or daily limits there; it can only pause apps chosen on that iPhone through Apple's Screen Time controls, and that has not yet been confirmed on a real iPhone.
Contact matching (optional, on your phone)
If you turn on contact photos, Orbities reads your phone's contacts on the phone to find the people in your circle and show the photo you already have for them. Contacts are not uploaded. To make the match, the server sends each circle member's phone number to your phone as a shortened one-way hash, never as the number itself.
Turning the setting off deletes the matched photos from the phone.
Security records
Sign-in attempts, with the IP address stored as a one-way hash rather than the address itself.
Audit log
A record of who changed what: sign-ins, people joining, leaving or being removed, permission and sharing changes, and changes to circles, places, pets and rules. Each entry holds who did it, who and what it was about by their identifiers, what kind of change it was, the time, the browser or app's user agent, and a one-way hash of the IP address. An entry does not store words you or your family typed, such as the name of a circle, place, pet, rule or parental rule, or a note on a guardian link: only that something was named, and how many characters it had. When our staff change something on an account, the entry keeps the reason they gave, and an entry for a licence, a gift or a staff invitation keeps the email address it was sent to.
Entries written before 3 November 2026 used to hold what was typed at the time. Those words have since been removed from them in the same way, leaving only their length. The log is append-only and each entry is chained to the one before by a hash, so that any change or removal would show; before the words were removed, the chain as it stood was recorded, and the cleaned entries were chained again from there, so the whole log can still be checked. Copies of those words remain only in our encrypted backups taken before then, until those backups expire. See “Not deleted on a schedule, even after you close your account” below.
Server logs
Our servers keep technical logs of requests, including IP addresses and the address searches you make, to operate and secure the service.
Every few minutes the logs are copied into one file per day on the server, readable only by its administrators, and each day's file is deleted after 14 days. Once a day is over, its file is also compressed, encrypted on our server with a key that is not kept on the server, and copied to Cloudflare R2, so that the logs survive if the server is lost; a rule in the storage itself deletes each copy 15 days after it was made. The running service also holds its own log from the moment it was last started or updated until it is next restarted or updated.

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.

400 days: raw positions
Every recorded position, with its accuracy and speed. After 400 days a scheduled database job deletes it.
400 days: trips, stops and coverage gaps
The trips, stops and gaps in coverage worked out from your positions. A scheduled job deletes each one 400 days after it ended, like the positions it came from.
400 days: hourly reporting summaries
Per hour, how many positions your phone sent, how accurate they were, battery levels and top speed. No positions. A scheduled database job deletes each hour 400 days on, like the positions it summarises.
400 days: where things happened
The position kept with an arrival, departure or other activity in your circle, with a check-in, and where a journey was going and the route it took. A scheduled job clears each one 400 days after it happened, like the raw positions. The activity, check-in or journey itself stays, without the position.
400 days: emails to emergency contacts
SOS and safety-timer emails sent to your emergency contacts, which hold the contact's address and a position. A scheduled job deletes each one 400 days after it was sent. One still waiting to be sent is never deleted.
Seven years: learner-driver logbook entries
A scheduled job deletes each entry seven years (2,555 days) after the drive started. A logbook may be produced to a licensing authority long after the licence was granted.
Closing your account erases the entries for your own drives, with the rest of your driving history, so make a copy first (History → Export includes your logbook) if you may need it. Entries for drives you supervised stay in the learner's logbook, shown as from “Deleted account”. Write to us if you want your entries deleted earlier.
Two years: your answers to “Was this alert right?”
Deleted by a scheduled job 730 days after you gave them.
One year: scans of a lost-item tag
When somebody scans a lost item's tag, the approximate suburb and a message they leave. Deleted by a scheduled job a year after the scan.
Item tags cannot be added to Orbities yet, so no scans are recorded today.
180 days after your last visit: places you have been before
Places you have stopped at, used to notice when a routine changes. Each one is deleted by a scheduled job 180 days after your last visit there.
180 days: account-recovery attempts
Requests to get back into an account, and the answers to them. Deleted by a scheduled job 180 days after the request, except one still waiting for an answer.
120 days: who viewed a location
Hour-level records of who viewed a location, deleted by a scheduled job. You can clear the record about you sooner in Who checked on me; the people who looked cannot.
The detailed view caps at 90 days, and weekly summaries are kept, so older hour buckets answer no question the product asks.
90 days: device health reports and integration logs
Battery, permission and connection reports from your phone, the record of when its health changed, its daily health scores and battery summaries, daily screen-time totals, and the log of what connected integrations read, each deleted by a scheduled job 90 days after the time or day it describes.
A diagnostic report sent from your phone is deleted when its 30 days are up.
90 days: notifications
The notifications we sent you, and when. A scheduled job deletes each one 90 days after it was sent. One still waiting to be delivered is never deleted.
Older alerts still appear in alert history under a general title such as “Arrived”, without the wording of the notification.
90 days: sound recorded during an SOS
A scheduled job deletes each recording 90 days after it started. You are told a week before, and can download it or keep it as evidence first. You can delete one yourself at any time.
A recording you keep as evidence is kept a year at a time. Each year you are told a month and again a week before, and it is deleted then unless you choose to keep it for another year. Closing your account deletes your recordings.
90 days: per-app screen-time totals
App names and daily minutes from an Android phone with Usage Access turned on. Deleted by a scheduled job 90 days after the day they describe.
90 days: car Bluetooth connections
When a phone was connected to a family car. Deleted by a scheduled job 90 days after it disconnected.
90 days after it stops working: sharing links
A link that shared your location outside the circle is kept for 90 days after it expired or was turned off, so you can still see who you sent it to, then deleted by a scheduled job. A link that still works is never deleted.
90 days after a circle is left empty: what its members shared there
When the last member of a circle leaves or closes their account, the circle is archived. 90 days later a scheduled job deletes what was shared in it: its places and their addresses, the Board and shopping lists, messages and photos, the emergency plan, pets, cars and their parked positions, rules, invitations and links, and the circle's name.
Billing records are kept for as long as tax law requires, and the audit log is kept as described above. What is about one person, such as an SOS they raised or their own trips, goes when that person closes their own account.
30 days: who was together
When two members' phones were together, and for how long. Deleted by a scheduled job 30 days after they parted.
30 days: hard braking the phone noticed
Hard braking and rapid acceleration that a phone's motion sensors found during a drive, with the speed before and after and where it happened, and when the phone was watching. Deleted by a scheduled job 30 days after it happened.
Before then it is added to the drive it happened in, and the drive keeps it as one of its events.
24 hours, and 30 days: sign-ups that are never confirmed
When a sign-up has to be confirmed from its email first, what you typed (your name, email address, date of birth and a scrambled form of your password) is kept for 24 hours waiting for the link, emptied as soon as the link is used, and deleted within a day after either. An account whose email address was never confirmed, with no circle shared with anybody, no messages and no positions, is closed 30 days after it was made, in the same way as closing it yourself: signing in within the next 30 days cancels that.
If somebody else confirms the same email address from a new sign-up, the address moves to their account and the unconfirmed account is closed in the same way.
30 days after it ends: a signed-in session
Session records are deleted 30 days after the session expires.
30 days: messages
Messages, sent and received, are deleted by a scheduled job 30 days after they are sent. A note pinned to the circle board is deleted once the expiry its author set has passed; one with no expiry stays until its author removes it.
Closing your account does not remove messages you sent to other members before then; see “Delete your account” below.
30 days: photos in chat
A photo goes with its message, 30 days after it was sent, and the stored picture is removed from Cloudflare R2 by a clean-up that runs once a day, so within a day after that.
Unsent photos go straight away. Closing your account deletes the photos you sent.
Until you delete them or close your account
Daily summaries built from your positions; drives, with the car and whether you were driving where that is known; journeys, pickups and check-ins; SOS, crash and fall records; safety timers; requests for help; spots marked “Not a place” in Suggested Places; your medical card and emergency contacts.
None of these has a scheduled deletion, except that the position on a check-in, and where a journey was going and its route, are cleared after 400 days (above). Delete history, in the app or on the website, deletes any date range of your positions, trips, stops, daily summaries and drives without closing your account. Closing your account erases all of them.
Until either person closes their account: requests to see or share more, and calendar subscribe links
“Ask to see” requests and a teenager's requests to share more, with their answers, are kept until the account of the person who asked, the person it is about, or the person who would have seen more is closed and erased. A calendar subscribe link that was turned off or replaced is kept, as a hash that no longer works, until its owner closes their account.
None of these has a scheduled deletion.
Kept while your family uses its circle: the Board, shopping lists and calendar links
Board lists, tasks, events, pickups, what to bring and who is going, shopping lists and their items, and the circle's calendar links have no scheduled deletion. Removing a list, task, event, item or shopping list takes it off the Board and the screens, but keeps it in our records. Changing or withdrawing your answer to an event, removing a usual item from a shopping list, or removing a calendar link, together with the events it brought in, deletes it.
When you close your account, your answers to events, the reminders sent to you, events private to you and your calendar subscribe links are erased. You are taken out of chore rotations, and a pickup for you stays on the Board without your name. Lists, tasks, events and items you added stay with your circle, shown as from “Deleted account”. A circle nobody is left in is archived, which hides it from everyone; for now its places, Board, shopping lists, plans and the rest of its contents are kept. Write to us to have any of these deleted.
Not deleted on a schedule, even after you close your account
Your circle's activity: arrivals, departures, alerts and the other things the circle was told. The position at the time is kept with each for 400 days, then cleared. Lost-pet reports and their sightings. Invitations to a circle and their answers. The audit log.
Activity is a record for the other people in the circle as well as for you. Delete history does not remove arrivals and departures your family was already told about. Closing your account removes the positions from activity about you, and leaves the rest linked only to the anonymised account. Lost-pet reports are kept even if the pet is removed from Orbities. The audit log cannot be edited, so its entries stay, linked to the anonymised account. Write to us to have any of these deleted, except the audit log.
Up to 40 days: backups
Since 2 November 2026, copies of the databases leave our server only encrypted, with a key that is not kept on the server, and are stored in Cloudflare R2. An encrypted copy is made every night and kept for 35 days; a rule in the storage itself deletes anything older than 40 days, and a lock stops anyone, us included, deleting a nightly copy in its first 35 days. Once a week the newest encrypted nightly copy is also kept with Backblaze B2 in the United States, under the same 35 and 40 days, so a problem at one provider cannot take every copy. An encrypted copy of account data is also made every hour, and one of location history every 6 hours, and each is kept for 72 hours. Unencrypted copies of the nightly backup are kept only on our server, for 14 days.
Before 2 November 2026 an unencrypted nightly copy was also stored in Cloudflare R2; a few of those are still there until we delete them. Copies we take on the server just before updating the service are deleted after 14 days, except the three most recent, which are kept whatever their age. Deleting data does not reach into a backup, so deleted data stays in a backup until that backup is deleted. So that a restore cannot bring a closed account back, we keep with the encrypted backups an encrypted list of the accounts that have been closed or erased, holding only their identifiers and dates, with no names or contact details. After any restore from a backup, every account on that list is erased again before the service is back.

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.

Inactivity alerts
If someone has turned on an inactivity watch and their phone stays in one place for longer than the hours they chose, outside the night hours they set, while the phone is still reporting, Orbities tells the circle members allowed to see their alerts. If they chose to be asked first, they get a check-in prompt and the circle is told only if they do not answer in the minutes they set. It uses their location history, when their phone last reported, and their check-ins.
Possible-crash alerts
If the phone detects what looks like a vehicle crash, Orbities asks whether they are OK. If nobody answers within 45 seconds, it raises an SOS marked as a possible crash, and the circle is told with their location. It uses the phone's motion sensors, its location, and whether they answered. Saying “I'm fine”, even late, stands the alert down.
Possible-fall alerts
Only if someone has switched on fall detection for themselves. If their phone's motion sensors see a drop, a hard landing and then stillness, Orbities asks them “Did you fall?” with an alarm. If they do not answer within 30 seconds, or they ask for help, it raises an SOS marked as a possible fall, and their family is told with their location. Saying “I'm OK” in time means nobody else is told. It uses the phone's motion sensors, its location, and whether they answered. The stream of motion readings stays on the phone; only the result is sent, with a few figures that describe it, such as how hard the impact was and how long the drop lasted, so that a false alarm can be understood.
Age bands
A child's date of birth, entered by a parent, places them in an age band (under 10, 10–12, 13–15, 16–17). The band decides which features can be turned on for them, as described under Children below. A child under 16 is always recorded as a passenger on a drive, never as the driver. No date of birth means no age band applies.
Arrivals and departures at saved places
When a phone's location shows it entering or leaving a saved Place, such as “School”, Orbities records an arrival or departure, and sends the place alerts and rules the circle set up. It uses the location, how accurate the reading was, and the Place's boundary. A reading too uncertain to trust is held back rather than sent, and every time a rule is checked, whether it fired or not, the reason is recorded.

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.

Cloudflare (network, backups, photos, exports and SOS recordings), United States
Every connection between the app or website and our servers passes through Cloudflare's network, which protects the service and routes traffic to Brisbane. Cloudflare processes that traffic, including location updates, while delivering it. Cloudflare R2, Cloudflare's storage service, also stores our database backups and encrypted copies of our server logs; photos sent in chat; profile photos and pet photos; copies of reported chat photos kept for our staff to review; the archives that History → Export builds; and sound recorded during an SOS you pressed, in a private store of its own that only our server can reach, with no public address and no caching. Our server encrypts every part of a recording before it leaves, with a key made for that recording, so Cloudflare holds only data it cannot play. Cloudflare, Inc. is based in the United States and runs its network worldwide, and R2 may hold what it stores outside Australia. When you sign up on the website, Cloudflare Turnstile may check that a person, not a program, is filling in the form; it looks at your browser and connection, sets no advertising cookie, and tells us only whether the check passed.
Since 2 November 2026 every database backup is encrypted on our server before it leaves, with a key that is not kept on the server (see “Up to 40 days: backups” above). Photos and export archives are kept in a private store that only our server can reach; they are not encrypted by us, and rely on the encryption Cloudflare applies to everything stored in R2. An export archive holds what you asked for, which can include your medical card, and is deleted by a daily clean-up once it is 7 days old. The store for SOS recordings is set to keep them in Cloudflare's Oceania region, which Cloudflare treats as a preference, not a promise. Deleting a recording destroys its key first, so it can no longer be played even before the stored parts are removed, which takes up to a day.
Backblaze (a weekly backup copy), United States
Once a week the newest nightly copy of our databases, already encrypted on our server with a key that is not kept on the server, is also kept with Backblaze B2, Backblaze's storage service, in a private store in the United States, so a problem at one provider cannot take every copy. Backblaze can read none of it. Backblaze, Inc. is based in the United States.
A lock in the store stops anyone, us included, deleting a copy in its first 35 days, and a rule in the store deletes it by day 40. Until 5 November 2026 Backblaze also stored sound recorded during an SOS; those recordings have moved to Cloudflare (above).
Expo (app updates and notifications), United States
Orbities is built with Expo. When the app opens it checks Expo's servers for updates, which gives Expo your device's IP address and app version. Notifications are sent through Expo's push service to Apple or Google, who deliver them to your phone. Urgent safety alerts (an SOS, a crash or fall check, Find My Phone) are also sent straight to Apple or Google, so they still arrive if Expo's service is down; you get one notification, not two. Expo (650 Industries, Inc.), Apple Inc. and Google LLC are all based in the United States.
A notification contains what you see on screen: a person's name and, for place alerts, the name of a saved Place such as “School”. It never contains coordinates.
Browser notifications, United States
If you turn on notifications in a web browser, they are delivered through that browser's own push service: Google for Chrome, Apple for Safari, Mozilla for Firefox, Microsoft for Edge. Each of these companies is based in the United States.
What a browser notification contains is the same as on a phone, and it never contains coordinates.
Error reports (180 Degrees IT Feedback Loop), United States
When something breaks on our server, a report of the error goes to 180 Degrees IT, the business that builds Orbities. The report passes through a Cloudflare service and is stored as an issue on GitHub (GitHub, Inc.), both based in the United States.
A report contains the error message with email addresses, phone numbers, dates, coordinates and sign-in tokens removed, the page or route it happened on, and a scrambled code in place of your account. It never contains your location, your messages or your health details.
Email (SMTP2GO), New Zealand
Email from Orbities is sent through SMTP2GO, which is run by Sand Dune Mail Ltd in New Zealand. That is the email confirming your address, invitations to a circle, password reset links and notices that your password was changed, notices that your account was recovered, the email asking an emergency contact whether they agree to be one and, for emergency contacts who agreed, SOS and safety-timer alerts. SMTP2GO receives the address and the whole email, which for an alert includes the person's name and their last position. Its privacy policy does not say in which countries it stores email for customers outside Europe.
Orbities has SMTP2GO's open and click tracking switched off, so it does not record whether an email was opened or which link was clicked, and links in our emails go straight to us.
The map (Google), United States
Maps in the app and on the website are drawn by Google. Your device requests map images directly from Google, so Google receives your device's IP address and the area of the map being shown, under its own privacy policy. Google LLC is based in the United States. Family markers are drawn by your device and are not sent to Google as map requests.
Buttons such as Directions open Google Maps with the position you chose, and an SOS or safety-timer email to an emergency contact holds a Google Maps link to the last position; opening one sends that position to Google. Orbities stopped serving its own map tiles on 22 September 2026. We made the trade for one reason: our own aerial imagery could only resolve a building across NSW and the ACT.
Address search (Google), United States
Address and business searches use Google Places and Geocoding. When you view an unnamed live location, trip endpoint or history stop, Orbities may send that coordinate to Google to look up its address or a public venue. Saved family Place names take priority; we do not send every tracking update for an address lookup.
Lookups go through our server with the search text or coordinate, without your Orbities account identity or device IP address. Google processes this information under its own terms and privacy policy. If Google is unavailable or a usage limit is reached, the location pin and saved family Places remain available; we do not substitute another map-data provider. Venue response content is not stored in a shared database. Permitted place IDs and account-isolated address records may be retained with expiry.
Journey routes (Google), United States, Premium only
When someone on a Premium plan starts a journey, or looks at its time before starting, Orbities sends Google Routes the starting point (their phone's last position), the destination point and how they are travelling, and gets back the route by road and how long it takes with traffic. The route is kept with the journey, so Orbities can ask if they leave it, and is deleted with it.
Sent from our server with the two points and the travel mode only: no name, account identity or device IP address. Google processes this under its own terms and privacy policy. If Google cannot answer, or a usage limit is reached, the journey uses Orbities's own estimate instead. Families not on Premium are never sent to Google for this.
Integrations you connect
If a circle admin connects another service, such as a home-automation system, through Orbities' API or webhooks, that service receives only what each member has individually agreed to share with it, by default “at a Place” rather than coordinates.
Every read through the API is logged, kept for 90 days, and shown to you.
Calendars you choose
If an adult makes a calendar subscribe link, the calendar app they add it to, such as Google Calendar, Apple Calendar or Outlook, fetches the Board events that person can see: titles and times, and addresses only if they chose to include them. If an adult adds a calendar link, our server fetches that outside calendar and sends it nothing about your family. Who runs these, and where, depends on the calendar chosen (see “Calendar subscribe links and calendar links” above).
The phone calendar is different: a Board event you add to it goes from the app straight into your phone's calendar, not through our server.

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.

See what we hold
A plain-language summary of every category of data held about you.
Take it with you
History → Export, in the app or on the website, makes a copy of everything we hold about you as JSON and CSV files, from your account, circles, places, location history, trips and messages to your safety records, Board, requests, consents and phone health. You can also ask for just one part of it. Left out on purpose: other people's positions and their messages to the whole circle; your password, two-factor secret, sessions and notification tokens; and the SOS described below. Photos and SOS recordings are listed in it rather than copied in: a photo opens from its message, and each recording has its own download. If you cannot use it, email [email protected] and we will send the same within 30 days.
An export never includes a silent SOS, or one raised with the duress password, or any sound recorded during one. Whoever is holding the phone can ask for an export, and that person may be the reason help was asked for, so these are left out for your safety. Every other SOS is included.
See who looked
Who checked on me lists each hour in which somebody in your circles looked at your location, and who, including your own family. You can clear it; they cannot.
Correct it
Change anything wrong in your account or your places.
Delete history
Delete any date range of your location history — positions, trips, stops, daily summaries and drives — without closing your account. Your circle is told that some history was deleted, never what it held.

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.