Why We Built House Sitting Australia on Google Firebase

When you hand someone the keys to your home, or move into another person’s home to care for their pets, trust is everything.

That trust begins with conversations, references and good judgement. But once those conversations move onto an online platform, trust also depends on how the technology handles private information. A platform should not merely promise to respect your privacy. It should be designed so that private information is difficult to access without the proper authority.

I began house sitting in 2007 and have run the House Sitting Australia community since 2011. When it came time to build a dedicated platform, I had one firm requirement: privacy and security had to be part of the structure from the beginning, not features added later.

After considering the available options, we chose Google Firebase as the technical foundation for House Sitting Australia.

Privacy Has to Be Built In

A house sitting listing contains information that needs to be handled carefully.

A homeowner may be describing their pets, their property, the dates they will be away and sometimes aspects of their daily routine. Sitters also provide personal profiles, references, identity information and private messages.

That does not mean all of this information should be visible to every member.

House Sitting Australia separates information intended for public listings from information that should remain private. Firebase gives us the tools to control who can read or change different parts of the database, based on who they are and what they are authorised to do.

This is an important distinction. Privacy does not depend only on hiding a field on the screen. Requests for protected information can also be checked against access rules before the database returns anything.

Your Street Address Is Never Shown Publicly

A House Sitting Australia listing displays the suburb and postcode so sitters can decide whether the location suits them. It does not publicly display the homeowner’s street address.

The location shown on the map is also deliberately approximate. The marker is moved away from the exact property so someone browsing listings cannot simply zoom in and identify the front door.

The homeowner’s full address, phone number and emergency details are stored separately from the public listing. They are not made available to every member or to every sitter who applies.

The chosen sitter receives the address through the confirmed sit process, after the homeowner has reviewed the applications, spoken with the sitter and decided to proceed.

Technically, private information still needs to travel securely between your device and the service. The important point is that it is not published as part of the listing or made available to people who have no reason to see it.

That is a considerable improvement over placing detailed travel dates, pet information and location clues into a large social-media group. Facebook remains an excellent place for homeowners and sitters to meet, but a dedicated platform provides a safer place to manage what happens next.

We explain that process further in:

Found Your House Sitter on Facebook? Here’s What to Do Next

Messages Should Not Disappear in a Busy Feed

House sitting often involves tight timelines.

A homeowner may be leaving within days. A sitter may be travelling through the area. Dates can change, questions need answering and several applicants may be under consideration at the same time.

Firebase supports real-time updates, which means a new message or application can appear without someone repeatedly refreshing the page. New listings can also become available as soon as they are published.

This does not replace email notifications or sensible follow-up. It simply makes the main conversation feel like a conversation rather than a collection of forms being sent backwards and forwards.

It also keeps house sitting discussions together. Instead of trying to remember whether a date was mentioned in a Facebook comment, Messenger conversation, text message or email, both people have a clearer record of what was discussed.

Designed for Regional Australia Too

House Sitting Australia is not being built only for people living in capital cities with perfect internet connections.

Many excellent house sits are found in country towns, coastal communities and rural areas where mobile reception can be inconsistent. I live in Mallacoota, so designing for regional conditions is not an abstract consideration.

Firebase can cache information that the app has already loaded. Where cached information is available, members may still be able to read it during a temporary loss of connection, with changes synchronising after the connection returns.

That does not mean every feature will work indefinitely without internet access. It does mean the app can behave more gracefully when coverage drops out, rather than becoming immediately useless because someone has driven beyond the nearest mobile tower.

For a sitter checking instructions in a regional property, that can make a practical difference.

Reliable Infrastructure Without Running Our Own Server Room

Traditional online services often require someone to configure servers, maintain databases, install security updates, monitor capacity and respond when traffic increases.

Firebase provides managed infrastructure through Google Cloud. That allows House Sitting Australia to concentrate on the application, its privacy rules and the needs of members rather than maintaining a rack of servers.

It also allows the service to grow without having to predict every future usage increase in advance. Computing resources and database services can be expanded as the community grows.

No online service can honestly promise that it will never experience an outage. What Firebase provides is mature, managed infrastructure and a practical way for a small Australian platform to achieve a level of resilience that would otherwise require a much larger technical operation.

Payments Are Handled by Stripe

House Sitting Australia does not need to collect or store members’ credit card numbers.

Payments are handled through Stripe’s secure payment system. When card information is entered through Stripe’s payment interface, the sensitive card details are sent to Stripe rather than being stored in the House Sitting Australia database.

HSA receives the information needed to confirm that a payment was completed, but not the member’s complete card details.

Keeping payment information out of our own systems reduces both the information we hold and the risk associated with holding it.

Firebase Is Not a Magic Security Button

It is important to be honest about what the technology can and cannot do.

Firebase provides authentication, database access rules, managed hosting, real-time updates and other useful tools. It does not automatically make every application secure.

Security rules must be written carefully. Public and private information must be stored separately. Changes need to be tested so that adding a new feature does not accidentally weaken an existing restriction. Administrative access must also be controlled.

There are broader trade-offs as well. Using Firebase means relying on Google’s platform, pricing structure and technical ecosystem. As the service grows, usage must be monitored and costs managed sensibly.

Those are real considerations, but they are preferable to pretending that a small platform can safely invent its own authentication, payment and database infrastructure from scratch.

The objective is not to claim perfect security. No responsible technology provider should make that promise. The objective is to reduce unnecessary exposure, limit access and keep reviewing how the system protects its members.

A Lean Platform Built for This Community

House Sitting Australia is independently built and operated. There is no venture-capital company behind it demanding rapid growth or trying to recover millions of dollars from members.

Using managed infrastructure allows us to remain lean. Time and money can be directed towards practical features such as profiles, messaging, applications, identity verification, pet care cards and digital sit agreements instead of server maintenance.

It is also one reason homeowner accounts can remain free until 31 December 2026 while the platform and community continue to grow.

The technology should support the community, not become the purpose of it.

The Bottom Line

We chose Google Firebase because it provides a sound technical foundation for an independently built house sitting platform.

It gives us strong access-control tools, real-time communication, managed infrastructure and better support for unreliable connections. Combined with careful application design and Stripe payment processing, it allows us to minimise the personal and financial information exposed through the platform.

Most members should never need to think about Firebase, databases or security rules. They should simply find that their address is not displayed publicly, their messages arrive promptly and the information they share is available only where it is needed.

That is what good technology should do. It should quietly make a human process safer, clearer and easier to manage.

House sitting since 2007. Community since 2011.

Explore the House Sitting Australia platform at hsa.oze.au, or contact me at hsa@oze.au with any questions about how it works.