Privacy Policy

Last updated August 2026.

This page explains what I’m looking for collects, why, and who can see it. The short version: your answers are private to the person who asked, your date of birth is never shown to anyone, and we don’t sell your data.

The service is operated by App2Mob, which is the controller responsible for the processing described here. Privacy requests can be sent to [email protected].

What we collect

• Account and profile: email address, first name, date of birth, city, and any optional bio, profile photo, and cover photo you add.
• Content and communications: posts, private answers, one-to-one chat messages, and optional photos, videos, or voice recordings you deliberately upload or record when those formats are enabled.
• Relationships, choices, and product interaction:connection requests and decisions, blocks, language and notification preferences, reports, and responses to product-interest questions.
• Sign-in data: if you sign in with Google or Apple, we receive the name, email, and profile photo that provider returns to verify who you are, but never your provider password. If you use email sign-in, we store a one-way, salted password hash — never the readable password — and short-lived, one-use verification or recovery-code records.
• Device and notification data: if you enable push notifications, Firebase Messaging auto-initialization is turned on and we store its device token and your choices for which activity notifications you want to receive. It remains off before opt-in and is turned off on refusal or sign-out.
• Network and security metadata: IP address, browser or app user agent, request path without search terms, response status, and timing are kept in restricted security logs for up to 14 days to protect the service, investigate abuse, and diagnose failures.
• First-party visitor counts: a random identifier, web or app platform, and first and latest activity times are kept for up to 30 days. They are used only for aggregate current and daily visitor counts in the protected administration console; we do not store a page path, search text, IP address, or raw user agent with this identifier.

Who can see what

Your date of birth is never shown to anyone, including other members; it is used to confirm that you are 18 or older. Your profile can show your first name, city, optional bio, profile and cover photos, and age only when you choose to show it. New posts default to App + Web, so the question, your public author details, and a link to your public profile can appear to website visitors and may be indexed by search engines. You can choose Members only before publishing instead. Inside the service, a private answer is visible only to its author and the person who posted the question, and a chat is available only to the two accepted connection members. The post owner may export answer text with our anonymous share card; it never includes the responder’s identity or original photo, video, or voice media.

How we use it

We use this information to create and protect accounts, operate and order the feed, deliver posts, private answers and chats to the right people, process connection and block choices, remember preferences, provide optional notifications and media, understand requested product formats, measure aggregate current and daily visitors, enforce the age requirement, prevent abuse, and review reports. When you report a member from inside a chat, the interface tells you before submission that an immutable snapshot of the latest eight messages will be attached for authorized safety review. Reports made from a profile never attach or infer chat history. Report-time text and limited profile metadata are retained while the report is open and for up to 90 days after resolution; public media URLs are not copied into the immutable evidence record. We do not sell personal information or use it for third-party advertising or cross-app tracking.

Where it’s stored

Account and content data is hosted for LookingFor by Hetzner. Cloudflare provides DNS, content delivery, and network security and therefore processes network requests and cached public assets for those purposes. Google and Apple process sign-in and our server verifies their identity tokens; Firebase Authentication is not used. Resend receives the email address and verification or recovery message needed to deliver a code. Firebase Cloud Messaging processes a device token and notification payload only after notifications are enabled. These companies act as service processors for those limited functions. Firebase is not the database for profiles, posts, private answers, connections, or chats.

Before a new profile or cover photo is published, our server sends that image to Google Cloud Vision SafeSearch for a limited automated safety check. Google processes the image for that check; Cloud Vision is not used as LookingFor’s image store.

When you use the optional city search, our server sends only the place text you typed and your interface language to OpenStreetMap-based geocoding services (Photon, and Nominatim for compatibility with older clients) to return suggestions. We do not send your LookingFor user ID, email address, or precise device location with that request. Those providers process the request under their own service and privacy terms. We limit service-provider access to the stated function and require appropriate confidentiality and security protections.

Retention, deletion, and backups

We keep account and content data while your account is active and only as long as needed to provide the service, protect members, resolve reports, or meet legal obligations. Verification and recovery records expire automatically. When account deletion completes, we remove your profile, bio, profile and cover photos, posts, private answers, chat messages and media, connections, blocks, preferences, device tokens, sign-in identities, and password credential from active systems. Limited security, fraud-prevention, moderation evidence, or legal records may be retained only where necessary. Report evidence is normally scrubbed within 90 days after the moderation decision. Encrypted, isolated disaster-recovery backups are retained for up to 14 days and are used only for disaster recovery, not routine processing. Data removed from active systems may remain in an older backup until that backup expires through automatic rotation.

Your choices

You can edit your profile information, change notification choices, block members, or delete your account at any time. Account deletion is available inside the app and on our web deletion page. You can also choose whether to show your age and whether to add a bio, profile or cover photo, media, or push notifications.

Children

This service is for adults 18 and older only. See our Child Safety Standards for how we handle and report any indication of underage use or child exploitation.

Contact

Questions about this policy or your data can be sent to [email protected].