Browsing the site
You can read every public page without an account. We use no analytics, advertising or tracking scripts, and no third-party cookies.
If you create an account
- Your name and email address.
- Your password, which is handled by Firebase Authentication, a Google service. We never see or store it.
- How you sign in: email and password, or Google.
- Your account role (customer, member or administrator), set by our servers and never by you or your browser.
We use this only to sign you in and to decide which parts of the site you can use.
If you apply for membership
- About the business: its name and any registered name, the kinds of stay it runs, how many properties it has, its area and address, and any registration or association numbers you choose to give.
- Who to contact: their name, role, phone number and email address.
The association’s administrators use this to review your application, and may contact you about it. You can see everything you sent, and the association’s reasons when it asks for changes or declines. We don’t ask for identity documents, bank details or uploads.
If you’re a member
For each property you add: its name, kind, location, description, rooms, amenities, accessibility details, house rules and a contact phone number or email. The association’s administrators review it. Approval doesn’t publish it: a property is shown publicly only once you publish its listing, and you can withdraw it at any time.
Records of decisions
Every decision or change of status on an application, a membership or a property, and every change to an account’s role, is recorded: the change, when, which account made it, and any reason given. Saving a draft isn’t recorded this way. These records are kept as a history, and on this site only the association’s administrators can read them.
Administrators sign in with an authenticator app as well as a password. We keep only the identifier of an administrator’s authenticator, never its secret, which stays in the app.
Our application keeps technical logs of events, such as a sign-in or a saved application. They identify accounts only by a shortened identifier, and contain no names, email addresses or details from your forms.
Messages
We tell you about your bookings, applications and properties in your account’s notifications, and may also email you about them. Firebase Authentication emails you to verify your address after you register, and to reset your password when you ask.
Cookies
One strictly necessary cookie keeps you signed in. Scripts on the page can’t read it. It expires after five days, or eight hours for administrator accounts, and it’s removed when you sign out.
Where it’s stored
Account, membership and property information is held in Google Firebase (Authentication and Cloud Firestore). We will state the storage region here once it has been confirmed.
What we don’t do
- Sell or rent your information.
- Share it with advertisers.
- Track you across other websites.
How long we keep it
We haven’t set retention periods yet. Until we do, after legal review, we keep what’s described here, with the dates it was created and changed, so that a policy can be applied to everything once it’s agreed.
Your choices
You can ask for your account and its information to be deleted, including an application or a member’s properties. Records of decisions are kept as history. How to contact us about this will be published here before the site opens to the public.