Privacy Policy

Information you provide

The public website may collect information you submit for support, an account-deletion request, or interest in a future career opportunity. A careers submission includes your name, email address, selected area of interest, short message, and an optional PDF or DOCX résumé or CV. It is not an application to a current opening. A mobile account requires profile information including name, date of birth, general area, gender, and who the member wants to meet, and also collects biography, interests, prompts, and profile photos. Religion and political views are optional profile entries. We also process profile-style selections, safety reports, messages, membership records, and limited historical transaction and support information. A limited number of legacy accounts may still have an encrypted delivery address that the member previously provided; the current app does not collect or update a reusable delivery address.

Optional verification and potentially biometric information

Didit is the current verification provider. A member with a permanent access unlock from a first legitimate Premium activation or one valid successful referred signup may separately consent to Didit processing government-ID images, selfie or liveness media, facial data, and document information for identity, age, liveness, and face-match checks. Buying Premium, referring people, or unlocking verification access does not grant Verified status or the Verification Reward pack. Only the member’s own successful verification confirmed by Our Next Everything earns the current Verification Reward pack permanently when one is selected. Our Next Everything records the provider result and grants the rose badge only after a successful result is confirmed by the backend. Limited legacy accounts may have operational references and results from an earlier AWS Face Liveness or face-match workflow; AWS is not the current verification provider. Our Next Everything stores operational results, a provider session reference, verified date of birth, consent records, and review status—not raw government-ID or selfie/liveness images. When an account is deleted, we queue deletion of current provider sessions and users and any known legacy provider reference, retry failures, and keep the request pending until configured cleanup succeeds; a provider’s own lawful retention rules may still apply.

Location and discovery area

We process a ZIP-derived general area, locality, state, coarse distance, and internal coordinates when needed to operate The Wheel, apply gradual discovery-radius expansion, and detect abuse. Radius expansion remains centered on the member’s normal discovery location. The mobile app uses manual city, ZIP, and area selection and does not request device location permission, background location, or continuous location history. Exact coordinates are not publicly displayed or transferred to advertising providers.

Sensitive profile choices and discovery

Members choose one or more groups to meet: Men, Women and Nonbinary people. We use these private selections and the member’s confirmed gender categories to determine new introductions only when both members’ selections permit the pairing. Members can update their selections or pause Discovery; existing conversations remain available under the usual account and safety rules. These selections are not public profile labels, and the current app does not publish gender labels in another member’s profile response. Taken together, profile information and appearing in Discovery can still allow an inference about sexual orientation; the app does not collect or require a separate sexual-orientation label. Religion and political views are optional. After response minimization, religion and politics are not included in discovery or profile responses sent to another member and are not shown to other members.

Profile photos and safety review

Before a selected profile photo can become public, it is processed by a self-hosted automated safety model on restricted infrastructure. The photo is not sent to an external moderation API. Pornographic and hentai classifications are denied; sexualized, drawing, uncertain, or failed-review results remain non-public for review or replacement. Only an approved photo is activated in Cloudflare R2, which is used for storage rather than moderation. The model supports safety enforcement but cannot identify every violating image, and one model result does not by itself create a permanent account ban.

Historical transaction and delivery records

Limited records from retired services may include order and provider references, fulfillment and support status, consent records, promotional-credit balances and activity, and a previously supplied encrypted delivery address or private acceptance link. These records remain restricted to applicable support, fraud prevention, reconciliation, accounting, deletion, and legal obligations. A retained delivery address is separate from public profiles and conversations and may be deleted without deleting the dating account. The current app does not collect or update a reusable delivery address. Delivery information is not derived from identity-verification data or used for discovery, matching distance, advertising, analytics, targeting, or recommendations, and is not exposed to a matched sender.

Activity, device, and technical data

We may process sign-in and account activity, optional verification attempts, Likes, passes, matches, messages and message-read state, referral attribution and qualification, historical referral milestone, permanent access and cosmetic-entitlement records, active profile-style selections, temporary cosmetic expiration, discovery preferences, moderation reports, membership status, store transaction and purchase-verification records, ad reward intents and validated reward events, device and browser information, IP address, notification tokens, security logs, support requests, and cookies or comparable storage. The mobile app creates a durable opaque installation identifier in protected device storage and sends it for account security, notification or presence registration, and focused referral-abuse review. It normally remains on that installation across sign-out. On Android, after an eligible Google Play referral install, the app asks Google Play for the install-referrer string, extracts only a valid existing referral code, and does not read the available click or install timestamps. The public referral code is retained locally only until account creation accepts it. The public account-creation flow uses the signed first-party installation cookie described in the Cookie Notice.

Advertising and consent

Eligible genuine Free members can receive production advertising supplied by Google Mobile Ads when client configuration and authoritative server and database authorization allow the placement. Protected owner, reviewer, internal, and Observer sessions use test or non-monetized inventory only. Free members may also voluntarily complete a rewarded ad for an expressly described Wheel, Rewind, privacy-safe Likes, or eligible 24-hour My Style cosmetic benefit. A reward is recorded only after authoritative completion and validation and is not earned when an ad is closed early. My Style reward intents are short-lived and bind the member, eligible cosmetic, reward type, expiration, and nonce so a raw client cosmetic identifier is not sufficient authority. Depending on your region and choices, Google may process device information, IP address, approximate location derived from network information, consent signals, and ad interaction or aggregated measurement data. The app requests applicable advertising consent before requesting ads, sends non-personalized ad requests, and provides advertising privacy choices where required. The current iOS configuration does not request App Tracking Transparency authorization and disables the Google Mobile Ads publisher first-party identifier before SDK initialization; if provider behavior or the configuration changes, the consent flow and disclosures must change with it. We do not send dating preferences, inferred orientation, religion, political views, identity-verification records, device location, private messages, safety reports, or moderation notes to the advertising service. Premium members do not receive ordinary ads while the validated Premium entitlement is active.

Referrals and achievements

If you use or share a referral or promotion code, we may process the opaque code, attribution, successful-signup and qualification timestamps, lifetime referral number, historical milestone issuance, permanent access and cosmetic-entitlement records, verification-access and reward eligibility, and duplicate, self-referral, fraud, account-eligibility, and exclusion signals. These records let us assign each genuine referred account once, permanently unlock verification access after one friend completes a valid signup through an invite, permanently unlock My Style only after the member’s own successful verification for both Free and Premium, record the actual current Verification Reward pack earned only after successful verification, prevent duplicate value, and preserve ownership across reinstall, device, Premium, catalog, and program changes. The referred friend does not need to complete verification for a signup to count. Sharing, copying, opening, clicking, install/open handoff, attribution capture, and account attachment do not create rewards.

For duplicate, self-referral, and fraud review, the server transiently binds the mobile installation identifier or signed browser-cookie token to a versioned keyed HMAC fingerprint. The raw installation identifier and raw browser token are not stored in the referral-evidence table. A matching fingerprint is a review signal, not proof of identity. Referral and support views use limited account references and do not expose a referred person's email, phone number, identity documents, or private verification material to the referrer. They also do not expose the installation value or fingerprint to the referrer.

We do not upload address books or automatically contact people on a member's behalf.

How information is used

We use information to provide the public website; evaluate potential candidates and communicate regarding current or future opportunities; create and secure mobile accounts; enforce adults-only eligibility; verify optional identity and age signals; operate profiles, My Style, The Wheel, matching, messaging, referrals, notifications, memberships; validate store purchases and ad rewards; preserve purchased and earned ownership; expire temporary access using server time; send service communications; prevent fraud and abuse; moderate content; respond to support and safety reports; comply with law; and protect members and the platform.

Discovery and capability records

We keep the profile, active style, cosmetic ownership and temporary-access state, general discovery area, eligibility state, Likes and passes, matches, messages, blocks, reports, allowance and reward records, Premium entitlement and permanent verification-access history, referral qualification, permanent access, verification-reward issuance and historical milestone records, optional verification results and consent records, and related service communications as needed to provide and protect the service. Internal geographic or density information may help operate discovery; eligible adults can enter Free after completing the ordinary account requirements. A member may leave by requesting account deletion; the deletion process and permitted retention described below still apply.

Service providers and disclosures

Information may be processed by providers supporting the service, including Didit for current identity, age, liveness, and face-match verification; Amazon Web Services for limited legacy verification records where applicable; Cloudflare and Cloudflare R2 for network and profile-photo storage; the hosting provider; Resend for transactional, careers, and inbound company email; Firebase Cloud Messaging and Apple Push Notification service for generic mobile notifications; Google or Apple for optional sign-in and linked-authorization management; Google Play for the limited Android install-referrer handoff described above; Google Mobile Ads for eligible ordinary and rewarded ads; and Google Play or Apple for mobile subscription and digital-cosmetic purchase validation and events.

When you send a careers submission, Resend receives the contact details, area of interest, message, delivery metadata, and any résumé or CV you choose to attach so the submission can be delivered to our designated inbox. When someone emails an address at our company domain, Resend receives the sender and recipient addresses, delivery metadata, subject, message body, and any attachments. After Resend sends a verified inbound event, our server retrieves the message and supported attachments from Resend and forwards them through Resend to our designated private inbox with the original sender available for reply. Support and careers messages retain their intended routing; other valid domain addresses use the same protected forwarding service. Unsupported or unsafe messages and attachments may be held for review. Forwarding metadata is retained to prevent duplicate delivery and diagnose failures; attachment files are not stored permanently on our server. Do not send identity documents, passwords, verification codes, payment credentials, private acceptance links, or delivery addresses through either channel.

Retired transaction providers may retain historical order and required support or audit records under their applicable retention obligations. Historical records do not make ordering available. We may otherwise disclose information to comply with law, protect safety and rights, investigate abuse, complete a business transaction, or with your direction.

Retention

Career-interest submissions are retained only as long as reasonably needed to consider future opportunities, administer recruiting, protect the submission process, and meet applicable legal obligations. Active-account information is retained while needed to provide and secure the service. A member may delete a retained historical delivery address separately from their account. After verified account deletion, ordinary profile, discovery, photo, session, device, push, verification, active style, temporary cosmetic access, retained historical delivery addresses and uncompleted historical order associations are deleted, canceled, or de-identified as appropriate. Limited pseudonymous records may be retained for a legitimate purpose: referral attribution, qualification and permanent milestone issuance, purchased or achievement ownership, versioned installation HMAC evidence, deletion tombstones, historical promotional-credit ledger, expiration, redemption, reversal, and audit records needed for financial reconciliation, idempotency, fraud prevention, disputes, support, accounting, tax, enforcement, or legal obligations; safety reports, blocks, moderation decisions, relevant message, match, or historical transaction-abuse evidence and consent records; historical order and store transaction history; and security, support, or deletion records needed to demonstrate and protect the process. These retained records are access-restricted and are not used to recreate a dating profile or make it discoverable.

Removing a conversation from an inbox does not erase the other participant’s history or necessary safety evidence. Clearing the referral installation cookie ends future continuity from that browser, but does not erase pseudonymous evidence or tombstones already retained for the purposes above. Provider systems and ordinary backups may take additional time to expire under their own lawful schedules. Restoring a backup must reapply deletion tombstones before service. A legal hold may extend otherwise applicable retention.

Security

We use administrative, technical, and organizational measures intended to protect information, including encryption at rest for retained historical delivery addresses, restricted private media, access controls, and redaction of delivery details from ordinary logs and support views. No system, transmission, verification process, or storage provider can guarantee absolute security.

Your choices and requests

You may delete a retained historical delivery address without deleting your dating account through Settings → Historical Gift Address in the mobile app. You may cancel paid membership separately from deleting an account. Requests to access, correct, delete, or receive a copy of eligible career-interest information may be emailed to support@ournexteverything.com. Dating-account deletion may be initiated through the account deletion page or the in-app control, which revokes active sessions immediately and starts the same cleanup process. We verify external requests before acting and retain only information supported by the purposes above or by law.

Children and child safety

Our Next Everything is only for adults age 18 or older. We do not knowingly permit minors to create accounts. Report a suspected minor account promptly using the in-app Report control or the contact method in our Child Safety Standards. Authorized personnel handle known or confirmed child sexual abuse material under the controlled safety process and make reports where applicable law requires; we do not claim a report has been made until it has actually been completed.

International access

The service is presently directed to the United States. If you access it elsewhere, information may be processed in the United States and other locations where providers operate, subject to applicable safeguards and law.

Policy changes and contact

Material changes will be posted or communicated as required by law and will identify a new effective date. Questions and privacy requests may be sent to hello@ournexteverything.com.