Security
How xPi Digital Signage protects your account and your organisation’s data, which companies handle that data, and how long it is kept.
How the service protects you
- Encryption in transit
- The console and the service are reached over HTTPS, and the console tells browsers (HSTS, for two years) to refuse a plain-HTTP connection to it. Where the service has a password key set up, passwords are also sealed in the browser with its public key before they are sent.
- Passwords
- Stored only as bcrypt hashes, never as the password itself.
- Two-factor sign-in and passkeys
- Accounts can add an authenticator app, with ten one-time recovery codes, and passkeys. An organisation’s Owner or Admin can require two-factor sign-in of everyone in it, or in it and every organisation under it.
- Separation between organisations
- Lists are limited to the signed-in account’s own organisation and the organisations under it. The exception is xPi Team staff accounts, which run the platform and can see every organisation.
Reporting a vulnerability
Write to [email protected] with what you found and the steps to reproduce it. Please do not read, change or delete data that is not yours, and give us time to fix the problem before you publish it.
Subprocessors
The companies the service runs on, and what each one does.
- Railway
- Runs the console and the service behind it.
- MongoDB
- Database for screens, content, playlists, layouts, schedules and the change log.
- Backblaze B2
- Stores the files you upload, which screens download to play.
- Cloudflare
- Carries traffic to the service, runs the sign-in security check (Turnstile) and caches the media files screens download.
- Resend
- Sends the service’s email, such as one-time codes, invitations and password-reset links.
- Razorpay
- Takes subscription payments.
- Better Stack
- Checks from outside that the service is up.
- Doxper
- Only for an organisation whose QMS has the Doxper integration switched on: supplies the patients its queue calls.
Services used only by a feature
These are called only when someone uses the feature that needs them, and receive only what is listed.
- OpenWeather
- Receives the place a weather app is set to show.
- Pixabay
- Receives the words you search the stock library for.
- Google, Meta and Microsoft
- Only when someone in your organisation connects one of these accounts under Connections; the service then reads what that connection allows.
How long data is kept
The periods after which the service deletes these records on its own.
- Sign-in history
- 365 days
- Notifications
- 90 days, and at most the newest 500 per person in each organisation
- Change log (who changed what)
- 365 days
- Play reports
- 396 days (13 months)
- Screen history
- 365 days unless the organisation’s Owner sets 30 to 730; a deleted range can be restored for 90 days
- Screen positions
- 30 days; after that only each screen’s latest position, and none once its organisation switches reporting off
- QMS patient names, phone numbers and UHIDs
- 30 days unless the organisation sets 1 to 365
Erasing a person deletes their account, memberships, sessions, passkeys and sign-in history at once. The change log keeps its entries about them for its period above, to meet a legal obligation.