Security
What Dislab does to protect your account, your files and your screens, said plainly. Where we haven’t done something yet, this page says so.
Where your data is kept
Your account details, signs, playlists and menus are kept in a database in Sydney, Australia. Your photos, videos and other files are kept in private storage in Oceania. Nothing is public: every file is fetched with a short-lived link, and a screen only receives the files its own playlist uses. Every connection to Dislab uses HTTPS. Our privacy policy lists the services we use and how long each kind of data is kept.
Signing in and who can do what
- Passwords are at least 10 characters. You can also sign in with an emailed link, or with Google.
- Sign-in, sign-up and password reset are protected against bots and guessing, and sign-in attempts are limited by address.
- Everyone in an account has their own login and a role. Owners look after billing and the account. Managers do everything else. Editors change what screens show. Staff only see the phone pages, such as marking an item sold out or moving a queue number. A new feature stays closed to editors and staff until it is deliberately opened to them.
- A person can be limited to some of your locations.
- Signs, playlists and menus show who last changed them, and a sign keeps its recent versions. Deleted signs, playlists, photos and videos wait 30 days in the Bin before they are gone.
Your photos and videos
- Every upload is checked by its first bytes before any tool opens it, then converted for TV in a locked-down worker with a short list of file types and a memory limit.
- Camera location is removed from photos, and the file you uploaded is deleted soon after your TV-ready copy is made.
- Files are stored under a fingerprint of their contents, and a screen checks that fingerprint after it downloads a file.
Your screens
- A screen pairs once, with a short code you type in the console. Nothing is typed on the TV.
- Each screen carries a licence that we sign and the app checks. It is valid until your renewal date plus a few days of grace, and the app guards against the clock being wound back.
- The software that draws signs on the screen arrives in packages we sign. A screen only accepts a package our key signed, so a stolen server could not put its own code on your screens.
- Signs are data, not programs. Colours and values are checked before they are saved, and the screen draws them without building web code from them.
- Live updates, such as a score or a sold-out item, reach only the screens that show them, on a private channel for each screen.
Payments
Cards are handled by Stripe. Dislab never sees or keeps your card number.
Dislab staff
- Our staff sign in with a separate staff login and an authenticator app, never a customer login.
- Every change a staff member makes to an account needs a note and is logged.
- Support can look at an account the way its owner sees it, read only, for 30 minutes at a time. Our designers work in a studio account of their own and send finished work to you to approve.
- Our staff cannot see your guests’ event photos.
Event photos
Photos guests send to an event wall are private to your account. Thirty days after the event ends they leave your console, and you can delete an event and all its photos at once. The guests’ page tells them that you decide what shows and are responsible for the photos.
Deleting your data
You can delete your account in Settings. It removes your data and files and cancels your subscription. Smaller records are tidied on a schedule, which the privacy policy sets out.
What we haven’t done yet
- Dislab has no SOC 2 or ISO 27001 certification. We will pursue one when customers need it.
- Single sign-on for companies is not available yet.
- Two-step sign-in for account owners is planned but not built.
We would rather say this than have you assume.
Reporting a problem
If you think you have found a security problem, email support@dislab.app with what you found and how to reproduce it. Please give us a reasonable time to fix it before you tell anyone else. There are more details in Support.
Questions about security?
Ask us and we will answer plainly, including what is not done yet.