PRIVACY NOTICE

1. OVERVIEW

Greetings from Avero (“we”, “us”, “our”), a social‑focused service built to help users build genuine interpersonal connections. This privacy notice lays out how we collect, process, store, release, and safeguard your personal data whenever you access our mobile application Avero - Meet Beyond Borders (Package ID: com.avero.bloomy) alongside associated offerings (collectively named the “Services”).

We maintain full dedication to abiding by relevant privacy statutes and regulatory rules, among which are:

• California Consumer Privacy Act (CCPA) and California Privacy Rights Act (CPRA)
• Virginia Consumer Data Protection Act (VCDPA)
• General Data Protection Regulation (GDPR) for end‑users located within the European Economic Area
• Children’s Online Privacy Protection Act (COPPA)
• Google Play Data Safety specification criteria
• Other applicable federal and state‑level privacy statutes within the United States

By making use of our Services, you confirm you have read through, comprehended, and given consent for our gathering and handling of your personal details as laid out within this file. Should you disagree with our operational approaches, please refrain from utilizing our platform.

Crucial Reminder: This privacy notice applies to every Avero end‑user, regardless of geographical residence. If you live outside United States territory, please be aware your personal records could get transferred over and processed inside United States territories or other jurisdictions where we carry out commercial operations.

2. DATA WE GATHER

We pull user‑related records from multiple sources in order to deliver and refine platform services, enable social interaction, and match you with compatible platform participants. Information obtained falls under the categories listed below:

2.1 Manually‑Provided User‑Supplied Data

This category covers all details you actively submit while interacting with platform offerings:

• Account‑Creation Details: While setting up an account (including quick‑access login flows), you may supply your mobile phone number (used for identity verification), email address, or profile facts originating from third‑party authentication providers (for instance, display name and email linked to Google or Apple accounts).
• Profile‑Related Content: Custom details filled into your user profile, such as display name / alias, age bracket, gender identity, hobbies, personal interests, lifestyle preferences plus any other facts you opt‑in to share for improving matching accuracy.
• Interaction‑Generated Content: Materials shared during peer‑to‑peer exchanges, for example text conversations, voice snippets and media assets transmitted between platform accounts. By default we will not preserve this material unless local law enforcement mandates retention or content moderation is required to address platform‑rule violations.
• Feedback & Support‑Related Input: Information you submit when reaching out to our support workforce (via belushfend@gmail.com), including your questions, formal complaints and user feedback submissions.

2.2 Automatically‑Collected Technical Information

As you interact with our Services, our backend automatically gathers specific device‑level, usage‑pattern and interaction metadata. This collection supports stable platform operation and delivers personalized end‑user experiences:

• Device‑Specific Metadata: Facts about your handheld hardware including hardware model, operating‑system build version, unique hardware identifiers (Device ID, IMEI, UDID, Android ID, Advertising ID), MAC hardware identifier, public IP address, screen dimension specifications, battery‑level metrics and device‑configured language preferences.
• Usage‑Tracking Metrics: Records capturing how you engage with platform features, including access timestamps, activated functionalities (profile browsing, chat initiation), session duration metrics, interaction volume, user‑engagement benchmarks, application crash traces and performance‑diagnostic data.
• Location‑Derived Records: After receiving your explicit approval, we may pull coarse‑grained or precise positional data (sourced via IP geolocation or hardware GPS module) to surface nearby participant matches. Location‑related data is only fetched following your explicit approval; you are able revoke this permission anytime through device‑system configuration panels.
• Network‑Level Technical Traces: Details about your internet connection including signal strength metrics, Wi‑Fi operational mode, bandwidth consumption statistics, connectivity classification (Wi‑Fi / cellular mobile network), plus carrier‑provider identifiers; these metrics help fine‑tune platform performance and resolve technical malfunctions.
• In‑App Behavioral Logs: Traces of your actions within the application: viewed interface segments, clicked controls, search keywords entered and feature‑utilization patterns, used to polish platform offerings and tailor individual‑user journeys.

Transparency Regarding Data Capture

We maintain full openness about every piece of information we collect. Following Google Play’s Data Safety regulatory obligations, we clearly document all collected data categories, their intended operational purposes, plus facts regarding third‑party data distribution.

2.3 Information Obtained From External Partners

We may receive user‑related records originating from outside‑platform sources, including:

• External Authentication Providers: Whenever you leverage one‑tap login flows through Google, Apple or comparable external platforms, we receive profile attributes granted by you from those external services.
• Outsourced Operational Vendors: Our contracted third‑party service operators may forward usage‑related metrics back toward us to sustain platform workflows and drive iterative product enhancements.

3. DATA UTILIZATION

We leverage your stored information for these legitimate business‑driven objectives, staying compliant with applicable legal frameworks:

• Deliver & Sustain Platform Services: To instantiate and administer your user account, facilitate peer‑user communications, process incoming user‑initiated requests, and guarantee stable runtime performance for our offerings.
• Enable Smart‑Matching Capabilities: Process your profile entries, personal interests plus usage‑behavior logs to connect you with other platform participants sharing comparable preferences.
• Refine & Individualize Platform Experience: Analyze behavioral trends, pinpoint product‑improvement opportunities and customize service‑encounters for individual users.
• Maintain User‑Oriented Correspondence: Relay important service‑related announcements, respond to user‑submitted inquiries and deliver customer‑support assistance.
• Enforce Platform‑Wide Safety & Defensive Safeguards: Detect and block fraudulent conduct, block unauthorized access attempts and sanction rule‑breaking platform‑user activity.
• Fulfill Statutory Duties: Respond to legally‑valid official inquiries originating from governing authorities and satisfy regulatory‑compliance obligations.

Legal Grounds Behind Data‑Processing Activities

Under CCPA / CPRA regulatory text, our legal justifications for gathering and processing your personal datasets include fulfilling contractual commitments, pursuing legitimate commercial‑operational interests, satisfying legal‑statutory obligations and obtaining end‑user affirmative consent.

4. DATA DISCLOSURE PRACTICES

You retain the right to learn whether your personal datasets get handed over to external entities. We fully document the full scope of our data‑sharing workflows and you may submit requests for further granular particulars.

We never sell your personal‑identifiable information to third‑party actors in exchange for monetary profit. Information hand‑offs only take place within the scenarios listed underneath:

4.1 Sharing With Other Platform Participants

To enable interpersonal connections, we surface certain profile‑based attributes including your display alias, hobbies and personal interests toward other registered platform‑users.

4.2 Hand‑Off To Contracted Service‑Delivery Vendors

We onboard third‑party operational contractors to assist us in running and enhancing our platform ecosystem. These external contractors may access personal‑user data solely for executing assigned tasks commissioned on our organization’s behalf.

• Cloud‑hosted storage solution operators
• Behavior‑analytics solution providers
• Cybersecurity‑focused service operators
• Customer‑support tooling suppliers
• Payment‑transaction handling providers
• Content‑delivery network (CDN) infrastructure operators
• Advertising‑campaign collaboration partners

4.3 Disclosure Triggered By Legal‑Regulatory Requirements

We might release your stored datasets if statutory provisions compel us to do so, or when we conclude disclosure is reasonably necessary for safeguarding organizational rights, owned assets or personal‑user safety interests.

4.4 Information Transfer During Corporate‑Restructuring Events

In scenarios where Avero undergoes corporate‑merger proceedings, acquisition transactions, bankruptcy‑related proceedings or asset‑liquidation events, your personal‑user datasets may shift ownership as part of such corporate‑asset transfers.

5. USER DATA ENTITLEMENTS

For individuals residing within California jurisdictional boundaries, CCPA and CPRA statutes grant defined entitlements governing your personal‑information datasets.

Under applicable United States‑based privacy‑related statutes including CCPA alongside CPRA, you hold concrete entitlements over your own personal‑user records.

5.1 Entitlements For California‑Located Consumers

• Right To Access Record Details: You may submit requests to receive information covering categories plus concrete fragments of personal‑data we have accumulated linked to your user‑identity.
• Right To Request Erasure: You possess authority to demand removal of your personal‑stored records, subject toward legally‑defined exception clauses.
• Right To Opt‑Out: You are entitled to decline participation in interest‑driven promotional targeting and block prospective personal‑data sales operations.
• Right Against Retaliatory Treatment: Platform services cannot discriminate against you for exercising your statutorily‑endowed privacy‑related entitlements.

5.2 Right To Correct Inaccurate Entries

You maintain authority to amend erroneous or incomplete personal‑data entries stored within our systems.

• Revise your own‑profile material directly inside platform‑setting panels.
• Reach out to our team to file formal correction petitions for stored personal‑records.
• Supply corrected factual content for verification‑validation workflows.

5.3 General‑Scope User Prerogatives

• Access Privilege: Permission to inspect your stored‑profile content.
• Consent‑Revocation Prerogative: Ability to withdraw previously‑granted approval for selected data‑collection workflows.
• Account‑Termination Prerogative: Authority to fully erase your platform‑user account.

5.4 Steps For Exercising Your Legal Entitlements

To activate any privacy‑focused user‑prerogative, get in touch with us supplying your full legal name, account‑identifying details plus unambiguous written description outlining your formal petition.

6. DATA PROTECTION MEASURES

We attach high priority to securing your personal‑user datasets and deploy multi‑layered technical, administrative plus physical defensive safeguards.

6.1 Technical Defensive Countermeasures

• Cryptographic Encryption: We deploy mainstream‑industry cryptographic protocols to shield stored and transmitted user‑information.
• Secure Identity‑Verification Mechanisms: Hardened authentication workflows govern user‑account entry points.
• Network‑Layer Defensive Infrastructure: Our backend‑server environments are guarded by security‑oriented systems to block unauthorized intrusion attempts.
• Recurring Security‑Patch Rollouts: System components plus application code receive regular security‑maintenance upgrades.
• Secured Application‑Programming Interfaces: Every API‑based communication channel gets secured by encryption plus identity‑validation mechanisms.

6.2 Administrative‑Operational Safeguards

• Role‑based access‑permission restriction regimes
• Internal‑staff security‑awareness instruction sessions
• Formalized internal security‑governance documentation
• Documented incident‑response operating playbooks

6.3 Physical‑World Protective Controls

• Physical‑security enforcement inside data‑center premises
• Hardware‑device protection protocols

6.4 Response Procedures For Data‑Security Compromises

If a data‑breach incident materializes, we will immediately launch investigative procedures, notify impacted platform‑users and circulate actionable guidance for safeguarding their personal‑information assets.

7. DATA RETENTION POLICIES

Our data‑preservation workflows are structured to satisfy statutory‑regulatory requirements alongside justified commercial‑operational necessities.

• Account‑Related & Profile‑Stored Content: Kept throughout the period your user‑account stays in active operational state.
• User‑generated Communication‑Material: Normally not persistently stored by our backend infrastructure by default.
• Application‑Usage Metrics: Preserved for platform‑optimization initiatives plus security‑threat‑detection purposes.
• Payment‑transaction‑associated datasets: Maintained for the duration required to satisfy legal‑statutory obligations.

7.2 Post‑Termination Account‑Handling Rules

After you trigger account‑deletion procedures, our systems halt fresh‑data ingestion linked to your profile. Most personal‑identifiable datasets will get erased or anonymized once legally‑mandated holding periods conclude.

8. MINOR‑USER DATA‑HANDLING RULES

We take safeguards for under‑age end‑users very seriously and adhere toward applicable youth‑focused privacy‑related statutes.

8.1 Minimum‑Age Usage Restrictions

Our platform offerings are not built for usage by human participants younger than thirteen years old.

8.2 Response Upon Discovering Under‑Age‑User Records

• Promptly eliminate such improperly‑collected datasets.
• Terminate the minor‑linked user‑account instance.
• Block further data‑gathering activities originating from that user‑identity.

9. CROSS‑BORDER DATA‑TRANSFER PROTOCOLS

Avero’s operational headquarters sits within United States territory. User‑information assets may get relocated, stored and processed inside United States infrastructure plus other international territories.

9.1 Approved Cross‑Border Transfer Mechanisms

• Standard‑model contractual‑clause legal frameworks.
• Official governmental adequacy‑determination rulings.
• Alternative statutorily‑authorized transfer‑enabling instruments.

10. EXTERNAL‑PLATFORM HYPERLINKS & EXTERNAL INTEGRATED SOLUTIONS

Our service offerings might incorporate clickable links leading toward outside‑party web resources or implement integrations with third‑party software‑solutions.

• External identity‑authentication service providers.
• Social‑media‑platform interoperability components.
• Payment‑processing external‑system connectors.
• External behavioral‑analytics service modules.

11. REVISION MECHANISMS FOR THIS DOCUMENT

We aim to keep this privacy‑related notice current and factually‑accurate at all times.

• Whenever substantial functional‑policy adjustments take place.
• Whenever regulatory‑statutory rules impose required textual‑updates.
• When newly‑introduced platform‑functions alter existing data‑collection workflows.

12. DATA‑CONTROLLER IDENTITY & COMMUNICATION‑CHANNELS

In case you hold questions, expressed worries or formal petitions associated with this privacy‑notice document, feel free to reach our organizational representatives.

• Full‑Name Data‑Controller Entity: Belui Fende | Avero Development Company
• Designated Primary Correspondence‑Contact: Belui Fende
• Primary Electronic‑Mail Correspondence‑Address: belushfend@gmail.com