Privacy Policy

Effective 2 September 2026. Last updated 2 September 2026.

Butler ("Butler", "we") is a personal home-display application that shows your upcoming calendar events, the weather, and currently playing music on an LED panel in your home. This policy explains exactly what data Butler touches, where that data lives, and how to get rid of it.

1. Who is responsible

Butler is maintained by an individual developer and is not a company. Contact: hello@butler.ly.

2. Google user data Butler accesses

Butler has two parts, and they share one Google sign-in: the home display described above, and Availability Picker, a browser extension that reads your free/busy times so it can drop a list of times you are free into an email you are writing. Both request the same single read-only scope, and nothing more:

• https://www.googleapis.com/auth/calendar.readonly — read-only access to your Google Calendar.

Using that scope, Butler reads, from the calendar you choose:

• the event title;
• the start and end time, and whether the event is all-day;
• the name of the calendar the event came from.

It requests only events that start within the next 14 days, and at most a handful at a time. It does not read attendees, guest lists, descriptions, locations, attachments, or any other calendar field. Because the scope is read-only, Butler is technically incapable of creating, editing, or deleting anything on your calendar.

What Butler does not touch

Your email. Butler has no Gmail access of any kind — no Gmail API scope is requested, granted, or used. The browser extension places availability text into the message you are composing by typing it into the page, exactly as you would yourself. It runs only on mail.google.com, only when you ask it to insert times, and it does not read, collect, store, or transmit the contents of your mailbox.

3. What Butler does with it

The event title and time are drawn onto the LED panel in your home so you can see what is coming up. In the browser extension, your busy times are used to work out which slots are free, so that list can be inserted into the email you are writing. Those are the only purposes. The data is not used for advertising, profiling, analytics, resale, credit assessment, or training artificial-intelligence or machine-learning models.

4. Where the data is stored

• Calendar events are never written to disk. They are held in the running program's memory, replaced at the next refresh (about every ten minutes), and lost entirely when the program stops.
• Your Google credential is stored on your own device, in a file readable only by your user account, so that Butler can refresh its access without asking you to sign in again.
• We hold nothing. There is no Butler server, database, backup, or log that your data passes through. Requests travel directly from your device to Google's API.

5. Who Butler shares data with

Nobody. Butler does not sell, rent, trade, or transfer your Google user data to any third party. It does not transfer that data to anyone except as necessary to provide the display feature on your own device — which, in practice, means it never leaves the device at all.

6. Limited Use disclosure

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

7. Other services Butler can talk to

These are optional features you configure yourself. Each connects directly from your device, and none of them receive your Google calendar data:

• Spotify — reads what is currently playing on your account so the panel can show the album art. Governed by Spotify's own privacy policy.
• Open-Meteo — receives the latitude and longitude you configure, in order to return a forecast. No account, and no personal identifier, is involved.
• Telegram — if you enable the optional bot, messages you send to it pass through Telegram's servers under Telegram's privacy policy. Only chat IDs you explicitly allow can control the display.

8. This website

butler.ly is a static site. It sets no cookies, runs no scripts, embeds no fonts or resources from other domains, and has no analytics or tracking of any kind. Our hosting provider processes standard server request logs on our behalf.

9. Retention, revoking access, and deletion

You are in control, and no request to us is required:

• Revoke Butler's access at any time at myaccount.google.com/permissions. Butler immediately loses the ability to read your calendar.
• Delete the stored credential by deleting Butler's token file from your device, or by uninstalling Butler.
• Event data needs no deletion — it exists only in memory and is gone as soon as the program stops.

Because we never receive your data, there is nothing on our side to request, export, or erase. If you believe otherwise, write to hello@butler.ly and we will respond within 30 days.

10. Children

Butler is not directed at children under 13 and we do not knowingly collect data from them. A family calendar shown on a household screen may of course mention children; that information stays on your device like everything else.

11. Security

Your Google credential is stored with file permissions restricting it to your own user account, and all communication with Google, Spotify, and Telegram uses encrypted HTTPS connections. No system is perfectly secure, and the physical security of the device in your home is your responsibility.

12. Changes to this policy

If this policy changes materially, the effective date above will change and the updated policy will be posted at this address before the change takes effect.

13. Contact

Questions about this policy or about your data: hello@butler.ly.