Privacy Policy

Who is responsible

OUVO is operated by Emanuel Cohen. For privacy questions, correction requests, or deletion help, email support@ouvo247.com.

Information we handle

• Accounts: Apple or Google authentication identifiers, verified email when provided (including an Apple relay address), OUVO user ID, and credentials needed to maintain and revoke your session. OUVO does not receive your Apple or Google password.
• Profile: your username, display name, optional home city, gender selection, optional birth year, profile photo, and profile change history needed to enforce change limits. Birth year is stored with your account; it is not displayed on your public profile. OUVO uses it to calculate approximate age groups for Crowd Insights, showing grouped percentages only when minimum response thresholds are met.
• Content and activity: comments, replies, uploaded photos, comment likes, interested or saved events, reports, blocks, and moderation status. Approved comments, usernames, and profile photos can be seen by other users, including guests. Pending submissions are held privately for operator review. Do not upload private information about yourself or others that you do not want to share.
• Usage and technical data: OUVO records account-linked events such as event impressions, detail views, shares, opening shared events, ticket-link clicks, saves, and comments, with event IDs, timestamps, and limited context. Servers also process network and request information, such as IP addresses and requested URLs, in operational access logs. Searches and selected event markets are sent to the backend to return results. These legal and support pages include no analytics scripts or application-set cookies; their host may process request information.
• Location: if you choose current location, iOS asks for location permission. The app uses coordinates on your device for distance calculations and location selection. OUVO’s event discovery requests do not send your device coordinates to our backend. Your selected market and any home city you enter are separate from precise device location. You can choose a city without granting location permission.
• Support: if you contact us, we receive your contact details and anything you include, such as screenshots, issue descriptions, or appeal information.

Why we use information

We use this information to sign you in, manage your account and profile, return event results, save your interests, provide comments and crowd information, moderate content, handle reports and blocks, prevent abuse, troubleshoot issues, secure the service, and understand how OUVO is used. Optional birth year and profile details can be removed or corrected in Edit profile.

Providers and sharing

• Apple and Google: these providers handle the sign-in you choose. OUVO verifies their credentials and uses provider identifiers and verified email for account access. Provider credentials may also be used to disconnect access when you delete your OUVO account.
• OpenAI: when you submit content, OUVO automatically sends comment or reply text, attached comment photos, and profile photo uploads to OpenAI's API for automated safety moderation. The moderation request does not attach your OUVO account ID, email, or profile fields, but the submitted text or image may itself contain personal information. Automated results inform publication or review decisions; operators can review held content and appeals. You can choose not to submit content; browsing and other account features remain available.
• AWS: OUVO's configured backend infrastructure uses AWS hosting and PostgreSQL database services to process and store account data, activity, and content. Uploaded photos are stored in backend media storage. Authorized operators use OUVO's control room to manage moderation and support.
• Support email: email to support@ouvo247.com is routed through Zoho Mail. Its mail infrastructure processes messages, contact details, and attachments you send for support, privacy requests, or appeals.
• External content and links: event information comes from external websites and platforms. Some event artwork URLs may load directly from external hosts, which then receive normal network request information such as your IP address. When you open an organizer, ticketing, or source link, that site's own privacy rules apply. OUVO does not process ticket payments in the app.

OUVO uses service providers for the purposes described above. Their handling of personal data is governed by the applicable service terms and data-protection commitments, which depend on the provider, service, and configuration. For questions about OUVO's use of a provider or requests concerning your personal data, email support@ouvo247.com.

Service providers may process information in countries other than yours. Their processing locations and obligations depend on the service and its configuration. OUVO does not use these activity records for cross-app advertising tracking or share them with data brokers.

Retention and account deletion

Account information and activity remain in the service while your account exists unless you remove them or they are removed through moderation. Some content and operational records do not expire automatically. We do not state a fixed retention period for them here.

Delete your account in OUVO → Profile → Privacy & Account → Delete Account. The app asks you to confirm. Account deletion removes the live account, profile, sessions, authentication mappings, saved events, likes, blocks, reports made by you, and account-linked usage events. Your original comment text and photos are removed. An empty, unattributed comment may remain to preserve another person's replies.

Media deletion and provider disconnection use a retryable cleanup queue, so external cleanup may finish after the account record is removed. Encrypted provider credentials or media keys remain in that queue until cleanup succeeds. Short-lived hashed deletion and replay-prevention records expire after 24 hours and are cleared by scheduled cleanup. Shared operational records may remain with user attribution removed. Existing backups and service-provider records are not erased synchronously with the live account; their retention depends on the applicable infrastructure and provider arrangements.

If Apple authorization is unavailable, deletion can still complete and the app explains how to disconnect OUVO manually in Apple's settings. Deleting OUVO does not delete your Apple or Google account.

Your choices and requests

You can browse without signing in, choose a city without location access, change location permission in iOS Settings, edit optional profile details, remove your profile photo, delete your own comments, block users, and choose not to submit content for automated moderation. To request access, correction, deletion help, or exercise rights available under applicable law, email support@ouvo247.com. We may need to verify that a request relates to your account. Do not send passwords or sign-in tokens.

Security

OUVO uses HTTPS for the hosted API, verified Apple and Google credentials, iOS Keychain storage for refresh tokens, hashed server refresh tokens, encrypted provider revocation credentials, access controls for operator tools, and validated photo uploads re-encoded without original metadata. No service can guarantee absolute security.

Changes and questions

We may update this policy as OUVO's practices change. The effective date appears above. Material changes to personal-data sharing may require new disclosure or permission. For questions, email support@ouvo247.com.