Data processing addendum

How VenueOS processes personal data on behalf of its customers — schools and businesses alike.

Last updated: October 22, 2026

This document is boilerplate drafted for VenueOS and is not legal advice. Review it with your own organization's legal counsel before relying on it.

This Data Processing Addendum ("DPA") forms part of the Terms of Service or other written agreement (the "Agreement") between Twin Oaks Farm & Tech LLC ("VenueOS", "we") and the Customer. It applies whenever we process personal data on the Customer's behalf. Section 10 adds terms that apply only when the Customer is an educational institution. A Customer that needs a countersigned copy, or a state-specific student data privacy agreement, can request one at privacy@venue-os.app.

1. Roles

The Customer is the controller (or "business") of Customer Data that contains personal data, and VenueOS is its processor (or "service provider"). Where the Customer is itself a processor for another party, we act as its sub-processor.

2. Instructions

We process Customer Data only to provide, secure and support the Service under the Agreement, on the Customer's documented instructions (including those given through the Service's settings), or where the law requires it — in which case we will tell the Customer unless the law forbids it. We do not sell or share Customer Data for cross-context behavioral advertising, do not combine it with data from other sources except as needed to provide the Service, and do not use it to train artificial-intelligence models. Annex A describes the processing.

3. Confidentiality and personnel

Personnel with access to Customer Data are bound by confidentiality obligations and receive access only as needed for their role. Access by our personnel to a Customer's organization in the Service requires approval by the Customer's administrators, except time-limited emergency access that is recorded and notified to those administrators immediately.

4. Security

We maintain appropriate technical and organizational measures to protect Customer Data, including: encryption in transit and at rest; role-based access control enforced on every request; separation of each Customer's data; multi-factor authentication available to every user, which the Customer can require for its administrators and for users permitted to send emergency alerts; salted Argon2 password hashing; signed emergency alert messages; immutable audit records of privileged actions; nightly encrypted backups; and processes for reviewing changes and handling vulnerabilities. We may update these measures provided the overall level of protection is not reduced.

5. Sub-processors

The Customer authorizes us to use the sub-processors listed in Annex B. Each is bound by written terms that protect Customer Data at least as strictly as this DPA, and we remain responsible for their performance. We will update Annex B and notify the Customer's administrators at least 30 days before adding or replacing a sub-processor. The Customer may object on reasonable data-protection grounds; if we cannot reasonably accommodate the objection, the Customer may terminate the affected Service and receive a refund of prepaid fees for the remaining term.

Services the Customer chooses to connect (for example its own point-of-sale system, calendar, streaming service, single sign-on provider or its own AI provider key) are the Customer's own providers, not our sub-processors.

6. Assistance and data-subject requests

Taking into account the nature of the processing, we will help the Customer respond to requests from individuals to access, correct, delete or export their personal data, and with data-protection assessments and consultations the law requires. If we receive such a request directly, we will refer the individual to the Customer and will not respond ourselves except as the Customer directs or the law requires.

7. Security incidents

We will notify the Customer without undue delay, and in any event within 72 hours, after becoming aware of a security incident that leads to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Data. The notice will describe what is known about the incident and the steps taken, and we will provide updates as more becomes known. Notice is sent to the Customer's administrators.

8. Return and deletion

During the subscription, administrators can download uploaded files (one at a time or as a ZIP), export the audit log and proof-of-play reports as CSV, and remove content, playlists, screens and users in the Service. A complete export of Customer Data in a machine-readable format is provided on written request to privacy@venue-os.app. After the Agreement ends, the Customer may export its data for at least 90 days; after that, or sooner on written request, we delete Customer Data, except where the law requires us to keep it. Encrypted backup copies expire within 30 days. Audit records may be kept longer where needed for security, safety or legal reasons, and remain protected by this DPA while kept.

9. Audits and information

On written request, no more than once a year (or after a security incident), we will answer reasonable security questionnaires and provide information needed to demonstrate compliance with this DPA. Our hosting providers maintain their own independent security audits, which we can point the Customer to. Any other audit must be agreed in writing in advance and will be conducted at the Customer's cost, with reasonable notice and confidentiality.

10. Educational institutions

This section applies only when the Customer is a school district, school or other educational institution.

  • School official. For personally identifiable information from education records, we are a "school official" with a legitimate educational interest under FERPA (34 CFR § 99.31(a)(1)(i)(B)), under the Customer's direct control regarding its use and maintenance, and we do not re-disclose it except as the Customer directs or the law requires.
  • Student data use. We use student data only to provide the Service. We do not sell it, use it for targeted advertising, build profiles of students except to provide the Service, or use it to train AI models.
  • COPPA. Where the Customer uses the Service with information about children under 13, the Customer consents on behalf of parents for the use and benefit of the school only, and is responsible for the related notices to parents.
  • Directory information. Student names and photos are hidden on public sports screens by default. They are shown only after a Customer administrator confirms that the Customer's directory-information notice and photo releases allow it, and never for a student whose family has opted out. The Customer is responsible for the accuracy of those confirmations.
  • Parent requests. Requests from parents or eligible students are handled by the Customer; we will help as described in section 6.
  • State laws. Where a state student-privacy law requires additional terms, we will work with the Customer on a state-specific agreement, which controls over this DPA where they conflict.

11. Location of processing

Customer Data is stored in the United States. Where the law that applies to the Customer requires a transfer mechanism for personal data leaving another country, the parties will put an appropriate one in place on request.

12. Order of precedence

If this DPA conflicts with the Agreement regarding the processing of personal data, this DPA controls. A separately signed data processing or student data privacy agreement controls over this DPA.

Annex A — Description of processing

  • Subject matter and duration: providing the Service for the term of the Agreement and the export period after it.
  • Nature and purpose: hosting, storing, transmitting and displaying content on the Customer's screens; scheduling; emergency alerting; user authentication; reporting; support.
  • Data subjects: the Customer's authorized users; people who appear in content the Customer uploads; and, for educational Customers, students and staff whose information the Customer chooses to display.
  • Categories of personal data: names, email addresses, roles and sign-in data of authorized users; content the Customer uploads, which may include images of people; screen and network information; audit records.
  • Sensitive data: the Service is not designed for health, financial or other sensitive personal data, and the Customer should not upload it.

Annex B — Sub-processors

ProviderPurposeLocationWhen it receives data
Supabase (on Amazon Web Services)Database and file storage for accounts, settings and uploaded contentUnited States (US East)Always
RailwayApplication service hosting and real-time messaging to screensUnited States (US West)Always
VercelWeb dashboard and screen-player application hosting and deliveryGlobal edge networkAlways
GitHubStorage of encrypted database backupsUnited StatesAlways (encrypted backups only)
ResendTransactional email (sign-in codes, invitations, notifications)United StatesAlways
Forward EmailInbound email forwarding for support@venue-os.app and security@venue-os.app, including the content of messages sent to those addressesUnited States / European UnionWhen someone emails a VenueOS support or security address
SentryError monitoring, with sensitive values removed before sendingUnited StatesAlways
StripeSubscription billing and card payments on Stripe-hosted pagesUnited StatesWhen the Customer pays by card
OpenAI, Google (Gemini) and AnthropicAI features such as generating designs, copy and image descriptionsUnited StatesOnly when an AI feature is used with VenueOS-provided AI
Google Maps PlatformAddress lookup when setting a location, and the Google Reviews appUnited StatesWhen an address is looked up or the Reviews app is used
OpenStreetMap Foundation (Nominatim)Address lookup and weather location lookupEuropean Union / United KingdomWhen a weather location is resolved, or the primary address lookup is unavailable
U.S. Census Bureau GeocoderFallback address lookup (the address being looked up only)United StatesOnly when the primary address lookup cannot find an address
Norwegian Meteorological Institute (MET Norway)Current-hour weather forecasts using the configured coordinates, requested through our APINorwayWhen a widget has a weather location configured
U.S. National Weather ServiceU.S. multi-day weather outlook using the configured coordinates, requested through our APIUnited StatesWhen a U.S. forecast outlook widget is configured
PexelsStock-photo search for AI-designed boards (search words only)GlobalOnly when an AI board design looks for a stock photo
Meta Platforms (Instagram, Facebook)Displaying posts from accounts the Customer connectsUnited StatesOnly when the Customer connects an Instagram or Facebook account

Contact

VenueOS
7575 State Highway 134 E., Columbia, AL 36319
Privacy: privacy@venue-os.app · Security: security@venue-os.app