This Privacy Policy explains how Kerényi Gergő egyéni vállalkozó (Kerényi Gergő e.v.), a Hungarian sole entrepreneur with tax number 42985244-1-23 ("Lobby", "we", "us" or "our"), handles personal data when you use the Lobby mobile application, visit our websites lobbyapp.eu and lobbyapp.hu, or join our waitlist.
In short: Lobby is an adult-only social discovery app. We collect the data needed to create accounts, show profiles, run events and chats, send notifications, keep the platform safe, process reports, verify photos, diagnose crashes and comply with law. We do not sell personal data, do not show targeted ads and do not use advertising identifiers.
1. Controller and Contact
The data controller is Kerényi Gergő egyéni vállalkozó (Kerényi Gergő e.v.), tax number 42985244-1-23, registered seat: 6430 Bácsalmás, Mausz Rezső utca 6., Hungary. Privacy, legal and general requests: info@lobbyapp.eu. If we appoint a Data Protection Officer or become legally required to do so, we will add the DPO's contact details here.
2. Personal Data We Collect
Some data is required to provide Lobby. If you do not provide required account, profile, photo or safety information, you may not be able to use the relevant feature. Optional profile fields and free-text content are your choice.
|
Category |
Examples |
Why we use it |
|---|---|---|
|
Account and authentication |
User ID, sign-in method, account timestamps, email verification status, the email address you sign up with, and the email address, name and (Google only) profile-picture link that Apple, Google or another sign-in provider shares with us. If you sign up with an email address and password, the password is handled by Firebase Authentication and is not visible to us. |
Create and secure your account, authenticate you and provide support. |
|
Profile data |
First name or display name, date of birth and the age calculated from it, city, approximate location, languages, interests, prompts (predefined-choice and free-text), bio, education, workplace, drinking and smoking habits, favourite places, verified status and endorsement count. |
Create your profile, show you to other users and help people discover relevant events and connections. |
|
Photos and face verification |
Profile photos, event banners, upload metadata, moderation results, live selfie for verification, similarity score, the photo the selfie was compared with, verification status, the time you gave biometric consent and other timestamps. |
Moderate photos and banners, reduce impersonation and verify that your selfie matches your main profile photo. Face verification is required to create a profile; we ask for your explicit consent before any biometric processing begins. |
|
Events, chat, friends and endorsements |
Event details, host and participant IDs, join requests, invitations, event chat messages, events you save, friend requests, friend connections, users you block, positive endorsements and in-app notifications (such as friend requests, join requests and invitations). |
Run group events, enable event coordination, social connections and trust features. |
|
Location, device and notifications |
Selected city (including city-centre coordinates used for geohash calculation — not your device's GPS position), derived geohash, search radius, app language, notification tokens, notification preference settings (push on/off, message, event and announcement notifications), device/platform information needed by Firebase, whether location permission is enabled and, only if you allow location access, your device's current position, which is used on your device. |
Show nearby events, send service notifications, secure and operate the App. If you allow location access, the App reads your device's position on your device to suggest your nearest supported city, to search for events in the surrounding area and to show distances. To search, the App sends our database an approximate area rather than your exact position. We do not store your device's position on our servers; the coordinates we store are the city-centre point from our city database. |
|
Reports, moderation and safety |
Reports about users, rooms, events or content that you submit or that concern you, report category, description, moderation notes, decisions, restrictions and safety signals. |
Enforce the Terms, protect users, prevent fraud, handle appeals and comply with law. |
|
Support and legal correspondence |
Your email address, message content, attachments such as screenshots and our replies. |
Respond to requests, exercise rights, investigate issues and keep records where needed. |
|
Crash diagnostics |
Crash logs, non-fatal error reports, short technical event logs, stack trace, app version, operating system version, device model, memory state and a pseudonymous Firebase installation ID. |
Find and fix technical problems. We do not intentionally include your messages, photos, name or account ID in crash reports. |
|
Purchases and subscriptions |
App-store purchase token, product ID, subscription plan and billing period, entitlement status, renewal and cancellation status, whether you are on a free trial and when it ends, a unique purchase reference we register before your purchase so we can reliably match store notifications to your account, which Lobby account a store subscription is currently active on (and, when it is moved, the account it moved from and when), and limited transaction metadata. We do not receive your card details. |
Provide paid features, manage subscriptions, verify entitlements, restore previous purchases, handle support and meet accounting, tax and legal obligations. |
|
Free allowance records |
A one-way (SHA-256) hash of a stable identifier for you, being your Apple sign-in identifier where available and otherwise your normalised email address, together with how many events you have hosted and joined under the promotional free allowance in the current calendar month, the month those counts belong to, and the account IDs that have drawn on the allowance. The record holds no email address, name or other readable identifier. |
Give each person the promotional free allowance once per calendar month, and stop it resetting when an account is deleted and a new one is created. |
|
Welcome offer records |
The same kind of one-way (SHA-256) hash of a stable identifier for you, together with whether the welcome free month has been granted to you, the place number it used, the dates it started and ended, and the account IDs associated with that hash. The record holds no email address, name or other readable identifier. |
Give each person the welcome free month once, and stop a deleted and re-created account from receiving a second one or using up a further place. |
|
New member offer records |
The same kind of one-way (SHA-256) hash of a stable identifier for you, together with the date that identifier was first seen, the one-time free allowance and how much of it has been used, which of the offer's steps you have completed and when (with the IDs of the events concerned), until when the introductory price may be claimed and whether it has been used, and the account IDs associated with that hash. Before you buy the monthly membership on the App Store we also receive, from the App, Apple's signed record of your App Store installation, and use its transaction identifier only to sign whether the introductory price applies to that purchase. On Google Play the App asks us whether the offer applies before you buy, and no installation record is sent. The record holds no email address, name or other readable identifier. |
Offer the new member allowance and introductory price only to people who have not used Lobby before, once per person, and tell the App Store or Google Play whether a purchase may use the introductory price. |
|
Website and waitlist |
If you join the waitlist on our website: your email address, the time you signed up, which form you used and the version of the waitlist terms shown to you. To honour a launch offer promised to waitlist members, we may also keep your email address with a one-way hash of it in our app database, so that it can be matched to an account created with the same email address. When you visit our websites, your browser sends our web host technical data such as your IP address and the pages requested; Meta Pixel data is collected only if you accept it (see Section 10). |
Tell you when Lobby is available, honour the launch offer promised to waitlist members, prevent duplicate sign-ups, and keep the websites secure and working. |
If you voluntarily include sensitive information in your profile, prompts, event details, messages or reports, you choose to make that information available to the relevant audience in the App. Please do not share sensitive information unless you are comfortable with that use. Biometric face verification is handled separately and only with explicit consent.
Inside the App we do not collect advertising identifiers, do not sell personal data and do not use third-party behavioural analytics SDKs. Our public websites (lobbyapp.eu and lobbyapp.hu) use the Meta Pixel to measure how visitors find Lobby and to support our advertising, but only if you accept it in the cookie banner; until then nothing is loaded and no cookie is set. See Section 10.
3. How We Use Data and Our Lawful Bases
|
Processing |
Lawful basis |
|---|---|
|
Account creation, profile setup, events, chat, friends, endorsements and service notifications. |
Contract: processing is necessary to provide Lobby under the Terms. |
|
Photo moderation, reports, safety investigations, fraud prevention, abuse prevention and platform security. |
Legitimate interests: keeping Lobby safe, trustworthy and lawful. You may object where GDPR allows. |
|
Face verification using a live selfie and face comparison. |
Explicit consent for biometric processing under Article 9(2)(a) GDPR, plus consent or contract/legitimate interests for related account operation where applicable. |
|
Crash diagnostics and reliability improvements. |
Legitimate interests: maintaining and improving the App. |
|
Responding to privacy/legal requests, handling purchases and subscriptions, accounting and regulatory obligations. |
Legal obligation and, where needed, contract performance or legitimate interests for legal claims and platform operation. |
|
Applying the promotional free allowance and preventing it from being reset by re-registration. |
Legitimate interests: running the promotion on fair terms for everyone and preventing abuse of it. Contract performance where the allowance forms part of the service we provide under the Terms. |
|
Granting the welcome free month once per person and preventing it from being claimed again by re-registration. |
Legitimate interests: running a limited offer on fair terms for everyone and preventing abuse of it. Contract performance where the free month forms part of the service we provide under the Terms. |
|
Running the new member offer once per person, and telling the App Store or Google Play whether a purchase may use its introductory price. |
Legitimate interests: running the offer on fair terms for everyone and preventing abuse of it. Contract performance where the allowance and the introductory price form part of the service we provide under the Terms. |
|
Using your device's location to suggest your city and find events near you. |
Consent, given through your device's location permission, which you can withdraw in your device settings at any time. |
|
Waitlist sign-up, telling you when Lobby is available and honouring the launch offer. |
Consent, given when you submit the waitlist form, which you can withdraw at any time by asking us to remove your email address; and steps taken at your request before you start using the App. Website security and operation: legitimate interests. |
|
Optional marketing or product news if introduced later. |
Consent. We do not send marketing emails today. |
4. What Other Users Can See
Other users may see your public profile information, photos, age, city, prompts, interests, verified status and endorsement count. Event participants may see event details, your participation and messages you send in that event chat. Friends may see friend-related activity. Your date of birth is not shown to other users; your age is. Events you host, including their title, description, banner, place and time, can be seen by users who can discover them. When you host or join an event, your name and profile photo are shown on it to everyone who can see the event, including users who have not joined it. Your name and profile photo may appear in event chats, in automatic chat messages (for example when you join or leave) and in notifications sent to other users; a notification about a chat message you send shows your name, the event title and the beginning of your message. If you block someone, we limit what you see of each other in the App. Event participants can see when you are typing and your reactions to messages. Someone you give an endorsement (kudos) to sees only how many they have received, not who gave them. We do not tell a reported user who reported them, unless the law requires us to. Reports are not shown publicly, but we may share limited information where needed to explain a moderation decision, protect users or comply with law.
5. Who We Share Data With
We share personal data only where needed to operate Lobby, comply with law, protect users or receive professional support. We do not sell personal data and do not share it with third parties for their own advertising.
|
Recipient |
Role |
Typical location |
|---|---|---|
|
Google / Firebase |
Authentication, Firestore database, Cloud Functions, Cloud Messaging, Crashlytics and related infrastructure. |
Database in Europe (Belgium and the Netherlands) and Cloud Functions in Belgium; other services are configured for European regions where available. Firebase Authentication, Cloud Messaging and Crashlytics are global services that may process data in the United States, under the safeguards in Section 6. |
|
Amazon Web Services (AWS) |
Profile photo storage (Amazon S3) and delivery to the App (Amazon CloudFront), moderation of profile photos and event banners, and face verification, using AWS services such as Rekognition. |
Storage and processing in the EU region, currently Frankfurt (eu-central-1). CloudFront delivers photos through AWS's global network and may serve cached copies from locations outside the EEA. |
|
Apple |
Sign in with Apple, App Store distribution, in-app purchases/subscriptions, operating-system notification services, receiving the unique purchase reference we register before each purchase so Apple can match payment events to your account, and applying an introductory price only where our signed answer for that purchase allows it. |
EU/worldwide under Apple's terms. |
|
Google Play / Android services |
Sign in with Google, Android app distribution, in-app purchases/subscriptions, operating-system services, receiving the unique purchase reference we register before each purchase so Google Play can match subscription events to your account, and applying the new member offer's introductory price only to a purchase our answer for it allows. |
EU/worldwide under Google's terms. |
|
Email delivery and website hosting providers |
Delivering account verification emails, hosting our websites and storing waitlist sign-ups. |
EEA where practical; see Section 6. |
|
Meta Platforms Ireland |
Meta Pixel on our websites, only if you accept it (see Section 10). |
EU, with possible transfers outside the EEA under Meta's terms. |
|
Authorities, courts, advisers or successors |
Legal compliance, safety, claims, audits, insurance, corporate transactions or insolvency. |
As needed for the relevant lawful purpose. |
Our processors must process personal data only on our instructions and under appropriate data processing terms where required by Article 28 GDPR.
Verification email and abuse prevention
Verification email delivery and abuse prevention: our email hosting provider receives your email address and a one-time Firebase action link to deliver account verification messages. Firebase remains responsible for validating verification links. We keep limited delivery status, request IDs, timestamps and a keyed hash of the email address to prevent repeated sending; the hash is pseudonymous, not anonymous. Per-account delivery state is removed during account deletion. Mailbox and aggregate sending budgets may remain briefly to prevent abuse through account recreation; inactive records are scheduled to expire after seven days, with asynchronous deletion. Provider delivery logs and copies in your mailbox follow the relevant provider's retention practices. Google and, on supported Apple devices, Apple process app/device attestation signals to help protect the sending endpoint. Authentication pages do not use advertising or analytics trackers.
6. International Transfers
We aim to keep Lobby data in the European Economic Area where practical. Some providers are part of global groups or may provide support from outside the EEA. Where personal data is transferred outside the EEA or the United Kingdom, we use appropriate safeguards such as adequacy decisions, the EU-US Data Privacy Framework where applicable, Standard Contractual Clauses, transfer impact assessments and supplementary measures where required.
7. Retention
We keep personal data only as long as needed for the purposes above, then delete or anonymise it. These periods may be shorter where possible or longer where law, safety, disputes or legal claims require it.
|
Data |
Retention |
|---|---|
|
Account and profile data |
For as long as your account is active, then deleted or anonymised after account deletion unless a limited exception applies. |
|
Profile photos |
Approved photos are kept while they are on your profile. Photos you remove stop being shown and are deleted from storage later, at the latest when your account is deleted. Rejected or pending photos may be kept for up to 30 days for moderation and abuse prevention. |
|
Face verification |
The live selfie is processed transiently for verification and is not stored as an image by us. Verification metadata (the result, the similarity score, the photo the selfie was compared with and timestamps) is kept while needed for account integrity, abuse prevention and legal claims, which may continue after your account is deleted. |
|
Event chat messages |
Automatically deleted about 35 days after the scheduled event date, unless limited retention is needed for safety, legal or technical reasons. Messages are not removed earlier when you leave an event or delete your account. |
|
Event banners |
Deleted when they are rejected in moderation, when the event closes or when the event is deleted. |
|
Events, friends and endorsements |
Kept while needed for the account and feature. Endorsements may be anonymised so aggregate counts remain accurate after deletion. |
|
Reports and moderation records |
Usually up to 24 months after resolution, or longer where needed for safety, repeat-abuse prevention, legal duties or claims. |
|
Banned account markers |
Kept as long as reasonably needed to prevent re-registration and protect users. |
|
Support correspondence |
Usually up to 24 months after the case closes. |
|
Security logs and crash diagnostics |
Usually up to 90 days, unless needed for an investigation. Crashlytics retention follows Firebase's standard limits. |
|
Subscription and payment records |
Subscription entitlement status (whether you have an active plan, its type and expiry) is kept while needed to provide paid features, resolve disputes, comply with law or prevent fraud. The links between a store subscription or purchase and your account are deleted when you delete your account; the subscription itself stays with your Apple or Google account until you cancel it there. Payments and purchases are processed by the Apple App Store and Google Play, which act as the seller and issue your receipt; we do not store card or payment data. Business sales and accounting records derived from the app stores are retained for the period required by Hungarian tax and accounting law. |
|
Free allowance records |
Kept for 60 days from the last time the record changed, then deleted automatically. This record is deliberately not deleted with your account: it is what stops the monthly free allowance resetting when an account is deleted and a new one is created for the same person. It holds no readable contact details. |
|
Welcome offer records |
Kept for 12 months from the last time the record changed, then deleted automatically. Like the free allowance record, it is deliberately not deleted with your account: it is what stops a second free month being granted when an account is deleted and a new one is created for the same person. The longer period reflects that the free month is a one-off rather than a monthly reset. It holds no readable contact details. |
|
New member offer records |
The offer's progress is kept for 12 months from the last time it changed, then deleted automatically; the one-time allowance and the date your identifier was first seen are part of the free allowance record and are kept for 60 days from its last change, but never deleted before the allowance itself has ended. Like the records above, they are deliberately not deleted with your account: they are what stop the offer being claimed again when an account is deleted and a new one is created for the same person. They hold no readable contact details. |
|
Waitlist sign-ups |
Kept while the launch offer for waitlist members can still be claimed, and in any case for no longer than 24 months after you sign up, unless you ask us to remove your email address earlier. |
|
Device location |
Not stored on our servers. Your device's position is used on your device while the App needs it. |
8. Your Rights
Subject to GDPR conditions, you may request access, rectification, erasure, restriction, portability and objection. Where processing is based on consent, you may withdraw consent at any time without affecting earlier lawful processing. You also have rights relating to automated decision-making where Article 22 GDPR applies.
To exercise your rights, contact info@lobbyapp.eu. We normally respond within one month. If a request is complex, we may extend the response period by up to two further months and will tell you within the first month. We may ask for information needed to verify your identity.
You can complain to the Hungarian National Authority for Data Protection and Freedom of Information (NAIH), 1055 Budapest, Falk Miksa utca 9-11, ugyfelszolgalat@naih.hu, https://www.naih.hu, or to the supervisory authority in the EU/EEA country where you live or work.
9. Choices and Permissions
You can edit most profile information in the App, turn push notifications, or individual types of them (messages, events and announcements), off in the App's notification settings or in your device settings, withdraw location permission in your device settings, ask us to remove your email address from the waitlist, and delete your account in the App. You may withdraw consent for face verification by deleting your account; as face verification is required to use Lobby, withdrawing biometric consent means your profile will be removed. If you withdraw other permissions, the related feature may stop working or become limited.
Push notifications are delivered through Apple Push Notification service and Firebase Cloud Messaging. A notification about a chat message contains the sender's name, the event title and up to the first 150 characters of the message, and may be shown on your lock screen depending on your device settings; you can hide notification previews in your device's notification settings. The App uses your camera and photo library only when you take or choose a photo, including the selfie for face verification, and uploads only the photos you select. Your device may ask for your permission first.
10. Cookies and Device Storage
Our public websites (lobbyapp.eu and lobbyapp.hu) use the Meta Pixel, a tool provided by Meta Platforms Ireland Ltd. When you accept it in the cookie banner, the Pixel sets cookies (such as _fbp) and sends Meta information about your visit — for example the page viewed, a page-view event and, if you newly join the waitlist after accepting, a lead/waitlist signup event that does not include your email address in our event code — so we can measure how people find Lobby and how our advertising performs. This happens only with your consent (Article 6(1)(a) GDPR and the applicable ePrivacy rules). Until you accept, the Pixel does not load and sets no cookie; if you decline, or later change your mind via "Cookie settings" in the website footer, we do not load it and remove its cookies. No other analytics or advertising cookies are used on the websites, and accepting the Pixel is optional — it is not required to use the site or join the waitlist. Meta may process this data in countries outside the EEA and for its own purposes; details are set out in Meta's own policies.
Separately, the App and its SDKs store necessary information on your device, such as authentication tokens, local cache, city data, notification tokens and operating-system app data. This storage is used to make the App work, not for cross-app advertising tracking.
11. Security
We use technical and organisational measures designed to protect personal data, including TLS in transit, cloud-provider encryption at rest, access controls, Firebase security rules, AWS IAM permissions, signed upload URLs, rate limits, Firebase App Check and internal access restrictions. App Check asks Apple (App Attest or DeviceCheck) or Google (Play Integrity) to confirm that requests come from a genuine copy of the App on a genuine device, which involves device attestation data processed by Apple and Google. No system is perfectly secure. If a personal data breach requires notification under GDPR, we will notify the competent authority and affected users where required.
12. Automated Processing
Lobby uses automated systems for profile photo and banner moderation, face comparison, abuse prevention, rate limits, eligibility for promotions and offers, and event discovery/ranking. The order of events in your feed is worked out on your device from your selected city, the distance from you, the interests on your profile and the event date, with a small random share of other events added; you can influence it by changing those settings and filters. These systems help operate and protect the App. We do not intend them to make decisions that produce legal or similarly significant effects within the meaning of Article 22 GDPR. You can ask for human review of moderation or verification outcomes by contacting info@lobbyapp.eu.
13. Children
Lobby is for adults aged 18 and over. We do not knowingly collect data from children or allow under-18 users. If we learn that an under-18 user created an account, we will close the account and delete related data, except limited information needed for safety or legal reasons. Parents or guardians can contact info@lobbyapp.eu.
We rely on the date of birth you give us; a profile cannot be completed with a date of birth showing an age under 18.
14. Account Deletion
You can delete your account in the App or by contacting info@lobbyapp.eu from the email linked to your account. We will delete or anonymise your profile, remove active photos, revoke authentication, remove you from future events where practical, delete notification tokens and handle endorsements and chat messages according to the retention rules above. Some content already shared with other users, system messages, safety records or legally required records may remain for a limited period.
Deleting your account does not cancel a store subscription; manage it in your Apple or Google account. Messages you sent in event chats are not removed when you delete your account: they stay visible to the other participants until they are deleted automatically as described in Section 7, and your name may appear in an automatic message saying that you left. If you host an event that still has other participants, hosting passes to one of them and the event continues; an event in which you are the only participant is deleted together with its chat.
Some records are deliberately kept when you delete your account, as described in Section 7. The free allowance, welcome offer and new member offer records identify you by a one-way hash rather than by your email address or name, record only whether and how much of a promotion has been used, and are deleted automatically 60 days or 12 months after they last changed; without them, deleting an account and creating a new one would reset the monthly allowance, hand out a second welcome free month or let the new member offer be claimed again. Face verification metadata, reports and moderation records, and records we must keep by law are kept for the periods set out in Section 7.
15. Changes and Contact
We may update this Policy to reflect changes in the App, law, vendors or our processing. Material changes will be notified in the App or by another appropriate method. If new processing requires consent, we will ask before it begins.
Privacy enquiries, user-rights requests and legal/general contact: info@lobbyapp.eu Tax number: 42985244-1-23. Our name and registered seat are set out in the "Controller and Contact" section above.
-- End of Privacy Policy --