Privacy Policy

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.
• 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.
• Support messages: the selected contact category, message text, optional reply email, and submission time. These are sent to StrangR support through Resend and are not stored in StrangR’s D1 database. Do not include passwords, full payment details, or private media.
• 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, PHP currency, payment status, method, processor references, creation/confirmation times, and entitlement start/expiry. StrangR does not receive a QR wallet password or payment-account credentials through the checkout flow.
• 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 real provider is connected. No 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

Text messages are routed in real time between the two authenticated participants by the matchmaking WebSocket/Durable Object. Message contents are not written to StrangR’s D1 database as chat history. The browser and network must transmit messages to the other participant, who can copy, photograph, or record them 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 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.

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. You can clear local storage in your browser; doing so resets saved preferences and promotional display timing, not 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 to StrangR support when email delivery is configured.
• PayMongo: QR Ph checkout and payment confirmation. QR Ph is the only enabled payment method. PayPal’s capture endpoint is disabled; PayPal and other payment methods are not enabled.
• Rewarded-ad provider: none is currently configured. If an ad network is selected, StrangR will update this Policy with the provider and relevant data before enabling it.

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 and profile information is kept while the account is active. 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 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, blocks, skips, daily match usage, reward activity, appeals, 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. This retention is limited to the records described above; it is not a stored chat transcript or media recording.

8. Your choices and requests

In Account Settings, you can download a JSON export of basic account, profile, block, match, safety, 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, live media, or message contents because those are not available as stored StrangR records. 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, and we do not knowingly invite children to create accounts. If you believe a minor has an account, report it through StrangR’s safety tools. 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.