Domet – Video Chat & Sharing

This Privacy Commitment Framework sets forth transparent practices governing how Domet gathers, processes, retains, shares and protects user‑related information when you use our interest‑driven video‑chat social environment. This document applies to all interactions within the application, covering account creation, interest preference configuration, real‑time video and voice sessions, feedback submission and in‑app reporting operations. It describes both what data we handle and the full scope of control mechanisms available to each participant over their personal information.

Categories of Information We May Process

Information actively provided by users

• Account‑related inputs: usernames, user‑generated profile descriptions, self‑declared interest tags covering music, gaming, travel, pets, art, cooking and other hobby categories, contact email supplied for account recovery and support correspondence.
• Media voluntarily submitted: profile photographs and other imagery you choose to display on your public profile page.
• User‑submitted narrative content: text you enter for feedback forms, incident reports, supplementary notes in account‑management workflows.
• Voluntary identity‑verification materials: only supplied when you actively opt‑in for identity validation flows; such materials will never be demanded as a precondition for basic app access.

Information automatically obtained during service utilisation

• Device‑derived metadata: device model, operating‑system version, application build version, basic device‑level configuration markers used for crash diagnostics and performance tuning.
• Session‑derived operational signals: session timestamps, feature‑access behaviour, interest‑topic browsing patterns, interaction‑session duration statistics used to refine interest‑matching logic and stabilise service performance.
• Network‑related technical data: network connection type, approximate network latency metrics, utilised for optimising real‑time audio‑video transmission quality.

We explicitly note: raw real‑time video frames and voice audio streams within normal interest‑based chat sessions are transient streaming data. These live streams are consumed for immediate peer‑to‑peer interaction and are not systematically logged or archived for routine purposes.

Purposes For Which User Information Is Utilised

All data processing operations are tied to defined functional goals:

• Enable core interest‑driven matching: leverage self‑declared hobby and preference tags to connect participants with overlapping interests for video‑chat conversations.
• Maintain service stability: diagnose runtime faults, resolve audio‑video streaming anomalies, conduct performance optimisation for multi‑participant real‑time interaction.
• Uphold community atmosphere: support moderation review of user‑submitted reports, identify patterns that may signal disruptive behaviour, enforce published community standards.
• Deliver account‑management capabilities: process account‑related requests, respond to deletion submissions, complete identity verification for recovery scenarios.
• Conduct product iteration: aggregate de‑identified statistical insights to refine topic discovery workflows and overall application usability; no raw personal identifiers are included within such aggregated analytics outputs.
• Respond to user outreach: process incoming emails, feedback tickets and support enquiries sent to official contact channels.

Conditions Under Which Information May Be Shared

Domet will not sell user personal information to outside parties. Limited disclosure may only occur under constrained circumstances:

• Explicit user consent: data may be shared when you provide clear, affirmative permission for a specific sharing scenario initiated by yourself.
• Trusted service operators: we may pass necessary minimal datasets to vetted technical subcontractors who assist us in cloud infrastructure, crash‑analysis or support‑ticket handling. Such subcontractors are contractually bound to uphold equivalent privacy safeguards and are forbidden from repurposing the data for independent objectives.
• Platform safety necessities: when there exists credible evidence of substantial harm risk, relevant information may be disclosed to safeguard the wellbeing of platform participants, in alignment with our published safety protocols.

Data Retention Lifecycle & Erasure Rules

• Active‑account phase: profile metadata, interest tags and contact details are retained while your account remains active, so your interest‑based matching functions can operate normally.
• Transient session data: real‑time video‑chat streaming payloads exist only for the duration of an ongoing conversation and are not stored long‑term upon session close.
• Support‑ticket records: correspondence tied to support enquiries is preserved for a limited window needed to resolve your issue and handle potential follow‑up questions, then later pruned.
• Account deletion trigger: once your permanent account‑deletion request is fully processed within published working‑day timelines, all stored personal profile data, hobby tags, uploaded profile media and associated account metadata will be systematically erased from primary production systems. Certain residual anonymised aggregate statistical records which can no longer be linked back to an identifiable individual may be retained for analytical use.

Your Available User‑Control Entitlements

You retain extensive authority over your own information within Domet :

• Profile adjustment: you are free to revise, alter or remove your self‑written profile text, interest‑hobby tags and uploaded profile imagery at any moment directly inside application settings.
• Access review: you may submit a request to obtain a copy of the personal data the platform holds tied to your account identity.
• Correction requests: if you believe stored account‑associated details contain inaccuracies, you can file a correction application through official support pathways.
• Restrict processing: you may adjust device‑level permission toggles for camera and microphone at operating‑system level, which will limit corresponding app‑level capabilities accordingly.
• Permanent account removal: submit an account‑deletion application, triggering the full data‑erasure workflow described in our dedicated account‑deletion documentation.

Security Safeguards Implemented For Stored Information

We adopt multi‑layer technical and procedural protections to mitigate information exposure hazards:

• Transmission‑layer safeguards: relevant data in transit utilises industry‑standard encrypted transport mechanisms between client application and backend services.
• Access limitation: internal system access to user‑identifiable datasets is strictly permission‑gated; only designated operational staff with justified business need can gain access, with access events logged for audit trails.
• Storage‑side minimisation: avoid retaining unnecessary personal fields; datasets are categorised so sensitive attributes receive heightened protection controls.
• Incident preparedness: we maintain internal response workflows for potential data‑security events to evaluate scope and take appropriate mitigating actions if unusual circumstances arise.

External Links And Third‑Party Resources

Our in‑app environment may occasionally contain references leading toward outside‑platform destinations. This Privacy Commitment Framework exclusively governs data activities performed by VECTOR CONTAINER TERMINAL. Once you navigate to external services, their respective privacy policies and operational practices will take precedence. We encourage you to independently examine the privacy declarations for any third‑party service you elect to interact with.

Revision Mechanism For This Privacy Document

As our interest‑based social product evolves, we may periodically update clauses within this Privacy Commitment Framework to reflect changed functional designs, refined data‑processing workflows or updated safeguard standards. Material revisions that meaningfully shift how we handle personal user information will be communicated via in‑app announcement prompts. Continued utilisation of Domet services after the updated document’s effective date signifies your acknowledgement of revised terms. You are encouraged to revisit this framework at regular intervals.

Scope Clarification Statement

This Privacy Commitment Framework works alongside our other public‑facing documents such as community‑conduct provisions, account‑deletion procedure pages and safety assurance clauses. If there exists interpretive inconsistency between this framework and those dedicated protocol texts, the specialised subject‑specific document shall take priority for its corresponding subject area. This document describes our data‑handling practices in good faith and does not create implicit guarantees beyond the safeguards explicitly laid out within its text.