ReactionSaaS Inc.

Privacy Policy

Version
2026-11-13
Status
Draft — effective on launch
Last updated
November 13, 2026

This Privacy Policy explains how ReactionSaaS Inc. collects, uses, shares and protects personal information, and the choices and rights you have. It covers reactionsaas.com, our dashboard and APIs, the ReactionSDK and ReactifySDK software that businesses add to their websites, and the account, payment, wallet and payout systems behind ReactifySocial.

1. Who we are

ReactionSaaS Inc. (“ReactionSaaS,” “we,” “us”) is a Delaware corporation with its principal operations in California, United States. Our mailing address is [MAILING ADDRESS — TO CONFIRM]. We operate two products:

  • ReactionSaaS (reactionsaas.com): a business platform with ReactionSDK (interactive overlays and interaction analytics on images and video) and ReactifySDK, also offered as UGCKings (camera reaction recording and reaction threads on businesses’ websites).
  • ReactifySocial (reactifysocial.com): a social app for adults (18+). We operate it, and its accounts, subscriptions, wallets, rewards and payouts run on the ReactionSaaS systems described here. The ReactifySocial privacy policy gives further detail about that app.

2. Our roles: when we decide, and when a business decides

  • We are the controller (the “business”) for information about visitors to reactionsaas.com, our business customers and their staff (“Customers”), sales and demo contacts, referral partners, and ReactifySocial account holders.
  • We are a service provider (a “processor”) for information our SDKs collect on a Customer’s website or app about the people who use it (“End Users”), including people who record a reaction (“Participants”). The Customer decides what is collected and why, under our Data Processing Addendum. If your information was collected on a business’s website, that business’s privacy notice applies and you should contact it first; we will help it respond.

3. Information we collect

3.1 Customers and site visitors

  • Account and contact details: name or company name, business email, username, role, domains you verify, and your password (stored only as a one-way hash).
  • Agreement records: when you accepted our Terms, which version, and a one-way hash of your IP address at that moment.
  • Billing: plan, subscription status and invoices. Card details are collected and held by Stripe; we receive only customer and subscription identifiers and payment status. Some plans are billed through Shopify instead.
  • Usage and device data: dashboard and API activity, IP address, browser and device type, and pages viewed (see Section 12).
  • Integrations: store domain, access tokens and installation details when you connect platforms such as Shopify, WordPress or HubSpot.
  • Sales and support: what you tell us in demo bookings, sales inquiries and support messages, including a phone number we verify by text-message code (through Twilio) for sales inquiries.

3.2 End Users of Customers’ websites (as a service provider)

  • Interaction events: taps, polls, ratings, sliders, clicks, playback milestones and timestamps.
  • Pseudonymous identifiers and technical data: a random viewer ID stored in the browser, session ID, hashed IP address, browser and operating system, screen-size class, referrer, approximate country, and campaign, template or thread identifiers.
  • Reaction recordings (ReactifySDK only): if a Participant chooses to record or upload a reaction, the video and audio (which show their face, voice and surroundings), thumbnails, merged videos, and related metadata such as duration and thread.

ReactionSDK interaction analytics do not use the camera or microphone. We do not use any recordings for facial recognition, voiceprints or other biometric identification, and our terms forbid Customers from doing so.

3.3 ReactifySocial accounts, rewards and payouts

  • Account: email, username, password hash, profile details, and your confirmation that you are 18 or older and when you gave it.
  • Subscriptions and purchases: plans, renewals, purchase history and consent records for automatic renewal.
  • Wallet: your Solana wallet address, balances and transaction history. We currently generate and hold each wallet’s private key on our servers in encrypted form, so that we can carry out transactions you request.
  • Rewards and payouts: Reaction Challenge rewards, referral and creator earnings (amounts, currency in RGC or U.S. dollars, status, dates), and Stripe Connect payout details. Stripe collects your identity, bank and tax information (such as Form W-9 details) in its own onboarding and issues tax forms; we receive only your Stripe account ID, account status, the last digits of your bank account and a bank-account fingerprint. We never receive your full Social Security or tax ID number or full bank account number.
  • Fraud-prevention signals: one-way hashed sign-up IP address and device identifiers, normalized email, account age, reward velocity and links between accounts, used only to prevent fraud and self-referral.

RGC is an in-app credit. It has no cash value and cannot be withdrawn or converted to cash; we keep RGC records for accounting and fraud prevention.

3.4 Referral and partner programs

If you join a referral or partner program, or sign up through a referral link or code, we collect the referral code used, the referrer, the sign-up date, your program application (name or business name, website or channel, country, audience description and the program terms version you accepted), your earnings and payout history, and the fraud-prevention signals described above. Referral links set a first-party cookie for up to 90 days. Your referrer sees only a masked username, your sign-up date and whether you are a paying or qualified referral, never your email, payment details or purchases.

4. How we use information

  1. To provide, operate and secure our sites, dashboard, APIs, SDKs and apps.
  2. To deliver analytics and reaction content to the Customer whose website collected it.
  3. To create and authenticate accounts and keep records of agreements and consents.
  4. To process payments, subscriptions, rewards, payouts and tax reporting.
  5. To run referral programs and prevent fraud, abuse and self-referral.
  6. To send service, security, billing and account messages, and, where allowed, product news you can unsubscribe from at any time.
  7. To provide support and respond to sales, demo and privacy requests.
  8. To improve our products using aggregated or de-identified information.
  9. To comply with law, enforce our terms and protect rights and safety.

We do not use End User data or reaction recordings for our own advertising, to build profiles for anyone else, or to train AI models.

5. How we share information

  • With the Customer whose website or thread collected End User data or reactions.
  • With service providers who process data for us under contract: see our Subprocessors page (hosting by Vercel, database by MongoDB Atlas, media storage on Cloudflare R2, key management and legacy storage on Amazon Web Services, payments by Stripe, text messages by Twilio, email delivery, rate limiting and video processing).
  • With platforms you connect, such as Shopify or HubSpot, as needed for the integration.
  • With your referrer, limited to the masked details in Section 3.4.
  • On public blockchains: Solana transactions you make are public by design and cannot be deleted by us.
  • With professional advisors, in a business transfer such as a merger or acquisition, and where required by law or to protect rights and safety.

We do not sell personal information and do not share it for cross-context behavioral advertising.

6. Storage and security

Our databases and servers are in the United States. Uploaded and recorded media is stored in Cloudflare R2 object storage; some older media remains in Amazon S3 while it is migrated, and encryption keys are managed with AWS Key Management Service. We use encryption in transit, encryption at rest by our providers, hashed passwords and API keys, hashed IP addresses, access controls and monitoring. No system is perfectly secure; please keep your password private and tell us at security@reactionsaas.com about any concern.

7. Retention

How long we keep information
InformationHow long
End User interaction events90 days by default, then deleted or anonymized automatically (longer only if a Customer’s contract says so, up to 2 years)
Reaction recordingsFor the life of the thread or campaign, or until the Customer, Participant request or account closure leads to deletion
Customer account dataWhile the account is open, then up to 30 days for export before deletion, except records we must keep by law
Billing, invoices and agreement records7 years after the transaction or account closure, for tax, accounting and legal purposes
Reward, referral, payout and RGC recordsLife of the account plus 7 years, for tax and audit purposes
Hashed fraud-prevention signals and bank-account fingerprintsOnly as long as needed to prevent fraud, and no longer than the related account records
Sales, demo and support messagesUp to 3 years after the last contact
Aggregated or de-identified statisticsMay be kept indefinitely because they no longer identify anyone

8. California notice at collection (CCPA/CPRA)

This table covers information we collect as a business (controller) in the past 12 months and going forward. Information we process for Customers as a service provider is covered by the Customer’s own notice.

Categories of personal information under the CCPA
CategoryExamplesSourcesPurposesDisclosed for a business purpose toSold or sharedRetention
IdentifiersName, email, username, IP address, account and wallet IDsYou; your deviceAccounts, security, support, billingService providers; payment processorNoSee Section 7
Customer records (Cal. Civ. Code §1798.80)Billing details, payout account statusYou; StripePayments, payouts, taxStripe; advisorsNo7 years
Commercial informationPlans, purchases, subscriptions, rewards, earningsYou; our systemsBilling, programs, fraud preventionService providers; StripeNo7 years
Internet or network activityPages viewed, dashboard and API use, device and browser typeYour deviceOperating and securing the services, improvementHosting and analytics providersNoUp to 2 years
Geolocation (approximate)Country derived from IP addressYour deviceFraud prevention, analyticsHosting providersNoWith the related record
Audio and visual informationReaction videos you record on ReactifySocialYouProviding the app and your contentStorage and video-processing providersNoUntil deleted
Professional informationCompany, role, websiteYouAccounts, sales, partner programsService providersNoSee Section 7
Sensitive personal informationAccount login with password; wallet private keys held for youYou; our systemsOnly to provide the service you asked for and to keep it secureHosting, database and key-management providersNoWhile the account is open
InferencesNone. We do not create profiles about you———No—

Advertising on the ReactifySocial website, if any, is described in the ReactifySocial privacy policy, together with the opt-out choices it offers. We use sensitive personal information only for purposes the CCPA permits without a right to limit (such as providing the service and security), so we do not offer a “Limit the Use of My Sensitive Personal Information” link. We do not sell or share personal information, including of consumers under 16.

9. Your privacy rights

Depending on where you live (including California and other U.S. states with privacy laws), you may have the right to:

  • know what personal information we collect, use and disclose, and get a copy;
  • correct inaccurate information;
  • delete your information, subject to legal exceptions;
  • opt out of sale, sharing, targeted advertising or profiling (we do none of these);
  • appeal our decision on your request; and
  • not be treated differently for using these rights.

How to ask: email privacy@reactionsaas.com with the subject “Privacy request,” or write to us at the address in Section 15. We will confirm receipt within 10 business days and respond within 45 days (we may extend by another 45 days where the law allows and will tell you why). We will verify your identity by matching information we already hold, such as confirming control of your account email. An authorized agent may make a request with your signed permission; we may ask you to confirm your identity directly. To appeal a decision, reply to our response with the subject “Privacy appeal.” We treat a Global Privacy Control signal as a request to opt out of sale and sharing.

End Users of a Customer’s website: please send your request to that business. If you contact us, we will pass it on and help the business respond.

10. International users

We are based in the United States, and our services are designed for U.S. users. If you use them from elsewhere, your information will be processed in the United States, where laws may differ from yours. Where we process personal data of people in the European Economic Area, United Kingdom or Switzerland, our legal bases are performing a contract, our legitimate interests (such as security and fraud prevention), legal obligations and, where required, consent; you may also have rights to restrict or object to processing, to data portability and to complain to your data protection authority. For data we process for Customers, transfers are covered by the Standard Contractual Clauses in our Data Processing Addendum.

11. Age requirements

ReactifySocial accounts are only for people 18 or older, and we do not process rewards or payouts for anyone under 18. Our business services are for adults acting for a business, and our terms forbid Customers from recording or inviting reactions from anyone under 18. We do not knowingly collect personal information from children. If you believe a child has given us information, contact privacy@reactionsaas.com and we will delete it.

12. Cookies and analytics

We use a small number of cookies and browser storage items, mainly to keep you signed in and to credit referrals, and Vercel Web Analytics (which does not use cookies) on our home page. Our SDKs may store a random viewer ID in the browser on Customers’ websites. Details are in our Cookie Notice.

13. Changes

We will post updates here with a new version number and date. If we make a material change, we will tell account holders by email or in the product before it takes effect.

14. Governing law and disputes

Disputes about this policy or our handling of your information are resolved under the dispute-resolution terms of the agreement that applies to you: our Terms of Service for business Customers, or the ReactifySocial Terms of Service for ReactifySocial users. If no agreement applies to you, the laws of your state or country of residence apply. Nothing in this policy limits rights you have under privacy laws, including the right to complain to a regulator.

15. Contact

ReactionSaaS Inc.Attn: Privacy[MAILING ADDRESS — TO CONFIRM]Email: privacy@reactionsaas.com