Privacy Policy

About this policy

Divomi helps people build connections. This policy explains the information involved in those connections and the choices available to account holders. The responsible legal entity and privacy contact have not yet been designated for publication. No company registration, representative or contact address belonging to another app applies to Divomi.

The current preview

The mobile design preview uses fictional profiles. Profile edits, preferences, gems, HMU posts and conversation examples are saved on the device through local app storage. The preview is not connected to a production account, payment, advertising or messaging service. Uploaded preview photos remain local unless you explicitly use a separately configured service.

A separate email signup client can contact the configured authentication provider when its environment is supplied. That client does not turn the fictional preview into an authenticated production account. Development hosting can receive routine network requests and technical logs.

Account and profile information

The intended account flow asks for an email address, date of birth, display name and profile information. Photos, interests, biography and optional social accounts support discovery and conversation. A protected birth date determines eligibility; other members see age rather than the full birth date. Age cannot be hidden.

Profile photos must satisfy moderation requirements. The planned service accepts at most five profile photos and requires three approved distinct face photos before adding people beyond the initial allowance.

Conversations and optional sharing

Messages, HMU content, requests and reports are information you choose to create. Other members receive the content addressed to them or visible to their eligible group. An optional social account handle is shared according to the permission choice attached to it. Recipients may capture or retain shared messages outside Divomi.

Profile capture protection is a planned safeguard that needs device testing. It cannot guarantee that every external recording method is prevented. Chat capture is permitted.

Age groups and safety

Members aged 13 through 17 may use friendship features within their age group. Adults aged 18 through 90 belong to a separate group. Adult dating preferences do not apply to teen accounts. Restrictions must be enforced by the server and cannot be removed through a paid plan.

Divomi prohibits sexual content, nudity, sexual solicitation, harassment, impersonation and fraud. Moderation may examine reported content and relevant account activity. Staff access is intended to depend on assigned responsibilities and recorded actions.

Verification and sensitive information

The local photo quality prototype can identify possible image quality or face count problems. It does not establish identity, age or liveness and cannot award a verification badge.

Before collecting verification selfies or biometric information in a live service, Divomi must publish the actual method, provider, processing purpose, applicable consent choices, retention period and deletion process. No indefinite selfie storage or automatic identity verification is represented by this draft.

Device permissions and technical records

Camera, microphone and photo library access support features you choose to use. Device permission prompts apply before access. You can change permissions in your phone settings.

Location based discovery, push notifications, diagnostics and analytics require a final implementation inventory. This preview does not request precise location. A live policy must identify which technical records are actually collected, their purposes and retention periods.

Payments and advertising

No payment or advertising network is connected to the preview. Gem balances and subscription previews are simulated.

The intended store flow will rely on the selected payment platform for payment credentials and receipts. Rewarded ads must be optional and rewarded only after a valid completion. Any advertising identifiers, partners, tracking permissions and regional consent requirements must be disclosed before an ad integration is enabled.

Service providers and disclosures

Divomi plans to use infrastructure providers for authentication, storage, delivery and hosting. Final providers, processing locations and contracts must be confirmed before real member data is collected. The present draft does not claim a completed international transfer arrangement.

A live service may need to preserve or disclose limited records to comply with a valid legal obligation or investigate abuse. Such access must be limited to the information required for the stated purpose.

Storage, deletion and account controls

The preview retains its saved state on the device until local data is reset, app storage is cleared or the app is removed. Browser storage may persist across visits. Resetting local preview data does not delete an unrelated live account.

The live deletion workflow, backup expiry, moderation retention and verification retention are launch requirements. Pausing an account should hide it from discovery while preserving existing conversations. Deletion must explain its consequences and require confirmation. Store subscription cancellation is a separate action.

Your requests and choices

Before release, Divomi must supply a working privacy contact and a route for access, correction, export, restriction and deletion requests as applicable. Incorrect birth dates require a reviewed correction process.

Notification preferences and privacy switches in the current preview are saved locally. They do not change an operating system permission or claim that an unconnected server has enforced them. You may contact your relevant data protection authority where applicable.

Policy updates

The final policy will carry an effective date and a revision history. Material changes should be communicated before they take effect. This draft must be updated to match the deployed service and reviewed for the countries where Divomi launches.