Español

Jelo privacy policy

Updated: 2026-10-20

Essential information

Jelo uses data to manage accounts, connect people, organise plans, facilitate bookings and payments and protect the community. The controllers are identified in section 1. Exercise your rights via soporte@jelo.live. This policy applies to the Jelo app and its public website, including Google sign-in.

1. Responsibility and contact

Identity: Francisco Lopez Ortega y Alejandro Expósito Pontiveros.

The identified individuals jointly determine the purposes and means of Jelo’s processing and act as joint controllers. You may exercise your rights against either of them and request the essence of their allocation of responsibilities.

Contact soporte@jelo.live for privacy enquiries and to exercise your rights. The service provider’s identity and address are available in the legal notice.

2. Data and purposes

For professional accounts we process the business application, name, description, city, venue address, public email, website, categories, logo, cover image and adult/representation declarations to review and manage the account. Approved professional profiles publish the contact and presentation details supplied for that purpose; the representative's birth date is not published there. Applications under review and reviewer notes are private. The last approved version may remain visible while changes are reviewed.

Professional plan drafts and their cover images are available only to their authenticated owner. Saving a draft does not publish a plan or create bookings or notifications. Administrative decisions are recorded to manage applications and their review.

2.1. Google sign-in and data received from Google

Access and data: if you choose “Continue with Google”, Google authenticates your account and sends authorised basic data to Keycloak, Jelo's identity service. The permissions are openid, email and profile: your Google account identifier, email and verification status, name, surname and other basic information supplied by Google, such as your profile picture URL. We do not request Gmail, Drive files, Calendar or contacts access. The birth date requested by Jelo is supplied in Jelo; these permissions do not provide access to your Google birth date.

Use: we use this data to verify your identity, create or link your Jelo account, sign you in and complete basic profile information. Your Google photo does not replace the photos you choose to publish in Jelo. We do not receive your Google password. Your email and Google identifier are not displayed on your public profile; your name in Jelo may be visible as described in section 3.

Storage and security: Keycloak manages your identity and its link to Google; profile data needed for Jelo is stored in the service's database. Google tokens are used for authentication and are not retained to access Google services later. The app receives Jelo session tokens issued by Keycloak: it stores them using system secure storage on Android and iOS and browser session storage on the web. Sign-in uses Authorization Code with PKCE and production communications use HTTPS. The API checks authentication and permissions; administrative functions require authorisation. We do not claim end-to-end encryption for chats.

Recipients and transfers: Google provides authentication and Railway hosts Jelo's identity and database services. Authorised Jelo personnel may access information necessary for support, security and legal obligations. Providers and international processing are described in section 5. Other users only receive the profile information needed for the social features described in this policy. We do not send Google tokens to organisers or other users.

Limited use: Jelo's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including Limited Use requirements where applicable. We do not sell Google data or use or transfer it for personalised advertising, data brokers, credit assessment or training general-purpose AI models. We do not request Google Workspace permissions for these purposes.

Retention, revocation and deletion: imported identity information and the Google link follow section 6. You can revoke Jelo's access from your Google Account connections. Revocation may prevent future Google sign-ins; it does not automatically delete previously received data or an existing Jelo session. To close your account and request deletion of Google data retained by Jelo, contact support or follow Delete account. You do not need the app installed. Closing Jelo does not delete your Google Account.

3. What others can see

Your public name, age, city, biography, photos and social activity displayed in the profile are visible to other users. Relationship status is hidden by default; choosing a status displays it on your profile, and you can hide it again in Edit profile. It is not used to segment or recommend people. Plans and shared links may display public information outside the app. Published photos should not be considered private. Do not publish sensitive data, third-party addresses or images without permission.

Group messages are intended for the organiser and authorised participants. Exact meeting details depend on plan access rules. Identity verification and payment details are not displayed as public profile information.

4. Lawful bases and required information

Managing the account, profile, plans, bookings, chat and requested social features is based on performance of the service (GDPR Article 6(1)(b)). Compliance with accounting, tax and legal requirements is based on Article 6(1)(c). Fraud prevention, security and proportionate incident handling rely on the legitimate interest in protecting people and the service (Article 6(1)(f)), subject to assessment and the right to object. Optional processing that requires consent relies on Article 6(1)(a); you may withdraw consent without affecting the lawfulness of earlier processing. Operating-system permission for photos, location or notifications does not mean accepting advertising or replace the lawful basis for each processing activity.

Without information required for sign-in, booking or payment we cannot provide those functions. Optional profile fields may be left empty. You may refuse location permission and choose a place manually.

5. Providers and recipients

We use hosting and database services to operate Jelo; Keycloak for identity; Stripe for payments and organiser payouts; Google/Firebase Cloud Messaging on Android and Apple Push Notification service on iOS for notifications; Photon/Komoot for place searches; and map providers when you choose to open a meeting point. Searches and coordinates sent to a place provider, and data sent when opening maps, are also processed under that provider's terms.

The in-app map uses OpenStreetMap tiles. Opening it sends your IP address and requested map areas to that provider, without sharing your Jelo credentials or chat content.

Railway hosts the API, PostgreSQL and Keycloak services. The operator's migration record dated 15 October 2026 places those services and the PostgreSQL volume in Amsterdam, Netherlands; it does not establish residency for all logs, backups, support tools or subprocessors. Keycloak manages sign-in and linking to Google when you choose that option. Stripe processes payments, refunds and organiser onboarding and payouts through Checkout and Connect. Cloudflare serves the website and forwards support email; the destination mailbox uses Gmail. Access recovery uses the mail service configured for identity. Google/Firebase Cloud Messaging and Apple Push Notification service deliver enabled notifications; Photon/Komoot provides place searches; OpenStreetMap provides integrated map images. External maps are also subject to the terms of your chosen provider. Providers receive data needed for their function and may process information outside the European Economic Area; server location does not guarantee that all processing stays in the EU. Contact support to identify the entities involved in your transaction and obtain information about applicable transfer safeguards. We do not claim that all these providers have the same legal role or that hosting location replaces their contracts and safeguards.

Information may be disclosed to authorities where legally required or under a valid request. This policy is not a blanket authorisation to sell data or send advertising.

6. Retention

Account, profile, sign-in and activity data are retained while needed to provide requested features and manage the account. Plans, messages and reviews may remain as history for authorised people; no verified general automatic expiry applies to that content. Erasure requests are recorded and require processing: receipt does not mean immediate deletion. Where paid booking history exists, direct deletion is blocked and closure requires review and financial reconciliation; information needed for payments, refunds, obligations or claims must be separated from public profile exposure. Professional-account applications and reviews are retained to manage approval and appeals. Professional plan drafts are private; their owner can delete them together with their cover image. Reports, moderation decisions and audit records are retained to investigate and review incidents, with authorised access. Technical notification cleanup selects expired delivery records over seven days old and disabled devices last seen over thirty days ago in batches; deletion exactly at those deadlines is not guaranteed. Enabled devices do not automatically expire for inactivity. No automatic deletion period is claimed for logs, backups or every data category. You may ask support about retained account data, its purpose and the applicable period or criterion, and request erasure or restriction where applicable.

These criteria include the identifier, email, basic information and sign-in link received from Google. They are used while needed for the account and its management; after a closure request they are reviewed for deletion, anonymisation or limited retention under a justified obligation or claim. Retaining financial information does not justify keeping a public profile or active access longer than necessary. Backups and logs require their own criteria and access controls.

7. Your rights

You may request access, rectification, erasure, restriction, objection and portability where applicable, and withdraw consent where it is the lawful basis. Write to soporte@jelo.live identifying the right and account. We will request additional identity information only where necessary and proportionate; do not send passwords or card details.

We will respond to rights requests without undue delay and, as a general rule, within one month of receipt. Where justified by the complexity or number of requests, this may be extended by up to two additional months; we will explain the reasons within the first month. This response period does not mean that all data must be destroyed immediately: we will explain any obligations requiring limited information to be retained and the measures applied to the rest of your data.

You may complain to the Spanish Data Protection Agency or your competent supervisory authority. To request erasure without installing the app, see Delete account.

8. Age, security and changes

Jelo is intended exclusively for people aged 18 or over. Contact support if you detect use by a minor. Production API communications use HTTPS. No service can guarantee the complete absence of incidents; relevant incidents will be handled under applicable obligations.

Category levels and achievements are calculated from activity and ratings. They do not verify physical attendance or professional qualifications, or guarantee activity safety. You may request review of incorrect data or calculations.

Updates to this policy will be published here and significant changes communicated through appropriate means. If access to Google data expands or its purposes change, we will update the information and obtain the required authorisations before using it for the new purpose.

9. Cookies and device storage

Jelo's information pages do not include our own advertising or analytics tools. The hosting provider may use technical mechanisms for security and abuse prevention. During sign-in, Keycloak and Google use their authentication technologies; Stripe uses those required for payments when you open its forms. Jelo's local tokens maintain your session and are not used for advertising.

If non-essential cookies or technologies requiring consent are introduced, we will explain their provider, purpose and duration and enable acceptance, rejection and withdrawal before activation. You can manage storage and permissions through your browser or device; clearing session data may sign you out. Location, photos and notification permissions are managed separately.