Privacy Policy
For Botler. Last updated: on release.
Botler is a demonstration product built by Harfred Labs in Melbourne to show what renting a humanoid robot could feel like. This policy explains, honestly, what that demonstration collects and does with it today, and what would change if Botler became a real service. It is written to be read, not to be survived. If anything here is unclear, ask us at support@harfredlabs.com.
The short version
Today, Botler is a seeded simulation: there is no live fleet, and your addresses, payment details and booking history live in your own browser or app, not on a server. The one exception is deliberate and is described in full below: when you confirm a booking, a short summary of what you booked — not where you live — is sent to us, because a robot rental that does not operate yet has no other way to know whether anyone wants one. Your street address, your phone number and your card never leave your device. We do not sell your personal information, we do not share it with advertisers, we do not run any analytics on you, and we do not build advertising profiles about you.
What we collect when you book
Booking a robot asks for the same information a real rental would need. Unless it is named in “Confirming a booking, and what it sends us” below, all of it stays on your device:
- Your name, phone number and email address, so we can confirm a booking and contact you about it.
- The service address and any access instructions you give the driver or robot — a gate code, where to park, which entrance to use.
- Payment method details. Botler does not process real payments today, and there is no payment provider connected — so there is nowhere in the app to type a real card number, expiry or security code. What you can do instead is attach a single demonstration card, and only a masked version of it (card brand and last four digits) is ever stored, on your own device. In a commercial release, full payment details would be held by a payment provider under its own security standards, and Botler would never see or store your card number.
- Booking history and task notes — which robot you booked, when, for how long, and any instructions you left for the job.
- Incident reports you submit — what happened, when, and which booking and robot it relates to — so it can be looked into.
The robot's sensors and cameras
Where a robot profile says a unit has cameras or other sensors, they exist to let the robot navigate safely and carry out the booked task — not to watch you. In a commercial release, footage would be retained only as long as needed to resolve a specific incident or safety concern, then deleted, and would never be used for advertising or sold to anyone. Some bookings involve a remote human operator assisting the robot with part of a task; where that applies, it is disclosed on the robot's profile before you book, along with what the operator can and cannot see.
Where your data lives today
Almost everything you enter — your addresses, the masked card, your booking history, your task notes, your incident reports — is stored locally in your browser or the app on your device. We cannot read it, and we cannot recover it if you lose the device or clear your browser data. If and when Botler introduces real accounts, that data would move to cloud infrastructure hosted in Australia, so it stays under Australian privacy law.
The exception is the booking summary described in the next section, which is the only thing the app sends us.
Confirming a booking, and what it sends us
Botler does not operate. Nothing is dispatched, nothing is charged, and no robot is coming. Confirming a booking in the app is therefore not an order — it is you telling us you would have placed one, which is the only honest way to find out whether this product is worth building. The app says so on the screen where you confirm, before you tap.
What is sent to us when you confirm:
- Which robot you chose, and its name.
- How you booked it — as soon as possible, scheduled, or repeating.
- The start time and the duration.
- The price we quoted you.
- Your suburb, postcode and service area — so we know which parts of Melbourne to serve first.
- Whether it was your first booking.
- The task description you wrote, if you wrote one.
- Your email address, only if you saved one in the app — so that we can tell you when robots reach your suburb. If you have not saved one, none is sent, and the app offers you the waitlist instead rather than promising a reply it cannot make.
- A random identifier the app generates once and keeps on your device. It is a random string: nothing about your device, browser or network goes into it, and it cannot be used to recognise you anywhere else. It exists so that three bookings from one curious person are not counted as three interested households. Clearing your browser data throws it away.
What is never sent, at any point:
- Your street address or unit number, and your access instructions. Suburb and postcode go; the line above them does not.
- Your phone number.
- Your card — not the number, not the masked version, not the brand, not the expiry.
- Your name.
These summaries are stored as individual records in Google Cloud Storage in the australia-southeast1 region (Sydney), in a private bucket that is not readable from the internet, and a copy is emailed to us through Resend, the same email provider that runs the waitlist. They are read by one person, to count how many people wanted a robot and where. They are not sold, not shared, not used for advertising, and not combined with anything else.
Bookings you make in the demo are never sent. Everything under /demo runs on invented sample data in memory, so it is not evidence of anything and it is not collected.
The waitlist
If you join the Botler waitlist from our website, we collect your email address and use Resend, an email delivery provider, to send you updates about the service. We use your email for that purpose only — never for advertising, and never sold or shared with anyone else. You can unsubscribe at any time using the link in any email we send, or by writing to us.
Analytics
We do not run any analytics or tracking on Botler. There is no Google Analytics, no advertising pixel, no session recorder and no third-party script watching what you tap. Nothing about how you move around the app is measured or sent anywhere.
The single thing we count is the confirmed booking described above, and we have set it out field by field rather than hiding it behind the word "analytics", because it is the one place where this policy could have been quietly untrue.
How to delete your data
Because almost all of your data lives on your own device, you are mostly in control of it directly. In the app, go to Account → Reset my data to clear your bookings, addresses and payment methods and start fresh.
For the booking summaries we hold — and for a waitlist address or an incident report — write to support@harfredlabs.com and say you want them deleted. To find yours we need enough to identify the records, and the least you can give us is the suburb and the rough date of the booking. If you saved an email address in the app, give us that instead and we will find every summary that carries it. We will delete them and confirm when it is done; we do not require a reason and there is no form.
Children
Botler is not directed at children under 13, and we do not knowingly collect personal information from them. If you believe a child has given us personal information, write to support@harfredlabs.com and we will delete it.
Changes to this policy
If we change this policy we will update this page and the date at the top. If Botler becomes a commercial service handling real bookings and payments, this policy will be rewritten to match, and we will make that change clear before it takes effect.
Contact
Botler is a demonstration product operated by Harfred Labs, Melbourne. For any privacy question, or to have your data removed, write to support@harfredlabs.com.