Beco Privacy Policy

Application: Beco: A New Face, A New Story
Android package: chat.page.beco.gp
Effective Date: October 15, 2026
Last Updated: October 15, 2026
Contact: service@beco.page

Beco helps adults meet through one-to-one video calls, discover people through random video matching, send virtual gifts, follow other users, and continue conversations by text. This Privacy Policy explains the personal information involved in those experiences, the reasons we process it, the circumstances in which it is disclosed, and the choices available to you.

References to "Beco," "we," "our," and "us" mean the operator responsible for the Beco application and related support services. "Personal information" means information that identifies you or can reasonably be linked to you, including information associated with your account rather than your real name. Beco is for individuals aged 18 and older only.

Read this Policy together with the Beco Child Safety Standards. Sections 11 and 23 describe in-app reports and child protection; Sections 16 and 19 explain related disclosures and retention. For account deletion, see Section 20.

1 Application of This Policy

1.1 What this Policy covers. This Policy applies when you register for Beco, appear in discovery, participate in calls or matching, exchange messages or gifts, follow users, upload content, or communicate with our support team. It also covers associated account, technical, transaction, and safety records. It is separate from our Terms of Service and Community Guidelines. Our Beco Child Safety Standards explain prohibited child sexual abuse and exploitation and the related reporting and enforcement process; this Policy explains how information used in that process is handled.

1.2 Responsibility for processing. Beco determines the purposes and means of processing information for its services. Providers engaged to operate parts of the service act under the arrangements described in Section 17. A platform you use for payment or sign-in may separately determine how it handles information under its own privacy policy.

1.3 Notices for specific features. A feature may present an additional notice explaining sensitive or otherwise unexpected processing before it occurs. This Policy does not replace required in-app disclosures, device permissions, or affirmative consent. Contact service@beco.page for information about the responsible operating entity or any practice described here.

2 Registration and Account Administration

2.1 Information supplied during registration. We collect the information submitted through your selected registration method, which may include an email address or phone number, account name, authentication information, and date of birth or age declaration. If you select a supported external sign-in method, we receive the identifier and permitted profile information supplied by that provider.

2.2 Account records. We assign an account identifier and maintain records of registration, sign-in events, account status, relevant settings, accepted policy versions, and consent choices. These records allow us to authenticate access, preserve your preferences, meet eligibility requirements, and respond to account requests.

2.3 Necessary and optional information. Registration screens identify information needed to open or secure an account. Additional profile information can be optional. If you decline information objectively necessary for a particular service, that service may be unavailable; this does not permit collection of unrelated information as a condition of access.

3 Profiles and Home Screen Discovery

3.1 Profile information. We process your display name, profile photo, biography, age or age range, country or region, language, and other fields you choose to complete. We use submitted profile details to create the profile that other users encounter in discovery and during interactions.

3.2 Visibility to other users. Your displayed profile and any availability indicators associated with it may appear on the home screen, in matching, in follower relationships, or within conversations. Information you put in a visible profile field should be treated as shared with that audience. Confidential registration details are not made public merely because you create a profile.

3.3 Discovery activity. When you browse profiles or initiate a call from the home screen, we process the relevant account identifiers and interaction event. These records help route your request, operate discovery, troubleshoot problems, and investigate misuse. You may edit available profile fields or request correction through service@beco.page.

4 One to One Video and Audio Processing

4.1 Data transmitted during a call. When you use a video call, your device captures camera images and microphone audio and sends the live communication through the infrastructure needed to connect you with the other participant. Beco and its communications processors handle the media and network information required to establish and maintain the session. The participant receives the image and sound you transmit.

4.2 Information about the session. We process participant account identifiers, request and connection events, timestamps, duration, call outcome, and relevant quality measurements. These records support connection management, fault investigation, abuse handling, and any applicable transaction reconciliation. A session record describing when a call occurred is different from a recording of its content.

4.3 Recording and sensitive analysis. Camera or microphone permission for a live call is not blanket authorization for recording, transcription, biometric identification, or unrelated analysis. Any service feature that retains call content beyond necessary transmission and temporary technical processing must provide a specific notice explaining the information captured, purpose, recipients, and retention, with consent where required. Separately submitted report evidence is handled under Sections 11 and 19.

4.4 Your surroundings and other participants. Video can reveal faces, voices, bystanders, rooms, documents, and background sounds. Take care when choosing what to disclose. Another participant may independently capture information using a device outside our control. We cannot promise that all copies made by another person can be prevented or recovered.

5 Random Video Matching

5.1 Matching records. Starting random matching requires us to process your account identifier, matching request, availability, connection information, and relevant eligibility or safety restrictions. We also process the resulting pairing, whether the connection succeeds, and related session events.

5.2 Information exchanged on connection. A matched user receives the profile information displayed in the matching experience and the live media transmitted once communication begins. Starting a match does not authorize access to your address book, private support correspondence, payment credentials, or unrelated device files.

5.3 Randomness and applicable controls. A random match can still be subject to account eligibility, blocking, availability, regional service restrictions, and preferences offered by the feature. It does not guarantee compatibility or a particular outcome. We use matching records to operate this experience, diagnose repeated failures, assess quality, and address harmful conduct.

6 Text Messages and Follow Relationships

6.1 Message content and delivery data. We process message text, supported attachments, sender and recipient identifiers, timestamps, and delivery information. Stored messages and attachments support delivery, conversation history, synchronization where provided, and investigation of reported problems or violations.

6.2 Following other people. We maintain follower and following relationships so you can locate people you want to contact again. Relevant relationships may be displayed in the social features where they are used. Your interactions may also inform discovery as explained in Section 14.

6.3 Privacy within conversations. A message is delivered to its intended recipient rather than published as a general post. Authorized staff or processors may nevertheless access relevant stored records when necessary for a support request, safety report, security incident, or lawful demand. This Policy does not represent that all communications are end-to-end encrypted; any such claim must be specific to an implemented feature.

6.4 Copies and removal. Recipients may retain or independently copy information they receive. Deleting a conversation from your view is not necessarily the same as deleting an account or every associated server record. Contact us for removal requests beyond the controls available in the app.

7 Virtual Gifts and Purchase Information

7.1 Gift activity. Sending a virtual gift generates records such as the sender and recipient account identifiers, item selected, gift value, time sent, and delivery status. Where a balance or virtual currency is used, we also process the corresponding credits, debits, and remaining entitlement.

7.2 Payments and verification. For purchases, we process order identifiers, product details, amount and currency, purchase time, payment confirmation, and any refund or chargeback status. Payment platforms such as Google Play process the payment credentials you submit to them under their own notices. Beco receives the records needed to validate and fulfill the transaction and handle related disputes.

7.3 What other users see. A recipient may see your displayed identity and the gift you sent. Giving a gift does not disclose your full payment credentials to that recipient or authorize them to access other account records. Gift visibility otherwise follows the context in which the gift is delivered.

7.4 Reasons for retaining transaction records. Gift and purchase records help fulfill orders, investigate unauthorized spending, reconcile balances, prevent fraud, and comply with financial recordkeeping obligations. A gift is not consent to disclose private messages, contact information, or live-call content for unrelated purposes.

8 Device Information and Service Diagnostics

8.1 Technical data. We process IP addresses, device model, operating system, app version, interface language, time zone, network type, and app-generated or platform-permitted identifiers used for service operation and security. These records can be collected automatically when the app connects to our systems.

8.2 Performance and usage records. We process feature events, connection errors, crash reports, response times, and video or message delivery diagnostics. The purpose is to understand how Beco operates on different devices, correct faults, prevent unauthorized access, and assess service improvements. Diagnostic collection is limited to information relevant to those purposes.

8.3 Limits on device access. Installing Beco does not grant permission to read unrelated photos, contacts, SMS messages, telephone call logs, or the contents of other apps. Restricted access requires a justified feature purpose and the applicable permissions and disclosures. Permanent hardware identifiers are not linked to resettable identifiers or sensitive information in a manner prohibited by platform requirements.

9 Location and Regional Context

9.1 General location. We may derive an approximate country or region from your IP address and process the region or language you choose in your profile. This supports localization, service availability, security checks, and regional preferences where offered. An IP-based estimate is not a reliable statement of your precise physical location.

9.2 Precise device location. Precise coordinates are different from a self-selected country or an IP-derived region. If a feature requires precise location, it must explain why and obtain the necessary permission before access. This Policy is not authorization for undisclosed background location collection.

9.3 Location in shared content. A profile field, photo, embedded image metadata, message, or video background may reveal location even when GPS permission is disabled. Review the information you share and edit optional location fields as needed. Disabling device location permission does not stop ordinary network connections from disclosing your IP address to the services handling them.

10 User Generated Content and Ownership

10.1 Content we handle. User generated content (UGC) includes profile photos, biographies, messages, attachments, and other photos, videos, or text submitted through supported features. We collect the content, its account association, relevant timestamps, visibility settings, and technical file information needed to manage it.

10.2 Storage and use. We store, transmit, display, cache, resize, or compress content as necessary for the function you request. Content may also be examined in connection with a report, infringement complaint, or security issue. The audience depends on the feature: a discoverable profile and a direct message do not have the same visibility.

10.3 Copyright and permissions. You retain your ownership rights in content you submit, subject to any service license described in the Terms of Service. This Policy does not transfer your copyright to Beco. You must have the necessary rights and permissions to upload material, including an appropriate basis to disclose personal information about another person.

10.4 Infringement and violations. We may restrict, remove, or preserve relevant content while reviewing alleged infringement, unlawful disclosure, exploitation, harassment, or another prohibited activity. Send a copyright or privacy complaint to service@beco.page with information identifying the content and your concern. A lawful complaint process may require sharing relevant allegations with the uploader, with unnecessary personal details limited where possible.

11 Support Reports and Moderation Records

11.1 Information in a request. When you seek help or report an account or content, we process your contact details or account identifier, the reported account or content identifier, the reason selected, your description, and relevant evidence you submit. We may connect the request with relevant message, matching, call-session, or transaction records to investigate it. Other users may similarly provide information about you in their reports. We collect only information relevant to understanding and handling the concern.

11.2 Review and enforcement. Authorized personnel and specialist processors may review relevant information, assisted by automated tools where appropriate, to address fraud, harassment, impersonation, child endangerment, or other violations. Access is limited to the information needed. Safety review does not create permission to secretly record every conversation or collect unrelated device information.

11.3 Decisions and challenges. Outcomes may include content removal, reduced access to a feature, account suspension, or a referral required by law. Contact service@beco.page if you believe an action was mistaken or want to provide context. Report records and reviewer notes are not public profile information. We do not routinely disclose a reporter's identity to the reported user. Any disclosure needed for a lawful investigation or proceeding must be limited to what is necessary; we cannot promise absolute anonymity.

11.4 Support verification. We may ask for proportionate evidence that you control the account before handling sensitive requests. Do not send passwords, one-time sign-in codes, full payment-card details, or unnecessary identity documents to our support inbox. Any stronger verification process must explain its purpose and secure submission method.

11.5 Submitting feedback within Beco. Users can submit feedback, concerns, and reports through Beco's in-app reporting or feedback mechanism without leaving the app. Use the Report or feedback control, identify the relevant account or content, provide the concern through the available reporting fields, and submit it within Beco. Reports can concern suspected underage use, CSAE, CSAM, grooming, sextortion, or another safety issue. An external browser, separate email application, purchase, or agreement from the reported user is not required to submit an in-app report.

11.6 Submission and case records. We process the submission time, relevant app and technical information needed to deliver the report, the report's status, necessary follow-up correspondence, review findings, and action records. These records support receipt, prioritization, investigation, enforcement, appeals, and lawful reporting. We do not require users to obtain or upload suspected CSAM to make a report; account, content, or session identifiers and a description can identify the concern.

11.7 Reporting and blocking. Reporting communicates a concern to Beco for review. Blocking changes interactions with the blocked account and can be used separately. A block alone should not be treated as submission of a child safety report. You can end a call or stop communicating immediately and then report the account; you do not have to continue the interaction to provide evidence.

11.8 Supplementary contact. You can also email service@beco.page, using the subject "Beco Child Safety" for a child safety concern. This route is available to parents, guardians, affected individuals, and people without a Beco account. It supplements the in-app mechanism. Share relevant identifiers and a description; do not attach or forward suspected CSAM or send passwords, verification codes, or unnecessary identity documents.

12 Why Beco Uses Personal Information

12.1 Delivering the requested experience. We use account, profile, media, communication, technical, and transaction information to authenticate access, display profiles, route calls, form video matches, deliver messages and gifts, maintain follow relationships, and provide customer assistance.

12.2 Improving usability and reliability. We analyze relevant usage and diagnostic records to identify connection failures, simplify navigation, assess feature performance, and improve service quality. We use aggregated or de-identified records where individual information is unnecessary. A record is not anonymous simply because a username has been replaced by a numeric identifier.

12.3 Personalization and communications. Relevant profile preferences and interaction history may be used to personalize discovery or settings as described in Section 14. We also use contact information for security alerts, purchase notices, important service changes, and responses you request. Optional promotional messages, if offered, are subject to applicable consent and unsubscribe requirements.

12.4 Safety and legal responsibilities. Necessary information supports age restrictions, account protection, abuse and fraud prevention, dispute resolution, financial obligations, and compliance with lawful requests. We assess any new purpose before using existing information and provide additional notice or request fresh consent when required. Child safety reports, age-review evidence, and information identifying a child or reporter are not used for advertising, engagement recommendations, or unrelated profiling.

13 Legal Bases and Sensitive Information

13.1 Providing services under an agreement. Where a legal basis is required, processing objectively necessary to supply a requested Beco service may rely on performance of our agreement with you. Examples include routing a call, delivering a message, and fulfilling a purchase. Merely mentioning a practice in the Terms does not make all processing contractually necessary.

13.2 Legitimate interests and legal obligations. We may rely on legitimate interests for proportionate security, support, fraud prevention, and improvement after assessing the impact on your rights. We rely on legal obligations where applicable recordkeeping, reporting, or other laws require processing. Emergency processing to protect vital interests is limited to circumstances permitted by law.

13.3 Consent. We obtain consent when required for optional permissions, unexpected sensitive-data uses, certain tracking, or promotional communications. A lawful basis under privacy legislation does not remove a separate platform requirement for permission or prominent disclosure. You can withdraw consent through the routes in Section 22.

13.4 Sensitive disclosures. Your content may reveal health, beliefs, sexuality, identity documents, or other sensitive information even when Beco has not requested it. Do not share information you do not want a recipient to receive. Any deliberate collection or analysis of sensitive categories requires the additional safeguards and legal conditions applicable to that use.

13.5 Child safety processing. A safety purpose does not create unrestricted authority to collect information. We assess the lawful basis for reviewing reports, checking eligibility, preserving evidence, and disclosing information. Where information concerns a child, sensitive categories, or alleged offences, we apply any additional legal conditions and safeguards. Evidence requests must be proportionate to the issue and use a secure method; consent to use Beco does not authorize undisclosed biometric or other sensitive analysis.

14 Personalization and Automated Decisions

14.1 Information used for discovery. Where discovery is personalized, relevant factors may include selected language, region, stated interests, availability, follow relationships, interaction history, and safety restrictions. These factors help organize the experience rather than guarantee that another user shares your preferences or intentions.

14.2 Boundaries on profiling. Participation in a call does not constitute consent to infer sensitive personal traits from a face, voice, or background. We do not treat a gift or follow action as permission for unrelated profiling. Materially different uses require appropriate notice and a lawful basis before they begin.

14.3 Review and control. You may change the preferences offered in the app or contact us about personalization. Where applicable law grants rights concerning solely automated decisions with legal or similarly significant effects, you may request information, challenge the outcome, and seek human review. Reasonable temporary safeguards may remain while a safety matter is reviewed.

15 Permissions and Local Storage

15.1 Feature permissions. Camera and microphone access enable video calls. Access to selected photos or videos enables uploads. Notification permission enables alerts. We request access in connection with the relevant function and present additional explanation before unexpected processing, where required. Permission is not inferred from closing or ignoring a prompt.

15.2 Refusal and revocation. You can refuse a permission or change it through your device settings. The dependent function may stop working, such as video transmission after camera permission is removed. Unrelated features should remain available when they do not require the declined access.

15.3 Session and preference technologies. Local tokens, cached files, preferences, and similar technologies help keep you signed in and operate the service. Related web resources may use essential cookies. Nonessential tracking or analytics, where used, must be disclosed and made subject to the choices required by applicable law. Removing local data alone does not delete records already held on our servers.

16 Circumstances in Which We Disclose Information

16.1 Sharing required for your interactions. We disclose visible profile details to users who encounter your profile, live media to call participants, messages to recipients, and gift information to the receiving user. These disclosures are limited by the function and audience involved. Your password and confidential payment credentials are not part of those social disclosures.

16.2 Operational assistance. Necessary information is disclosed to providers supporting the functions described in Section 17, subject to appropriate contractual and security controls. A provider should receive what is needed for its role rather than unrestricted access to all account information.

16.3 Law and protection of rights. We may disclose proportionate information to comply with a valid legal demand, meet a reporting obligation, address a credible safety threat, investigate fraud, or establish or defend legal claims. We assess requests for authority and scope and notify affected users when appropriate and legally permitted.

16.4 Changes to the business. Relevant information may be reviewed or transferred during a merger, acquisition, restructuring, financing diligence, or transfer of Beco, under confidentiality and privacy safeguards. We provide legally required notice of a change in responsibility or material changes in use. Applicable privacy rights continue to apply.

16.5 Specific user direction. We may disclose information when you expressly request a transfer or provide valid consent for a clearly explained purpose. Such a direction does not authorize unrelated further disclosure or waive another person's rights.

16.6 Child safety disclosures. Our process for confirmed CSAM provides for reporting to the National Center for Missing & Exploited Children (NCMEC) or the relevant regional authority, in accordance with applicable law. Necessary account or content identifiers, relevant communications or evidence, available technical records, and information about a child or reporter may be disclosed where lawfully required or permitted. We assess the recipient, legal basis, and scope and limit the disclosure accordingly. Notice may be delayed or withheld where prohibited by law or where notice would create a serious risk to a child or a lawful investigation.

17 Third Party Services and SDKs

17.1 Categories and access. Beco may use hosting and database providers, real-time audio and video infrastructure, authentication tools, message and notification delivery services, diagnostics tools, payment validation services, customer support systems, and safety processors. Their data access depends on their role. A video infrastructure provider may process media and network data; a support processor may handle a ticket and its relevant evidence.

17.2 Our requirements for processors. Providers working on our instructions must protect information, restrict processing to authorized purposes, and support applicable deletion and retention requirements. We remain responsible for evaluating data collection performed by SDKs included in Beco. Integration of an SDK does not excuse undisclosed collection or unauthorized reuse.

17.3 Independent provider practices. Payment platforms, optional sign-in providers, and external services you choose may also process information independently. Their own notices govern that independent processing. The notice for a particular integration should identify its provider and any additional required data practices; contact service@beco.page for further information about recipients.

17.4 Sale and advertising. We do not sell personal and sensitive user data for money. This Policy does not authorize using private conversations for unrelated targeted advertising. If advertising, cross-app tracking, or other additional disclosures are introduced, the relevant data, providers, purposes, and controls must be explained before processing, with consent or opt-out mechanisms where required. We apply applicable statutory definitions when responding to rights concerning a sale or sharing of information.

17.5 Access to child safety records. Any provider assisting with child safety reviews receives only the information needed for its assigned task, subject to appropriate confidentiality, security, retention, and deletion controls. Such records must not be used for the provider's advertising, unrelated profiling, or general model training. Beco remains responsible for the disclosures and purposes of processing undertaken on its behalf.

18 Storage Locations and International Processing

18.1 Where processing occurs. Information is processed where Beco and the providers supporting the applicable service operate. Storage or support locations may differ from your country of residence. Calling or messaging someone in another country also involves delivering information to that participant's location.

18.2 Protection during transfers. Where international transfers are restricted by applicable law, we use a permitted transfer mechanism and safeguards appropriate to the transfer, such as a relevant adequacy decision or approved contractual protections. Additional technical or organizational measures are applied when required. We do not assume that privacy laws are identical across countries.

18.3 Requests for details. You may contact service@beco.page for information about the storage countries, recipient categories, and transfer safeguards applicable to your account. Where the law provides access to a copy of relevant safeguards, we make that information available subject to necessary protection of confidential terms, system security, and third-party personal information.

19 Retention and Secure Disposal

19.1 How retention is determined. We retain identifiable information only while it is reasonably needed for its disclosed purpose or a lawful obligation. Relevant criteria include whether the account remains in use, the function involved, the sensitivity of the data, outstanding transactions or disputes, security risks, and applicable statutory limitation or recordkeeping periods.

19.2 Records supporting an active account. Profile and account information supports continued access and account management. Stored messages, uploaded content, and follow relationships support the social functions you use, subject to deletion requests and controls. Matching events, call metadata, and diagnostics are retained while needed for operational review, troubleshooting, or a documented safety purpose. Temporary transmission of live media is distinct from storage of submitted content or report evidence.

19.3 Limited retention after a removal request. Transaction records may remain for tax, accounting, refunds, or chargebacks. Relevant report and security evidence may remain for an investigation, proportionate fraud prevention, legally required reporting, or legal claims. Retained exception records are restricted to those purposes and are not used to rebuild a deleted profile or continue optional marketing.

19.4 Backups and final disposal. Information removed from active systems may remain temporarily in restricted backups until scheduled overwrite or secure deletion. Backup copies are not used for routine access, and deletion instructions are reapplied if a backup is restored. When retention is no longer justified, information is deleted or irreversibly anonymized. You can ask us to explain the retention period or criteria for a particular category.

19.5 Child safety evidence and age checks. We separately assess the need to retain report records, limited age-review information, enforcement decisions, and evidence required for lawful reporting, investigation, or protection against further abuse. Retention follows the relevant legal period or documented necessity criteria and is reviewed when the case or obligation changes. A safety concern does not justify indefinite retention of all account information. Once the lawful need ends, the relevant records are securely deleted or irreversibly anonymized. Necessary preserved evidence remains unavailable for ordinary user access.

20 Deleting Your Account or Specific Information

20.1 Starting a request. Use the account deletion option within Beco or email service@beco.page with the subject "Beco Account Deletion" and information identifying your account. The email route is available without reinstalling the app. We may verify account control using proportionate information to prevent deletion by an unauthorized person.

20.2 Scope of account deletion. A verified account deletion request covers the account and its associated personal information, including the profile, uploaded content, stored communications, and social records, subject to the limited retention reasons in Section 19. Merely suspending access, logging out, or uninstalling Beco is not account deletion.

20.3 Completion and exceptions. We process requests without undue delay and within the deadlines applicable to you. Where an extension or lawful exception applies, we explain it and the relevant retention criteria. We instruct processors acting for Beco to apply deletion where required. Deletion is not conditional on buying a service or retaining an unwanted account.

20.4 Separate content and third-party copies. You may request correction or deletion of specific information without closing the entire account. Independently saved recipient copies and records retained by payment platforms may be outside Beco's direct control and subject to separate obligations. Deletion does not automatically cancel an app-store subscription, if any; manage it through the platform administering that subscription.

20.5 Requests involving children and reporters. A parent, guardian, reporter, or affected person may contact service@beco.page about information concerning them or a child, without opening a new account. We use proportionate checks of identity and authority before disclosing or deleting sensitive information, with particular care not to reveal a reporter or expose a child. Removal of a confirmed underage account includes deletion of associated personal information, subject only to the limited and lawful preservation described in Sections 19 and 23.

21 Access Correction and Other Rights

21.1 Access and accuracy. Review or edit the account and profile fields available in Beco, or email service@beco.page to request access to your personal information or correction of an inaccurate record. Where applicable, you may request confirmation of processing and information about purposes, categories, and recipients.

21.2 Additional rights. Depending on your location and the law governing the processing, you may request erasure, restriction, portability, or objection to particular uses. Certain laws also provide rights relating to targeted advertising, specified profiling, or disclosures legally defined as sale or sharing. Mentioning these rights does not mean Beco carries out every listed practice.

21.3 Request handling. Identify your account and describe the information or right involved. We use reasonable identity checks, consider authorized-agent requests where permitted, and respond within the applicable deadline. Requests are ordinarily handled without a fee. If a lawful fee, extension, or refusal applies, we explain the reason and how you may seek review.

21.4 Complaints and fair treatment. You may challenge our response by contacting service@beco.page and may complain to a competent privacy authority or regulator where applicable. We do not unlawfully discriminate against users for exercising privacy rights. Restricting information that is necessary for a function may make that function unavailable, which we will explain where relevant.

22 Withdrawing Consent and Communication Choices

22.1 Methods of withdrawal. Withdraw device permissions in your operating system settings, change the consent preferences offered within Beco, or contact service@beco.page for assistance with other consent-based processing. Where promotional messages are sent, use the unsubscribe mechanism or ask us to stop them.

22.2 What withdrawal changes. Withdrawal stops the relevant future processing based on consent after the choice is implemented. It does not invalidate earlier lawful processing or require deletion of information that must remain under a separate legal basis. Necessary security, purchase, and account administration messages may continue even if you opt out of promotions.

22.3 Different controls serve different purposes. Turning off the microphone stops permitted audio capture but does not erase previous messages. Blocking a user changes interactions with that person but is not a request to delete your account and does not by itself submit a child safety report. Use the in-app reporting mechanism to bring a concern to Beco's attention. Contact us if you need help identifying the control that addresses your concern. We do not require a reason for withdrawing consent.

23 Age Restrictions and Child Protection

23.1 Minimum age of 18. Beco is exclusively for adults aged 18 and older. Anyone under 18 is prohibited from registering or using its services, including with a parent's or guardian's permission. We do not knowingly collect personal information from minors for ordinary service use. Age declarations and proportionate eligibility checks support the restriction.

23.2 Suspected underage use. If we become aware of a suspected underage account, we take appropriate steps to restrict access while assessing eligibility. Once underage use is confirmed, we terminate access and delete the associated personal information without undue delay, subject only to limited lawful preservation for reporting, investigation, or protection against further abuse. Any verification request must explain the information needed, its purpose, secure submission method, and handling. Report concerns through the in-app mechanism or service@beco.page.

23.3 Child Sexual Abuse and Exploitation (CSAE). Beco prohibits Child Sexual Abuse and Exploitation (CSAE), including grooming, sexual solicitation of minors, sextortion involving minors, trafficking for sexual exploitation, and creating, possessing, or distributing child sexual abuse material (CSAM) through the service. An adult-only designation does not reduce our responsibility to address these harms.

23.4 Reports within the app. Users can submit child safety concerns through Beco's in-app reporting or feedback mechanism without leaving Beco. Identify the account, content, message, or call involved and describe the concern through the available reporting fields. An email is an additional contact option, not a required step in the in-app reporting process. Do not download, reproduce, capture, or forward suspected CSAM to make a report. If a child is in immediate danger, contact local emergency services or law enforcement as well.

23.5 Restricted safety evidence. We may preserve the minimum information needed for lawful reporting, an investigation, or protection of affected individuals. Access is limited to authorized personnel and appropriate recipients. Such evidence is not retained for recommendations, engagement, or marketing and is deleted when the lawful preservation need ends.

23.6 Removal and lawful reporting. When Beco obtains actual knowledge of CSAM on its service, we promptly remove it or disable user access to it, while preserving only evidence that may lawfully need to be retained. We take appropriate action against involved accounts and use our reporting process for confirmed CSAM to notify NCMEC or the relevant regional authority in accordance with applicable law. Other suspected abuse is assessed and escalated or reported where legally required or appropriate. Content removal, account action, evidence preservation, and external reporting are separate parts of the response.

23.7 Child and reporter confidentiality. Information about a child or reporter is accessible only to authorized personnel and recipients with a legitimate role in handling the concern. We do not publish child safety reports or identifying details of affected children. These records are not sold or used for advertising, recommendations intended to increase engagement, or unrelated profiling. Lawful disclosures and requests for access are assessed to protect the rights and safety of everyone involved.

23.8 Proportionate age review. Age-review information is used to assess eligibility and related safety concerns. A request for additional evidence must be limited to what is necessary, and information that is not needed should be omitted or redacted where compatible with verification. If a separate verification provider or a sensitive verification method is used, its role and relevant data practices must be explained before collection, with any required consent. A safety review does not create permission to retain identity documents indefinitely.

23.9 Published standards and responsible contact. The Beco Child Safety Standards apply to Beco: A New Face, A New Story (Android package chat.page.beco.gp). They explicitly prohibit CSAE and CSAM and describe reporting, removal, account action, and lawful cooperation. Contact the Beco child safety point of contact through service@beco.page with the subject "Beco Child Safety". The child safety contact coordinates the handling of reports and questions about these standards.

24 Security and Incident Handling

24.1 Safeguards. We apply technical and organizational protections appropriate to the sensitivity of the information and the risks involved. These include encrypted transmission, authentication controls, restricted administrative access, confidentiality measures, and incident-response procedures. Service providers acting on our behalf must maintain appropriate safeguards.

24.2 Your account security. Keep your device and credentials secure and notify service@beco.page if you suspect unauthorized access or disclosure. Avoid sharing account access or sending passwords and one-time codes to other users. No communication service can guarantee absolute security or control every action by a recipient.

24.3 Responding to incidents. When we learn of a personal data security incident, we investigate, contain the issue where possible, take reasonable corrective measures, and assess notification obligations. Affected individuals and competent authorities are notified when required by applicable law, with relevant information and protective steps.

25 Changes to This Policy and Contacting Beco

25.1 Policy revisions. We may revise this Policy to reflect changes in Beco's features, information handling, service arrangements, or legal obligations. The current version identifies its effective date. Material changes are communicated through a prominent in-app notice, email, or another appropriate method, before taking effect where required.

25.2 Consent to new processing. Updating a document does not by itself authorize materially different use of information already collected. If a change requires new consent, we request it before beginning the relevant processing. Continued app use is not substituted for an affirmative consent action required by law.

25.3 Privacy contact. Direct privacy questions, access or correction requests, consent withdrawals, account deletion requests, and concerns about data handling to service@beco.page. Use the subject "Beco Privacy" where appropriate and include enough information to locate your account and understand the request without disclosing unnecessary sensitive details. You may request information about the responsible operator or a previous Policy version through the same contact.

25.4 Child safety contact. Send child safety concerns to service@beco.page with the subject "Beco Child Safety", or submit them through Beco's in-app reporting mechanism. The designated child safety contact is responsible for coordinating appropriate review and responding to questions about our child safety practices. For account deletion, use the subject "Beco Account Deletion". The email address also permits contact by individuals who do not have an account.

Related policy: Beco Child Safety Standards.