Last updated: 11 August 2026
Who we are
This website is operated by LRB Solutions Ltd, doing business as LRB Solutions. Our address is Unit 2, 501 45 Street West, Saskatoon, SK S7L 5Z9, Canada. Privacy questions can be sent to info@lrbsolutions.ca.
Information submitted through the website
When someone sends a consultation or quote request, we receive the information they choose to provide, such as their name, email address, business name, service selection, message or product list, and an optional phone number.
We use this information to respond to the inquiry, prepare a quote, and discuss the requested service. Selecting the optional phone or text consent box allows LRB Solutions Ltd to contact that person about that inquiry. If it is not selected, we use email.
Services used to deliver inquiries
The inquiry form uses WPForms. Notifications are delivered through Brevo to LRB Solutions’ Google Workspace mailbox. Brevo processes the message content to deliver it, keeps a transactional delivery log for one month, and is configured not to retain full-content email previews in those logs for new transactional emails. Hostinger provides the website hosting.
We do not use external analytics or advertising-tracking services.
Retention
Quote and contact inquiries are intended to be kept for up to 12 months, unless they become part of an active customer or service record or must be retained for legal, accounting, security, or record-keeping reasons.
Store, payments, and delivery
Online checkout and payment processing are not open. Payment and carrier shipping providers will be added to this notice before those services are made available to customers.
Essential website functions
WordPress and WooCommerce may use essential cookies or similar browser storage for functions such as site administration, account access, cart operation, and security. We do not currently use external analytics or advertising cookies.
Questions and requests
To ask about personal information provided to LRB Solutions, request a correction, or request deletion where permitted, email info@lrbsolutions.ca. We aim to acknowledge requests within five business days. This is an acknowledgement target, not a promise that every request will be completed in that period.
LRB Screens (dashboard and television players)
1. Who we are
LRB Screens is a digital signage service operated by LRB Solutions Ltd., registered in Saskatchewan, Canada. Business and mailing address: Unit 2, 501 45 Street West, Saskatoon, Saskatchewan S7L 5Z9, Canada.
LRB Solutions Ltd. is accountable for the personal information under its control, and uses service providers (§7) to operate the service.
Privacy and support contact: help@lrbsolutions.ca. For privacy matters, please use the subject line “Privacy Request” so your message is routed and tracked as one.
2. In short
The plain-language summary. The rest of this policy is the detail behind each sentence.
- The televisions transmit operational device data only. The TV player has no accounts and no sign-in. Its application request bodies carry exactly five things — a random app-generated identifier, a short-lived pairing secret, its device credential, its software version, and which published menu it is showing — none of them derived from hardware or any person (§4). The request bodies carry no name, no location data, no hardware identifier and no advertising identifier.
- Network connections carry network information, as they always do (§4.3). As with any internet-connected service, the application server and hosting provider receive network connection information such as the source IP address. The pairing endpoint uses the source IP transiently to generate a keyed, opaque rate-limit value. The LRB Screens application does not store the raw source IP in its application database. Hosting providers may process connection metadata in their service logs under their applicable terms.
- Dashboard accounts are where personal information lives: a head-office user’s email address, name if provided, role and brand, plus a security audit trail that records actions with the request’s IP address and browser details (§5).
- We use this information to run the service — sign staff in, pair televisions, deliver published menus, show device status — and to keep each brand’s data isolated and secure. Nothing else (§6).
- Three service providers help us operate: Supabase (database, authentication, file storage — hosted in Canada), Hostinger (the dashboard application — hosted in the United States), and Google/Gmail (delivery of invitation and password emails). Service data may be processed in both Canada and the United States (§7).
- We do not sell personal information, show advertising, profile people, or use third-party analytics — in the dashboard or on the televisions (§5.2).
- To ask about, correct, or delete your information, email help@lrbsolutions.ca with the subject line “Privacy Request” (§9). If we cannot resolve your concern, you may complain to the Office of the Privacy Commissioner of Canada (§9.3).
3. What this policy covers
Two pieces of software, which handle very different data:
- The dashboard (
screens.lrbsolutions.ca) — a web application used by a restaurant brand’s head-office staff to manage locations, screens and menu images. Dashboard users have accounts. This is where personal information lives. - The TV player — an application installed on televisions in restaurant locations. It has no accounts, no sign-in, and no users in the ordinary sense. It is an unattended appliance that displays menu images, and it handles operational device data only.
The distinction matters throughout: the player is engineered not to know who anyone is.
4. The TV player — operational device data
4.1 What the player sends
The player transmits exactly the following, over HTTPS, to the dashboard’s device API:
| Data | What it is | When |
|---|---|---|
| Installation identifier | A random identifier (UUID) generated by the app on first run. It is derived from nothing — not the hardware, not the network, not any account — and a reinstall generates a new one. | During pairing |
| Pairing secret | A random, short-lived secret used once to pair the television with a screen. | During pairing |
| Device token | A random per-device credential issued at pairing. The server stores only a cryptographic hash of it; the token itself is shown to the device once and is not retrievable afterwards. | With each request after pairing |
| App version | The player software version (for example “0.3.0”). | Periodic status report |
| Content version and release identifier | Which published menu content the television is currently showing. | Periodic status report |
4.2 What the player deliberately does not collect
The player’s application request bodies carry exactly the five fields in §4.1 and nothing else (the network layer additionally carries connection information — see §4.3). None of the five names, describes or is derived from a person, and the installation identifier is random rather than drawn from the device. Specifically excluded from the request bodies, as an engineering decision recorded in the source code:
- No names, emails, accounts or sign-ins — none exist in the player
- No location data
- No serial numbers, MAC addresses, Android ID, or advertising identifiers
- No network details
- No microphone, camera, contacts, photos or files — the app requests no such permissions (its only Android permissions are internet access and starting after reboot)
- No analytics, advertising or crash-reporting software of any kind — the app contains no third-party data-collecting components
The player reads the television’s make, model and operating-system version for display on its own screen only (so an installer can identify the unit); these facts are not transmitted.
4.3 Network addresses
As with any internet-connected service, the application server and hosting provider receive network connection information such as the source IP address. The pairing endpoint uses the source IP transiently to generate a keyed, opaque rate-limit value. The LRB Screens application does not store the raw source IP in its application database. Hosting providers may process connection metadata in their service logs under their applicable terms.
Dashboard requests are different and are described in §5: the dashboard’s audit trail records the request IP address and browser user-agent for signed-in staff actions, with the redaction schedule in §8.
5. The dashboard — user account data
5.1 What we collect
Dashboard accounts exist for a brand’s head-office staff and for LRB Solutions Ltd. administrators. For each account:
- Email address (sign-in identity; also present in invitation records while an invitation is outstanding — invitations expire after one hour)
- Full name, if provided
- Role and brand (tenant) association
- Authentication data managed by our infrastructure provider: password credentials (stored hashed by Supabase Auth, never readable by us), session tokens, and for LRB Solutions Ltd. administrators, multi-factor authentication enrollment (required to reach administrative functions)
- Audit records. Security-relevant actions (sign-ins, content changes, publications, administrative actions) are recorded with a timestamp, the action, the actor’s pseudonymous account identifier and role, the affected item, and the request’s IP address and browser user-agent string
- Terms and privacy acceptance records. When your business accepts our terms of service — by signed order form or in-product — and when a user acknowledges the privacy policy or account rules, we record: the signer or acceptor’s name and business email, the authority confirmation (for terms acceptance), the document type and version, the acceptance time, the acceptance method and any order-form reference, and — when acceptance happens electronically — the request’s IP address and browser details. Purpose: proving the agreement, administering customer accounts, and resolving disputes. IP and browser details follow the same 24-month redaction schedule as audit records (§8). The signer’s name, business email and contractual acceptance record are retained for the life of the LRB Screens service so we can prove the agreement, administer the account and resolve disputes.
5.2 What the dashboard does not do
- No advertising, no ad networks, no tracking pixels
- No third-party analytics
- No sale of personal information, ever
- No profiling or automated decision-making about individuals
6. Purposes
We use the data above to:
- Operate the service — authenticate staff, pair televisions, deliver the menu images a brand has published, and report device status back to that brand’s dashboard
- Keep tenants isolated and detect misuse — the audit trail and rate-limiting exist for security
- Support and troubleshoot — device status data tells a brand which television is offline
- Meet legal obligations
We do not use the data for anything else. There is no advertising use, no marketing use without consent, and no secondary analysis.
7. Processors, hosting, and where data is processed
Personal information is processed on our behalf by:
| Provider | Role | Location |
|---|---|---|
| Supabase | Database, authentication and file storage | Canada — AWS ca-central-1 (Montreal) |
| Hostinger | Hosts the dashboard web application (Managed Web App) | Massachusetts, United States |
| Google (Gmail) | Delivers transactional email — account invitations and password resets — via the SMTP configuration of our authentication provider | Google processes email-delivery data under its applicable service terms; we do not control or represent where Google processes it |
Service data may therefore be processed in both Canada and the United States. The system of record — the database, authentication data and uploaded images — is hosted in Canada; the dashboard application that processes requests runs in the United States; and email delivery passes through Google. While in another jurisdiction, data is subject to that jurisdiction’s laws and may be accessible to its authorities under lawful process.
Uploaded menu images are stored in private storage; they are served only through short-lived signed links to authenticated dashboard users and to paired televisions.
8. Retention
- Dashboard accounts persist until deleted by an administrator or at the account holder’s request (§9).
- Audit records are kept for the life of the platform in minimized form. Personal detail within them — IP address, user-agent, email addresses and name-bearing labels — is redacted once a record is 24 months old. What remains afterwards is a pseudonymous security skeleton: timestamp, action, role, affected item, and an internal account identifier.
- Publication history (which menu was published, when, by which pseudonymous account) is retained for the life of the platform as the authoritative record of what appeared on screens; name-bearing attribution snapshots in it are redacted on the same 24-month schedule.
- Device records persist until the television is unpaired or its screen is deleted, at which point the device credential is revoked. A television that is factory-reset or has the app reinstalled abandons its old identifier entirely.
- Pairing sessions are short-lived and expire in minutes.
- Acceptance records (§5.1) are kept as evidence of agreement. Their IP and browser details are redacted on the same 24-month schedule as audit records. The signer’s name, business email and contractual acceptance record are retained for the life of the LRB Screens service so we can prove the agreement, administer the account and resolve disputes.
9. Your rights: access, correction, deletion, complaints
9.1 Making a request
Requests go to help@lrbsolutions.ca with the subject line “Privacy Request”.
- Access and correction. Dashboard users may request a copy of the personal information we hold about them and correction of anything inaccurate. Name and email are also directly visible to the user in the product.
- Deletion. Dashboard accounts can be deleted on request, subject to what we must retain: audit and publication records keep their pseudonymous form (with personal detail redacted on the schedule in §8).
- The TV player holds nothing to request. A television’s data consists of the operational fields in §4; unpairing the device revokes its credential, and deleting its screen removes its records.
- We aim to respond within 30 days of receiving a request, and sooner where we can. If a request is complex and we need longer, we will say so before the 30 days are up, with the reason.
9.2 Accounts arranged by an employer
Most dashboard users are employees of a restaurant brand using accounts their employer arranged.
9.3 If you are not satisfied — complaining to the OPC
Contact us first at help@lrbsolutions.ca (subject “Privacy Request”) — most concerns are fastest resolved directly, and the Office of the Privacy Commissioner of Canada itself recommends raising a concern with the organization before escalating.
If we cannot resolve your concern, you may contact the Office of the Privacy Commissioner of Canada, which can help resolve privacy complaints about organizations: https://www.priv.gc.ca/en/report-a-concern/
10. Security
Measures in place, stated factually:
- All transmission over HTTPS/TLS; the player refuses non-HTTPS configuration in release builds
- Tenant isolation enforced in the database itself (row-level security), so one brand’s staff cannot read another brand’s data
- Device credentials stored server-side only as cryptographic hashes; on the television, the credential is encrypted with a hardware-backed key where the platform provides one
- Private storage with short-lived signed links; no public file access
- Pairing codes are short-lived, single-use and rate-limited
- Multi-factor authentication required for LRB Solutions Ltd. administrative functions
- An in-database audit trail whose records cannot be altered or deleted by application code
- A documented incident-response procedure, including breach notification
11. Risks, stated honestly
No online service can promise that nothing will ever go wrong, and we do not promise that. The safeguards in §10 reduce the risks below; they do not eliminate them.
- Unauthorized access. Despite access controls and tenant isolation, a vulnerability or a compromised credential could expose data to someone who should not see it.
- Phishing and account misuse. A dashboard account is only as safe as its credentials. If a head-office user’s email or password is compromised, their account could be misused until it is secured.
- Disclosure of business-user information. The personal information we hold is limited (§5) — chiefly work contact details and the audit trail — but a breach of it would still disclose who works on a brand’s signage and what actions they took.
- Operational disruption. An outage or attack could interrupt the dashboard or the service. Connectivity loss may interrupt synchronization, reporting or content availability. Recovery behaviour depends on the device, platform version and deployment configuration.
- Reputational harm. For a restaurant brand, an incident involving its dashboard or screens could cause embarrassment or loss of trust even where no sensitive personal data is involved.
If an incident creates a real risk of significant harm, our incident-response procedure includes notifying affected brands and individuals and, where the law requires it, the Privacy Commissioner.
12. Children
The service is a business tool for restaurant brands. It is not directed at children, offers no child-directed content, and we do not knowingly collect personal information from children. The televisions display menu images to the public but collect nothing from viewers — the player has no camera, microphone or input surface facing the public.
13. Canadian law: PIPEDA and Quebec
We operate from Saskatchewan and host the system of record in Canada.
- PIPEDA is our baseline federal framework. The self-review checklist below assesses this draft against the OPC’s published guidance.
- Quebec (Law 25). LRB Solutions Ltd. has no current or imminent operations in Quebec, and no current brand operates there. Serving any brand that operates in Quebec requires reassessing this policy against Law 25 first — including the designated privacy officer requirement, privacy impact assessments, and Law 25’s breach-notification provisions. This reassessment is a recorded precondition, not an afterthought.
14. Changes to this policy
If we change this policy, we will update the effective date and notify brands through both a dashboard notice and email to head-office administrators, at least 30 days before material changes take effect. Where a change would use personal information for a new purpose or in a way that requires it, we will seek fresh consent rather than relying on notice alone.
15. Contact
help@lrbsolutions.ca — subject line “Privacy Request” for privacy matters. Postal address: LRB Solutions Ltd., Unit 2, 501 45 Street West, Saskatoon, Saskatchewan S7L 5Z9, Canada.