Baby tracker privacy in Australia: where the data goes, and what to ask

What does a baby tracker actually collect?

More than the feeds. A tracker holds an account (usually an email address), a profile for each baby including a date of birth, every activity logged against that baby, any photos attached to memories, the push-notification token of every device, and technical diagnostics when something goes wrong. Taken together that is a detailed record of a named child’s first year, tied to an adult’s identity.

BubSync collects those categories and says so in its privacy policy, section by section. Two details are worth knowing because they are unusual. Every photo is re-encoded on your phone before it is stored or shared, which strips camera details and GPS location from the file. And the app does not collect precise location at all: no entry carries a place, and nothing asks for one.

Where is the data physically stored?

BubSync’s primary account, family and activity data is hosted and processed in AWS ap-southeast-2, which is Sydney. That is where the database lives, where photos for Premium families are held encrypted, and where the AI features run by default.

It would be dishonest to stop there, so the policy does not. Delivering the website and app involves global content-delivery and routing services, so connection metadata such as an IP address, a timestamp and a browser identifier can be processed outside Australia. And when you ask the AI hub for a schedule or a summary, the structured summary of recent feeds, sleep and nappies it sends as context runs primarily from Australia but may be routed through another region when a model is unavailable locally. The stored record, the database that holds your baby’s day, stays in Sydney; the exception is that summary, for the moment it takes to answer you.

What does the Privacy Act 1988 ask of an app like this?

The Act sets out thirteen Australian Privacy Principles. The ones a parent should care about are easy to name: an entity must be open about what it does with personal information, collect only what it reasonably needs, tell you at the point of collection, use the information only for the purpose it was collected, take reasonable steps to secure it, give you access to it and correct it on request, and be accountable for anything it sends overseas. Since 2018, the Notifiable Data Breaches scheme has also required a breach likely to cause serious harm to be reported to the affected people and to the Office of the Australian Information Commissioner.

BubSync’s privacy policy commits to those principles and to the breach-notification scheme in its own words, and it is written to be read rather than clicked past. What the Act does not do is tell you where a company’s servers are, whether it sells data, or how long deletion takes. Those are the questions a policy has to answer for itself, which is why the four below are worth asking of every app.

Who can see what, once you start sharing?

Sharing is where most privacy questions about a baby tracker actually live, because the risk is rarely a stranger and usually a relative. BubSync answers it with roles. An invite asks who the person is: a parent, family, a carer, or a mix you define, and which babies they should see. A carer sees and logs activities for those babies only. Family can be given the memories and nothing else. Any single entry can carry its own answer to who can see it, and a memory can be set to Only me.

Removing someone is as plain as inviting them: a carer who loses access is told what they can no longer see, and everyone logs from their own account, so removing one person never means changing a password everyone else shares. The one deliberate exception is the 24-hour handover link. It opens for anyone who has it, for 24 hours, so it should be sent only to someone you would show that page to in person.

What never happens to your data?

It is not sold, and it is not used for targeted advertising; the policy says both in plain words. It is not used to train AI models: the AI hub sends structured summaries of recent activity as context to produce an answer for you, and under BubSync’s current arrangements those prompts and outputs are not used to train the underlying models. BubSync also takes no money from formula, pharmaceutical or employer-benefits companies, which matters in a category where the free app is sometimes paid for by someone who would like to sell you something.

Deletion is spelled out too. Deleting your account requires a one-time code sent to your email on top of the confirmation, so a stray tap cannot erase a family. Active data is removed within 30 days of the request being processed, and encrypted disaster-recovery backups expire within 35 days.

What should you ask any baby tracker before you trust it?

Four questions, all answerable from a privacy policy in about ten minutes. If a policy cannot answer one of them, that is the answer.

• •Where is the data physically stored, and what crosses borders?
• •Who is it shared with, and is it sold or used for advertising?
• •How does deletion work, how long does it take, and what about backups?
• •Once I share with someone, what exactly can they see, and how do I take it back?