Privacy policy
Draft. This policy is a draft under review and is not yet in effect. It describes how we intend the JBoards app and service to handle your data.
The short version
- The JBoards app talks to your lighting controllers directly on your home network. In that mode, nothing about your controllers or your show leaves your home.
- If the app crashes, it sends us a crash report so we can fix the bug. It doesn't include your name, your account or anything about your controllers, and you can turn it off.
- We don't run usage analytics, we don't show ads, and we don't sell or share your data for advertising.
- When remote access is available and you turn it on, a small summary of your controllers' status passes through our cloud so you can see and control them away from home and get alerts. Your show itself (lights, sequences, music) never does.
1. Using the app at home (no account)
The app finds JBoards controllers on the network your phone is connected to, and sends your commands straight to them. To do that it needs your phone's permission to use the local network.
What stays on your phone and your controllers, and never reaches us:
- the list of controllers the app has found, their names and network addresses;
- your controllers' settings, schedules, playlists, effects and sequences;
- anything you do in Full settings, which is your controller's own web page.
2. Crash reports
If the app crashes, it sends a crash report through Google's Firebase Crashlytics service. A report contains:
- what the app was doing when it crashed (a technical stack trace and app state);
- the app version, your phone's model and operating system version;
- a random identifier for the installation of the app, so we can tell one crash repeating from many.
It does not contain your name, email address, account, controller names or addresses, or anything you typed. We use crash reports only to find and fix bugs.
You can turn crash reports off in the app's Account settings.
Crash reports are kept for a limited period and then deleted by the service.
3. Remote access and alerts
Remote access is not available yet. This section describes how it will work, so you can decide before you turn it on.
Remote access is off until you turn it on. Turning it on is done at home, from the app, with your phone on the same network as your controllers.
3.1 Your account
To use remote access you sign in to your JBoards account. We receive:
- your email address (if you use Sign in with Apple's "Hide My Email", a relay address instead);
- an account identifier;
- which sign-in method you used.
We don't ask the sign-in provider for your contacts or anything else.
Your JBoards account is the same one you use on this website and at the Enclosure Designer store. It is provided by Supabase. Deleting it deletes it everywhere; see Delete your account.
3.2 Your display and controllers
When you add controllers to remote access, we store:
- the display's name you choose (we suggest not using your street address);
- for each controller: its device identifier (a hardware network address), model, firmware version, the name you gave it, and a public key it created so it can prove who it is to our service;
- which of your controllers connects to our service for the display, and the remote control level you chose on the controllers (View only, Control, or Configure);
- the people you share the display with, and their role.
3.3 Status that passes through our service
One controller per display keeps a connection to our service and sends a status summary: what is playing, brightness, whether outputs are on, health and warning counts, temperature, how long it has been running, and the same summary for the other controllers in the display. It also sends alerts (for example a temperature warning or a show that failed to start) and changes such as a playlist starting.
We keep only the latest status; each new one replaces the last. Alerts are kept for about 30 days so the app can show recent history. A record of commands sent through our service (who sent which command to which controller, and the result) is kept for a limited period for security and troubleshooting.
3.4 What never leaves your home
Even with remote access on, these are never sent to us:
- your show: pixel and channel data, sequences (FSEQ files), audio;
- Wi-Fi passwords and network settings;
- passwords or secrets stored on your controllers (for example webhook secrets);
- your controllers' location (used on the controller for sunset schedules);
- your controllers' local network addresses.
We can't open a general connection into your home network. Our service can pass only a fixed list of commands, and only up to the level you set on the controllers themselves. Network settings and factory reset can never be done remotely.
3.5 Notifications
If you allow notifications, the app registers your phone with Apple's or Google's push service and we store the push token that comes back. We use it only to send you the alerts you chose. Notification messages go through Google's Firebase Cloud Messaging and, on iPhone, Apple's push service.
3.6 Turning it off
Turning remote access off on a controller stops it from sending anything to us. You can also remove a controller or a whole display from your account in the app.
4. This website
This website sets no cookies, runs no analytics or advertising scripts, and has no forms. It is served by Cloudflare, which processes visitors' network (IP) addresses to deliver the pages and protect the site. Purchases are made at the Enclosure Designer store, which handles your order details under its own policies.
5. Who processes your data for us
| Provider | What for | Data |
|---|---|---|
| Google (Firebase Crashlytics) | Crash reports | Section 2 |
| Supabase (Supabase Auth) | Your JBoards account and sign-in | Section 3.1 |
| Google (Firebase Cloud Messaging) | Notifications | Section 3.5 |
| Apple (Sign in with Apple, Apple Push Notification service) | Sign-in, notifications on iPhone | Sections 3.1, 3.5 |
| Cloudflare (Workers, Durable Objects, D1, Pages) | Runs our service and this website, and stores the data in sections 3.2 and 3.3 | Sections 3.2, 3.3 and 4, and the network (IP) addresses of your phone and controller while they are connected |
These providers process data on our behalf under their terms. We don't sell your data or share it for advertising. We don't use it to build advertising profiles.
6. How long we keep data
| Data | Kept |
|---|---|
| Crash reports | A limited period set by the crash-report service |
| Latest controller status | Until replaced by the next one, or until you remove the controller |
| Alerts | About 30 days |
| Command records | A limited period, for security and troubleshooting |
| Account, display and controller records | Until you delete them or your account |
| Push tokens | Until you sign out, delete your account, or the push service tells us the token is no longer valid |
7. Deleting your data
- Without an account: uninstalling the app removes everything it stored on your phone. Crash reports aren't linked to you, so we can't find "yours" to delete; they expire on the schedule above.
- With an account: delete it in the app at Account › Delete account, or follow the steps at getjboards.com/delete-account. Deleting your account removes your displays, your controllers' records, the people you shared with (they lose access), your push tokens and your alerts. Your account is closed on the website and store too: you can no longer sign in, and your name and email are removed. Past store orders are kept without them, for our records. Your controllers keep running their shows; they simply stop connecting to our service. If you signed in with Apple, we also revoke the app's access with Apple. We may keep a limited record where the law requires it, and say so if asked.
8. Your choices and rights
- Turn off crash reports (section 2).
- Turn remote access off on any controller; remove controllers; choose which alerts you get; turn notifications off in your phone's settings.
- Ask us for a copy of the data we hold about you, to correct it, or to delete it: getjboards@gmail.com.
9. Children
The app is not directed at children and we don't knowingly collect their data.
10. Security
The app talks to our service over encrypted connections (HTTPS/TLS), and controllers connect to it only outward, over TLS, proving their identity with a key that never leaves the controller. On your home network the app talks to controllers over plain HTTP, the same way the controllers' own web page does. Passwords and pairing keys the app stores are kept in your phone's secure storage.
11. Changes
If we change this policy, we'll update the effective date above and, for significant changes, tell you in the app before they take effect.
12. Contact
JBoards, getjboards@gmail.com.