Privacy Policy

Version: 1.5 — Effective September 21, 2026 Version 1.4 — Effective September 1, 2026 Version 1.3 — Effective August 30, 2026 Version 1.2 — Effective August 2, 2026 Version 1.1 — Effective July 14, 2026 Version 1.0 — Effective March 15, 2026 Last Updated: September 21, 2026

Intimassy ("the App") is developed and operated by Significant Inc, a sole proprietorship based in Bonn, Germany. The App is available for Android and iOS. This Privacy Policy explains how we collect, use, store, retain, and delete your personal data, including health and sensitive data, when you use the App on either platform. Android versions of the App released before version 5.0 ("older versions") work differently in some respects; Section 15 describes them for anyone who has not updated.

The App asks you to review and accept this policy before you start using it. You give that consent in the App, by ticking a box on a screen that links to this policy and to the Terms of Use. You are not asked to consent by simply installing or opening the App. If you do not agree, do not accept; nothing described in Section 1 is uploaded to us, and you cannot use the App. Before you reach that screen the App walks you through a first entry and two setup questions. What you enter there is kept on your device so you can carry on where you left off. It stays on your device until you create an account or uninstall the App. Crash reporting and usage analytics are off until you turn them on; Section 9 explains that choice.

1. Health and Sensitive Data We Collect

Intimassy is an intimate activity tracker. Due to the nature of the App, we collect and process health and sensitive personal data as defined under GDPR Article 9. This data is only collected when you voluntarily enter it into the App.

The health and sensitive data we collect includes the following. Each list gives examples of what a feature stores, not a complete inventory.

Sexual Activity Logs (Entries)

  • Date of activity
  • Duration (in minutes)
  • Personal rating
  • Safety status (whether protection was used)
  • Initiator (who initiated: you, your partner, both, or spontaneous)
  • Orgasm counts (yours and your partner's)
  • Personal notes

Activity Details

  • Activity types (e.g., casual, oral, anal, and other sexual activity categories)
  • Places where activity occurred (e.g., bedroom, hotel, car, and other locations)
  • Sexual positions used, including custom positions with intensity levels
  • Toys used, including toys you name and describe yourself
  • Partners involved in the activity
  • Entry templates you save, which hold the same kinds of details as an entry

Partner Information

  • Partner name
  • Partner gender
  • Relationship type
  • Date added
  • Personal notes about the partner
  • Partner profile photo

Menstrual Cycle Data

Marking period days is optional. Nothing here is collected unless you use that feature. You can mark days for yourself, and you can keep a separate set of days for a partner you have added.

  • Days you have marked as period days, for yourself or for a partner
  • The settings and corrections you apply to the estimate. This includes, for example, a cycle length, days that should not start a new cycle, cycles left out of the estimate, and how the feature shows on your calendar.

From these days the App calculates an estimated next period and an estimated fertile window. The estimate is calculated on your device. The App does not upload the estimate. The days you mark are stored in your cloud backup like your other data, as described in Section 5. These estimates are informational only. They are not medical advice and must not be used as a contraceptive method or as a way to plan a pregnancy.

Sexually Transmitted Infection (STI) Records

Recording STI information is optional. Nothing here is collected unless you use that feature.

  • The names you give the record, each chosen from a list or typed by you. A record may carry more than one.
  • Whether the record is about you, about a partner you have added, or about someone not named in the App
  • The start date, the end date if any, and any note you add

The App uses these records to show them to you, for example on your calendar and next to your entries, and to work out on your device which of your logged activities fall inside a record's dates and which partners they involved. All of that stays on your device and is shown only to you. The records are stored encrypted in your cloud backup like your other data, as described in Section 5. They are informational only and are not medical advice.

Photos

  • Intimate photos attached to activity entries
  • Partner profile photos

All health and sensitive data listed above is used to provide you with the core features of the App: tracking, reviewing, and analyzing your intimate activity history for your personal use.

We also include a small number of coarse usage measures in our analytics, to understand how the App is used and improve it. These describe how you have set the App up — for example whether you saved an entry template, or whether the app lock is on — not what you logged. One measure counts how many fields you filled on an entry you saved, never which ones or what they said. The content of your entries is never sent to any analytics provider. We do not send your entries, notes, photos, partner names, activity types, places, positions, toys, STI records, ratings, orgasm counts, or protection status to Firebase Analytics or to any other third party for analytics purposes.

One thing we do send is your answers to the questions the App asks when you first set it up: your relationship situation and what you want to use the App for. You pick these from fixed options, and we send the options you picked, not free text. You can pick more than one reason for using the App, and we send all of them. They tell us which kinds of users the App serves. You answer them before you create an account, so they are not linked to your Firebase User ID. They are not derived from your entries, but they are about your sex life, so we treat them as health and sensitive data. The choice described in Section 9 turns them off, and that section explains how it works.

2. Personal Data We Collect

When you create an account, the data we collect includes:

  • Email address
  • Name or nickname
  • Gender
  • Authentication provider used (Google, Apple, or email/password)
  • Firebase User ID (a unique identifier assigned to your account)

In-App Purchase Information

  • Product IDs of items purchased
  • Purchase tokens or receipts (for verification with Google Play or the Apple App Store)
  • Order / transaction IDs
  • Purchase and entitlement status (managed via RevenueCat, keyed to your account ID)

Problem Reports

If you report a problem from inside the App, we store what you wrote, your account identifier, and the time you sent it. Please do not include details in that message you would rather not have stored. We keep a report until we have dealt with it, and we delete it when you delete your account.

3. Automatically Collected Data

The following data is collected without you typing it in. Crash reports and usage analytics are collected only if you turn them on, as described in Section 9; the rest does not depend on that choice.

  • Device information (manufacturer, model, operating system version)
  • App version
  • Timezone and language preferences
  • IP address, which Google uses to operate the services listed in Section 8 and to derive an approximate location (country or region). We do not collect your precise location.
  • Crash reports and error logs (via Firebase Crashlytics), only if you turn them on
  • App usage analytics (screen views, feature usage, the coarse usage measures and the setup answers described in Section 1, via Firebase Analytics), only if you turn them on

The App does not send push notifications and does not collect a push notification token. Android versions before 5.0 do; see Section 15. If we add reminders later, we will use Firebase Cloud Messaging, update this policy, and ask you to review it again before that starts.

4. How We Use Your Data

We use your data for the following purposes:

  • Service Provision: To provide you with the core features of the App, including activity tracking, statistics, partner management, and cloud backup/sync.
  • Cloud Backup and Sync: To securely back up and restore your data across devices using your account.
  • Analytics: To understand how the App is used and improve our services, and only if you turn analytics on as described in Section 9. This analytics data is pseudonymous. Most of it is linked to an account identifier (your Firebase User ID), so that usage can be understood consistently across your devices. The setup answers are not, because you answer them before you create an account. It consists of app usage events, coarse usage measures, and the setup answers described in Section 1, never the content of your entries.
  • Advertising: To display advertisements within the App (via Google AdMob). We do not ask for tracking permission and we do not use your data to personalise the ads you see; they are contextual only. We do not sell or share your personal data for cross-context behavioural advertising. You can remove ads entirely through an in-app purchase.
  • Aggregated Community Statistics: To provide anonymized, aggregated statistics (e.g., average activity frequency) to all users. These are computed only from accounts that have accepted our privacy policy. No individual data is identifiable in these statistics.
  • Purchase Verification: To verify in-app purchases and manage your feature entitlements.
  • Customer Support: To respond to your support requests and problem reports.
  • Security: To detect and prevent fraud, abuse, and security incidents.

We do not make decisions about you by automated means that have legal or similarly significant effects on you.

5. Data Storage and Security

Local Storage

Your data is stored locally on your device in a SQLite database. This data is protected by the operating system's built-in application sandboxing on both Android and iOS.

Cloud Storage

If you use the cloud backup feature, your data is stored in Firebase Realtime Database and Firebase Storage (operated by Google).

Encryption

We take the security of your sensitive data seriously:

  • The contents of your backup are encrypted using strong, industry-standard encryption before being uploaded to our servers. This includes your activity entries, partner information, app settings, and profile details. We intend to encrypt new kinds of backup data the same way, and we will update this section if that changes.
  • Photos are encrypted before being uploaded to Firebase Storage.
  • The app does not write your email address into the backup. It is held in your Firebase Authentication account. Backups and account records created by older versions of the app may still contain it; updating the app and making a new backup removes it from the backup.
  • Some items are not encrypted, and we would rather say so than round the claim up. These are technical values the app generates itself — for example your account identifier, internal record identifiers, the time of a backup, a counter we use to order backups, an identifier for the device that wrote it, the names of the kinds of data a backup holds, and a marker for how records are identified. Values like these are not text you entered in the app. Names you give to custom places, custom activity types and toys are used as storage keys. They are stored as a one-way value derived with your backup key, so nobody reading the stored backup can recover the name from the key. When the app sets a previous backup aside as a safety copy, the time it was set aside and a flag we use to manage that copy are stored unencrypted. Backups made with older versions of the app may hold some of your data unencrypted, including profile details and custom place names; updating the app and making a new backup encrypts or removes those values.
  • Encryption keys are derived using industry-standard key derivation functions.
  • All data in transit is protected by HTTPS/TLS encryption.
  • This encryption protects your data at rest on our servers and in transit against unauthorized access.

What We Can Decrypt, and Why

We want to be plain about one point. We hold the key material for your backup, so we are technically able to decrypt it. This is not end-to-end encryption, and we do not claim that we cannot read your data. We decrypt it only for the purposes below:

  • Aggregated community statistics. As described in Section 4, and only for accounts that have accepted our privacy policy.
  • Storage housekeeping. To find photo files that no backup refers to any more, so we can delete them.
  • Data format migrations. To convert stored data to a newer format, such as the change that moved profile details into the encrypted part of the backup. Data is re-encrypted and stays in place.

We do not read your data for any other reason. If we ever add a new purpose, we will list it here and ask you to review this policy again before it starts.

Data Location

Your cloud data is processed and stored on Google Cloud infrastructure (Firebase), which may include servers located in the United States and other countries. See Section 11 for information about international data transfers.

6. Data Retention

Active Accounts

Your data is retained for as long as your account remains active. You can access, modify, or delete your data at any time.

Inactive Accounts

We may remove the stored data of accounts that have been inactive for an extended period. This may include accounts that have an active in-app purchase. How long an account must be inactive before it qualifies, and when the cleanup runs, are decided by us and may change at any time. The cleanup removes:

  • Your user profile, cloud backups and preferences in Firebase Realtime Database
  • Your photos in Firebase Storage

The cleanup does not remove your Firebase Authentication account, your purchase records, or problem reports you sent us. You can still sign in afterwards. You can delete your account in full at any time, as described in Section 7. We may include accounts that hold an active in-app purchase in future runs.

Before the cleanup removes your data, we keep a copy of it, so that we can restore it if the cleanup needs to be reverted. That copy is held by us outside the services named in Section 5. The encrypted parts of your data stay encrypted inside it. Deleting the copy once the cleanup is confirmed is a step we carry out ourselves; no automatic process removes it.

To decide which accounts qualify, the cleanup first reads a small amount of account information for every account — when it was last active, whether it holds a purchase, and when its last backup was made — and keeps that on the same operator-held storage for up to a week so a re-run does not have to read it again. It does not contain your entries, photos or partner details.

Local Data

Local data stored on your device is deleted when you uninstall the App. Cloud data is not affected by uninstalling the App and will remain until you delete your account or the inactive account cleanup occurs.

Cloud Backups

Cloud backups are retained until you delete your account, manually clear your data, or your data is removed through the inactive account cleanup process.

Purchase Records

Purchase verification records (order IDs, purchase tokens, product IDs) are retained for as long as your account exists to prevent duplicate charges and to verify your entitlements.

Crash Reports and Analytics

Crash reports and analytics data are retained according to Firebase's standard retention policies (typically 90 days for crash data, 14 months for analytics data).

7. Data Deletion

In-App Account Deletion

You can delete your account and all associated data directly within the App using the account deletion option on the settings page. This permanently and irreversibly deletes:

  • All local data (the database on your device)
  • The app settings on your device that belong to the account, including your theme, your setup answers, and your record of accepting this policy. Your app-lock PIN is removed too, unless another account on the same device uses it. Some settings are kept because they belong to the device rather than to the account. These include your choice about crash reports and usage statistics, together with the date you made it and the policy version you were shown; your chosen language; and the date the account first opened the App, which we hold so that a deleted account cannot sign up again to earn a second first-install discount.
  • All data in Firebase Realtime Database (your user profile, all cloud backups, all preferences)
  • Any problem reports you sent us from inside the App
  • All files in Firebase Storage (all uploaded photos)
  • Your Firebase Authentication account

We also instruct RevenueCat to delete the customer record held for your account. If RevenueCat cannot be reached at that moment, the rest of your deletion still completes, and you can contact us to have that record removed. Google Play and the Apple App Store keep their own record of any purchase you made; we cannot delete those, and they are governed by the policies of those stores.

Two things this step does not reach. Usage analytics and crash data already sent to Google stay there until Google's retention period ends, as described in Section 6; nothing new is sent under your account after deletion. If your data was set aside by the inactive account cleanup described in Section 6, we also remove it from the copy we hold.

Request Account Deletion

You may also request deletion of your account and data without using the App, by emailing us at:

We will process your request within 30 days.

What Happens After Deletion

  • Deletion is permanent and cannot be undone. We cannot recover your data after deletion.
  • Aggregated, anonymized statistical data that was derived from your activity (and that cannot be used to identify you) may be retained.

What Happens When You Uninstall

  • Uninstalling the App deletes all local data stored on your device.
  • Cloud data (backups, photos, account) is NOT deleted by uninstalling. To delete cloud data, you must use the in-app account deletion option or contact us by email before uninstalling.
  • If you uninstall without deleting your account, your cloud data may be removed by the inactive account cleanup described in Section 6.

8. Third-Party Services

We use the following third-party services. We share data with them only for the purposes listed, under contracts that require each of them to protect your data at least as this policy and the app stores' rules require. Each service also processes data under its own privacy policy, linked below:

Firebase Authentication (Google)

  • Data shared: Email address, display name, authentication credentials, sign-in metadata
  • Purpose: User account management and authentication
  • Privacy Policy: firebase.google.com/support/privacy

Firebase Realtime Database (Google)

Firebase Storage (Google)

Firebase Analytics (Google)

  • Data shared: App usage events, device information, user properties and event parameters (the coarse usage measures and the setup answers described in Section 1, never entry content), Firebase User ID
  • Purpose: Understanding App usage patterns to improve our services
  • Note: The Firebase Analytics SDK also bundles Google's on-device conversion measurement component. The choice described in Section 9 governs it, as it does the rest of this entry.
  • Privacy Policy: firebase.google.com/support/privacy

Firebase Crashlytics (Google)

  • Data shared: Crash reports, stack traces, device information, app version
  • Purpose: Identifying and fixing bugs and crashes
  • Note: The choice described in Section 9 governs this entry. One choice covers crash reports and usage statistics together, and it starts off.
  • Privacy Policy: firebase.google.com/support/privacy

Sign in with Apple (Apple)

  • Data shared: Apple ID credential, email address (or Apple's private relay address), name
  • Purpose: User account sign-in on iOS
  • Privacy Policy: apple.com/legal/privacy

Google Sign-In (Google)

  • Data shared: Google account credential, email address, name
  • Purpose: User account sign-in with a Google account
  • Privacy Policy: policies.google.com/privacy

Firebase Remote Config and Cloud Functions for Firebase (Google)

  • Data shared: Device and app information with each request, a Firebase installation identifier that the Remote Config SDK generates for your copy of the App, and your Firebase User ID when a function acts on your account, for example account deletion or purchase verification
  • Purpose: Delivering app configuration, such as the policy version the App must ask you to accept, and running the server-side parts of the App
  • Privacy Policy: firebase.google.com/support/privacy

Google AdMob (Google)

  • Data shared: Device information, ad interaction data, IP address
  • Purpose: Displaying contextual advertisements within the App
  • Note: Every ad request the App makes is marked as non-personalised, so your data is not used to select the ads you see. Android versions before 5.0 do not mark their requests that way; see Section 15.
  • Note: No advertising identifier is available to us on either platform. On Android the App removes the advertising ID permission from the build. On iOS we do not show the App Tracking Transparency prompt, so there is no IDFA. Android versions before 5.0 do not remove that permission; see Section 15.
  • Note: The Google Mobile Ads SDK the App uses also bundles Google's User Messaging Platform component.
  • Note: You can remove all advertising by purchasing the "Remove Ads" feature within the App
  • Privacy Policy: policies.google.com/privacy

Google Play Billing (Google) and Apple App Store (Apple)

RevenueCat (RevenueCat, Inc.)

  • Data shared: Purchase tokens/receipts, product IDs, your Firebase User ID as the app user ID, device and app metadata
  • Purpose: Verifying in-app purchases and managing your feature entitlements across devices and platforms
  • Note: We instruct RevenueCat to delete your customer record when you delete your account.
  • Privacy Policy: revenuecat.com/privacy

App review prompts (Google Play and Apple App Store)

  • Data shared: The App may ask you to rate it. The rating dialog is provided and shown by Google Play or the App Store, and what you enter there goes to the store under its own privacy policy. We receive no personal data from it.
  • Purpose: Collecting app ratings and reviews
  • Privacy Policies: policies.google.com/privacy, apple.com/legal/privacy

Telegram (Telegram Messenger Inc.)

  • Data shared: A short alert on each purchase and subscription event, for example a new purchase, a renewal, a cancellation, an expiry or a billing problem. It names the event, the product, the store, the price, the currency and the time, and, when the store reports them, the billing period type and a cancellation reason. It carries no user identifier.
  • Purpose: Notifying us of purchase and subscription activity
  • Privacy Policy: telegram.org/privacy

9. Legal Basis for Processing (GDPR)

We process your personal data based on the following legal grounds under GDPR Article 6:

Explicit Consent (Article 6(1)(a) and Article 9(2)(a))

For processing health and sensitive data (sexual activity logs, partner information, menstrual cycle data, STI records, intimate photos), we rely on your explicit consent, which you provide when you create an account and begin using the App. You may withdraw your consent at any time by deleting your account.

Sensitive Data in Analytics

One kind of analytics data is treated as health and sensitive data, because it describes your sex life: the setup answers described in Section 1. We do not rely on legitimate interest for it. The coarse usage measures described in Section 1 describe how you have set the App up rather than what you logged, so we do not treat them as health data.

How you choose for this is different from how you choose for the data above, so we want to be exact about it. Analytics is not needed to run the App, so it is not part of the consent you give to use it. It is a separate choice, and it starts off. The App asks you when you first open it, with a box that is not ticked for you. Nothing described here is collected unless you tick that box. You can change the choice at any time in the App’s settings, without losing access to any feature. Turning it off stops further collection. What was already sent, including the usage measures held against your account, stays in Firebase Analytics until Google's retention period for that data ends.

One detail about crash reports. The App arms crash reporting as it starts, so that a crash during startup is not lost. While your choice is off, nothing is sent to us. Reports recorded before you turn it on may be sent when you turn it on.

Performance of Contract (Article 6(1)(b))

For processing data necessary to provide the App's services to you, including account management, cloud backup, and purchase verification.

Consent (Article 6(1)(a))

For crash reporting and for all usage analytics, including the general analytics that is not derived from your entries (screen views, feature usage, device and app information). One choice covers both, it starts off, and it is described above.

Legitimate Interest (Article 6(1)(f))

For security, to detect and prevent fraud, abuse and security incidents. We have assessed that this interest does not override your rights and freedoms.

10. Your Rights Under GDPR

If you are in the European Economic Area (EEA) or in a jurisdiction with similar data protection laws, you have the following rights:

  • Right of Access: You may request a copy of the personal data we hold about you.
  • Right to Rectification: You may request correction of inaccurate personal data. You can also update your data directly within the App.
  • Right to Erasure: You may request deletion of your personal data. You can do this directly in the App (via the account deletion option on the settings page) or by contacting us.
  • Right to Data Portability: You may request your data in a structured, commonly used, machine-readable format.
  • Right to Restriction of Processing: You may request that we restrict the processing of your personal data under certain circumstances.
  • Right to Object: You may object to the processing of your personal data where we rely on legitimate interest, as set out in Section 9. Where we rely on your explicit consent instead, the Right to Withdraw Consent below applies.
  • Right to Withdraw Consent: You may withdraw your consent at any time. For crash reports and usage statistics, use the switch of that name in the App’s settings; you keep full use of the App. For the health and sensitive data the App exists to store, withdrawing consent means deleting your account, because that data is the service. Withdrawing consent does not affect the lawfulness of processing performed before withdrawal.
  • Right to Lodge a Complaint: You may file a complaint with a supervisory authority. The authority responsible for us is the Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen (LDI NRW) in Düsseldorf, Germany. You may also complain to the data protection authority of the place where you live or work.

To exercise any of these rights, contact us at info@centertable.club or centertableinc@gmail.com. We will respond within 30 days.

11. International Data Transfers

Your data may be transferred to and processed in countries outside of the European Economic Area (EEA), including the United States. Our cloud infrastructure is provided by Google (Firebase), which operates servers globally, and purchase verification is handled by RevenueCat, Inc. in the United States.

These transfers are safeguarded by:

  • Standard Contractual Clauses (SCCs) approved by the European Commission, which form part of our contracts with Google and with RevenueCat
  • Google LLC's certification under the EU-US Data Privacy Framework
  • Encryption of your backup and photos before transfer

These safeguards, not your consent, are what makes the transfer lawful. Standard Contractual Clauses are the mechanism we rely on under Chapter V of the GDPR. The alert we send to Telegram (Section 8) contains no personal data, so no personal data is transferred to Telegram.

12. Children's Privacy

Intimassy is intended for users aged 18 and older. We do not knowingly collect personal data from anyone under the age of 18. If we become aware that we have collected data from a person under 18, we will take steps to delete that data promptly.

If you believe that a child under 18 has provided us with personal data, please contact us at info@centertable.club.

13. In-App Purchases

The App offers one-time in-app purchases (for example: Platinum Pack, Lock Feature (PIN/biometric app lock), Limitless Image Gallery, Limitless Partners, and Remove Ads) and auto-renewing subscriptions (for example: monthly and annual premium packages). Subscription billing, renewal, and cancellation are handled by Google Play or the Apple App Store.

When you make an in-app purchase:

  • The transaction is processed by Google Play (on Android) or the Apple App Store (on iOS). We do not collect or store your payment method details (credit card numbers, bank account information).
  • Purchase tokens/receipts, transaction IDs, and product IDs are processed by RevenueCat to verify your entitlements and prevent duplicate charges. Entitlements are keyed to your account, so purchases follow your account across devices and platforms.
  • Purchase records are retained for as long as your account exists. Google Play and the Apple App Store keep their own transaction records under their own policies, and those are not ours to delete.

14. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. When we make changes, we will update the "Last Updated" date at the top of this policy.

For significant changes, we will notify you via email (if we have your email address) and/or through an in-app notice.

When a new version of this policy changes how we process your health and sensitive data, the App asks you to review and accept it again before you continue using it. Your earlier consent is not carried over.

We encourage you to review this Privacy Policy periodically.

15. Older Versions of the Android App (before 5.0)

Android versions of the App released before version 5.0 no longer receive updates. If you still use one, everything above applies to you, with the differences listed here. We recommend updating to the current version.

In Android versions before 5.0:

  • Sign-in is offered with email/password, Google, or Facebook. If you signed in with Facebook, Meta received your sign-in request and holds its own record of it under its privacy policy, linked below. The current version does not offer Facebook sign-in.
  • The app sends push notifications through Firebase Cloud Messaging and holds a push notification token for your device. The current version does not (Section 3).
  • There is no such choice to make. Usage events go to Firebase Analytics and crash reports to Firebase Crashlytics for as long as the app is installed.
  • Ad requests are not marked as non-personalised, and the Android advertising ID permission is not removed, so an advertising identifier is available to Google for those ads. Whether ads are shown is a setting we control. Advertisements can be removed with the "Remove Ads" in-app purchase. The current version marks every request as non-personalised and removes the permission.
  • Purchases are made through Google Play Billing directly, without RevenueCat, and a record of them is stored under your account in Firebase Realtime Database without encryption. The current version restores these purchases through the store (Terms of Use, Section 6).
  • Backups made by these versions may hold some of your data unencrypted, as described in Section 5. Updating the app and making a new backup fixes that.
  • Account deletion is available in the app's settings ("Delete User"). It removes your cloud data, your local data and your sign-in account, as the current version does.

Third-party policy for these versions, in addition to those in Section 8: facebook.com/privacy/policy (Facebook Login).

To ask about data held for an older version, contact us at info@centertable.club.

16. Contact Us

If you have any questions, concerns, or requests regarding this Privacy Policy or our data practices, please contact us: