RStrangRBack to StrangR

STRANGR · EFFECTIVE SEPTEMBER 28, 2026

Privacy Policy

This Policy describes what StrangR collects, why it is used, how it is shared, and how to request a copy or delete your account. It reflects the current implementation as of October 2, 2026. The service is intended only for adults aged 18 or older.

1. Who is responsible

StrangR’s service operator determines how personal information is handled. The service is intended to be governed by the laws of the Republic of the Philippines, subject to mandatory privacy protections that apply where you live. The operator’s legal name and physical address have not yet been configured for this preview. For privacy matters, contact strangrsupport@gmail.com. This preview’s operator should not be inferred from the hosting URL.

2. Information we process

  • Account and authentication: email address, account name, verified-email status, Google sign-in identifier when Google is used, securely hashed email-password credential when email/password is used, and authentication session records/cookies. StrangR does not receive your Google password.
  • Date of birth and age check: your date of birth is collected at email sign-up or on the first sign-in when using Google, saved to your account, and checked server-side to enforce StrangR’s 18+ rule. An age-check result is stored so an account that does not meet the requirement remains blocked. A full birthdate is not saved when the submitted date shows that the account is under 18.
  • Profile: username, display name, selected country, optional gender, and selected conversation interests.
  • Approximate country: a two-letter country code may be read from Cloudflare’s request header to suggest a country. You can also choose a matching country. The app does not request GPS coordinates.
  • Matchmaking and service activity: match IDs, participant account IDs, start/end times, end reason, 60-second qualification records and daily counters, selected filters, queue/presence state, and recent skips. Queue and presence details are used transiently by the matchmaking Durable Object; persisted match metadata is in D1.
  • Likes, starred Connections, and direct messages: likes you send during active matches, mutual-connection records, per-account starred Connection records, and direct-message text and timestamps between mutual connections are stored in D1 so those conversations can continue later. A like is private unless it becomes mutual. Starred Connections are private to the account that created the star.
  • Support messages and attachments: the selected contact category, message text, optional reply email, submission time, and screenshots you choose to attach. These are sent to StrangR support through Resend and are not stored in StrangR’s D1 database. Do not attach passwords, full payment details, intimate or private images, or unrelated files.
  • Safety and moderation: block relationships, report category and optional reporter notes, report status, appeals, warnings, restriction/ban reasons and durations, moderation decisions, and administrator audit records.
  • PRO and payments: plan, amount, payment currency (PHP or USD as applicable), payment status, selected processor/method, processor references, creation/confirmation times, and entitlement start/expiry. QR Ph payments are processed in PHP only. PayPal payments may be processed in PHP or USD depending on the selected checkout currency. For PayPal checkout, StrangR sends the purchase amount, currency, plan description, and an internal order reference to PayPal and receives PayPal order/capture identifiers and status. StrangR does not receive your QR wallet password, PayPal password, or full card credentials through the checkout flow.
  • Display advertising: the signed-in chat page can load HilltopAds advertising code. HilltopAds and its advertising partners may process information needed to deliver, limit, measure, and target ads, such as IP address, browser/user-agent, device or operating-system information, approximate location derived from network information, referrer/page information, ad-zone identifiers, and impression/click activity. Their code may use cookies or similar browser identifiers where permitted.
  • Rewarded-ad activity: pending provider session identifiers, verification events, placement, successful reward records, daily usage, and temporary filter unlock expiry may be stored if a separate rewarded-ad provider is connected. No rewarded-ad provider is configured now, so no rewarded ad is currently completed or credited.
  • Abuse prevention: rate-limit counters use pseudonymized/HMAC-derived bucket keys. When Cloudflare supplies a client IP for authentication rate limiting, the application does not store the raw IP address in those rate-limit records.

3. Live text, audio, and video

Messages sent in an active random match are routed between the two authenticated participants by the matchmaking WebSocket/Durable Object and are not saved as match transcripts. During a match, either person may tap Like. If both people like each other, StrangR creates a mutual connection and enables direct messages in Connections; direct-message contents and timestamps are stored in D1 and shown only to those two accounts. Blocking a connection removes its stored DM history and prevents further messages. Participants may still copy, photograph, or record content outside StrangR.

Audio and video use browser WebRTC. Camera and microphone access are requested by the browser after a match or when you preview your camera. Media is peer-to-peer when network conditions permit; if Cloudflare Realtime TURN is used, encrypted media traffic is relayed through Cloudflare’s TURN service. StrangR does not store video/audio recordings. SDP and ICE signaling metadata is relayed for the active match and is not intentionally persisted as conversation content. Connection metadata may be processed by the browser, network, Cloudflare Workers/Durable Objects, and TURN service. You can deny device permissions, turn off your camera/microphone, or leave the match.

4. Why information is used

We use your date of birth and age-check result to verify the account meets the 18+ eligibility rule and block access when it does not. We use other information to create and secure accounts, set up usernames, match compatible users, enforce daily limits and filters, route live communications, process PRO purchases, prevent abuse, respond to safety reports and appeals, provide account export/deletion, operate the service, and comply with legal obligations. Depending on the law that applies to you, processing may be necessary to provide the service, meet legal duties, protect users and the service, or rely on consent where consent is required.

While your PRO entitlement is active, other users can see a PRO badge beside your username in live matches and mutual Connections. The server provides the active status and entitlement expiry time for displaying and expiring this badge; payment details are not shown to other users. The PRO Icebreaker feature chooses from preset conversation starters in your browser and only places the selected text into the message box. It does not call an external AI service or create a separate database record; the text is transmitted only if you choose to send it as a normal live-chat message. PRO users can also star up to 10 mutual Connections. Stars are stored per account in D1 and are used to pin those Connections first only while the server confirms that PRO is active. Expired PRO does not delete stored stars; they remain inactive until PRO is restored or the star/connection/account is removed.

5. Cookies and local storage

Better Auth uses essential session cookies to keep you signed in and protect authenticated requests. The web app also uses browser local storage for country/gender/topic preferences, recent matchmaking-use time, and the automatic PRO-promotion dismissal cooldown. These local values do not determine server-side match limits, ad caps, payments, or entitlements. The HilltopAds display-ad code and advertising partners may use cookies or similar browser identifiers for ad delivery, frequency limiting, measurement, fraud prevention, or advertising purposes where permitted. You can clear local storage and cookies in your browser; doing so can reset saved preferences, promotional display timing, and advertising identifiers, but does not erase StrangR server records.

6. Service providers and sharing

We share information with providers only as needed to operate the service:

  • Cloudflare: Workers hosting, D1 database, Durable Objects/WebSockets, and Realtime TURN when configured.
  • Google: OAuth sign-in when you choose Google.
  • Resend: verification, password-reset, and account-deletion confirmation emails, plus delivery of contact-form messages and any attached screenshots to StrangR support when email delivery is configured.
  • PayMongo: QR Ph checkout and payment confirmation.
  • PayPal: hosted PayPal checkout, order approval/capture, and verified payment-status webhooks when configured. PayPal may offer funding sources inside its own checkout according to its account, regional, and product rules.
  • HilltopAds: display advertising on the signed-in chat page. HilltopAds and advertising partners may receive browser/network and ad-interaction information as described above and process it under their own privacy and advertising policies.
  • Rewarded-ad provider: none is currently configured for the temporary-filter reward feature.

Providers process information under their own terms and privacy notices. We may also disclose limited information when required by law, to respond to valid legal process, enforce safety rules, protect users, investigate fraud, or protect StrangR’s rights. We do not sell personal information in this preview.

7. Retention

Account date of birth and profile information are kept while the account is active and are deleted with the account. For an underage Google sign-in, StrangR does not save the full birthdate, but retains an age-restricted account status so the account remains unable to access the service; the account can be deleted by contacting support. Mutual likes, connections, per-account Connection stars, and direct-message history remain available while the connection exists. Deleting a connection hides it from the requesting user's account first; its messages remain available to the other person for safety and reporting. The messages and connection are permanently removed only after both people request deletion. Blocking the other account deletes that connection’s DMs and any Connection stars for that connection. Account deletion removes the account’s likes, Connection stars, connections, and associated DMs. Match metadata, qualification records, payment ledger entries, reports, appeals, and moderation/audit records do not currently have a configured automatic deletion schedule; they may be retained while needed for service operations, payment accounting, safety, fraud prevention, appeals, or legal obligations. Contact messages and attached screenshots are not saved in StrangR D1; copies sent through Resend and received in the support mailbox are retained according to those provider/account controls and as needed to handle the request. Abuse-rate-limit buckets older than seven days are removed opportunistically. Reward and temporary-unlock records follow the current D1 implementation and are removed during account deletion.

When an account deletion completes, authentication and linked login records are removed; the profile, birthdate, age-check result, blocks, skips, daily match usage, reward activity, appeals, likes, Connection stars, connections, direct messages, and PRO entitlement/subscription are deleted. Payment orders, match metadata, safety reports, and moderation/audit records may be retained under a random pseudonymous ID. Reporter-provided notes are cleared when the deleted account submitted the report. Live random-match messages and video/audio are not retained as StrangR transcripts or recordings.

8. Your choices and requests

In Account Settings, you can download a JSON export of account, profile, block, match, safety, likes, starred Connections, connections, direct-message, PRO, and payment data; revoke active sessions; manage blocks; or request account deletion. When email delivery is configured, deletion requires confirmation by email. The export does not include passwords, authentication tokens, session cookies, or live media. For help with an account or data request, email strangrsupport@gmail.com.

Depending on your location, you may have rights to access, correct, delete, restrict, object to, or receive certain information. You can also raise a concern with your local data-protection authority. The applicable rights and response deadlines depend on the law that applies to you.

9. International users and security

StrangR is accessible internationally. Information may be processed in countries where Cloudflare and the selected authentication, email, and payment providers operate. Those countries may have privacy laws different from yours. We use access controls, authenticated server endpoints, D1/Worker infrastructure, and server-side rate limits, but no internet service can guarantee perfect security.

10. Children and changes

StrangR is not intended for anyone under 18. Email sign-up checks the birthdate before creating the account. Google users are held at an age-check page before accessing account features, matchmaking, or messaging. Underage accounts are blocked from the service. If you believe a minor has an account, contact StrangR support so the account can be reviewed or deleted. We may update this Policy as the service changes. We will update the effective date and, where required, give additional notice or obtain consent.

11. Privacy contact

For privacy questions, legal/privacy inquiries, or requests to access, correct, or delete personal information, email strangrsupport@gmail.com. The operator’s legal name and physical address remain unconfigured in this preview.

Last updated: October 2, 2026.

Terms & ConditionsPrivacy PolicyContact supportSign in