DirectorLink

Privacy

Last updated 5 November 2026

DirectorLink keeps your home's data between your own devices and your controller. This page lists exactly what reaches DirectorLink's servers.

On your home network

The app talks to the DirectorLink driver on your controller directly, over your home network. Device names, states, commands and camera pictures do not pass through our servers. The app locks each request with its own key there too, so its access key does not travel openly on your Wi-Fi. It keeps that key and the controller's address in your browser only; your preferences (language, theme, favorites, the rooms you hide), scenes and schedules are kept on your controller, shared by your own devices.

If your installer turns on Sonos, your controller also talks to your Sonos speakers, on your home network only: it asks them what plays and passes on your commands. DirectorLink uses no Sonos account and tells Sonos nothing. Away from home, what plays travels locked end to end, like everything else.

The weather

When a schedule uses the weather, or the app shows it, your controller asks Open-Meteo (api.open-meteo.com, a free weather service) for the weather at the location set in your Control4 project, rounded to about a kilometre, for a 5-day forecast every 6 hours (4 times a day). That request goes from your controller straight to Open-Meteo, not through our servers; Open-Meteo sees the location and your home's IP address. Without schedules that use the weather, it is asked only while someone has the app open on Home or on the Schedules page (Home shows the weather since version 1.12.1), and for an hour after.

Update checks

On devices with an admin key, the app asks GitHub (api.github.com) about twice a day, and when an admin taps Check now (at most once a minute), which DirectorLink version is the newest, to say when an update is out. That request goes from the device straight to GitHub, not through our servers: GitHub sees that device's IP address, and nothing about your home is sent. Devices with other access never ask.

Signing in with Google or Apple

Signing in is optional. It is for using your home away from the home network and for inviting family. You can sign in with Google or with Apple. When you sign in, Google or Apple tells us your account ID with them, your email address and your name. Apple's account ID is one Apple makes for DirectorLink only; Apple sends your name only the first time, as you enter it there, and gives us either the email address you choose to share or an address of its Hide My Email relay instead of yours. We ask for nothing else, never see your password, and use these only to know which homes your account belongs to and to match invitations. If you add Apple to your account in the app's Settings (or Google to an Apple account), both sign in to the same DirectorLink account; otherwise each is its own account. We do not sell or share any of it, and there are no ads, tracking or analytics.

Apple tells our servers when you stop using Sign in with Apple for DirectorLink, delete your Apple Account, or turn Hide My Email forwarding off or on. We then remove that Apple sign-in from your DirectorLink account, and sign the account out on every device if it was its only way to sign in, or update the address we keep. Your homes and memberships stay, unless you deleted your Apple Account and it was your account's only way to sign in: then we delete your DirectorLink account, or, if it owns a home, keep it only for that home, without your name and email. An account nobody can sign in to and nobody has signed in to for 90 days goes the same way. Apple sends nothing else, and we send nothing back.

If you open an invitation that was sent to another email address (for example because Apple hides yours), the home's owner is asked to let your account join: they see the name and email address of your account (or that Apple hides it), how it signs in, when it was made and when you asked, with a six-digit code that you read out to them.

If a new device of yours asks to join your home from another device (for example the app on your iPhone's Home Screen), our servers pass between your two devices what the new device calls itself (such as "Safari on iPhone"), a public key from each, and the invitation your other device makes for it, encrypted so that only the new device can open it. We cannot read the invitation. A request works for 10 minutes; it is deleted once used, declined or withdrawn, and otherwise within a day.

A device that has never signed in does not contact our account service until you tap Sign in or open an invitation link. It then asks which ways to sign in are available, without sending anything about you or your home.

What our servers store

Our servers run on Cloudflare, which keeps short-lived technical logs (time, IP address, path and status) to keep the service running.

Remote access

Remote access is off unless you switch it on in Composer. Then the controller keeps one outgoing connection to api.directorlink.io, encrypted with TLS, and your signed-in devices reach your home through it. Every request and answer is also locked end to end, with keys that only your devices and your controller hold: our servers pass them along but cannot read or change them, and store none of them. What our servers do see is which account talks to which home, when, and how much data. Scene links, below, are the one exception.

Scene links

An admin can give a scene a private link, so that a phone's own automations (iPhone Shortcuts, an Android app, an NFC tag) can run it. Such a request cannot be locked end to end: the phone sends the link and its secret to our servers over HTTPS, and they pass them to your controller, which checks them and runs that one scene. So our servers see the link and its secret each time it is used, with when and whether the scene ran, but never which scene it is: they have no names. We keep no secret, and the secret is never in our logs. Each run is in our service logs for a few days: the home, the link's id, the answer, whether the scene ran and how long it took. Whoever has a link can run its scene until an admin removes or replaces it, or revokes the key of the device that made it. A scene that opens doors or gates can never have a link, so a link can switch at most lights, air conditioning, fans, blinds, music and refrigerator settings, and homes without links send nothing of the kind.

A door or gate can instead have a link that asks first. It runs the same way, but opens nothing: your controller asks the person who made it, with a notification locked to their own devices, whether to open the door, and only their tap opens it, as any opening from the app. Our servers then also see whether the link asked, and which of the home's devices the locked notification went to, but never which door it is about or what it says.

Automatic backups

An admin can turn on automatic backups in the app (Settings → Controller → Backup) and set a backup password. Your controller then sends a backup of what DirectorLink keeps (scenes, schedules, preferences, room names, which devices have access, the link to your account) to our servers every night, through the remote access connection. It is encrypted on your controller with a key made from the backup password in your browser; the password itself never leaves your browser, and neither our servers nor your controller can open the backup. We keep the encrypted backup, its size and its date: the last 7 days, one a day, at most 5 MB a home. If the backup password is lost, nobody can open them, DirectorLink included.

Alerts

Anyone with access to a home can switch on alerts for a device: a notification when someone rings at the door, when the refrigerator door is left open, and, for admins, when a door or gate is opened (if they choose), when a schedule had a problem, or when the home has been offline for 10 minutes. Each device chooses which. Your controller decides who gets what, and encrypts what happened (which doorbell, which door and who opened it, which schedule) separately for each of those devices, with a key only that device and your controller hold: our servers pass it on without being able to read it. They learn which devices' keys an alert is for, when, and whether it is a doorbell's, which is kept for a minute only. Every alert has the same size, but whom it is for can tell its kind: our servers know which keys are admins', so an alert that is not a doorbell's and is for someone who is not an admin can only be the refrigerator's. They never learn which doorbell, door or refrigerator, who opened a door, or which schedule. The offline alert is our servers' own: it says only that, at which home (by its id) and when. Alerts are sent through the push service of the device's browser (Google, Mozilla, Apple or Microsoft), encrypted so that only that browser can read them. The push service sees that an alert went to the device, when, how long it may keep it, and its size, which is the same for every alert. The words you see are the app's, on your device.

DirectorLink in numbers

Once an hour our servers count how many homes are linked to an account (a home stays counted until its owner's account is deleted, also once it is no longer used), how many accounts can sign in, and how often the driver was downloaded (from GitHub's public list of releases). Only these three totals are kept. Once there are 25 homes, anyone can read them at api.directorlink.io/v1/stats; until then they are not public. Nothing about any one home or person is in them, and your controller sends nothing for them. When this website's home page opens, it asks for the totals, without cookies or anything about you, and shows them once there are 25 homes.

Cookies

api.directorlink.io sets one cookie that keeps you signed in, and one for ten minutes while you sign in. None can be read by the app's pages. The app and this website set no cookies.

Deleting your data

Signing out ends the session on that device; Sign out everywhere ends it on all your devices. Settings → Account → Delete account in the app deletes your account and signs out all your devices. An admin deletes a home's automatic backups in Settings → Controller → Backup; they also go when the home's owner deletes their account.

Contact

DirectorLink is open source. Questions go to github.directorlink.io/issues.