Privacy policy
Fluxgrid is made by Lonely Binary in Sydney, Australia. This page says what we keep about you, what we read from the accounts you connect, and how to take it away. Last updated 11 October 2026.
What we keep
- Your account: your email address, and the name Google or Apple gives us if you sign in with them. We email a sign-in code through our email provider, and a human check (Cloudflare Turnstile) runs on the sign-in form.
- What you make: your screen designs, the photos you upload, the screens you pair (their identity and what they last reported), your IoT dashboards and the readings they send.
- Cookies: one to keep you signed in, and short-lived ones while you sign in or connect an account. We do not use advertising or analytics cookies or scripts.
The accounts you connect
A screen can show your tasks and your calendar. You connect an account once, in a small window on the service's own page, and you can disconnect it at any time. Fluxgrid asks for read-only access: it never creates, changes or deletes anything in those accounts.
| Service | What we read | Permission |
|---|---|---|
| Todoist | The names and due dates of your open tasks, and your project names (to choose one) | Read tasks (data:read) |
| Microsoft (To Do, Outlook calendar) | Your To Do lists and the names and due dates of their open tasks; your calendars' names and the title, start, end, all-day flag and cancelled / declined / private state of your upcoming events; your name, for “Connected as” | Tasks.Read, Calendars.Read, User.Read |
| Google (Calendar, Tasks) | Your calendars' names and the title, start, end, all-day flag and cancelled / declined / private state of your upcoming events; your task lists' names and the titles and due dates of your open tasks | Read events, the calendar list and tasks, all read-only |
What we do with it
- We turn it into a few lines of text — “Today 09:00 Standup” — and show them on your own screens and in the preview in your editor. That is the only use.
- The tasks and events themselves are not saved in our database. They are fetched when a screen needs them and held only in the server's memory, reused for about a minute and then replaced by the next fetch.
- The line of text last sent to a screen is kept by our message broker so that a screen that reconnects shows it at once. The next update replaces it.
- The permission we keep is an access token and a refresh token, encrypted (AES-256-GCM) in our database, and the name of the account for “Connected as”.
- We do not sell it, rent it, use it for advertising, or share it with anyone. We do not use it to train any machine-learning or AI model. People at Lonely Binary do not read it, except where that is needed to keep the service secure, to follow the law, or because you asked us to.
Google user data
Fluxgrid'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.
Who else is involved
- Hosting: our servers are in the United States.
- Email: sign-in codes are sent through Resend.
- Sign-in: Google and Apple, if you choose them.
- The services you connect: Todoist, Microsoft and Google receive the requests we make to read your data, under their own privacy policies.
- Telegram: only if you link a Telegram chat to a screen; the messages you send to our bot are shown on that screen.
Removing it
- Disconnect a service from the list's settings in the editor. We delete the stored tokens at once, and the screens stop showing that data.
- Take back the permission at the service too: Google, Microsoft (personal accounts) or Microsoft (work or school), and Todoist under Settings → Integrations.
- Delete your account and everything in it by emailing office@lonelybinary.com from the address you signed up with.
Changes and questions
If this changes, the date above changes and the new version is here. Questions: office@lonelybinary.com. See also support.