PROPERTY LAYERS AU

Privacy — Property Layers AU

Updated 21 November 2026. Applies to Property Layers AU, its hosted account page and production backend.

Service and privacy requests

This policy describes the Property Layers AU Chrome extension and its production backend. For an account-data copy or deletion request, sign in to the extension, confirm your email, then open Account data & privacy. Requests are bound to your verified account and queued for manual review. Sending a request does not immediately delete data or cancel a subscription. For general support, privacy enquiries and correction requests, contact tony.bui911@gmail.com. Do not email passwords, verification codes or card details. The service is operated by Tien Bui, Australia.

Map requests and local preferences

School catchments are available without an account. To fetch and inspect available map data, the extension sends visible map bounding boxes, state/year/school level, selected map coordinates and school-search text to the Property Layers AU backend hosted on Google Cloud. These requests can reveal the area you are researching. Do not enter personal information in school searches. Requests use HTTPS and omit portal cookies. The extension does not send the full page contents, unrelated browsing history or portal login credentials to this backend.

An explicit catchment property-search action sends the chosen school, state, boundary year, level and buy/rent channel to our backend. It then opens realestate.com.au with an encoded approximate boundary and school-selection metadata in the URL. On that portal, existing search filters are retained. The portal processes this search under its own privacy policy. Clearing the extension filter removes the boundary and school metadata from the current search URL, but does not erase browser history or portal records. There is no typed street-address geocoding service.

School catchments and available archived school rankings are Free without sign-in, trial or payment. Ranking records are fetched from the backend and held in memory or the browser cache for map display; they are not packaged in the extension and contain no student-level records. Signing out does not remove Free school rankings. Archived figures are labelled Legacy and unverified, with their results year and source details.

Display preferences and onboarding state are stored in Chrome local storage. Temporary map caches may be held in memory or the browser HTTP cache. Removing the extension clears its extension storage. The consumer build uses the production backend; custom backend configuration is available only in development builds. The popup uses activeTab to identify a supported portal when opened.

Optional Google or email/password accounts

The hosted account page also supports Google and email/password sign-in through Firebase Authentication. Firebase stores the web sign-in session in browser session storage for this website. This session is separate from the extension session and is not sent to property portals. Signing out clears this website’s sign-in session. The website uses your Firebase identity to read account status and, only after you choose Start trial, request trial activation from the same backend. Use the same account in the extension to access those entitlements.

You can sign in with Google or with email and password. Email/password credentials are sent directly to Firebase Authentication; our backend does not receive your password. In the extension, Continue with Google starts Chrome’s identity flow only when you click it, requesting basic identity (OpenID, email, name and profile picture). Google’s access credential is exchanged directly with Firebase for the same kind of Firebase session used by email sign-in; the worker clears the Google access token from Chrome’s token cache after the exchange. Google’s credential is not sent to property portals or stored by our backend. Firebase may retain the Google-linked identity/profile information. The backend verifies the Firebase account ID, email and verification status to enforce access. Signing in or creating an account does not start a trial, checkout or payment. Signing out of the extension does not sign you out of Chrome or your Google account.

Firebase handles verification and password-reset emails. Account/plan timestamps and data-request status are stored in Firestore. The Firestore account database is in australia-southeast1 (Melbourne); this does not restrict all Google/Firebase processing to Australia.

Firebase ID/refresh tokens are held in Chrome session storage restricted to trusted extension contexts. They are removed on sign-out or browser-session end. ID tokens go to the production backend to verify account requests; refresh credentials go to Firebase. Portal page scripts receive only a minimal plan/availability summary, without your email, ID or credentials. Signing in creates Free access; it does not automatically start a trial or subscription.

Premium trial

Eligible verified new accounts may explicitly activate one seven-day Premium trial without a card. The backend records the activation and expiry in Firestore and checks expiry before granting Premium access. The trial does not create a paid Stripe subscription or an automatic charge; access returns to Free after expiry unless the user separately subscribes.

Subscription data

Optional Buyer Premium subscriptions open Stripe's hosted checkout. Monthly billing is A$29 and yearly billing is A$243.60 (30% less than twelve monthly payments). Paid subscriptions renew automatically until cancelled. A purchase during a card-free trial starts paid billing after confirmation in Stripe; the card-free trial itself never charges automatically. Subscriptions can be managed or cancelled through the customer billing portal in Account settings; cancellation normally takes effect at the end of the paid period. Stripe processes payment details; the extension and property backend do not store full card numbers. The backend records account/customer/subscription identifiers, trial use, status, relevant payment events and access dates in Firestore to enforce entitlements and prevent repeated trials. Account/payment responses are not publicly cached. Any enabled offer must disclose its trial, price, recurring charge and cancellation conditions before purchase.

Removed features and retained older records

The current version has no Saved Locations, comparison or lead-capture UI. Existing saved addresses/coordinates, listing links and notes from older account versions may remain associated with their account until removed through the data request process. Earlier lead, event, error and webhook HTTP endpoints have been retired; their existing records are retained for operator review and are no longer publicly served. Older optional lead records may contain names, email addresses, phone numbers, selected schools/states and request details. Historical diagnostic records may contain event metadata, error messages or URLs. These records are retained in backend storage for security review and authenticated support requests. Optional usage analytics require consent version 2. Earlier consent does not enable the expanded tracking; you will be asked again. If allowed, selected page/feature actions, fixed login/trial error categories, layer load outcomes and visible Premium layer events are sent through our v3 backend to PostHog in the United States. After sign-in, the backend assigns a random analytics account ID and links the consenting browser's random ID to it, allowing website and extension journeys and return usage to be measured. Emails, Firebase IDs, authentication tokens, portal URLs, addresses, coordinates, school-search text and page contents are not included. No session recording, DOM autocapture, fingerprinting or advertising pixel is used. The backend stores consent records for consenting browsers and the opaque analytics ID in the account record. With account consent, verified Stripe webhook outcomes may send first-payment, renewal, failed-payment and cancellation events with amount and currency; card details, Stripe customer/subscription/invoice IDs are not sent to PostHog. Stable event UUIDs support deduplication. Account sign-out rotates the local anonymous ID to prevent linking later users of the same browser. Use Analytics preferences to allow or decline; preferences are separate for the website and extension. Declining stops local collection and, when signed in, revokes this browser's account analytics consent. Other explicitly consenting browsers can remain enabled. Sign in to withdraw account analytics consent associated with this browser; if a privacy update cannot reach the backend, retry while signed in. Do Not Track and Global Privacy Control suppress local events where available. Previously collected events are not automatically deleted on opt-out; authenticated data requests are available in Account settings. The selected PostHog Free plan provides one-year analytics retention. Staging events are not sent to the production project. Analytics is best-effort and does not determine access or replace billing records. The current extension does not send account or map-search information to advertisers or data brokers.

Hosting logs, retention and backups

Google Cloud hosting receives IP/network information, timestamps, request URLs and response/error metadata. Request URLs may contain the map/search parameters above. New application request logs omit query strings; Google's infrastructure request logs may still contain them. The project's default Cloud Logging bucket currently retains logs for 30 days; separately required security or transaction records may be retained longer for a documented purpose. Historical logging is not erased by this release.

Account records are retained while the account exists unless the operator completes an authenticated deletion request. Signing out, uninstalling or cancelling a plan does not delete cloud records. Daily Firestore backups are scheduled with seven-day retention; deleted records can persist in these backups until expiry. If a backup is restored, fulfilled deletion requests must be reapplied. Stripe may retain payment-provider transaction records after account deletion under its own retention practices. Financial or security records needed for disputes, fraud prevention or recordkeeping may be retained separately; the operator explains any retained records and their purpose when reviewing a deletion request. Uninstalling the extension or sending an account-deletion request does not itself cancel an active subscription.

Access, correction and deletion requests

Verified signed-in users can open Account data & privacy on the account page to request an account-data export or deletion. The request type, timestamp and pending status are attached to your account in Firestore for manual operator review. This does not immediately delete data or cancel billing. The current in-app request form supports export and deletion only. For corrections and general privacy enquiries, contact tony.bui911@gmail.com. Account ownership is verified through Firebase. The operator reviews requests manually and must explain any retained records and confirm fulfilment. Do not send passwords, verification codes or card details. A deletion request and subscription cancellation are separate actions; any active subscription must be resolved before account deletion. The operator reviews authenticated requests and records their fulfilment. The request queue does not automatically send an acknowledgement email.

Complimentary access and account administration

The verified master account can view service account totals and account access status, and grant or revoke complimentary Premium access. Firebase stores the grant, optional expiry, operator note and a bounded history of the most recent 100 grant changes, including the operator account ID and time. These records support access management and account support. Complimentary access does not change an existing Stripe subscription. Account administration records stay in Firebase and are not sent to PostHog.

Product feedback

Feedback is voluntary and collected using a Google Form. We receive the category, message and any email address you choose to provide. We use these submissions to investigate problems, improve the product and reply when requested. Google hosts the form and stores responses in the operator’s Google account. No sign-in is required; automatic email collection and public response summaries are disabled. The extension does not attach account identifiers, map locations, browsing history or analytics IDs to the form. Feedback is separate from optional PostHog analytics and can be sent when analytics is declined. A local extension flag remembers whether the feedback invitation has already been shown. Please do not include passwords, payment details or private property information. For feedback removal, use the form’s Contact form owner option; authenticated account export/deletion requests remain available separately in Account settings.

Service providers and external links

Google Chrome provides extension storage; Google Cloud, Firebase Authentication and Firestore provide hosting, identity and account storage; Stripe handles payment processing when enabled. Provider processing follows their own terms and privacy policies. Property portals, map providers and official source websites opened through links operate independently and may receive their own normal browser requests. Links use appropriate referrer restrictions where supported.

This policy must be updated if features, processing, providers or retention practices change. The Chrome Web Store privacy disclosures must match the released extension.