How BondBack handles the personal information you submit through our forms
BondBack only collects what it needs to review enquiries and coordinate bond cleaning leads. We don't sell this information or share it for marketing. The plain-language summary below covers the contact, renter quote, and cleaner enquiry forms.
This policy explains the personal information BondBack collects, how we store it, who may receive it, and how you can ask for access or deletion. It applies to the general contact form at /contact, the renter QuoteForm at /quote and its embedded versions, and the cleaner enquiry form at /for-cleaners.
The general contact form submits a single row to the contact_leads table with the following fields:
name) — up to 255 characters, required.email) — up to 255 characters, required.subject) — up to 255 characters, required.message) — up to 5000 characters, required.source_page) — the page on BondBack where you opened the form (stored automatically so we can route your message to the right person).We retain the row while it is needed to review, route, and follow up the enquiry. These insert paths do not apply an automatic deletion window. To ask for access to your information or request deletion, use /contact and include the email address used in your submission; the team will review and handle the request operationally.
The QuoteForm on /quote and the renter-facing pages that embed it submit one row to the quote_leads table with the following fields:
name) — up to 255 characters, required.email) — up to 255 characters, required.phone) — up to 50 characters, optional.suburb) — free text, required.bedrooms) and Bathrooms (bathrooms) — integers 0–10, required.preferred_move_out_date) — ISO date (YYYY-MM-DD), optional.source_page) — the BondBack page the form was opened from.cleaner_slug) and preferred cleaner slug (preferred_cleaner_slug) — optional identifiers set when a cleaner profile is selected or the form is opened on that profile.The row is read by the renter-facing team to prepare an enquiry response and, when a cleaner slug is present, coordinate with that selected cleaner. It is not broadcast to cleaners generally.
The supplier-signup form on /for-cleaners submits a single row to the cleaner_leads table with the following fields:
business_name) — up to 255 characters, required.contact_name) — up to 255 characters, required.email) — up to 255 characters, required.phone) — up to 50 characters, optional.service_area) — free text (typically the suburbs you cover), required.company_size) — one of: solo, 2–5, 6–20, or 20+.website) — up to 500 characters, optional.source_page) — the page where the form was opened.We retain the row while the team reviews the application, follows up, and handles any listing decision. These insert paths do not apply an automatic deletion window; use /contact to request access or deletion.
These three lead types are stored as rows in PostgreSQL through the existing BondBack database pool: contact_leads, quote_leads, and cleaner_leads. The stored row includes the fields listed above and the database-created timestamp. We retain rows for operational review and follow-up; there is no automatic deletion window in these handlers. The forms do not ask for or store payment card, bank account, or other payment details.
Contact enquiries are reviewed and routed by the BondBack team. A renter quote request is handled by the renter-facing team and uses the selected cleaner slug when one is present; without one, it remains with BondBack for follow-up. A cleaner enquiry is reviewed by the BondBack team as part of supplier vetting.
The contact, renter quote, and cleaner enquiry handlers emit tagged notifications through notifyLead and notifyLog. They always write a structured server log entry. If the operator has explicitly configured the optional LEAD_NOTIFY_URL webhook, the notification payload may also be sent to that endpoint. Webhook delivery is non-fatal: a failed or unavailable webhook does not undo a successful database insert.
Lead details may be seen by authorised BondBack team members who review and follow up enquiries. A renter quote's details may be shared with the selected cleaner when a cleaner slug is included, so that cleaner can respond to the enquiry. Lead details may also be sent to the explicitly configured LEAD_NOTIFY_URL endpoint. This is operational lead routing, not marketing-list sharing: BondBack does not sell, rent, or share these three lead types with marketing partners.
The site analytics beacon is a page-view signal and does not receive the form fields. No payment details are collected through these forms.
Send your request through the /contact form with the email address you submitted on the original form so we can locate matching rows in contact_leads, quote_leads, or cleaner_leads. The team will review the request and respond operationally.
Send a deletion request through the /contact form with enough detail for the team to identify your submission. We will review the request and handle it through the relevant operational process.
No. A quote request uses the selected cleaner slug when present; if you did not select a cleaner, the request stays with BondBack for follow-up. We do not broadcast a quote request to multiple cleaners or to the directory.
The forms post to the BondBack lead endpoints over the same origin. The page-view beacon sets a pseudonymous visitor identifier in localStorage and does not read form-field values.
Use the /contact form for privacy questions, access requests, or deletion requests.