1. About this addendum
This Data Processing Addendum ("DPA") applies between Goose Productions (Goose Productions, 550 West B Street, Suite 310, San Diego, CA 92101) ("we", "us") and each organization that uses Setclock ("Customer") whenever we process Customer Personal Data. It is part of the Terms of Use (the "Agreement"). If this DPA conflicts with the Agreement, this DPA controls for the processing of Customer Personal Data; if it conflicts with the Standard Contractual Clauses, the Standard Contractual Clauses control.
Capitalized terms not defined here have the meanings in the Agreement.
2. Definitions
- Applicable Data Protection Laws: privacy and data protection laws that apply to our processing of Customer Personal Data, including the California Consumer Privacy Act as amended by the California Privacy Rights Act and its regulations ("CCPA"), other U.S. state privacy laws, the EU General Data Protection Regulation ("EU GDPR"), the EU GDPR as it forms part of UK law ("UK GDPR") and the Swiss Federal Act on Data Protection ("FADP"), as applicable.
- Customer Personal Data: personal data or personal information in Customer Data, meaning information Customer or its users put into the Service, including Show Content, that we process on Customer's behalf.
- Controller, processor, data subject, processing, business, service provider: have the meanings given in Applicable Data Protection Laws.
- Security Incident: a breach of our security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Customer Personal Data. It doesn't include unsuccessful attempts or activities that don't compromise security, such as pings, port scans, blocked sign-in attempts or denial-of-service attacks.
- SCCs: the standard contractual clauses approved by the European Commission in Implementing Decision (EU) 2021/914.
- UK Addendum: the International Data Transfer Addendum to the SCCs issued by the UK Information Commissioner, version B1.0, in force 21 March 2022.
- Sub-processor: any third party we engage to process Customer Personal Data.
3. Roles and instructions
Customer is the controller (or business) and we are a processor (or service provider) of Customer Personal Data. Where Customer is itself a processor for another controller, we are Customer's sub-processor and Customer is responsible for passing on that controller's instructions.
We process Customer Personal Data only on Customer's documented instructions, which are: the Agreement and this DPA; Customer's and its users' configuration and use of the Service; and any other reasonable written instructions consistent with the Agreement. We'll tell Customer if, in our opinion, an instruction breaks Applicable Data Protection Laws, unless the law prohibits it. We may process Customer Personal Data where the law requires us to, and will tell Customer first unless the law prohibits it.
Customer is responsible for the lawfulness of the personal data it puts into the Service and its instructions, and confirms it has given all notices and obtained all consents and rights needed for us to process Customer Personal Data under the Agreement. Customer won't put special categories of personal data, information about children, or government ID, financial account or health information into the Service.
4. California and U.S. state law terms
When we process Customer Personal Data as a service provider or processor under the CCPA or another U.S. state privacy law, we:
- Won't sell or share it (as those terms are defined in the CCPA), or use it for targeted advertising
- Won't retain, use or disclose it for any purpose other than the business purposes in the Agreement, including for any commercial purpose other than providing the Service, or outside our direct business relationship with Customer
- Won't combine it with personal information we receive from or on behalf of others, or collect ourselves, except as the CCPA permits
- Will comply with the CCPA and give it the same level of privacy protection the CCPA requires of businesses
- Will tell Customer if we can no longer meet these obligations
Customer may take reasonable and appropriate steps to ensure we use Customer Personal Data consistently with its obligations and, on notice, to stop and remedy unauthorized use. We certify that we understand and will comply with these restrictions.
5. Confidentiality of our people
We limit access to Customer Personal Data to people who need it to provide, secure or support the Service, and make sure they're bound by confidentiality obligations. Access to an organization's shows for support requires that organization's permission, is time-limited and is recorded in an audit log that can't be edited.
6. Security
We implement and maintain the technical and organizational measures in section 17 (Annex 2), which are designed to protect Customer Personal Data against Security Incidents and to keep it confidential, available and intact. We may update these measures as long as the overall level of protection isn't reduced. Customer is responsible for the security of its accounts and devices, including using two-step sign-in, setting PINs or allowed networks for screens and managing who it invites.
7. Sub-processors
Customer gives us general authorization to engage the Sub-processors listed in section 18 (Annex 3). We'll impose data protection terms on each Sub-processor that are at least as protective as this DPA, to the extent applicable to its services, and we remain responsible for their performance of those obligations.
Before we add or replace a Sub-processor, we'll update the list on this page and notify owners by email or in Setclock at least 15 days in advance. Customer may object on reasonable data protection grounds within that period by emailing setclock@gooseproductions.co. We'll work with Customer in good faith to resolve the objection; if we can't, Customer may end its use of the affected part of the Service as its sole and exclusive remedy.
8. Requests from individuals
If we receive a request from an individual about Customer Personal Data, we'll pass it to Customer without responding to it ourselves, except to confirm it relates to Customer. The Service lets Customer find, correct and delete Customer Personal Data and download show reports. Where Customer can't do something through the Service, including exporting its data, we'll provide reasonable assistance, taking into account the nature of the processing.
9. Security incidents
We'll notify Customer without undue delay, and in any event within 72 hours, after we confirm a Security Incident affecting Customer Personal Data. We'll provide the information reasonably available to us to help Customer meet its own obligations, including the nature of the incident, the categories and approximate number of people and records affected, likely consequences and the measures taken or proposed, and update Customer as we learn more. We'll take reasonable steps to contain and remedy the incident. Notifying or responding to a Security Incident is not an acknowledgement of fault or liability.
10. Assessments and consultations
Taking into account the nature of the processing and the information available to us, we'll give Customer reasonable assistance with data protection impact assessments and prior consultations with supervisory authorities that Applicable Data Protection Laws require of Customer in relation to the Service.
11. Audits
We'll make available the information reasonably necessary to demonstrate our compliance with this DPA. Customer agrees to exercise any audit right by asking us, no more than once every 12 months, to answer a reasonable written security questionnaire and provide relevant documentation. An on-site audit may take place only where required by a supervisory authority or following a Security Incident affecting Customer Personal Data, on at least 30 days' written notice, during normal business hours, without disrupting our operations, subject to confidentiality obligations, and at Customer's expense. Audit rights under the SCCs are exercised in this way.
12. International transfers
We may process Customer Personal Data in the United States and in other countries where we or our Sub-processors operate. For any transfer of Customer Personal Data from the EEA, the UK or Switzerland to a country without an adequacy decision, the parties agree that:
- EEA: the SCCs are incorporated by reference, using Module Two (controller to processor) and, where Customer is a processor, Module Three (processor to processor). Clause 7 (docking) applies; under Clause 9(a), Option 2 (general written authorization) applies with the notice period in section 7 of this DPA; the optional wording in Clause 11 doesn't apply; under Clause 17 the SCCs are governed by the laws of Ireland; under Clause 18 disputes go to the courts of Ireland; and Annexes I and II of the SCCs are completed with sections 16 and 17 of this DPA. The competent supervisory authority is the one determined under Clause 13.
- United Kingdom: the SCCs apply as amended by the UK Addendum, which is incorporated by reference. Table 1 is completed with the parties' details in this DPA, Table 2 with the modules and options above, Table 3 with sections 16 to 18 of this DPA, and in Table 4 either party may end the UK Addendum as set out in its Section 19.
- Switzerland: the SCCs apply with these changes: the Swiss Federal Data Protection and Information Commissioner is the competent supervisory authority for transfers under the FADP; references to "Member State" include Switzerland, so data subjects there can enforce their rights in their place of habitual residence; and references to the GDPR include the FADP.
If a transfer mechanism is invalidated or replaced, we'll work with Customer to put an appropriate alternative in place.
13. Return and deletion
Customer can delete its Show Content in the Service at any time, and Customer's users can delete their own accounts in Profile. Customer can ask us for an export of its Customer Personal Data at any time, including within 30 days after its account ends. After that, we'll delete Customer Personal Data, except copies in backups (deleted as backups expire on their normal schedule) and anything the law requires us to keep, which remains protected by this DPA for as long as we hold it.
14. Liability
Each party's liability arising out of or relating to this DPA, including the SCCs to the extent the law permits, is subject to the limitations and exclusions of liability in the Agreement, and any reference to a party's liability there means the aggregate liability of that party under the Agreement and this DPA together.
15. Changes
We may update this DPA to reflect changes in Applicable Data Protection Laws, a regulator's guidance or our Sub-processors, or to add protections. If a change materially reduces Customer's protections, we'll notify owners at least 30 days in advance, as the Agreement describes.
16. Annex 1: Details of the processing
| Item | Details |
|---|---|
| Parties | Data exporter: Customer, as controller (or processor), contact as given in its organization profile. Data importer: Goose Productions, Goose Productions, 550 West B Street, Suite 310, San Diego, CA 92101, setclock@gooseproductions.co, as processor (or sub-processor). |
| Data subjects | Customer's users; performers and artists; crew, staff and contractors; promoters, venue and supplier contacts; and people who view or control Customer's screens |
| Categories of personal data | Names and stage names; contact details, including users' email addresses and mobile numbers; roles; set times and schedules; notes and technical requirements; messages sent to screens; logos, images, videos and fonts, including sponsor logos and lineup board backgrounds; lineup photos (processed transiently); questions to the AI assistant and the show and support-conversation summaries sent with them; support conversations with Setclock staff; device names, IP addresses and browser details of screens; paired lineup board screens (screen name, device identifier, browser and a one-way fingerprint of the device secret); green room camera stream links and NDI source names, and the NDI source names screens find on Customer's network; the names of devices that send local link updates; activity history |
| Crew access data | Crew phone identifiers, access-key fingerprints, device descriptions, last-seen times, notification tokens and choices, and hashed network fingerprints for wrong PIN attempts; removed when access is revoked, renewed or expires |
| iOS notification data | Device/activity tokens, notification preferences, muted show identifiers, notification text and Lock Screen countdown artist, set type, timing, status, next act and cue, delivered only when the user enables these features |
| Special categories | None. Customer agrees not to put them into the Service. |
| Frequency | Continuous, for as long as Customer uses the Service |
| Nature and purpose | Hosting, storage, synchronization, display and transmission to Customer's screens and users, including directly between Customer's devices over the local network or Bluetooth, encrypted for each paired screen, when the internet is unavailable (local link); public display of Customer's lineup, branding and sponsor logos on the lineup boards Customer sets up; extracting draft lineups from photos Customer uploads; answering questions in the AI assistant; backups; security; support. Solely to provide the Service under the Agreement. |
| Duration and retention | The term of the Agreement and the deletion period in section 13 of this DPA |
| Transfers to Sub-processors | As listed in Annex 3, for the same nature, purpose and duration |
17. Annex 2: Security measures
- Encryption: all connections use HTTPS (TLS). Data is stored with our providers' encryption at rest.
- Access control: database rules isolate each organization's data; roles (owner, admin, stage manager, viewer) limit what each person can do; screen links can require a view or control PIN and allowed networks.
- Authentication: passwords, PINs and paired screen secrets are stored only in hashed form; two-step sign-in with an authenticator app is available to everyone, can be required by an organization, and is required for our staff to take account or support actions.
- Invites: invite links are single-use, tied to one email address, expire, and are stored only as fingerprints.
- Staff access: limited to people who need it; support sessions need the organization's permission, have a reason and time limit, show a banner and notify owners.
- Logging: an audit log of administrative and owner actions, including who, when and from where, that no one can edit.
- Abuse prevention: bot checks, rate limits per network and blocking of throwaway email domains on public forms.
- Resilience: managed database backups by our infrastructure provider; screens keep running from a local copy if the network fails.
- Development: changes are reviewed and tested, including automated security and accessibility checks, before release.
- Incident response: a process to investigate, contain and notify, as described in section 9 of this DPA.
18. Annex 3: Sub-processors
| Sub-processor | Purpose | Location |
|---|---|---|
| Lovable | Application hosting, database, sign-in, file storage, email delivery and AI gateway (Lovable Cloud); also stores anonymous native app free-timer counts separately from Customer Personal Data | United States and European Union |
| Supabase | Database, authentication, storage and real-time infrastructure behind Lovable Cloud, including storage of anonymous native app free-timer counts | United States and European Union |
| Google (Firebase Cloud Messaging) | Deliver enabled native iOS notifications and Lock Screen countdowns using device tokens and notification/countdown content | United States and other countries where Google operates |
| Apple | Apple Push Notification service delivers enabled iOS notifications and Live Activity updates, receiving device/activity routing tokens and notification/countdown content; Sign in with Apple, for users who choose it | United States and other countries where Apple operates |
| Cloudflare | Network, hosting and security for the Service, through Lovable; receives all traffic to the Service, including IP addresses | Global network, including the United States and European Union |
| Automattic (Gravatar) | Profile pictures for Customer's users who haven't turned them off; receives a one-way hash of the user's email address and the viewer's IP address | United States |
| Open-Meteo and the U.S. National Weather Service | Weather and official alerts on Customer's screens, when Customer turns weather on; receive the venue location and the screen's IP address | Open-Meteo: Europe; National Weather Service: United States |
| Gemini AI model, used only to read lineup photos Customer uploads and return a draft, and to answer questions Customer's users ask the AI assistant. Google Sheets, from which the Service downloads the sheets Customer chooses to import or follow. Google Fonts, which serves fonts to Customer's screens (monitors, lineup boards and pairing screens) that use a Google font or show Hebrew, Arabic or Japanese, and so receives those screens' IP addresses and browser details | United States |