Third-Party Services

Account access

Purpose: Optional way to create an account or sign in, using the standard Google OAuth 2.0 authorisation-code flow. Only used if you choose "Continue with Google" — email and password sign-in never contacts Google.

Data processed: Email address and display name returned by Google after you approve the sign-in. Pairscape never sees your Google password.

Payments

Purpose: Processes payments when you buy points. Checkout happens on PayPal’s own pages — Pairscape never sees your card or PayPal login details, and stores only the order identifier and the points it bought.

Data processed: Order and capture identifiers, payment amount and currency. Your payment details stay with PayPal.

Payments

Purpose: Processes point purchases made inside the Pairscape Android app. Google Play handles checkout and charges your Google Play account, so Pairscape never sees your card details. On the website, points are bought with PayPal or crypto instead.

Data processed: A purchase token and an order id, which Pairscape uses to confirm the purchase and credit your points. Your payment details stay with Google.

Security

Purpose: Tells people and bots apart on sign-up, login, password reset and the first time an account joins the matching queue, so accounts and the service are protected from abuse. It runs only on those three forms and on the pages that start the queue, and only until an account has joined once. It is a security control, so it is not tied to the cookie banner.

Data processed: Device and interaction signals (for example how the page is used and your IP address), sent to Google when you use one of those forms or join the queue for the first time. Google returns a score that tells us whether the request looks automated. Use of reCAPTCHA is subject to the Google Privacy Policy and Terms of Service.

Video & Network

Purpose: TURN/STUN servers for WebRTC video and audio connections between matched users, plus edge network and DDoS protection.

Data processed: IP address, WebRTC session metadata. No video or audio content is stored.

Analytics

Purpose: Session replay and heatmap analytics that help us understand how users interact with the interface so we can improve usability.

Data processed: Anonymised interaction data (clicks, scrolls, page navigation). Clarity automatically masks sensitive input fields.

Marketing

Purpose: Measures how well TikTok ad campaigns perform. Two routes carry the same information: a pixel that runs in your browser, and — because ad blockers stop the pixel for many people — a direct server-to-server report of the two conversions that matter, a completed purchase and a new account. Both are off until you accept marketing cookies, and both stop when you switch that category off.

Data processed: Page views, referral source, device type and IP address. For a purchase or a new account: the amount and currency, plus your email address and account identifier, hashed (SHA-256) before they are sent so TikTok never receives either in readable form. The click identifier from the ad you arrived through is stored in a first-party cookie so a purchase can be credited to the right campaign.

Marketing

Purpose: Measures how well Facebook and Instagram ad campaigns perform. A pixel running in your browser reports page views so a visit can be credited to the ad that brought you here. It is off until you accept marketing cookies, and stops when you switch that category off.

Data processed: Page views, referral source, device type and IP address. The pixel sets Meta’s own first-party cookies (_fbp, and _fbc when you arrive through a Facebook or Instagram ad) to link your visit to the ad you clicked.

Marketing

Purpose: Measures how well Google ad campaigns perform and supports remarketing. A tag running in your browser reports page views so a visit can be credited to the ad that brought you here. It is off until you accept marketing cookies, and stops when you switch that category off.

Data processed: Page views, referral source, device type and IP address. The tag sets Google’s own first-party cookies (such as _gcl_aw when you arrive through a Google ad) to link your visit to the ad you clicked.

Marketing

Purpose: Measures how well ad campaigns on the TrafficJunky network perform. A tag running in your browser syncs an advertising identifier with the network so a visit can be credited to the ad that brought you here, and reports a completed purchase back to it. It is off until you accept marketing cookies, and stops when you switch that category off. It is not loaded inside the Android app.

Data processed: Referral source, device type and IP address, plus an advertising identifier synced with the network. For a purchase: the amount — no name, email or account identifier is attached.

Translation

Purpose: Translates incoming chat and direct messages into the language you choose. This is off by default and only runs after you pick a target language from the translate menu, and turning it off again stops it immediately. Requests are made by our servers, never by your browser, so Google does not see your IP address or your account.

Data processed: The text of the messages you receive while translation is on, and the language you asked for, sent from our servers without your IP address, name or email. Only messages sent to you are shared; the messages you write are not.

Translation (backup)

Purpose: The backup translation service. It is used only when Google Translation is not configured on our side, in place of Google Cloud Translation, never alongside it. It translates incoming chat and direct messages into your chosen language. This is off by default and only runs after you pick a target language from the translate menu, and turning it off again stops it immediately. Requests are made by our servers, never by your browser, so the service does not see your IP address or your account.

Data processed: The text of the messages you receive, and the language you asked for. Only messages sent to you while translation is switched on are shared; the messages you write are not. No name, email or account identifier is attached.