Privacy

What stays on your device, what you choose to share and the services that may be involved.

Operator
Davy Bangratz EI (PrimeTech Solutions)
7 rue des Cerisiers, 67280 Niederhaslach, France
Contact
support@primetech-solutions.fr
Version
1.0.0 · préparation / pre-launch

Access without registration

Without an email or password, Ozyduo creates a separate technical identifier and nickname for each partner. The partner code only joins a duo; the private personal code restores your own access. Only its hash is stored on the server. Save it outside the app: without a personal code or active session, access cannot be recovered. Deletion remains available in My account using the personal code and displayed confirmation.

Google and Apple sign-in

With Google or Apple, Ozyduo verifies an account identifier and receives an email address when available. Your Ozyduo password and intimate content are not sent to these services. Linking another method requires verification in My account.

Ephemeral media

New photos: deleted after 30 days unopened, or 7 days after the recipient first opens them. Both partners can see the expiry. Copies/screenshots remain possible; files are excluded from app backups. Older media keeps its existing rules.

Your personal space

Your local profile, raw Discover answers, declines, preferences, exclusions, notes, favourites, check-ins and drafts stay on your device. Local storage has no app-level encryption. A local export is a personal plain-text file: it includes text and notes, but no media or credentials.

Your account and duo

Registration sends a nickname, email address and authentication information to the configured server. It stores derived password and recovery-code hashes rather than their original text. Your partner sees your nickname. Messages, sent files, signs, published desires and challenges are shared with the two linked accounts through their explicit actions.

Comparison and private choices

Discover comparison sends only a separately confirmed positive selection. Your partner sees the intersection, not one-sided choices. This copy can be withdrawn. A match or an expression of interest never constitutes consent to an activity.

Photos, videos and storage security

Files are selected, previewed and explicitly sent. The server receives the original before preparing a copy and removing supported metadata; older files may retain metadata. Messages, databases, files and backups are not end-to-end encrypted. The operator and host can access server storage. Public access requires HTTPS; the local HTTP preview is for fictional tests only.

Sessions and technical information

The web uses an HttpOnly session cookie; the native app keeps its session in the phone’s secure storage. The server processes connection data and the IP address needed for operation and abuse prevention. It exposes no presence or message-read indicator. Recovery uses a personal code prepared in advance; no automatic email recovery service is promised.

Trial and purchases

The 14-day Premium trial is voluntarily activated for the duo, without a card or automatic charge at its end. A purchase is a separate action. When mobile purchases are configured, Apple or Google processes payment and RevenueCat verifies access using technical account identifiers and necessary purchase data. The store presents price, duration and any renewal before you confirm. Your answers, notes and conversations are not sent as purchase attributes.

Optional advertisements

When ads are configured, only Google non-personalized ads may be requested after your explicit choice and the provider’s consent-management form (CMP). You can decline or withdraw that choice in settings. Non-personalized does not mean anonymous: the provider may still process technical data such as IP addresses or identifiers needed for frequency limits and ad reporting. Answers, desires, exchanges and check-ins are not used for targeting; ads are not shown in private conversations.

Optional notifications

System notifications require an explicit activation and your phone’s permission. If configured, the installation token and necessary settings are sent to the server and Expo, which routes notifications through APNs or FCM. Text is generic, without intimate conversation content or filenames. Disabling, signing out, unlinking and blocking revoke the relevant registrations according to their scope; an already received notification cannot be recalled.

Blocks and reports

Blocking unlinks the duo and revokes shared access. A report stores a reason, receipt and, only if you choose, a reference to a still-accessible partner message. No intimate text, file or history is copied automatically and no report alert is sent to the partner. Handling requires an authorized operator; no response time or active moderator is assumed.

Deletion, retention and providers

You can delete your account in the app or request assistance through the public contact. Deletion removes associated data from active storage and unlinks the duo; your partner’s account is retained. Local spaces, copies saved by others, store subscriptions and operational backups are separate. Actual hosting locations, enabled providers, retention periods, backup deletion and request procedures must be specified by the operator before publication. No legal retention period or certification is invented here.

Contact

Never send passwords, recovery codes, session tokens or intimate content to support.