Interlove Privacy Policy

1. Scope and Responsible Entity

This Policy applies to the Interlove user application, related websites, and the registration, browsing, recommendation, interaction, chat, identity verification, Love Beans, women's VIP application, customer support, and safety services that we provide.

The entity responsible for personal information is:

This Policy does not apply to the independent conduct of other users outside the platform. It also does not replace the privacy notices provided by Didit, Apple, Google, or other third parties when they independently determine the purposes and means of processing.

2. Information We Collect

We collect information only to the extent necessary to provide the relevant features, maintain safety and security, perform our contractual obligations, or comply with legal requirements. The information we collect depends on the features you actually use.

2.1 Guest Preferences, Account Information, and Login Information

• Guest preferences: The gender you select for browsing, onboarding completion status, and language preference.
• Account identifiers: User ID, nickname, country or region code, telephone number, or email address.
• Verification information: Verification-code request identifier, delivery channel, purpose, sending and verification times, and failed-attempt or retry records. Verification codes are used only for verification and should not serve as long-term account credentials.
• Third-party login: If and only if Sign in with Apple, Google, or WeChat is genuinely available in the version you use and you choose it, we receive the third-party account identifier and information necessary to complete the login. We do not receive your password for the third-party account.
• Agreements and status: Versions of the User Agreement and Privacy Policy you accepted, time of consent, registration progress, account status, and account closure requests and reasons.

2.2 Profile Information and Filter Criteria

When you create or update your profile, we may process the following information:

• Photos, nickname, gender, full date of birth, height, and weight;
• Current country, state, province, or city and place of birth that you manually select;
• Marital status, whether you have children, plans for children, race or ethnicity, religion, and body type;
• Education, occupation, position, employment status, income range, immigration status, years in your current country, and willingness to relocate;
• Languages, drinking and smoking habits, and interests;
• Personal introduction, family background, relationship goals, partner preferences, and other free-form text;
• Search criteria you set, including age, location, education, occupation, marital, parental, and family-planning criteria, race or ethnicity, religion, income, lifestyle, verification, or VIP status.

Your full date of birth, race or ethnicity, religion, income, immigration status, marital status, parental status, plans for children, and certain free-form text may constitute sensitive or highly private information. Other than to provide the profile display, filtering, and matching features you choose, we will not use this information for purposes inconsistent with your reasonable expectations.

2.3 Photos, Camera, Photo Library, and Microphone

You may use your camera or photo library to select content for registration photos, your personal gallery, images in Matched chats, report and appeal evidence, customer support materials, and identity verification. Your personal gallery may contain up to nine photos, and the first photo serves as your profile photo. We may process the file content, name, size, format, dimensions, upload time, order, and review status.

The microphone is used only when voice input or an identity-verification liveness process requires it and the feature is actually available in the current version. You control operating-system permissions. Denying a permission does not prevent you from using features unrelated to that permission.

2.4 Interactions, Relationships, and Communications

• Profile views and first-visit records, likes, revoked likes, mutual likes, blocks, and unblocks;
• Human-arranged match invitations, recommendation reasons, advisor and approval information, the 48-hour validity period, acceptance or rejection, Matched status, and requests and reasons to end a match;
• Conversation participants, text, basic emoji, images, sending time, sender time zone, message status, review status, read or recalled status, and the number of Love Beans deducted;
• If translation is available, the text submitted for translation, target language, translation result, and necessary cache;
• If real-time voice or video features are available, the session metadata required to establish the connection. We will not record real-time call content unless we provide clear notice before the call begins and obtain consent as required by law.

2.5 Identity, Age, and Qualification Verification

When you use a verification feature, we or a verification service provider may process your legal name, date of birth, country or region, identity-document type and number, images of the front and back or data page of the document, selfie, liveness video or image, facial characteristics or comparison results, verification-session identifier, device and network anti-fraud information, and verification status and time. Education or employment verification may also include supporting documents.

This information is sensitive. Facial and biometric processing requires separate, express consent where applicable law requires it. The data, recipients, storage, retention, and deletion rules are set out in Section 7.

2.6 Love Beans, App Store Transactions, and VIP Applications

• Love Beans: Balance, purchase package, quantity, local currency and amount, Apple or Google platform, product ID, order ID, store transaction identifier, receipt-verification result, order status, and transaction history.
• Payment information: Apple or Google processes your app store payment credentials. We generally do not receive your full payment-card number or app store account password.
• VIP advisor application: Legal name, telephone number, optional WeChat ID, relationship goals, budget, and comments voluntarily submitted by eligible women.
• Offline agreements: If you sign a VIP or advisor-services agreement, we process the agreement, payment, service, and communication records in accordance with that agreement and its accompanying privacy notice.

2.7 Reports, Safety, Customer Support, and Appeals

We process the identities of the reporting and reported users, the reason and description, related messages, image or file evidence, whether the reporting user chooses to block the reported user, case number, handling status, type and duration of enforcement, reasons and evidence for appeals, and the category, subject, description, attachments, and correspondence associated with customer support tickets. To protect against retaliation, we generally do not disclose a reporting user's identity to the reported user.

2.8 Device, Network, and Operational Information

When you connect to the Services, we may automatically receive your IP address, request ID, request method and route, response status, time and duration, account ID, operating system, app version, build version, language, and time zone. If push notifications are actually available and you authorize them, we also process the platform and push token. The server does not automatically obtain your contacts or GPS location merely because the app has network access.

The current version does not integrate third-party advertising or cross-app attribution SDKs. After the privacy-compliance switch is enabled, Firebase Analytics and Firebase Crashlytics process app-instance identifiers, screen and core-feature events, crash traces, and necessary device and operational information for product analytics and troubleshooting. We do not intentionally send chat text, photos, identity documents, or facial materials as analytics event parameters. See Section 8.3.

3. Sources of Information

We obtain personal information from the following sources:

• You: When you register, complete your profile, upload content, make a purchase, complete verification, contact customer support, or exercise your rights;
• Your device and the app: When you connect to the Services, save preferences, or grant device permissions;
• Other users: When another user likes, blocks, or reports you, or chats or otherwise interacts with you;
• Service providers and platforms: Verification results returned by Didit or Tencent Cloud Huiyan, login and transaction status returned by Apple or Google, and push, translation, real-time communication, verification-code, hosting, and security information provided by Firebase, Tencent Cloud, Alibaba Cloud, and other enabled providers;
• Information we generate: Age, account status, relationship status, free-message allowance, Love Beans deductions, content-review results, safety flags, and customer support records.

We do not purchase personal profiles from data brokers or automatically import contacts from your address book.

4. How We Use Information

We use personal information for the following purposes:

• To create and maintain accounts and manage login verification, agreement records, profile maintenance, and account closure;
• To provide guests and members with limited public profiles, search, filters, recommendations, visit records, likes, mutual likes, and human-arranged matching;
• To transmit, review, display, meter, and maintain chat and media features;
• To complete identity, age, or qualification verification and prevent impersonation, fraud, and account abuse;
• To process Love Beans orders, store receipts, balances, transaction histories, refunds, or chargebacks;
• To handle VIP advisor applications, customer support, reports, appeals, content moderation, and safety incidents;
• To operate the Services, troubleshoot issues, monitor unusual access, and protect users and our systems;
• To conduct app-usage analytics through Firebase Analytics and perform aggregated or de-identified capacity planning and product improvements;
• To fulfill contractual, tax, accounting, consumer-protection, law-enforcement-response, and other legal obligations;
• To establish, exercise, or defend legal claims.

If we wish to use personal information for a new purpose that is materially different from the purpose for which it was collected, we will provide advance notice and obtain new consent when required by law.

5. Visibility and User Interactions

5.1 Logged-Out Visitors

Guests may view limited profile cards for users who are not in hidden mode. These cards generally include photos; age calculated from date of birth, rather than the full date of birth; the general location manually selected by the user; education; occupation; interests; online or recently active status; verification status; and VIP status. We do not display your identity documents, contact information, full date of birth, private messages, or original verification materials to guests.

5.2 Logged-In Members

Subject to product rules, logged-in members may see the profile details you provide and permit us to display, including potentially sensitive details about marital status, children, family-planning intentions, race or ethnicity, religion, income range, or immigration status. You should provide only information that you are willing to disclose to potential dating partners. Other users may take screenshots of or save information you voluntarily make public outside the platform, and we cannot fully control their subsequent conduct.

5.3 Visits, Interactions, and Privacy Settings

When you view another person's profile, we may show that person a record of your visit. Likes, mutual likes, chats, reports, and matches disclose the relevant identity and status to the participants as needed. Hidden mode can reduce general public visibility, but it does not delete prior interactions or prevent internal processing for safety, customer support, or legal purposes.

6. Human Review of Chats

The initial version of Interlove's chat-safety program includes human review. Text and chat images sent by users may first enter a pending-review status, and recipients may see them only after approval. This review is intended to identify fraud, harassment, unlawful content, impersonation, risks involving minors, exchange of contact information, and attempts to move users off the platform. As a result, messages may be delayed, blocked, or undelivered.

To the extent required by their responsibilities, trained moderators, customer support staff, safety personnel, or appeals personnel who are subject to confidentiality obligations, as well as service providers that supply controlled review systems to us, may access message content, images, senders and recipients, conversation context, report records, and review results. We restrict access under the principle of least privilege and maintain appropriate activity records.

Messages are not end-to-end encrypted private communications. Recalling a message changes only its display in the conversation and does not automatically delete copies required in our systems for review, safety, reporting, or legal purposes. Do not send identity documents, verification codes, bank account details, home addresses, or other unnecessary sensitive information through chat.

7. Identity Verification and Biometric Information

7.1 Didit's Role

For the verification route outside mainland China, Didit Identity, Inc. and Didit Identity Spain, S.L. provide document verification, selfie capture, liveness detection, facial comparison, and fraud detection. The verification flow processes document images, including the portrait on the document; selfie images or video frames; and facial features or biometric templates used to compare faces and detect duplicate identities. It also processes extracted identity details, verification decisions, session identifiers, IP addresses, device information, and risk indicators. See Didit's Verification Privacy Notice.

Didit's SDK collects verification materials and sends them to Didit. Our account-verification record stores the returned name, document type and number, date of birth, issuing country, document expiry date, verification status, session identifier, timestamps, and rejection reason where applicable. Our service also receives the original verification notification, which can contain material links and additional verification or risk details. We do not download Didit selfies or liveness videos into our account-verification record or maintain our own facial-template database.

Didit acts as our verification processor and also describes limited independent processing for security, fraud prevention, legal compliance, and related purposes in its notice. Didit publishes the European Union as its default processing and storage region. Interlove's copies of returned records and notifications are stored as described in Section 7.3.

7.2 Tencent Cloud Huiyan's Role

For the mainland-China verification route, Tencent Cloud Computing (Beijing) Co., Ltd. provides the Huiyan SDK for identity-card OCR, liveness detection, facial comparison, and device-risk checks. The flow processes your name, identity-card number, document images containing your portrait, facial photographs, and liveness video. The SDK also processes device and network information for verification security, including device model, operating system, network type, IP address, camera and sensor information, and platform-specific identifiers such as IDFV on iOS. Tencent describes the data and its embedded service providers in its Huiyan SDK Personal Information Protection Rules.

The app uploads the front and back identity-card images to Interlove's private file storage and submits your name, identity-card number, date of birth, issuing authority, and document validity information to our service. Tencent receives the information needed for its identity and face checks. Under Tencent's rules, the CTID trusted identity-authentication platform may receive the name, identity-card number, and facial photograph for authoritative comparison. Tencent states that information collected by this SDK in mainland China is stored in mainland China.

Our server queries Tencent for the final result and stores the verification status, provider reference, timestamps, and any failure reason together with the submitted identity details and document-image references. Our integration does not request or archive Tencent's liveness photographs or videos and does not store a facial template. The identity-card photographs we retain do contain your face. Tencent's storage rules apply to its copy; our Singapore storage described below applies to the copies held by Interlove.

7.3 Interlove's Use, Access, and Storage

We use verification information to establish identity, age, and document validity, maintain account-verification status, investigate impersonation or duplicate-account abuse, and handle verification disputes and legal requests. We do not use it for dating recommendations, advertising, or artificial-intelligence model training. The setting that would allow verification data to be used to improve Didit's models is turned off for our Didit organization. Original identity documents, selfies, facial templates, and liveness materials are not public-profile information.

Interlove's production database, private uploaded files, and verification-notification storage are hosted on Alibaba Cloud infrastructure in Singapore. This includes the mainland-China identity-card images uploaded to Interlove and the identity details and results returned through either verification route. Transfers to our service use HTTPS. Access to verification records and private documents is restricted to authorized personnel and services for the purposes stated above. Alibaba Cloud provides hosting; Didit and Tencent provide the face-verification processing described in Sections 7.1 and 7.2.

7.4 Retention Periods

• Interlove's identity records and uploaded identity-card images: Retained while your account remains open for the purposes in Section 7.3. Once account closure takes effect, we automatically delete the identity-verification record and its associated identity details, document images, and other original verification materials. You do not need to submit an additional email request. Failed deletion operations are retried until completed.
• Original Didit notifications held by Interlove: Our notification storage has a seven-day retention setting and clears data in storage batches. Removal of a particular notification can occur after its individual seven-day point because cleanup operates on batches.
• Didit verification data: Retained during the life of your Interlove account. Once account closure takes effect, we automatically send Didit a privacy-erasure instruction for the associated verification sessions, covering document images, selfies, liveness media, extracted identity details, results, and facial templates. Failed requests are retried until deletion is confirmed. Facial templates are not retained separately after this erasure. Didit describes the scope in its session-deletion documentation. Separately maintained audit activity follows its own retention rules and is not the original facial or document material.
• Tencent's verification materials: Tencent's published Face Verification FAQ states that sensitive images and videos used for troubleshooting are retained for three days and then cleared, while non-sensitive logs are encrypted and retained for one year. These supplier periods do not delete the identity-card images or verification records held separately by Interlove. Tencent's rules also describe retention required for legal proceedings and other applicable exceptions.

7.5 Your Choices and Deletion Requests

You can leave the verification flow before submitting materials or revoke camera permission in your device settings. Features requiring verified status may be unavailable if verification is not completed. Accepting the User Agreement does not replace any separate consent required for facial or biometric processing. Revoking a permission stops the related future collection; it does not erase information already submitted.

Account closure automatically initiates the deletion in Section 7.4; no separate request is required. To request access, correction, withdrawal of consent, or deletion while your account remains open, email contact@interlove.net with the subject "Verification Data Request." Include your Interlove account identifier and the request; include a verification session reference only if you have it. Do not attach an identity-card image or facial photograph to the initial email. We verify the request and coordinate the handling of our copies and the relevant supplier's copies. Deletion covers the retained documents and files as well as the verification record.

Where a legal obligation or valid legal hold requires retention, we will identify the affected records and explain the applicable reason and period. Responses follow the deadlines and rights described in Section 14. We handle deletion of Interlove's copies and the relevant supplier's copies separately and check the outcome of each operation.

8. How We Disclose Information

We do not disclose personal information arbitrarily for commercial gain. We may make disclosures as necessary in the following circumstances:

8.1 Other Users and Visitors

We display your public profile, interactions, and relationship status as described in Section 5. Chat participants receive content that you send and that passes review. When handling reports, we may disclose the outcome to relevant parties, but generally do not disclose the reporting user's identity or unnecessary evidence.

8.2 Service Providers

We may provide necessary data to service providers that are contractually restricted to processing information for specified purposes, including:

• Identity-verification providers: Didit and Tencent Cloud Huiyan process identity documents, facial and liveness data, device information, and anti-fraud information according to the verification region;
• App platforms and Firebase: Apple and Google provide app distribution, login, in-app purchases, push messaging, crash diagnostics, and app-usage analytics;
• Communication and translation providers: Volcengine veRTC transmits real-time call media and signaling, Tencent Cloud TokenHub processes a message and necessary context when you request translation, and Alibaba Cloud SMS sends verification codes you request;
• Infrastructure providers: Alibaba Cloud provides cloud servers, networking, and related infrastructure used by the production Services;
• Professional advisors: Attorneys, accountants, auditors, or insurers process information to the extent necessary to perform their professional responsibilities.

The table below describes each service's actual trigger, data categories, and official notice. We do not represent potential vendors as providers that already receive data. When adding a provider, we update the list or provide contextual notice as required by law.

8.3 Third-Party SDKs and Services

This table covers both SDKs embedded in the client and server-side third-party services that receive user data. Open-source user-interface components, local-only utilities, and operating-system interfaces that do not transmit data to their developers are not listed as data recipients.

8.4 Legal, Safety, and Corporate Transactions

When we have a reasonable basis and disclosure is permitted by law, we may disclose necessary information to comply with legal process, respond to competent authorities, prevent an imminent threat of physical harm, investigate fraud or infringement, or protect the rights of users and the platform. In connection with a merger, financing, reorganization, or transfer of assets, personal information may be transferred subject to confidentiality and appropriate safeguards. We will provide legally required notice of material changes.

8.5 At Your Direction

In other circumstances, we will explain the recipient, data, and purpose before disclosure and obtain your consent when required. Information that you independently copy, share, or send to another user is not a separate disclosure by us to a third party.

9. Sale, Sharing, and Advertising

We currently do not sell personal information or share personal information for cross-context behavioral advertising. The current version does not serve third-party targeted advertising and does not integrate advertising or cross-app attribution SDKs such as AppsFlyer, Umeng, or AdMob. Firebase Analytics is used only for Interlove's own product analytics; ad storage, ad user data, and ad-personalization signals are denied by default, and Google Signals and ads personalization are not enabled. Accordingly, there is currently no need to display a link to opt out of sale or sharing.

Transferring necessary information to processors that contractually provide hosting, verification, verification-code delivery, payment verification, or security services to us is not a sale. However, we treat an entity as a service provider or contractor only when the actual arrangement satisfies applicable legal requirements.

If we begin selling personal information or sharing personal information for cross-context behavioral advertising in the future, we will update this Policy before doing so, provide a "Do Not Sell or Share My Personal Information" link, and recognize and honor valid opt-out signals such as Global Privacy Control as required by law.

10. Retention and Deletion

We do not retain personal information indefinitely solely because it might be useful in the future. Retention periods depend on how long the information is needed to provide a feature, account status, reasonable user expectations, the sensitivity of the information, fraud and security risks, statutes of limitation, backup cycles, and legal obligations related to tax, accounting, consumer protection, and law enforcement.

The account-closure process includes a fourteen-day cooling-off period. Account functionality may be restricted during this period, and you may withdraw the request by following the instructions on the relevant page. Once closure takes effect, identity-verification data is automatically deleted under Section 7.4; you do not need to email a separate deletion request. Other personal information is handled under the deletion or de-identification rules above. A legal-retention exception applies only to the specific records that must be retained and does not justify retaining all facial or identity materials.

Information stored locally by the app may remain on your device after you log out until you clear the app's data or uninstall it. See Section 11.

11. Device Permissions and Local Storage

11.1 Device Permissions

• Camera and photo library: Requested only when you take or select profile photos, chat images, verification materials, or report evidence.
• Microphone: Requested only when needed for an actually available liveness-detection or voice feature.
• Notifications: When push notifications are actually available, the operating system asks whether you wish to allow them. You may disable them in system settings or app preferences.

The current Services do not require precise GPS location or contacts permission. If we add such features in the future, we will explain their purpose before requesting permission. Refusal will not affect unrelated features.

11.2 Local Storage

The app may store login status, access and refresh tokens, user ID, expiration time, guest gender preference, onboarding status, language preference, and translation resources and cache locally on your device. Logging out clears account login credentials, but guest preferences, language, and resource caches may remain. You may remove local copies by using your system's "Clear App Data" function or uninstalling the app.

Use a device screen lock and do not share a logged-in device with others. The app writes to the device clipboard only when you deliberately copy chat text. The current app does not read clipboard content.

12. Cross-Border Processing

INTERLOVE INC is a U.S. company. Interlove's production database, private uploaded files, and verification-notification storage are hosted on Alibaba Cloud infrastructure in Singapore. Identity information and identity-card images submitted to Interlove, including through the mainland-China route, are stored there. Tencent states that its SDK data collected in mainland China is stored in mainland China; Didit publishes the European Union as its default processing and storage region. See Section 7.3 for the copies held by each recipient.

We use contractual terms, access controls, transfer-security assessments, or other appropriate safeguards as required by applicable law, and require recipients to process information only for agreed purposes. Where cross-border transfers require separate notice or consent, we will identify the overseas recipient, data categories, purpose, method, and means of exercising rights, and obtain the necessary authorization before transfer.

Other payment, communication, and support information may be processed where the relevant providers operate. The applicable data-protection laws may differ from those in your jurisdiction. Privacy requests concerning Interlove's copies or coordination with a verification provider can be sent to contact@interlove.net.

13. Information Security

We use administrative, technical, and physical measures appropriate to the nature and risks of the information, such as access controls, separation of duties, access records, service-provider restrictions, security testing, backups, and incident response. Only personnel authorized based on a business need may access personal information.

No network, device, or storage method can guarantee absolute security. You should protect your phone, email account, verification codes, and login status, and avoid sending unnecessary sensitive information through chat. Contact us immediately if you suspect unauthorized access.

If a personal-information security incident may affect your rights and interests, we will investigate, contain the risk, and notify you and competent authorities as required by applicable law.

14. Your Privacy Rights

Depending on the law where you live, you may have some or all of the following rights:

• To confirm whether we process your personal information and request access to or a copy of it;
• To correct inaccurate information or complete information that is incomplete;
• To delete personal information or close your account, subject to legal exceptions;
• To withdraw consent-based processing. Withdrawal does not affect the lawfulness of processing that occurred before withdrawal;
• To object to or restrict particular processing, and to receive portable data when applicable;
• To appeal decisions concerning enforcement against your account, content review, or a privacy request;
• To lodge a complaint with a data-protection, consumer-protection, or judicial authority with jurisdiction.

You can edit your profile, manage photos and notification preferences, or initiate account closure in the app. As a general rule, you cannot change your gender yourself, but data-entry errors or correction requests made under applicable law may be handled manually through customer support.

To submit another request, email contact@interlove.net with the subject line "Privacy Request" and identify your account, the type of request, and the applicable jurisdiction. To prevent fraudulent requests, we verify your identity using measures proportionate to the sensitivity of the request. We will not require additional information unrelated to verification.

We will respond within the period required by applicable law. We may be unable to delete or fully provide certain information immediately when it is needed to complete transactions, maintain safety, respect the rights of others, comply with a legal hold, or satisfy another legal exception. If so, we will explain the reason and any available appeal process.

15. Supplemental Notice for California Residents

This Section provides additional transparency for California residents. To the extent the California Consumer Privacy Act (CCPA) applies to us, we comply with its mandatory requirements. Even if we do not meet the statutory applicability thresholds during a particular period, we will handle user requests under this Section to the extent reasonably practicable.

15.1 Categories of Personal Information in the Preceding 12 Months

Full date of birth, immigration status, income, and marital, parental, or family-planning information may not all fall within the CCPA's statutory definition of sensitive personal information, but Interlove still protects them as sensitive or highly private information as described in Section 2.2.

None of these categories was sold or shared for cross-context behavioral advertising during the preceding 12 months. We will not deny services, charge different prices, reduce service quality, or engage in other discrimination prohibited by law because you exercised a CCPA right.

15.2 California Rights

When the CCPA applies, you have the right to request information about, access to, and a portable copy of your personal information; request deletion or correction; opt out of sale or sharing; limit the use and disclosure of sensitive personal information when applicable; and submit a request through an authorized agent. We currently use sensitive personal information only to provide the Services you reasonably expect, maintain safety and security, verify identity, and comply with law. We do not use it to infer characteristics unrelated to the Services. Accordingly, a separate "Limit the Use of My Sensitive Personal Information" link generally is not currently required.

Submit a request through the in-app channel or by emailing contact@interlove.net. For requests to know, delete, or correct, when required by law, we generally confirm receipt within 10 business days and respond within 45 calendar days. If an extension is reasonably necessary, we will explain why. Requests to opt out of sale or sharing, limit the use of sensitive information, or exercise similar rights will be processed within any shorter period prescribed by law.

An authorized agent should provide authorization signed by you. We may still verify your identity and authorization directly with you. We use information collected for verification only to complete the verification, prevent fraud, and maintain compliance records.

15.3 Notice at Collection

This Policy also serves as our general notice at collection. For identity verification, device permissions, human review of chats, report evidence, purchases, or other sensitive contexts, we provide a notice at or before the point of collection that identifies the categories of information, purposes, retention period or criteria, and a link to this Policy.

16. Browser Signals and Cross-Service Tracking

Because the industry does not uniformly interpret the traditional browser "Do Not Track" signal, Interlove does not alter processing necessary for the core Services in response to that signal. The current Services do not use third-party targeted advertising or cross-site or cross-app tracking to create advertising profiles.

Global Privacy Control is a signal used to communicate an opt-out from sale or sharing. We currently do not sell or share personal information. If we engage in such activities in the future, we will recognize and honor valid GPC signals as required by applicable law and will not require a user to create an account solely to opt out.

17. Minors

Interlove is intended only for adults who are at least 18 years old. Minors may not register for or use the Services. We do not knowingly collect personal information from anyone under 18. If we discover that an account belongs to a minor, we will restrict or terminate the account and take reasonable steps to delete the related information, except for records necessary to protect minors, investigate safety matters, or comply with legal obligations.

If you believe that a minor has provided information to us, contact us immediately using the information at the end of this Policy and provide enough information for us to identify the relevant account.

18. Updates to This Policy

We may update this Policy to reflect changes in features, service providers, law, or security practices. We identify the version, last-updated date, and effective date at the top of the page. We will provide advance notice of material changes through the app, email, or another reasonable method. If a new use requires consent by law, we will obtain consent again before beginning that processing.

We will not expand the use of previously collected private messages, identity information, or biometric information to a purpose materially incompatible with the original purpose merely by amending this Policy.

19. Contact Us

If you have questions about this Policy, our personal-information practices, or your privacy rights, or if you wish to report a suspected data-security incident, contact us through in-app customer support or at:

When submitting a request, identify your account, location, and specific request. Do not send original identity documents, full identity-document numbers, payment-card information, or verification codes through ordinary email. If additional materials are necessary, we will provide an appropriate submission method.