ReactionSaaS Inc.
Data Processing Addendum
- Version
- 2026-11-13
- Status
- Draft — effective on launch
- Last updated
- November 13, 2026
This Data Processing Addendum (“DPA”) forms part of the Terms of Service between ReactionSaaS Inc. (“ReactionSaaS”) and the Customer that accepted them. It applies automatically when you accept the Terms; no separate signature is needed. Customers that need a countersigned copy can request one from legal@reactionsaas.com.
1. Scope and roles
This DPA applies when ReactionSaaS processes Customer Personal Data to provide the Services. For Customer Personal Data, Customer is the controller (or “business”) or a processor acting for its own customers, and ReactionSaaS is the processor (or “service provider”), or a sub-processor where Customer is itself a processor. This DPA does not apply to Account Data, which ReactionSaaS handles as a controller under its Privacy Policy.
2. Definitions
- “Data Protection Laws” means all privacy and data protection laws that apply to the processing of Customer Personal Data under the Terms, including the California Consumer Privacy Act as amended by the California Privacy Rights Act and its regulations (“CCPA”), other U.S. state consumer privacy laws, the EU General Data Protection Regulation (“GDPR”), the UK GDPR and Data Protection Act 2018, and the Swiss Federal Act on Data Protection.
- “Customer Personal Data” means personal data or personal information within Customer Data that ReactionSaaS processes on Customer’s behalf.
- “Security Incident” means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Customer Personal Data.
- “Subprocessor” means a third party that ReactionSaaS engages to process Customer Personal Data.
- “SCCs” means the Standard Contractual Clauses approved by European Commission Implementing Decision (EU) 2021/914.
- Terms such as “controller,” “processor,” “data subject,” “processing,” “business,” “service provider,” “sell” and “share” have the meanings given in the applicable Data Protection Laws. Other capitalized terms have the meaning given in the Terms.
3. Customer responsibilities
Customer is responsible for:
- having a lawful basis and giving all notices for the processing, including the notice and consent duties for camera and audio recording in Section 7 of the Terms;
- the accuracy and lawfulness of Customer Personal Data and of its instructions;
- not configuring the Services to collect special-category or sensitive data (such as health data or government identifiers), data about children, or biometric identifiers, none of which the Services are designed to process; and
- responding to data subjects’ requests, with our help as described below.
The Terms, Customer’s configuration of the Services and Customer’s use of the dashboard and APIs are Customer’s complete documented instructions. Additional instructions require written agreement. ReactionSaaS will tell Customer if, in its opinion, an instruction breaches Data Protection Laws.
4. CCPA service-provider terms
For Customer Personal Data subject to the CCPA, ReactionSaaS acts as a service provider and:
- processes it only for the limited and specified business purposes of providing, securing, supporting and improving the Services for Customer, as described in the Terms and Annex 1;
- does not sell or share it (including for cross-context behavioral advertising);
- does not retain, use or disclose it for any purpose (including any commercial purpose) other than those business purposes, or outside the direct business relationship with Customer, except as the CCPA permits;
- does not combine it with personal information it receives from or on behalf of anyone else, or collects from its own interactions with consumers, except as the CCPA regulations permit for business purposes;
- complies with the CCPA and provides the same level of privacy protection the CCPA requires of businesses;
- notifies Customer if it determines it can no longer meet its CCPA obligations, and allows Customer to take reasonable and appropriate steps to stop and fix unauthorized use;
- allows Customer to take reasonable steps to ensure that it uses Customer Personal Data consistently with Customer’s CCPA obligations, as described in Section 10; and
- if it receives deidentified data, keeps it deidentified, publicly commits not to re-identify it, and passes these duties on to anyone it shares it with.
ReactionSaaS certifies that it understands and will comply with these restrictions. The same commitments apply under other U.S. state privacy laws that use “processor” terms.
5. Processor obligations (GDPR Article 28)
ReactionSaaS will:
- process Customer Personal Data only on Customer’s documented instructions, including for transfers, unless the law requires otherwise (in which case it will tell Customer first unless the law forbids it);
- ensure that people authorized to process Customer Personal Data are bound by confidentiality;
- implement the technical and organizational measures in Annex 2, which may be updated as long as overall protection is not reduced;
- meet the Subprocessor conditions in Section 6;
- taking into account the nature of the processing, help Customer by appropriate measures to respond to data subjects’ requests to exercise their rights, and forward any request it receives directly to Customer without responding (other than to direct the person to Customer);
- help Customer with security, breach notification, data protection impact assessments and prior consultations with regulators, taking into account the information available to it;
- return or delete Customer Personal Data as described in Section 9; and
- make available the information needed to demonstrate compliance with Article 28 and allow audits as described in Section 10.
6. Subprocessors
Customer gives general authorization for ReactionSaaS to use the Subprocessors listed on our Subprocessors page (reproduced in Annex 3). ReactionSaaS will: (a) impose data protection terms on each Subprocessor that are at least as protective as this DPA; (b) remain responsible for each Subprocessor’s performance; and (c) give at least 30 days’ notice before adding or replacing a Subprocessor, by updating the Subprocessors page and emailing customers who ask to be notified at privacy@reactionsaas.com. Customer may object on reasonable data protection grounds within that period; the parties will discuss a solution in good faith, and if none is found Customer may terminate the affected Services and receive a refund of prepaid fees for the unused period.
7. Security incidents
ReactionSaaS will notify Customer without undue delay, and in any case within 72 hours, after becoming aware of a Security Incident. The notice will describe, to the extent known, the nature of the incident, the categories and approximate number of people and records affected, likely consequences, and the measures taken or proposed. ReactionSaaS will take reasonable steps to contain and remedy the incident and will update Customer as more information becomes available. Notice is not an admission of fault.
8. International transfers and Standard Contractual Clauses
ReactionSaaS and its Subprocessors process Customer Personal Data in the United States and other countries where they operate. Where Data Protection Laws require a transfer mechanism:
- EEA. The SCCs are incorporated into this DPA by reference: Module 2 (controller to processor) where Customer is a controller, and Module 3 (processor to processor) where Customer is a processor. Customer is the data exporter and ReactionSaaS is the data importer. Clause 7 (docking) applies; under Clause 9, option 2 (general written authorization) applies with the notice period in Section 6; the optional wording in Clause 11 does not apply; under Clause 13, the supervisory authority is the one competent for the data exporter; under Clauses 17 and 18, the SCCs are governed by Irish law and disputes go to the courts of Ireland. Annex I is completed by Annex 1, Annex II by Annex 2, and Annex III by Annex 3 of this DPA.
- United Kingdom. The International Data Transfer Addendum to the EU SCCs issued by the UK Information Commissioner applies, completed with the information in this DPA; either party may end it as allowed by its Section 19.
- Switzerland. The SCCs apply with the changes the Swiss Federal Data Protection and Information Commissioner requires, including that references to the GDPR include the Swiss Federal Act on Data Protection and that the competent authority is that Commissioner.
If the SCCs conflict with this DPA or the Terms, the SCCs control.
9. Return and deletion
During the subscription, Customer can delete Customer Personal Data through the dashboard or by request. Interaction events are deleted or anonymized automatically after the retention period (90 days by default, or as agreed in an Order Form). After the Terms end and the 30-day export period in the Terms has passed, ReactionSaaS will delete Customer Personal Data, except data it must keep by law (which it will keep protected and use only for that purpose) and data in backups, which is deleted as backups rotate.
10. Information and audits
On written request, no more than once a year (or after a Security Incident or at a regulator’s request), ReactionSaaS will answer reasonable security questionnaires and provide available summaries of its security practices and its Subprocessors’ third-party audit reports. If that is not enough to show compliance, Customer (or an independent auditor bound by confidentiality and not a competitor) may audit ReactionSaaS’s relevant processing on at least 30 days’ notice, during business hours, at Customer’s cost, in a way that does not disrupt operations or expose other customers’ data.
11. General
This DPA lasts as long as ReactionSaaS processes Customer Personal Data. Each party’s liability under this DPA is subject to the limitations in the Terms, except where Data Protection Laws or the SCCs do not allow it. Governing law and disputes follow the Terms, except as the SCCs require. If this DPA conflicts with the Terms on the processing of personal data, this DPA controls. Questions: privacy@reactionsaas.com.
Annex 1: Details of processing
| Item | Description |
|---|---|
| Parties | Data exporter: the Customer named in the account (contact: its account administrator). Data importer: ReactionSaaS Inc., [MAILING ADDRESS — TO CONFIRM] (contact: privacy@reactionsaas.com). |
| Subject matter and duration | Providing the Services under the Terms, for the term of the Terms plus the deletion period in Section 9. |
| Nature and purpose | Hosting, collecting, storing, analyzing, merging, transcoding, displaying and deleting data to provide interactive overlays, interaction analytics, reaction recording, reaction threads and related reports to Customer; security, fraud prevention and support. |
| Data subjects | End Users who visit or interact with Customer Properties, including Participants who record or upload reactions; Customer’s own staff where they appear in Customer Content. |
| Categories of data | Interaction events (taps, polls, ratings, sliders, clicks, playback milestones, timestamps); pseudonymous identifiers (session IDs, hashed device identifiers, hashed IP addresses); browser, operating system and screen-size class; referrer; approximate country or region; campaign, template and thread identifiers; and, for recording features, video and audio recordings (which show a person’s face, voice and surroundings), thumbnails and merged videos, with related metadata. |
| Sensitive data | None intended. Recordings may incidentally reveal sensitive information; they are not used to identify people or infer sensitive traits, and biometric identification is prohibited (Terms Section 7.3). |
| Frequency | Continuous, while the SDKs are installed and the Services are in use. |
| Retention | Interaction events: 90 days by default (configurable up to 730 days by agreement). Reaction media: for the life of the thread or campaign, or until Customer deletes it. Then as in Section 9. |
| Subprocessor transfers | As listed in Annex 3, for the purposes stated there. |
Annex 2: Technical and organizational security measures
- Encryption of data in transit (TLS) and at rest by our hosting and storage providers.
- Envelope encryption with a managed key service (AWS KMS) for the most sensitive secrets; passwords hashed with bcrypt; API keys stored as hashes; IP addresses stored as one-way hashes for analytics and fraud prevention.
- Private media storage, accessed through short-lived signed links; SDK keys restricted to verified customer domains.
- Role-based access to production systems on a least-privilege basis, multi-factor authentication for administrative access, and separate credentials for each service.
- Rate limiting, fraud and abuse detection on event ingestion and login, and security headers (including a Content Security Policy) on the web application.
- Secure development: code review, signed commits, automated malware and secret scanning in continuous integration, and dependency vulnerability alerts.
- Automated retention jobs that delete or anonymize raw interaction events.
- Logging and monitoring of production systems, backups, and an incident response process with customer notification as in Section 7.
- Confidentiality obligations for all personnel with access to Customer Personal Data.
Annex 3: Subprocessors
The current list is maintained on our Subprocessors page and reproduced here.
Current subprocessors
| Subprocessor | Purpose | Data processed | Location | Used for |
|---|---|---|---|---|
| Vercel Inc. | Website and application hosting, edge network, privacy-friendly site analytics | All data processed by the web application in transit and in memory; request logs; page-view analytics | United States (global edge network) | Customer Data (SDK); Account and billing; ReactifySocial only |
| MongoDB, Inc. (MongoDB Atlas) | Primary database | Account records, SDK interaction events, reaction metadata, billing and ledger records | United States | Customer Data (SDK); Account and billing; ReactifySocial onlyHosting region to be confirmed. |
| Cloudflare, Inc. | Object storage (R2) for uploaded and recorded media; network and security services | Reaction videos and audio, campaign media, thumbnails; IP address and country headers | United States (global network) | Customer Data (SDK); ReactifySocial only |
| Amazon Web Services, Inc. | Key management (KMS) for encryption keys; legacy S3 media storage during migration to R2 | Encrypted key material; media files stored before the move to Cloudflare R2 | United States | Customer Data (SDK); ReactifySocial only |
| Stripe, Inc. | Subscription billing, payment processing, Stripe Connect payouts and tax forms | Billing contact details, payment method tokens, invoices; payout identity and tax details | United States | Account and billing; ReactifySocial only |
| Email delivery provider (SMTP) | Sending account, security, billing and service emails | Recipient email address, email content, delivery metadata | United States | Account and billing; ReactifySocial onlyProvider to be confirmed (the code sends through SMTP and references Resend). |
| Redis hosting provider | Rate limiting, short-lived caches and job queues | Hashed identifiers, counters and short-lived job data | United States | Customer Data (SDK); Account and billing; ReactifySocial onlyProvider to be confirmed (for example Upstash or AWS ElastiCache). |
| Video processing service host | Merging and watermarking reaction videos (our own service, run on a cloud host) | Reaction videos and source media while they are being processed | United States | Customer Data (SDK); ReactifySocial onlyHosting provider to be confirmed (for example Railway). |
| Twilio Inc. | One-time SMS verification codes for sales and demo requests | Phone number and verification status | United States | Account and billing |
| Solana RPC provider | Reading and submitting Solana blockchain transactions for ReactifySocial wallets | Public wallet addresses and signed transactions (public on the blockchain) | United States | ReactifySocial onlyProvider to be confirmed. Not used for SDK Customer Data. |
| IP geolocation service | Country-level location for fraud prevention and analytics | IP address (to look up a country code) | Varies | Customer Data (SDK)Optional: used only if configured; otherwise country comes from Vercel or Cloudflare headers. |