Privacy policy
How HostAlly handles personal data
HostAlly is software for people who run short lets in Malta: hosts, the agencies that manage flats for their owners, and their teams. This policy says what personal data HostAlly holds, why, who else receives it, how long it is kept and how to ask for it to be removed. It covers the web app at my.hostally.app, the HostAlly phone app, and the pages a guest is sent for their stay.
Who is responsible
HostAlly is run from Malta by Nick Scerri, who is responsible for it until a company is formed to run it. In this policy, "we" means HostAlly and the person who runs it. You can reach us at the address at the end of this policy.
For the account of a member of a host's team, we decide what is held and why, and we are its controller.
For a request for access, we decide what is held and why, and we are its controller.
For a guest's details, the host or agency the guest booked with decides what is held and why, and is its controller. We hold those details for the host, as their processor, and use them only to run HostAlly for that host. A guest who wants to know what a host holds about them asks that host first, and may also write to us.
What we hold
HostAlly holds what a host needs to run their lets, and nothing more:
- Members of a host's team: the name the team sees, an email address, a password if they set one, which is stored so that nobody can read it, a mobile number for texts if one is set, a role, and the tasks a member is given with their pay.
- Owners of the flats an agency manages: name, address, email, phone, company, the bank account they are paid into, and the statements issued to them.
- Guests: name, email address, phone number, nationality, language, the dates of the stay, how many people stay and what was paid.
- The guest register: for a stay, the full name, nationality, date of birth and identity document type and number that Malta's law asks a host to record. Only the members who handle compliance can read it.
- Online check-in: when the guest expects to arrive, where they are coming from, their note to the host, and when they agreed to the house rules.
- Messages between a guest and the host, through the booking platform, WhatsApp, email or the stay page, with the files sent in them, and whether the guest agreed to be messaged on WhatsApp.
- Payments on a host's booking site, which a guest makes through the host's own account with a payment provider. Card details go to the payment provider alone and never reach HostAlly.
- Phones signed in to the phone app: a push token and whether pushes are on, so that a member is told of a new message or task.
- Receipts a member uploads for an expense.
- People who ask for access to HostAlly: what they type on the request access page, which is their name, email address, organisation, phone, how they host, how many units they look after and anything else they choose to tell us.
Most of a guest's details come from the booking platform the guest booked through, or from the host. The rest the guest gives on the stay page.
We do not take a photo of an identity document. If that changes, this policy will say so, and how long a photo is kept, before the first one is taken.
Why we hold it
- To give a member an account, sign them in and show them the work of the organisations they belong to. The basis is our contract with the member.
- To run each stay for the host: take the booking, keep the host's calendars and listings in step, prepare the flat, send and answer messages, and take payments and deposits. The basis is the host's contract with the guest.
- To keep the guest register and work out the eco-contribution. The basis is the host's legal obligation under Malta's law. A guest's date of birth says whether they are under 18 and owe none.
- To message a guest on WhatsApp. The basis is the guest's agreement, which they may withdraw at any time, after which the host reaches them another way.
- To prepare the statements an agency owes each owner and pay them. The basis is the agency's contract with the owner.
- To keep HostAlly secure and working. Each request writes a log line with an id, the organisation, the user and whether it succeeded, and never what was typed or shown. The basis is our legitimate interest in a service that is secure and works.
- To reply to a request for access and arrange its walkthrough. The basis is the steps the person asked us to take before any contract with them.
- To text a member on duty when an access code is withheld, a flat out of service has a guest arriving, or a deposit's claim window is closing. The basis is our contract with the member.
The guest register's details are required by law. Without them, the host cannot complete the guest's check-in.
We do not sell personal data, show advertising, or build profiles of anyone for marketing. No decision with legal or similarly significant effects on anyone is made by automated means alone.
Replies drafted with a language model
HostAlly uses a language model from a specialist provider to read a guest's message in English, to draft a reply in the guest's language that a member approves or that is sent as the host's settings allow, and to suggest facts about a property from the host's own words.
The model is given what a reply needs: the conversation's recent messages, the guest's first name, the unit and the property, the dates and state of the stay, and the property's facts. It is never given an access code, a guest's surname, email address, phone number or identity documents, or another guest's messages. The provider deletes what it is sent within 30 days and does not use it to train its models.
Who else receives it
We use service providers to run HostAlly. Each processes personal data only on our instructions, under data processing terms, and only for the service it gives:
- Hosting providers in the European Union, in Frankfurt: the database, the files, the sign-in accounts, the service and its logs, and the web app.
- An email provider: sends and receives email, among them a guest's messages by email and sign-in links.
- A language model provider: the model described above.
- A channel manager: connects a host's listings on the booking platforms, and carries their reservations, guests' details and messages.
- WhatsApp's business messaging service: carries WhatsApp messages, on the host's own business account.
- Push notification services, among them those of the phone's maker: deliver pushes to members' phones. A push holds a guest's first name, the unit and the start of a message.
- A payment provider: takes payments and deposits on a host's booking site, on the host's own account with it.
- A map service: finds a property on the map from its street and locality, and is sent nothing else.
- A mailbox provider in the European Union: holds the email we receive at our own addresses, among them requests for access.
- A service that checks a form is filled in by a person: sees the network address and the browser of whoever fills in a booking site's or the request access page's form.
- An SMS provider: delivers those texts to members' mobiles. A text names the flat, a time and an amount, and never a guest.
We name each provider, and where it holds data, to any host, and to anyone who asks us.
The booking platforms and WhatsApp are also services the guest uses themselves, under their own privacy policies. We give personal data to a public authority only where the law requires it.
Some providers, among them the email provider and the language model provider, hold data in the United States, and others may process it outside the European Economic Area. Each such transfer is made under a safeguard the GDPR allows: an adequacy decision of the European Commission, such as the EU-US Data Privacy Framework, or the Commission's standard contractual clauses. Write to us for a copy of the safeguard that applies.
How long it is kept
We have not yet set a fixed period for every kind of data. Until we do, nothing a host holds about a guest, an owner or a stay is deleted except when someone asks for it to be removed, and this policy will say each period once it is set.
- A member's account: until they ask us to delete it. When a membership ends, the organisation keeps the member's name on the work they did there.
- A signed-in session: until the member signs out, or after 30 days unused.
- The guest register: for as long as Malta's law requires the host to keep it, even after a request to remove a guest's data.
- Invoices, receipts and the other documents a host must keep for tax: at least six years from the end of their year, as Malta's VAT Act requires, even after a request to remove a guest's data.
- Records of how emails and channel updates arrived: 30 days. Records of pushes sent: 24 hours.
- A phone's push token: until its member signs out on it or is removed, or the phone stops taking pushes.
- Log lines: the short period our hosting provider keeps them. They hold no message, name or address.
- A request for access: in our mailbox until 12 months after our last message with the person who sent it.
- Records of texts sent: 90 days.
Your rights and removing your data
You may ask to see the personal data held about you and who has received it, to correct it, to have it removed, to limit or object to its use, or to receive a copy of it to take elsewhere. Where we hold something on your agreement, you may withdraw it at any time, which does not undo what was done before.
A guest asks the host they booked with, or writes to us. A member or an owner writes to us. We may ask you to confirm who you are before we act, and we answer within one month.
When a guest's data is removed, their name, their contact details and the words and files of their messages are cleared. Their guest register entry and the documents the host must keep for tax are kept, because the law requires them.
Removed data can stay in our database's backups for up to seven days, until each is replaced.
You may also complain to Malta's Information and Data Protection Commissioner, at idpc.org.mt, or to the data protection authority where you live or work.
Cookies
The web app sets cookies that keep a member signed in, and one that ties a sign-in link to the browser that asked for it. No script on the page can read them, and they are sent only over a secure connection.
It also sets cookies that keep a member's choices on that browser for up to 400 days: the organisation they last opened, Light, Dark or System, whether the sidebar is narrow, and whether the setting-up checklist is hidden. One more keeps their place in setting up for a day. None of them names a person, and HostAlly's service stores none of them.
Each of these cookies is needed for the web app to work as the member asked, so none needs consent.
HostAlly uses no analytics, advertising or tracking cookies.
Children
HostAlly's accounts are for adults. Of a guest's party, HostAlly holds how many people there are, and the details of the guest who books and checks in, and nothing about the others.
Changes to this policy
When this policy changes, the date at its top changes with it. A change to how a host's guests' data is handled is told to hosts before it takes effect.
Contact
Write to us about anything in this policy, or to ask for any of the rights above.
privacy@hostally.app