Localizable

Privacy Policy

Effective October 23, 2026.

1. Who operates the app

This policy describes the data the Android and iOS apps collect, how it is used, and how to delete an account.

2. Who the app is for

The app is for adults 18 and older.

3. Information you provide

Creating an account requires a phone number, verified by a text message, and an email. Google and Apple sign in can also be used instead of an email. From Google or Apple the app receives the email address on that account and, when Apple provides it, your name. You then add a profile: name, age, photos, and any of the optional details you choose to fill in, such as a short introduction, height, if you have children, relationship intent, personality, and tags.

You can manually enter the phone numbers of people you do not want to be seen by or see. The app does not read the address book on your phone.

If you send a like or a message, that content is stored so you and the other person can see it. Your name and profile photo are attached to likes and messages you send. If you report a profile, the report stores the reason, the reported person's account id, and your account id. A bug report stores the text you type and your account id.

4. Location

With your permission, the app reads your device's precise location, or any location that you choose to share. The pin you publish (its latitude and longitude) is stored with your profile and is shared with other signed-in users so the app can display nearby users. A separate search pin is used only to center your own search, is stored in your account data, and is not published.

Map tiles and place lookup are provided by Google Maps. A place search is sent to Google.

5. Photos and face data

Profile photos come from the camera or the photo library. Other signed-in people can see the photos on a visible profile. A photo address can also be opened by anyone who has that address.

Before a profile photo is shown, Google Cloud Vision checks it for abbusive, violent, or adult content. That check does not identify who is in the photo. Photos that fail the check are rejected.

Face verification uses the camera. On the phone, Google ML Kit detects a face. A verification selfie is uploaded and stored for your account only. It is not placed on your public profile. On iPhone, the system may allow microphone access while the camera is open. The app takes still photos and does not store audio.

6. Information collected while you use the app

The app stores a Firebase Cloud Messaging token so it can notify you about likes and messages. You can refuse notification permissions. The token stays with your account.
If you leave activity status on, the app shares a last-active time on your visible profile. You can turn that off in the app settings.
Release builds send crash reports to Firebase Crashlytics and a few product events to Firebase Analytics, including app opens and when you copy a profile link.
The app uses Google Play Integrity on Android and Apple App Attest on iPhone to confirm the install is genuine.
The phone keeps a local database of your profile, people you have loaded, and your inbox, so the app can open without waiting on the network. That database stays on the device until you delete the account, clear the app's storage, or uninstall it.

While your profile is visible, other signed-in people can see the profile you published, including your name, age, photos, the details you filled in, your published pin, and your last-active time if that switch is on. Your phone number stays on your private record. It is not part of the profile other people see. While search by phone is on, someone can find that profile by searching the number. You can hide your profile, turn off name search, turn off phone search, and turn off activity status in the app settings.

The other person in a like or a message can see that like or message, along with the name and photo attached to it. People you have blocked are hidden from you. Blocking does not by itself notify them.

Personal information is not sold. The app does not show ads. Apple or Google processes a subscription payment. Localizable stores the plan name and when the current period ends. It does not receive a card number.

8. Services that process it

The app runs on Google Firebase: Authentication, Cloud Firestore, Cloud Storage, Cloud Functions, Cloud Messaging, Analytics, Crashlytics, and App Check. Files and database records are held in Google Cloud, in the United States (regions us-central1). Sign-in is also processed by Google or Apple, depending on the button you use. Maps, place lookup, photo safety checks, on-device face detection, Play Integrity, and Android subscription payments are Google services. Apple processes Sign in with Apple, App Attest, push delivery to iPhones, and iPhone subscription payments.

Their policies are at policies.google.com/privacy, firebase.google.com/support/privacy, and apple.com/legal/privacy.

9. How long it is kept, and how to delete it

Account information is kept while the account exists. In the app, open Settings and tap Delete Account, then confirm. That deletes your sign-in and removes your profile, messages, likes, matches, blocks, saved list, profile photos, verification photo, and your profile listing. It also clears the app's database on that phone.

You can make the same request without the app at integridate-app.web.app/delete-account. Email [email protected] and include the phone number on the account.

An abuse report can keep the reason and the account ids that were part of the report. A bug report you sent can keep the text you wrote. Google may keep crash and analytics records under its own schedule, and short-lived backups can take a while to roll off. A copy of your profile can remain on another person's phone until that phone refreshes.

10. Changes

Updates to this policy are posted on this page. The date at the top changes when the text changes.

11. Contact

Email [email protected].