Security
This page describes how msgbrd.tv secures your data in transit, at rest, and in cache, and how we protect individuals' personal data under India's Digital Personal Data Protection Act, 2023. It is intended to support your security and privacy assessment.
1. Architecture at a Glance
msgbrd.tv is a cloud SaaS platform. We do not run a live per-screen media stream. Screens operate on a lightweight pull model:
- Each screen periodically fetches a small JSON manifest describing what to show, then pulls only the slides it needs.
- Media (images, video) is stored in object storage and delivered from a CDN edge close to the screen — not proxied frame-by-frame through our application servers. Videos are transcoded once and cached.
- Urgent updates (emergency broadcasts) use a small real-time notification with a polling fallback — a control message, not a media stream.
- Screens cache their content on-device, so they keep working through network interruptions.
This minimises the data that flows, offloads heavy content to the edge, and removes single-server bottlenecks — which is how the platform scales.
2. Data in Transit
- All traffic is encrypted with HTTPS/TLS.
- Every screen authenticates with a unique 64-character random token that is never reused.
- Slide content is scoped to the screen: a screen can only retrieve slides belonging to a playlist assigned to it.
- Live/queue data (for example clinic boards) is served through time-limited signed URLs.
- Public endpoints are rate-limited; session requests are protected against CSRF.
3. Data at Rest
- Passwords are stored only as a one-way hash — we cannot read them.
- Media objects are held in object storage with access governed by a bucket policy: only intended media is publicly readable; everything else is private. The storage provider encrypts objects at rest.
- Customer data is logically isolated per organisation so one customer cannot access another's data.
- Full-server backups are captured daily and retained on a rolling 7-day window, after which they are automatically deleted. These backups are stored encrypted at rest by our infrastructure provider (DigitalOcean).
4. Caching and CDN
- Server-side manifest caches are short-lived and keyed per screen token, so cached data cannot be served across tenants.
- CDN-cached slide URLs are scoped to the requesting screen's token — a cached render cannot be delivered to a different organisation.
- On-device caches hold only that screen's own content and are invalidated automatically when content changes.
5. Access Control and Authentication
- Administrative access uses session authentication with role- and permission-based authorisation.
- Accounts are gated by user type; only authorised staff reach administrative functions.
- Every action is scoped to the user's own organisation(s).
6. Privacy by Design at the Screen
Screens display content only. They use no cameras, microphones, sensors, facial recognition, or audience analytics. Screen telemetry is limited to device-level technical data (such as connectivity and playback status) and never captures information about viewers or the physical environment.
7. Sub-processors
We use the following processors, who handle data only on our instructions:
- DigitalOcean Spaces — Media storage (slide images & videos)
- Resend — Transactional email delivery
- Razorpay — Subscription billing & payment processing
- Firebase Cloud Messaging — Push notifications to devices
Each sub-processor operates under its own published data-processing terms, which we accept as part of using their services.
8. Protecting Individuals' Data (DPDP Act, 2023)
Our handling of personal data is governed by our Privacy Policy. In summary: we maintain an internal data map of every personal-data field with its purpose and retention; enforce retention automatically; capture and record consent with easy withdrawal; and support the rights of access, correction, erasure, and nomination. Individuals can raise a grievance with our Grievance Officer and escalate to the Data Protection Board of India. Where a customer displays others' personal data (for example a school displaying a student's name), the customer is the Data Fiduciary and is responsible for lawful basis and consent; msgbrd.tv acts as their Data Processor.
9. Vulnerability Management and Testing
Our software dependencies are automatically scanned for known vulnerabilities on every code change and on a weekly schedule, using Composer's security-advisory database and npm audit, with automated pull requests raised to apply security updates. Identified vulnerabilities are remediated promptly and dependencies are kept current. We do not currently engage an independent third party for penetration testing.
10. Incident Response and Breach Notification
In the event of a personal-data breach we will assess and contain the incident, and notify affected individuals and the Data Protection Board of India in the manner and within the timelines required by the DPDP Act and its rules. Data-protection queries and breach reports can be directed to our Grievance Officer (see section 12).
11. Data Residency
Our servers are operated in India. If you access the platform from outside India, your data may be processed in India.
12. Security Contact
To report a security concern or request more detail for an assessment, contact:
Grievance Officer, msgbrd.tvEmail: [email protected]