When you sign in with your Google account, we receive and store:
Your name
Your email address
A unique identifier associated with your Google account
This identifies your account, tracks your free trial period, and manages your subscription status.
2. Usage data
Reaction Sync records events about how the extension is used, so we can understand where people get stuck and what needs fixing. These events are tied to your account, and to a random identifier generated when the extension is installed.
What the events contain
The addresses of the videos you pair. When you pair two tabs, and again when that session ends, we record the web address of the source video and of the reaction video, along with which sites they were on and how long the session lasted. These addresses can identify the specific title or episode you watched.
Which screens you reached and what you clicked. Opening the extension, signing in, how many tabs were available to pair, pressing pair, adding a sync point, sharing a script, and any errors along the way.
The extension version, so we can tell whether a problem is specific to one release.
A random install identifier. Generated on your device when the extension is installed and sent with every event. It lets us connect events from before you signed in to your account afterwards — for example, to see how many people install the extension but never get as far as signing in. It contains nothing about you or your device, and it is discarded if you uninstall.
What the events do not contain
Anything from a page other than its address — no page content, no video frames, no audio, no text you have typed
Addresses of pages you visit that are not part of a pairing
Your browsing history
Your payment details
3. How we use this information
Identify your account and maintain your sign-in session
Track your 30-day free trial start date and expiry
Verify your subscription status and grant or restrict access accordingly
Process payments (via Razorpay) and associate payment events with your account
Understand which sites and combinations people actually use, so we know what to support next
Find where people run into trouble — a screen that hangs, a pairing that fails, a tab that never appears
We do not sell this data, share it with advertisers, or use it to build a profile of you for any purpose other than operating and improving Reaction Sync.
4. What the extension does on the pages you visit
On the video sites listed in section 7, Reaction Sync runs a small script in the page so it can read the current playback position and control play, pause and seeking. This is what keeps the two videos aligned.
That script reads only the video player. It does not read the rest of the page, and nothing it reads is sent anywhere except the playback position, which is exchanged between your own two tabs to keep them in sync.
5. Third-party services
Google OAuth — for sign-in. Google's privacy policy applies to the sign-in process.
Supabase — database and authentication infrastructure. Account data and usage events are stored on Supabase servers in the ap-south-1 (Mumbai) region.
Razorpay — payment processing. Razorpay collects and processes payment information directly. We do not see or store your card details.
Plausible Analytics — on the reactionsync.com website only, not in the extension. It records page views without cookies and without collecting personal data.
We do not sell, share, or disclose your personal information to any other third parties.
6. Data retention
We retain your account information and usage events for as long as your account exists.
To have your data deleted, email privacy@reactionsync.com. We will delete your account, your usage events, and any sync scripts you have shared within 30 days.
7. Permissions used by the extension
tabs — to list the tabs that contain a supported video, so you can choose which two to pair.
storage — to save your sign-in session, your pairing state, and the install identifier on your own device.
scripting — to run the playback-control script described in section 4.
identity — to open the Google sign-in flow through Chrome's identity API.
host permissions — so that script can run on the sites we support. The current list is on the homepage.
These permissions apply only to the sites listed. Reaction Sync has no access to any other page you visit.