ONYX APPLICATION PRIVACY POLICY
Effective Date: November 10, 2026
This Privacy Policy sets out the rules for processing the personal data of users of the Onyx mobile application (the "Application").
1. Data Controller
The Controller of personal data processed in connection with the use of the Application is:
Data Controller: Marcin Kęski (Poznań, Poland) (the "Controller")
Data and privacy contact: support.onyxapp@gmail.com
For matters related to personal data protection, please contact us exclusively by email at the address above.
The Controller processes personal data in accordance with applicable law, in particular Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 (General Data Protection Regulation – "GDPR"). Use of the Application is permitted strictly for adults (18 years of age or older).
2. Categories of Data We Process
Depending on how you use the Application, we may process the following categories of data:
2.1. Account and General Profile Data
- • email address (including its SHA-256 cryptographic hash used for account indexing) and information provided by your Google account (if you choose to sign in via Google)
- • nickname (display name), age, gender, and preferred grammatical form (pronouns)
- • profile bio and profile photos
- • physical and relationship attributes provided voluntarily: height, weight, body type, relationship status, and dating goals
- • interests (along with their percentage distribution) and results of personality and strengths assessments (including the calculated personality archetype)
- • discovery preferences regarding other users (gender, age range, geographic radius)
• activity metrics and internal Application economy data: Onyx Points balance, daily limit usage history, awarded bonuses, and the profile reputation score (calculated based on profile completeness, quiz consistency, interaction history across chats, Dice draws, matches, and profile visits, as well as any moderation penalties; the reputation summary is visible to other logged-in users on the profile card).
2.2. Special Categories of Data (Intimate Preferences and Sexuality)
With the user's explicit consent, expressed by voluntarily completing dedicated calibration quizzes or profile fields, the Application processes data concerning sex life and intimate preferences, in particular:
- • answers provided in the intimate preferences quiz (kink/BDSM)
• calculated compatibility scores across specific categories, preferred role (e.g., dominance/submission, spectrum indicator), affiliation with thematic groups (tribes), list of fantasies, and hard limits (taboos).
• Note: Detailed results of intimate preferences are not publicly visible to all users – access to them requires granting separate permission to a selected user within the Application.
2.3. Location Data
• The Application uses approximate device location (GPS) or a location manually pinned by the user on the map in order to operate the radar, live matching (Dice), and discovery features displaying users within a specified area (country, continent, kilometer radius).
• Before being stored, location coordinates are rounded to a geographic grid in accordance with the user's privacy settings. In exact mode, a grid corresponding to approximately 111 m (3 decimal places) is applied, and in approximate mode – approximately 1.1 km (2 decimal places).
• The Application does not share the user's geographic coordinates with other users. Other users may only see the relative distance and – depending on privacy settings – the name of the city and country. The user may hide the display of their city name at any time in the privacy settings.
2.4. Communication Data and Social Interactions
- • information about sent and received likes, matches (pairs), profile visits, and blocked users
- • encrypted text messages, reactions, and photos sent in chat (in standard, one-time private, or 24-hour timed mode)
- • Ogg/Opus mono 48 kHz voice messages up to 90 seconds in length, encrypted end-to-end (AES-256-GCM); the key and nonce of a given recording are transmitted strictly within the E2E message envelope
- • communication metadata (message timestamp, message edit timestamp, read receipt status, typing indicator status, and technical data necessary to process and deliver voice messages)
• content of Terms of Service violation reports submitted to moderation.
2.5. Technical and Cryptographic Data
To ensure the proper functioning and security of the Application, we process:
- • account identifier (UID), email verification status, and information regarding applied moderation restrictions
- • device token used for delivering push notifications (FCM)
- • generated device identifiers (subject to a limit of up to 3 active devices per account), information about their status and role, public keys used by the multi-device end-to-end encryption (E2E) mechanism, and an encrypted backup of private keys (if the user has configured key recovery via a PIN code)
- • key recovery mechanism data: a 9–12 digit PIN code, Argon2id key derivation function (KDF) derivatives using a server-side pepper, and an encrypted backup of private keys; the legacy 12-word BIP-39 recovery phrase is supported solely as a fallback legacy method
- • installation attribution and referral system data: the referral code assigned to the account (refCode), referral code redemption history, and a one-time installation identifier (installId) along with the referrer parameter provided by the application store (Google Play Install Referrer)
- • timestamp of the last activity in the Application (lastActive)
- • application crash logs and technical error reports (crash reports: device model, OS version, technical error stack trace)
• telemetry and analytics data regarding the use of Application features (depending on the consents granted).
3. Voluntariness of Data Provision
Providing an email address, age (at least 18 years old), nickname, gender, and basic discovery preferences is voluntary, but necessary to enter into the agreement and create an Account in the Application – failure to provide them prevents registration. Providing all other data (in particular photos, bio, location, and completing the personality and intimate preferences quizzes) is entirely voluntary and serves to expand the functionality of the Application.
4. Purposes and Legal Bases for Data Processing
We process personal data for the following purposes:
- • creating, authenticating, and operating the Account, as well as providing electronic services within the Application (radar, live matching, chat, matching, and compatibility profiling between users) – Article 6(1)(b) GDPR (performance of a contract)
- • processing data regarding intimate and sexual preferences in order to calculate the compatibility profile and share it with selected users – Article 9(2)(a) GDPR (explicit consent of the user, which may be withdrawn at any time)
- • operating the referral program, installation attribution, and awarding bonus Onyx Points – Article 6(1)(b) GDPR (performance of program terms under the contract) and Article 6(1)(f) GDPR (legitimate interest of the Controller consisting in preventing abuse and duplicate bonus claims)
- • moderating profile photos prior to publication in order to protect the community – Article 6(1)(a) GDPR (consent granted prior to uploading a photo) and Article 6(1)(f) GDPR (legitimate interest of the Controller consisting in ensuring safety)
- • ensuring the security of the Application and its users, verifying device integrity, preventing spam (including blocking disposable email addresses), detecting abuse, calculating and displaying the reputation score, and handling reports of Terms of Service violations – Article 6(1)(f) GDPR (legitimate interest of the Controller)
- • ensuring the technical stability of the Application, including analyzing crash logs (crash reports) – Article 6(1)(f) GDPR (legitimate interest of the Controller)
- • establishing, exercising, or defending against potential legal claims – Article 6(1)(f) GDPR
- • fulfilling legal obligations incumbent upon the Controller – Article 6(1)(c) GDPR
• displaying advertisements (including rewarded video ads granting Onyx Points or unlocking features) and conducting Application statistics and analytics – Article 6(1)(a) GDPR (user consent managed via the UMP mechanism) or Article 6(1)(f) GDPR (with respect to basic server-side verification of rewarded ad completion – Server-Side Verification).
5. Profiling and Automated Decision-Making
In order to calculate user compatibility, display profiles on the radar and in live matching, and calculate the reputation score, the Application uses profiling, i.e., automated analysis of provided attributes, interests, quiz results, and interaction dynamics within the Application (Article 4(4) GDPR). The reputation summary (expressed on a point scale and broken down into axes: Conversation, Intentions, Profile) is displayed to other logged-in users on the profile card to support safety and interaction quality within the community (asymmetric mechanism – the account owner does not view their own summary within the Application interface, while retaining the right of access as described in Section 12).
The Controller does not make decisions concerning users that are based solely on automated processing and produce legal effects concerning them or similarly significantly affect them (Article 22 GDPR). In the event of automated photo moderation (SafeSearch) or automated preventive measures (such as temporary profile visibility restriction – a so-called shadow-ban – applied automatically after receiving reports from at least 3 independent users within 24 hours), such cases are subject to human review (by a moderator), and the user always has the right to contact the Controller to obtain human intervention and contest the decision.
6. Message Encryption and Chat Privacy
• The content of text messages sent via chat between users is protected by end-to-end encryption (E2E) using RSA and AES algorithms. Private keys are stored on the user's devices (and optionally in an encrypted backup protected by a PIN code unknown to the Controller). The recovery code takes the form of a 9–12 digit PIN. Argon2id KDF and an additional pepper stored exclusively server-side are used to derive cryptographic material, and the backup is encrypted using AES-256-GCM. The former 12-word BIP-39 phrase remains available solely as a legacy fallback recovery method. In the event of losing all authorized devices and the recovery code, the user may initiate an emergency reset of conversations and devices via an email verification code (preserving the profile and matches) or submit a request for a full account security reset (Hard Reset E2EE), executed after a 72-hour grace period during which the request may be cancelled at any time from any active device.
• Voice messages are encrypted individually for each recording using the AES-256-GCM algorithm. The recording key and nonce are contained within the E2E message envelope, ensuring that the storage server never receives the plaintext audio recording.
• For photos sent in chat (in standard, one-time private, and 24-hour timed modes), image files are stored in secured cloud infrastructure for the period determined by the selected mode, while the URL pointing to the photo is transmitted inside an end-to-end encrypted message.
• Voice messages are stored in Firebase Storage under the chatAudio/ path in AES-256-GCM encrypted form. The key and nonce are transmitted exclusively inside the E2E message envelope. Storage security rules do not allow clients to read these files directly. The recipient obtains access following an authorized server request, which issues a short-lived signed URL valid for 5 minutes. The server stores the file in encrypted form and has no access to its plaintext content. Recordings are retained for a maximum of 48 hours; a server-side cleanup job running every 5 minutes deletes files once this period expires.
• During normal operation of the Application, the Controller has no technical ability to read the content of users' encrypted conversations or decrypt voice messages stored on the server. System and administrative messages (e.g., moderation warnings) are not subject to E2E encryption.
• Moderation exception (reports): If a user reports a message or conversation for violating the Terms of Service, the Application transmits from the reporting user's device to the server a decrypted evidentiary transcript comprising: the reported message along with up to 5 preceding messages (when reporting a specific message) or up to the 15 most recent messages (when reporting an entire conversation). This material is used exclusively to review the report and take moderation action.
7. Photo Moderation
• Profile photos uploaded to the Application undergo automated analysis prior to publication using Google Cloud Vision (SafeSearch) and may be subject to review by a moderator (the Controller).
• The analysis serves exclusively to detect prohibited content, in particular nudity, violence, or depictions of minors.
• Photos rejected by moderation or unverified within 7 days are automatically deleted.
8. Advertisements, Analytics, and Consent Management
• The Application does not use the content of private conversations or data regarding intimate preferences to personalize third-party advertisements.
• For users in the European Economic Area (EEA), we implement the certified Google User Messaging Platform (UMP) consent management mechanism. Users can change their ad privacy settings at any time in the Application Settings.
• When using rewarded video advertisements (Rewarded Video) to grant Onyx Points or unlock features, the user identifier is transmitted as part of technical Server-Side Verification with Google AdMob to prevent abuse.
• Depending on the consent granted, the Application uses Google Firebase Analytics (in Consent Mode) to collect aggregated information on how the Application is used.
9. Data Recipients and Processors
To ensure the operation of the Application, we use the services of trusted third-party providers:
- • Google Ireland Limited / Google LLC (Google Cloud Platform / Firebase) – database hosting (Realtime Database), file storage (Cloud Storage), serverless compute (Cloud Functions), authentication (Firebase Authentication, Google Sign-In), app integrity verification (App Check), push notifications (Firebase Cloud Messaging), crash reporting (Firebase Crashlytics), and analytics (Firebase Analytics)
- • Google Cloud Vision API – automated safety analysis of profile photos
- • Google AdMob – ad serving and rewarded ad verification (in accordance with user consent settings)
• OpenStreetMap Foundation (OpenStreetMap) – map rendering and reverse geocoding (converting coordinates into a locality name) during manual location selection on the map.
• Converting GPS coordinates into a locality name during automatic location detection may additionally rely on the device's native system geocoding services (Google Play Services on Android / Apple CoreLocation on iOS).
10. International Data Transfers Outside the EEA
The primary server infrastructure of the Application is located within the European Union (europe-west1 region). However, certain service providers (in particular Google group companies and OpenStreetMap) may process some data outside the European Economic Area (e.g., in the USA). In such cases, data transfers are carried out on the basis of an adequacy decision adopted by the European Commission (EU-U.S. Data Privacy Framework) or Standard Contractual Clauses (SCC) approved by the European Commission.
11. Data Retention
• Account and profile data: retained for the duration of holding an Account in the Application.
• Chat photos: photos sent in private (one-time) mode are marked as viewed immediately upon being opened by the recipient and scheduled for deletion after 30 seconds, while timed photos expire after 24 hours; expired files are periodically and permanently deleted from the server by an automated cleanup job running every 5 minutes. Photos sent in standard mode are stored until the message, conversation, or Account is deleted.
• Photo moderation queue: photos awaiting moderation in the queue are stored for a maximum of 7 days.
• Evidentiary transcripts from reports: decrypted message content submitted with a violation report is automatically and permanently deleted after 30 days.
• Voice messages in chat: encrypted files are retained for a maximum of 48 hours from creation and are subsequently deleted by a server-side cleanup job running every 5 minutes.
• In-app notifications: notification entries are automatically deleted after 14 days. The cleanup mechanism also reconciles unread notification counters so that the badge reflects current entries.
• Account Deletion: once an Account is deleted by the user, their profile, photos, matches, conversations, and cryptographic keys are deleted in accordance with the Account deletion procedure, and any open moderation reports are anonymized. For the period necessary to defend against legal claims (generally up to 3 years in accordance with statutory limitation periods), prevent circumvention of active bans, or resolve open violation reports, the Controller may retain strictly necessary archival information based on its legitimate interest.
• Inactive conversations – R1–R5 retention mechanism: effective November 10, 2026, an automated procedure for qualifying and deleting inactive conversations operates in the production environment. Qualification covers five categories: conversations linked to a deleted account, a banned account, a block between the parties, a lack of active device keys enabling further access to the conversation, and conversations in which both parties remain inactive for over 365 days. Once qualified, a conversation enters a 90-day grace period during which an in-chat banner informs participants of the scheduled deletion. For category R5, both parties additionally receive an in-app warning and a push notification 30 days in advance. Upon expiration of the applicable grace period, the conversation is permanently deleted; the mechanism removes up to 100 conversations per day. Conversations with open moderation reports and conversations with pending key rewrap requests (peer-rewrap) are excluded from qualification.
12. User Rights
Under the GDPR, you have the right to:
- • access your personal data and receive a copy thereof
- • rectify (correct) your personal data
- • erase your personal data ("right to be forgotten")
- • restrict the processing of your data
- • data portability
- • object to the processing of data based on the legitimate interest of the Controller
• withdraw consent at any time (e.g., by clearing quiz data, deleting a photo, or changing ad privacy settings in the Application), without affecting the lawfulness of processing based on consent before its withdrawal.
Withdrawal of consent for intimate data: withdrawing consent to process data from the intimate preferences quiz (by resetting or deleting its results) immediately stops compatibility calculations in this category; this does not restrict access to the core features of the Application.
Data Export (right to data portability under Article 20 GDPR): Users can download a JSON file in the Application Settings containing the data covered by the "Export data" feature, in particular profile data, public profile mirror data, conversations, matches, and likes. The export does not include internal push notification tokens (FCM), cryptographic keys, or the reputation score.
Access to reputation data (Article 15 GDPR): the exclusion of the reputation score from the automated export and from the user's own profile view does not limit the user's right to obtain information about data concerning them. A user may contact the Controller at support.onyxapp@gmail.com to request access to data regarding their reputation as well as information on the core parameters and logic involved in its calculation. This information is provided through individual handling of the access request; it is not included in the automated JSON export.
Account Deletion: Users can independently, permanently, and irreversibly delete their Account directly from the Application Settings or – without needing to have the Application installed – via the dedicated web page: https://onyx-c8208.web.app/
13. Right to Lodge a Complaint
If a user believes that the processing of their personal data infringes the provisions of the GDPR, they have the right to lodge a complaint with a competent supervisory authority, in particular in the EU Member State of their habitual residence, place of work, or place of the alleged infringement. In Poland, the supervisory authority is:
President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych – UODO)
ul. Stanisława Moniuszki 1A, 00-014 Warsaw, Poland.
14. Data Security
The Controller implements advanced technical and organizational measures to protect data against unauthorized access, loss, or disclosure, including:
- • end-to-end encryption (E2E) of text messages with per-device authorization (QR code pairing, primary device management)
- • separation of private data and intimate preferences from public profile data at the database security rules level
- • automatic stripping of metadata (including EXIF/GPS tags) from photos before they are uploaded to the server
- • mechanisms restricting screenshots and screen recording at the operating system level (Android FLAG_SECURE / iOS screen protection)
- • optional protection of access to the Application using a local PIN code and biometrics (biometric data is verified strictly locally by the device's operating system and is never transmitted to the Controller)
• application integrity verification using Firebase App Check.
15. Changes to the Privacy Policy
The Controller may update this Privacy Policy in the event of changes to the Application's features, third-party services used, or applicable laws. Users will be notified of material changes within the Application. The current version of the document is always available in the Application Settings.
16. Contact
All questions or requests regarding the processing of personal data and the exercise of rights under the GDPR should be directed to:
Email: support.onyxapp@gmail.com
This Privacy Policy is effective as of November 10, 2026.