Privacy policy

Brolly ("we", "us") runs brolly.day, a service that shows a household's weather, nearby Santander Cycles availability and calendar events on a screen at home. This policy explains what we collect, why, and the choices you have. Questions? Get in touch.

What we collect

• Your account: your name, email address, a salted Argon2 hash of your password (never the password itself), your timezone, and, if you turn it on, the secret for two-step sign-in.
• Your households: each household's name, postcode and the approximate location we derive from it, the bike docks you pin, its members and pending invitations (including the invitee's email address), and the screens paired to it with when they last checked in.
• A Met Office key, if you add one: stored encrypted, used only to fetch your household's forecast.
• Records of emails we send you (verification, password reset and invitations), so we can rate-limit them.

Google user data

If you connect Google Calendar, Brolly requests the calendar.readonly scope, plus your basic profile email so we can show which Google account is connected. Here is exactly how that data is used:

• What we access: the list of your calendars (names and colours), and, for the calendars you choose for a household, the events in the current and following week: their start and end times, titles, colours and identifiers.
• How we use it: only to display those events on the screens and previews of the households you've chosen them for. Event titles and times are shown; descriptions, locations, attendees and attachments are never displayed.
• What we store: an encrypted OAuth refresh token, the connected account's email address, and the IDs, names and colours of the calendars you selected. We do not store your events: they're fetched from Google when a screen refreshes and kept only in short-lived memory.
• Who can see it: the events from your chosen calendars appear on the screens of households you've added them to, so people who can see those screens or are members of the household can see those event times and titles. Other members can't see your calendar list, which calendars you chose, or change your choices.
• Sharing: we don't sell Google user data, use it for advertising, or share it with anyone, and humans at Brolly don't read it except with your permission for support, for security purposes, or where the law requires it.
• Deletion: you can disconnect Google at any time from your account page. Disconnecting revokes our access with Google and deletes your token and calendar choices immediately. You can also revoke access from your Google account settings.

Brolly's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Services we rely on

• Cloudflare hosts the service and its database.
• Resend delivers our emails.
• postcodes.io turns your postcode into a location; Open-Meteo or the Met Office provide forecasts for that location (rounded, never linked to you); TfL open data provides bike availability.

Cookies

We use a small number of essential cookies: one to keep you signed in, one that lets a paired screen show its household, and a short-lived one while a screen is being paired. No advertising or analytics cookies.

How long we keep things

We keep your account while you use it. Deleting your account removes you from your households, disconnects Google and anonymises your account. Households are deleted when their last member leaves. Unaccepted invitations expire after 7 days.

Your rights

Under UK GDPR you can ask to access, correct, export or delete your personal data, or object to how we use it. Use our contact form. You can also complain to the Information Commissioner's Office (ico.org.uk).

Changes

If we change this policy in a way that matters, we'll update the date above and, for significant changes, email you.