Aller au contenu
Premeets

App terms of use

Last updated : 10 June 2026

This is a courtesy translation, provided for convenience only. It has not been reviewed by a legal professional and has no contractual value. Only the French version is legally binding.

Version 2.5 - Last updated: 10 June 2026

Key changes since version 2.4:

  • Article 5.11 (new): rules for the “Partner offers” service, now in production. A partner venue creates an offer; the User claims it by attaching an Outing or a Trip at the same location; the User redeems it in person, on site, in front of the venue’s staff (validation slider). Since the June 2026 redesign, an offer is redeemable as soon as it is received.
  • No-warranty clause (new, §5.11.1): Premeets acts solely as a technical intermediary (consistent with Art. 17.1) - the offer is provided and honoured by the partner, not by the Publisher; no guarantee that the partner will honour a redeemed offer; no monetary value, not exchangeable for money, non-refundable; redemption is single and final and must take place in the presence of staff (an offer redeemed outside that presence is lost, with no recourse); the terms of the offer (cap on beneficiaries, end date) are set by the partner.
  • Exercising GDPR rights (clarification): exporting your personal Data (right to portability, Art. 20 GDPR) is now done by email to contact@premeets.com; correcting your details and deleting your account remain available directly from the Application’s settings.

Key changes in version 2.4 (recap):

  • Token system disabled: in the current version of the Application, publishing Outings/Trips and accessing the full Premeets lists are free; no Token is earned, bought or spent. Article 6 and every mention relating to Tokens (referrals, missions, in-app purchases, service tiers) are suspended for as long as the system remains disabled (see §6.0).

Key changes in version 2.3 (recap):

  • Article 5.10 (new): detail on deleting an Outing or a Trip by its creator - automatic cascade onto the associated group conversation, retention of one-to-one private conversations with friends, in-app notification sent to participants to inform them of the cancellation.
  • Article 14.1: CDN cache duration for venue photos aligned to 30 days maximum (consistent with the cycle of the other Places caches and with the legal maximum in the Google Places ToS §3.4).
  • Article 14 ter: added a mention of the materialised views refreshed periodically (performance optimisation for the trending screens - 15 minutes maximum between refreshes).

The full and binding text is the one rendered in the Application (Settings → Terms of Use). This markdown document serves as the editorial reference.


Preamble

Welcome to Premeets. These Terms of Use (the “Terms”) govern the use of the Premeets mobile application and of all the services attached to it.

Signing up for and using Premeets implies full and unreserved acceptance of these Terms, as well as of the Privacy policy, which forms an integral part of them. If you do not accept any part of these terms, you may not use the application.


1. Definitions

In these Terms, the following words have the precise meaning given below:

  • “Application” or “Premeets”: the mobile application published by Premeets SAS, its updates, its associated web interfaces and all the services attached to them.
  • “Publisher” or “We”: Premeets SAS, a simplified joint-stock company registered with the Angers Trade and Companies Register under number 927 958 975, whose registered office is at 7 avenue des Pépinières, 49240 Avrillé, France, with a share capital of €2,300.
  • “User” or “You”: any natural person of full age registered on the Application.
  • “Premeets” (capitalised, as a common noun): the other users of the application who may share an Outing or a Trip with you.
  • “Outing”: a short plan (a few hours, the same day or the following day) created by a User, attached to a place, a date and a category (nightclub, bar, restaurant, café, culture, event, sport, activity, outdoors, beach, shopping, coworking).
  • “Trip”: a longer plan (a few days to several weeks) attached to a destination, start and end dates, and a vibe (holiday, weekend, festival, road trip, Erasmus, skiing, backpacking).
  • “Plan”: a generic term covering an Outing or a Trip without distinction.
  • “Crew” or “Group”: a set of friends invited to take part together in a Plan, created by the Plan’s organiser.
  • “Match” or “Like”: the action by which a User expresses interest in another User in the context of a shared Plan, initiating a conversation request.
  • “Token” or “Premeets” (plural, as a virtual currency): the Application’s internal unit of account, with no monetary value outside the Application, used to unlock certain features.
  • “Content”: any information published by a User (text, photo, message, plan, bio, etc.).
  • “Stores”: the Apple App Store and the Google Play Store, the mobile distribution platforms from which the Application can be downloaded.

2. Purpose of the Application

Premeets is a social application that allows Users of full age to:

  1. Create and publish Plans (short Outings and longer Trips)
  2. Discover other Users whose Plans are compatible with theirs (same place, same date, same destination, same category)
  3. Talk through private or group messaging tied to a Plan
  4. Invite friends to take part in a Plan as a Crew
  5. Meet in person within the Plans that are organised
  6. Acquire and use Tokens to access premium features

Premeets is a tool for putting people in touch. The Publisher is neither the organiser, nor a participant, nor a guarantor of the Plans published or of the meetings that follow from them. See Article 17 - Liability.


3. Acceptance, changes and applicable version

3.1. Initial acceptance

The Terms are accepted when the account is created, by explicitly ticking a box provided for that purpose (“I accept the Terms of Use and the Privacy policy”). That acceptance is time-stamped and retained as evidence by the Publisher.

3.2. Changes

The Publisher may change the Terms at any time to reflect changes in features, in regulation or in operational needs.

  • Minor changes (editorial corrections, cosmetic additions): applicable without notice; the User will be informed through the update of the date at the top of the document.
  • Substantial changes (affecting rights, obligations, liabilities, prices or termination conditions): 15 days’ notice by in-app notification and by email. During that period, the User may refuse the new Terms and close their account free of charge.

The applicable version is the one in force at the time you use the Application.


4. Registration and user account

4.1. Cumulative conditions for registration

To register, you must:

  1. Be a natural person aged 18 or over.
  2. Have the legal capacity to contract (not under a guardianship or curatorship order preventing the conclusion of digital contracts).
  3. Have a valid, personal email address to which you have access.
  4. Provide accurate, up-to-date and non-misleading information, in particular your first name, your date of birth and your gender.
  5. Accept the Terms and the Privacy policy.
  6. Not have been previously banned from the Application.

4.2. Age verification

Age is calculated from the declared date of birth. The Publisher reserves the right to request proof of age (a partially redacted copy of an identity document) in case of doubt, and to suspend the account while the verification takes place.

Any account detected as belonging to a minor is immediately and permanently deleted, without notice and without refund.

4.3. Authentication

The User may register and log in using:

  • Email + password
  • Sign in with Apple (on iOS, Apple may hide your email address)
  • Sign in with Google (Google OAuth)

The User undertakes to:

  • Choose a unique and strong password (12 characters minimum, combining letters, numbers and symbols)
  • Not share it with anyone
  • Notify the Publisher immediately if they suspect it has been compromised (contact@premeets.com)

4.4. Single, personal account

A User may hold only one account. The following are strictly prohibited:

  • Multiple or alternative accounts
  • Sharing an account between several people
  • Using an account on behalf of a third party
  • Impersonation (using another person’s name, photo or address)
  • Accounts created by an automated process, a bot or a script

Breaching these rules results in the permanent deletion of the account or accounts concerned.


5. Detailed description of the Services

5.1. User profile

You may complete your profile with the following elements, all optional except first name, date of birth and gender:

  • Profile picture (avatar) + up to 2 additional photos
  • Bio (free text, 300 characters max)
  • Home city
  • School, employer (optional)
  • Relationship status (single, in a relationship, married, it’s complicated, not specified)
  • Passions (closed list, up to 10 passions from a catalogue)
  • Unique username (handle) allowing friends to find you
  • Matching preferences (age range, preferred gender)

Uploaded photos must show you clearly and recently (less than 12 months old). Blurred or masked photos, photos containing only objects or animals, AI-generated images, composites, or photos of other people are prohibited.

5.2. Creating Outings

An Outing is a short Plan. When creating one, the User defines:

  • Category (from 12 predefined ones)
  • Venue (via Google Places search, optional) or simply a city or geographic area
  • Scheduled date and time (scheduled_at)
  • Expected duration (a few hours)
  • Description (free text)
  • Goal tags (e.g. “dancing”, “dinner”, “networking”)
  • Mode: Solo (User alone) or Group (with invited friends)
  • Visibility: Public (all Users) or Friends only
  • Crew (optional): invited friends

The User warrants that the Outing is real, planned and lawful. Fictional Outings, jokes, provocations or unlawful content lead to the deletion of the Outing and to sanctions against its author.

5.3. Creating Trips

A Trip is a long Plan (a few days to several weeks). The User defines:

  • Vibe (from 7 predefined ones)
  • Destination (city, region, country)
  • Accommodation (campsite, hotel, hostel - optional)
  • Start and end dates
  • Description (the trip’s “bio”)
  • Goal tags (e.g. “party”, “culture”, “après-ski”)
  • Mode: Solo or Group
  • Visibility: Public or Friends only
  • Crew (optional)

Trips involve physical travel, the organisation of which (transport, accommodation, insurance, vaccinations, visas, currency) is the User’s sole responsibility. Premeets provides none of these services.

5.4. Discovering Premeets (Swipe)

Premeets automatically works out which other Users have Plans compatible with yours, according to the following criteria:

  • For Outings: same venue OR same category + same city, within a time window of ±12 hours
  • For Trips: identical destination OR similar vibe, with overlapping dates

Profiles are shown in a swipe card interface. The User can “like” a profile to initiate a conversation request (see §5.5).

The matching algorithm may change without notice. No commitment is given as to the number, quality or frequency of the matches offered.

5.5. Conversation requests, likes and chat

When you like a profile in the context of a Plan:

  1. A conversation request (is_request = true) is created. You may attach an introductory message to it.
  2. The recipient receives a notification and can accept or ignore the request.
  3. A request that is not accepted is automatically archived after a period set by the Plan’s context (typically 48 hours after the end of the Outing or 7 days after the end of the Trip).
  4. If the request is accepted, or if you were already friends, the conversation becomes an ordinary discussion.

You may at any time refuse, ignore, archive or block another User (see §13).

5.6. Chat (one-to-one and group)

Conversations are strictly private between the participants. No third party (another User, an employee of the Publisher, a moderator) can access the content of the messages except:

  • Following an explicit report by a participant
  • To respond to a formal judicial requisition
  • For automated and anonymised security audits (spam and attack detection)

Group conversations are tied to a Plan: every member of the accepted Crew is automatically a participant.

Messages are kept for as long as the conversation is active. A conversation is archived automatically after the end of the Plan it is attached to (set by archive_at). Archived conversations can be reactivated if one of the participants restarts the discussion.

5.7. Friendship system

A User may send a friend request to another User they have already met or exchanged messages with. The limit is set at 30 friends per account, to preserve the app’s focus on quality.

Once the request is accepted, the two Users become mutually visible with a “friend” status, and can see each other’s Plans set to “Friends only” visibility.

Friendship can be ended at any time unilaterally, without notifying the other party.

5.8. Geolocation

The Application uses geolocation only while it is open (never in the background), in order to:

  • Suggest nearby Outings (adjustable radius)
  • Calculate the distance to a venue on maps
  • Pre-fill the “city” field when creating a Plan

You may refuse the geolocation permission at any time from your iOS / Android settings. In that case, some proximity-based features are unavailable, but the app remains usable in “declared city” mode.

5.9. Push notifications

The Application may send you push notifications for:

  • A new friend request / message / match
  • A reminder about an upcoming Outing or Trip
  • Activity in a conversation

You can disable push notifications at any time:

  • Globally from your iOS / Android settings
  • Granularly from the Application’s settings

5.10. Deleting an Outing or a Trip

The User who created an Outing or a Trip can delete it at any time from the Plan’s discovery screen (three-dot menu, top right).

Deletion automatically results in:

  • The permanent deletion of the Outing or Trip from the database (an irreversible action);
  • The deletion of the group conversation associated with the Plan, along with the message history exchanged in it;
  • The sending of an in-app notification (bell) to every participant invited to or having joined the Plan, to inform them of the cancellation;
  • The purging of any technical list-unlocking data linked to that Plan (not applicable in the current version, since the Token system is disabled - see §6.0).

The one-to-one private conversations the User has with other Users (outside the Plan’s group conversation) are not affected: they remain accessible, as do their messages.

An invited User (not the creator) may leave the Plan without deleting it: they will be removed from the list of participants while remaining, by default, in the group conversation, to preserve the social link with the other guests.

5.11. Partner offers

Some partner venues may publish, through the Application, an offer (a discount, a complimentary drink or another benefit) attached to their venue. The mechanism is as follows:

  1. The partner venue creates an offer, setting a benefit, a validity period with an end date and, where applicable, a maximum number of beneficiaries.
  2. A User who publishes an Outing or a Trip attached to the venue concerned, during the validity period, may claim the offer from within the Application.
  3. The claimed offer appears in Profile → My Offers. It is redeemed in person, on site, in front of the venue’s staff, using a validation slider (“slide-to-validate”). Since the June 2026 redesign, an offer is redeemable as soon as it is received.

5.11.1. No warranty on Partner offers

The User expressly acknowledges and accepts that:

  • Premeets is only a technical intermediary (consistent with Article 17.1): the offer is proposed, provided and honoured by the partner venue, not by the Publisher. The Publisher is neither the author, nor the debtor, nor the guarantor of the offer.
  • The Publisher gives no guarantee whatsoever that a venue will honour an offer, even one redeemed in the Application.
  • An offer has no monetary value, is not exchangeable for money or for any other instrument, and is not refundable.
  • Redemption is single and final (“one-shot”): it can take place only once and must be carried out in the presence of the venue’s staff. An offer redeemed outside the presence of staff is permanently lost, with no recourse or compensation. Redemption relies on the Publisher’s server clock and requires a connection; it is impossible offline.
  • The terms of each offer - in particular the cap on beneficiaries and the end of the validity period - are set freely by the partner venue. They may make the offer unavailable (cap reached, offer expired) without any liability on the part of the Publisher.

6. Token system (Premeets)

6.0. Token system currently disabled - the Application is free

In the current version of the Application, the Token system is entirely disabled. Publishing Outings and Trips, and accessing the full Premeets lists, are free and require no Token and no payment. No Token is earned, bought, spent or debited.

All the provisions of this Article 6 - and every other mention of Tokens in these Terms (referrals §7, changes §13.3, forfeiture §16, cap §17.3) - are suspended and have no effect for as long as the Token system remains disabled. The paragraphs below (§6.1 to §6.7) will apply only if it is reactivated, which would be the subject of a new version of the Terms requiring fresh acceptance.

Tokens (or “Premeets”) are a virtual currency internal to the Application, with no discharging power and no legal tender status.

  • They do not constitute a means of payment within the meaning of Article L.314-1 of the French Monetary and Financial Code.
  • They cannot be exchanged for a currency (euro, dollar, etc.).
  • They cannot be transferred between Users.
  • They cannot be used outside the Application.
  • They are not refundable, except in the cases set out in Article 6.5.

6.2. How they are acquired

Source Quantity Frequency
Welcome gift (completing registration) 100 Tokens One-off
Registering with a referral code used +5 additional Tokens One-off
A referee registering with your code +5 Tokens (referrer) For each referee
Weekly claim 1 Token 1× / 7 days
Mission completed (one-off) 1 to 3 Tokens One-off per mission
Weekly mission 1 to 2 Tokens 1× / week
In-app purchase (see §6.4) 10 / 50 / 200 Tokens Unlimited

The Welcome gift of 100 Tokens is credited automatically when registration is effectively completed (creation of a full profile including the initial mode selection). This credit is a commercial gesture by the Publisher without consideration, has no monetary value (see §6.1), is neither refundable nor transferable, and may be suspended or changed at any time for future registrations only, with 15 days’ notice for any reduction.

The rates may change. Any reduction is preceded by 15 days’ notice for recurring sources. “One-off” sources are guaranteed only on the terms shown in the Application at the moment they are triggered.

6.3. How they are used

Tokens are used to unlock:

  • Access to the full list of Premeets on an Outing (1 Token)
  • Access to the full list of Premeets on a Trip (3 Tokens)
  • Other future premium features

Unlocking is instant and final for the list concerned. No refund is granted after unlocking, except in the event of a technical failure attributable to the Publisher (see §6.5).

6.4. In-app purchases

Tokens can be bought through the Stores (App Store, Play Store) as packs:

Pack Quantity Indicative price (€)
Small 10 Tokens ~€2.99
Medium 50 Tokens ~€9.99
Large 200 Tokens ~€29.99

Exact prices are set and collected directly by the Stores, depending on the country, the local currency and the applicable VAT.

The Publisher stores no payment information (card number, security code). The transaction is handled entirely by Apple / Google through their approved processor (RevenueCat for consolidation on the Premeets side).

6.5. Right of withdrawal and refunds

In accordance with Article L.221-28 13° of the French Consumer Code, the right of withdrawal does not apply to digital content supplied on an intangible medium whose performance has begun with the consumer’s express agreement. When a pack of Tokens is purchased, those Tokens are credited to your account immediately, which constitutes the beginning of performance.

Refund requests:

  • First instance: with the Store concerned (Apple Support or Google Play Help), which alone holds the payment information.
  • In the event of a technical failure attributable to the Publisher (Tokens not credited, balance accounting error): open a ticket at contact@premeets.com with proof of the transaction. Reviewed within 15 days.

Cases of automatic refund:

  • Cancellation by the Store
  • Duplicate transaction
  • Technical crediting error

6.6. Forfeiture of Tokens

All Tokens are permanently lost, without consideration or refund, in the following cases:

  • Deletion of the account by the User
  • Permanent ban following a breach of the Terms
  • Prolonged inactivity (3 years without logging in) leading to automatic deletion of the account

6.7. Anti-abuse and anti-fraud

The Publisher reserves the right to:

  • Freeze the Tokens of a suspicious account while an investigation takes place
  • Cancel Tokens credited fraudulently (chargeback, exploit, abused bug, bot)
  • Cap earnings from referrals or missions in the event of abuse

Any attempt to manipulate the Token system (software exploit, fake accounts to refer oneself, abusive purchase-and-return) results in a permanent ban and possibly an action for damages under Article 1240 of the French Civil Code.


7. Referral system

7.1. Principle

Every User has a unique referral code generated at registration. When a new User registers by entering your code within the 24 hours following their registration:

  • Your referee receives +5 Tokens in their balance
  • You receive +5 Tokens in yours

7.2. Conditions

  • Self-referral is strictly prohibited (creating a fake account to refer oneself = fraud).
  • A User can be linked to only one referrer.
  • The code must be entered within the 24-hour window after registration.
  • Referrer and referee accounts must remain active and compliant with the Terms in order to keep the Tokens received.

7.3. Tiers and bonuses

Reward tiers may exist (e.g. “3 friends referred = additional bonus”). The exact terms are published in the Application and may change.

7.4. Anti-fraud

Any attempt at referral fraud (fake accounts, registration scripts, trading codes outside the authorised channels for payment) results in:

  • Cancellation of the Tokens earned
  • A ban on the accounts concerned
  • Proceedings for breach of the Terms and for fraud

8. Expected behaviour and community rules

8.1. General principle

The User undertakes to use the Application with respect, honesty and consideration, in compliance with the law in force and with the rights of other Users.

8.2. Strictly prohibited behaviour

Any form of:

  • Harassment, threats, intimidation (verbal, graphic, persistent)
  • Discrimination based on origin, gender, sexual orientation, religion, disability, age, appearance, or social or economic circumstances
  • Hate speech, denialist, racist, sexist, homophobic, transphobic, antisemitic or Islamophobic content, or content contrary to human dignity
  • Explicit sexual content, nudity, pornography, unsolicited sexting
  • Non-consensual sexual solicitation (unsolicited explicit pictures, repeated requests for nudes, aggressive sexual propositions)
  • Photos of third parties without their consent (in particular of a former partner, a colleague, or children)
  • The presence of minors in photos (even clothed, even at a public event)
  • Spam, commercial or charitable advertising, proselytising (religious, political, philosophical, MLM, pyramid schemes)
  • Unlawful content (glorification of terrorism, drugs, weapons, counterfeits, copyright infringement, child sexual abuse material)
  • Attempted fraud (fake accounts, abuse of the Token system, exploitation of bugs, scraping, bots)
  • Reverse engineering, disassembly or modification of the Application’s code
  • Circumventing security measures (RLS, rate limiting, authentication)
  • Requests for money, scams, so-called “romance scams”
  • Disclosing confidential information about other Users (doxing, sharing screenshots of private conversations without consent)
  • Promoting competing services in messages or bios
  • Misusing the Application for commercial purposes (recruitment, prospecting, B2B sales)
  • Creating content for the purposes of provocation, jokes or testing that corresponds to no real Plan

8.3. Graduated sanctions

The Publisher applies a moderation policy with several levels:

Level Action
1 Private warning by notification or email
2 Temporary hiding of reported Content
3 Suspension of the account (24h, 7 days, 30 days depending on severity)
4 Permanent ban without refund
5 Report to the competent authorities (PHAROS, public prosecutor)

For serious offences (child sexual abuse material, serious physical threats, fraud), levels 4 or 5 are applied directly and without notice.

8.4. Appeals

You can challenge a sanction by writing to contact@premeets.com within 30 days, setting out your reasons. The Publisher undertakes to reply within 15 working days.


9. Content published by the User

9.1. Ownership and licence

The Content you publish (photos, bio, Plan descriptions, messages, etc.) remains your property.

By publishing that Content, you grant the Publisher a non-exclusive, worldwide, royalty-free licence, transferable to its technical processors (hosts, CDN), limited to the duration of your registration, allowing the Publisher to:

  • Store, host, duplicate and back up the Content
  • Display it to other Users within the framework provided by the Application
  • Adapt it technically (compression, resizing, format conversion) for the needs of the service

This licence ends when your account or the specific Content is deleted, apart from backup copies kept for a maximum of 30 days.

9.2. The User’s warranties regarding Content

You warrant:

  1. That you hold all rights in the Content published (that you are the author or the holder of the licence to use it)
  2. That you have obtained the explicit consent of any identifiable person appearing in your photos
  3. That the Content infringes no third-party rights (image rights, moral rights, copyright, registered trade marks)
  4. That the Content is lawful in the country of publication and in the country of the recipients
  5. That the Content complies with the Terms and the community rules

In the event of a dispute with a third party concerning published Content, the User indemnifies the Publisher against any judgment resulting from that publication, and undertakes to compensate it for defence costs and any damages (Article L.122-4 of the French Intellectual Property Code).

9.3. Moderation

The Publisher reserves the right, without being obliged to:

  • Moderate after the fact any reported Content
  • Delete without notice manifestly unlawful Content
  • Pass on to the authorities Content amounting to a criminal offence (Article 6 of the French LCEN Act of 21 June 2004)

The Publisher has no general obligation to monitor published Content (Article 6-I-7 of the LCEN).


10. Visibility and privacy within the Application

10.1. Default visibility

The following are visible to other authenticated Users as part of how the app works:

  • First name, photos, calculated age, bio, city, school, employer, relationship status, passions, verified badge

The following are never visible to other Users:

  • Email, surname, FCM token, Token balance, referral code, matching preferences (age, gender), purchase history, technical data (IP, device ID).

10.2. Visibility of Plans

When creating a Plan, the User chooses:

  • Public: visible to all Users sharing the context (same category, same date, same destination, etc.)
  • Friends only: visible only to the User’s Premeets friends

This visibility can be changed at any time from the Plan’s screen.

10.3. Blocking a User

You can block another User from their profile page. Effects of blocking:

  • No further content from the blocked User is shown to you
  • The blocked User no longer sees you either
  • Your existing conversations become inaccessible to both parties
  • The blocked User is not notified of the block

Unblocking is possible at any time from “Settings → Blocked users”.

10.4. Reporting

Any User can report Content or another User using the “Report” button present on every profile and every Plan. Reports are handled within 48 working hours by the moderation team.


11. Meeting in person and safety

11.1. What the Application is for

Premeets encourages meeting in person, in real life (“IRL”). That is its whole purpose. Any meeting, whether it takes place in a bar, at a festival, in a flat, on a trip abroad, and so on, is organised and carried out under the sole responsibility of the Users concerned.

11.2. Safety recommendations

The Publisher strongly recommends:

  • A first meeting in a public place (bar, restaurant, open event), never at a private home
  • Telling someone close to you the identity of the person, the place and the time of the meeting, and keeping them updated in real time
  • Checking identity through live photo exchanges or a video call before the meeting
  • Never accepting a lift from someone you do not know (car sharing between strangers, private car)
  • Not drinking alcohol or taking drugs to the point of losing control, and never leaving your drink unattended
  • Having your own means of transport so you can leave at any time
  • Having your own budget: never depend on anyone financially to get home

11.3. For Trips abroad

In addition:

  • Check visa requirements, vaccinations and the country’s safety situation (recommendations from the French Ministry of Foreign Affairs)
  • Take out travel insurance covering health, repatriation and personal liability
  • Keep a digital copy of your identity documents
  • Never transfer money to another User in advance, even for shared bookings

11.4. The Publisher does not vet Users

The Publisher does not check:

  • The real identity of Users (beyond the basic checks provided for in §4.2 and §17.4)
  • Their criminal record
  • The truthfulness of what they say about their personal circumstances (relationship status, occupation, etc.)
  • Their intentions
  • Their behaviour in person

The User alone is responsible for assessing the risks of the meetings they arrange through the Application.

11.5. Emergency numbers

In a dangerous situation during a meeting:

  • France: 17 (police), 18 (fire service), 112 (Europe)
  • Abroad: the local emergency number + the French embassy
  • Stop-Violences (French Ministry of the Interior): 3919

The Publisher may, on judicial requisition, provide the authorities with data useful to an investigation (conversation logs, metadata, geolocation at the time of the events).


12. Intellectual property in the Application

12.1. Reserved rights

The Application, its name, its logo, its design, its interfaces, its source code, its trade mark, its graphics and all the elements making it up are the exclusive property of the Publisher or of its technical processors.

Any reproduction, representation, modification, translation, adaptation, derivation, distribution or exploitation, in whole or in part, by any means whatsoever, without the Publisher’s prior written authorisation, is strictly prohibited and constitutes infringement punishable under Articles L.335-2 et seq. of the French Intellectual Property Code.

12.2. Third-party trade marks

The trade marks shown in the Application (venues, partner logos, etc.) remain the property of their respective owners.


13. Availability and maintenance

13.1. Provision of the service

The Application is provided “as is”. The Publisher uses its best efforts to maintain 99% availability, excluding maintenance and force majeure.

13.2. Maintenance

Scheduled maintenance is announced in the Application at least 24 hours in advance, and carried out preferably during off-peak hours.

Urgent maintenance (critical security flaw, infrastructure failure) may take place without notice.

13.3. Changes

The Publisher reserves the right to:

  • Develop the Application (adding, changing or removing features)
  • Change the matching algorithm, the Token rates or the referral conditions
  • Discontinue all or part of the service with 90 days’ notice given in the Application

13.4. Unavailability

No compensation is due in the event of unavailability, unless it results from a clear fault of the Publisher and exceeds 5% of the cumulative time over a calendar month.


14. Personal data

The processing of your personal Data by the Publisher is governed by the Privacy policy, which forms an integral part of the Terms.

In particular, you have the following rights: access, rectification, erasure, objection, restriction and portability (see Articles 15 to 22 of the GDPR).

14.1. Technical retention periods

In addition to the Data retention periods described in the Privacy policy, the Application implements automatic purging of technical data, for performance reasons and to comply with the conditions imposed by third-party service providers (in particular Google Places - see §14 bis):

Data Purpose Retention period Mechanism
Google Places search cache Performance, API quota savings 30 days maximum Daily scheduled task
Venue details cache Performance 30 days maximum Daily scheduled task
City autocomplete cache Performance 30 days maximum Daily scheduled task
Venue photos (CDN cache) Performance 30 days maximum (automatic server-side re-fetch at day 28) Scheduled task + re-fetch on next access
Places API call log (audit) Security, anti-abuse, statistics 7 days Daily scheduled task
Registered but unfinished account Database hygiene 48 hours Daily scheduled task

Personal Data as such (profile, outings, trips, conversations, etc.) is governed by the Privacy policy and is never deleted by these technical tasks.

14.2. API call logging

The Publisher keeps, on a rolling 7-day basis, an anonymised log (the User’s internal identifier, the function called, a timestamp, a hash of the request) of calls to the Google Places services through the Application’s internal gateways. This log allows:

  • Detection of abusive usage (limiting calls to a reasonable number per rolling 24 hours),
  • Maintenance and optimisation of third-party API costs.

No sensitive information (password, message content, payment data, precise geolocation) is logged. The log is purged automatically after 7 days by a scheduled task.


14 bis. Third-party technical providers

The Publisher uses the following technical providers to deliver the Application. Each is bound by its own terms of use and privacy policy, which the User acknowledges having had the opportunity to consult:

Provider Service provided Data transmitted Links
Supabase, Inc. (United States) Database hosting, file storage, authentication, server functions All data needed to operate the service Privacy · Terms
Google LLC (Google Places API New, Google Maps SDK) Venue search, map display Text queries, approximate geographic position Privacy · Maps Terms
Google LLC (Sign in with Google) Federated authentication (OAuth) Email, name, Google identifier Privacy
Apple Inc. (Sign in with Apple) Federated authentication (OAuth) Email (real or Apple relay) Privacy
Firebase Cloud Messaging (Google) Delivery of push notifications Device identifier (FCM token) Privacy
RevenueCat, Inc. Management of in-app purchases and subscriptions Purchase identifier, User identifier Privacy
Sentry (Functional Software, Inc.) Technical monitoring, error detection Anonymised error trace, Application version Privacy
Apple App Store / Google Play Store Distribution of the Application, processing of in-app payments Store account data, payment method Apple · Google

This list is updated regularly. Any substantial change (adding or changing a strategic provider) is notified through a new version of the Terms requiring fresh acceptance (see §19).

Transfers outside the European Union (in particular Supabase, Google, Sentry, RevenueCat - United States) are covered by the European Commission’s Standard Contractual Clauses (Decision 2021/914), in accordance with the GDPR.


14 ter. Technical and organisational security measures

In accordance with Article 32 of the GDPR, the Publisher implements the following measures to ensure a level of security appropriate to the risk:

  • Encryption in transit: all communications between the Application and the servers are protected by HTTPS/TLS 1.2 or above.
  • Encryption at rest: the database is encrypted by the hosting provider (AES-256).
  • Row-level access control (Row Level Security): each User has access only to the Data concerning them; sensitive operations go through functions with controlled privileges.
  • Code obfuscation of the distributed mobile Application, to limit reverse engineering and the reading of technical keys by an attacker.
  • Rate limiting per User on calls to paid third-party APIs, to prevent abuse and protect the service.
  • Audit log of sensitive actions (administration, access to third-party APIs) with short retention (see §14.2).
  • Materialised views refreshed by scheduled tasks every 15 minutes for frequent aggregations (destination trends, match counts) - this reduces server load and improves the Application’s responsiveness. Materialised views contain only data that is already public or anonymously aggregated.
  • Passwords never stored in plain text: User passwords are stored hashed and salted with the authentication provider, never in plain text by the Application.
  • Immediate erasure from memory of transient secrets (registration passwords, OTP codes) as soon as they are no longer needed.

No measure can guarantee absolute security. The Publisher undertakes to notify the CNIL of any personal Data breach within 72 hours of discovering it, and to inform the Users concerned where the law requires it (Article 34 of the GDPR).


15. Communications from the Publisher

The Publisher may send you:

  • Transactional emails relating to your account (confirmation, security, password change): these cannot be unsubscribed from, as they are necessary to the service
  • Push notifications in the Application (matches, messages, reminders): these can be disabled in the settings
  • Marketing emails (news, promotions): sent only after your explicit consent, and unsubscribable at any time using the link at the foot of the email

16. Suspension and termination

16.1. Termination by the User

You can delete your account at any time, without notice or justification, from: Settings → Account → Delete my account

Effects:

  • Immediate erasure of the personal Data directly linked to you (profile, photos, plans, messages - the latter being anonymised)
  • Retention of certain data for legally required periods (financial transactions: 10 years; security logs: 90 days)
  • Permanent forfeiture of any remaining Tokens (without refund)
  • A 30-day grace period (soft delete) during which registering again with the same email is blocked
  • Permanent erasure after 30 days

16.2. Termination by the Publisher

The Publisher may suspend or terminate your account without notice in the event of:

  • A serious or repeated breach of the Terms
  • Behaviour damaging the security, integrity or reputation of the Application
  • Fraud, abuse of the Token system, exploitation of vulnerabilities
  • Prolonged inactivity (3 years without logging in)
  • Judicial requisition or administrative decision
  • Complete discontinuation of the service (with 90 days’ notice)

16.3. Effects of termination by the Publisher

Where termination is due to the User’s fault:

  • No refund is due (Tokens, any subscriptions)
  • The User undertakes not to create a new account
  • The Publisher retains the necessary evidence (for the legal period)
  • A possible action for damages remains open (Article 1240 of the French Civil Code)

16.4. Automatic purging mechanism

When a User account is deleted (at the initiative of the User or of the Publisher), the following technical operations are triggered automatically and in cascade:

  • Deletion of the profile and associated media (photos, bio, preferences)
  • Anonymisation of dependent Content kept for service continuity (messages in shared conversations, etc.) - see §16.1
  • Immediate erasure of the third-party API call audit logs attached to the User (see §14.2), by cascade on the foreign key
  • Erasure of the push notification token (FCM), to prevent any further notification being sent to a device that should no longer receive them

Data kept for legally required periods (financial transactions, moderation evidence in the event of a dispute) remains available only to the competent authorities and is no longer accessible through the Application’s ordinary channels.


17. Limitations of liability

17.1. Nature of the Application

Premeets is a technical tool for putting people in touch. The Publisher is neither:

  • The organiser of the Plans published by Users
  • The host or the operator of the venues listed
  • A travel agency or a booking intermediary
  • A matchmaking or dating service
  • A background-checking service on Users

17.2. Exclusions of liability

To the fullest extent permitted by law, the Publisher is not liable for:

  1. The behaviour of other Users in the Application or in person (words, acts, verbal, physical or sexual assault, defamation)
  2. Meetings in person arranged through the Application: how they unfold, their consequences, injuries, theft, accidents or harm to health
  3. Decisions taken by the User on the basis of information published by other Users (transport, accommodation, spending)
  4. The accuracy, truthfulness or quality of the Content published by Users
  5. Disputes between Users, whether civil or criminal
  6. Indirect loss (loss of profit, loss of opportunity, damage to reputation, loss of data)
  7. Unavailability caused by external factors (cloud provider, internet network, Store outage, force majeure)
  8. The acts of malicious third parties (hacking, phishing targeting an account, denial-of-service attack)
  9. Misuse of the Application (fake accounts, circumvention of the rules)
  10. The acts of the Stores (Apple, Google): removal of the Application, changes to their own terms, blocking of a developer account
  11. The User’s failure to follow the safety recommendations set out in §11

17.3. Liability cap

Should the Publisher’s liability be established by a court decision (other than for personal injury or in cases of wilful misconduct or gross negligence, which remain fully compensable), it would be capped, across all heads of loss combined, at the higher of the following amounts:

  • €100 (one hundred euros)
  • The total amount of in-app purchases made by the User over the 12 months preceding the triggering event

17.4. The Publisher’s undertakings

Without constituting a warranty, the Publisher undertakes, as a diligent professional, to:

  • Implement reasonable technical and organisational security measures to protect the Data and the integrity of the Application
  • Regularly audit permissions, RLS policies, RPCs and configuration files
  • Moderate reported content within 48 working hours
  • Allow the account to be deleted in a few taps
  • Respond to GDPR requests within the legal time limits (one month)

18. Force majeure

Neither party may be held liable for a failure to perform its obligations resulting from an event of force majeure within the meaning of Article 1218 of the French Civil Code (natural disaster, state of war, terrorist attack, major infrastructure failure not attributable to the parties, administrative decision, a health pandemic imposing restrictions, etc.).

Performance of the obligations is suspended for the duration of the force majeure event. If it lasts more than 60 consecutive days, either party may terminate the contract without compensation.


19. Assignment and subcontracting

The Publisher may assign these Terms and the obligations arising from them to a third party (acquisition, merger, restructuring), provided it notifies the User 30 days in advance. The User may then close their account free of charge.

The Publisher may subcontract all or part of the technical services (hosting, payment, analytics, monitoring) to carefully chosen processors, under a DPA (GDPR data processing agreement) (see Privacy policy §3).

The User may not assign their account or the associated rights to a third party.


20. Severability

Should any provision of the Terms be declared void, unlawful or unenforceable by a court decision, the remaining provisions remain fully applicable. The parties undertake to replace the invalidated provision with one equivalent in spirit and compliant with the law.


21. Governing law and jurisdiction

21.1. Governing law

These Terms are governed by French law, excluding its conflict-of-laws rules.

21.2. Prior mediation

In the event of a dispute, the User is invited to contact the Publisher first at contact@premeets.com in order to seek an amicable solution. Failing agreement within 60 days, the dispute may be referred to a consumer mediator, in accordance with Articles L.612-1 et seq. of the French Consumer Code.

21.3. European online dispute resolution platform

Users residing in the European Union may also use the ODR platform:

https://ec.europa.eu/consumers/odr

21.4. Competent courts

Failing an amicable or mediated resolution, and subject to the mandatory rules protecting consumers:

  • For disputes between the Publisher and a consumer User: the courts having jurisdiction under the rules of the French Consumer Code and the Code of Civil Procedure
  • For disputes between the Publisher and a User acting for professional purposes: the courts of the district of the Publisher’s registered office, including in the event of a warranty claim or multiple defendants

  • Publisher: Premeets SAS - simplified joint-stock company
  • Share capital: €2,300
  • Registered office: 7 avenue des Pépinières, 49240 Avrillé, France
  • Trade and Companies Register: Angers - 927 958 975
  • Database host: Supabase Inc., 970 Toa Payoh North #07-04, Singapore 318992
  • Application host (mobile): Apple Inc. (App Store), Google LLC (Play Store)
  • Main processors: RevenueCat (payments), Sentry (monitoring), Google Cloud Platform (Maps & Places), Firebase Cloud Messaging (push)

23. Contact

Subject Address
User support contact@premeets.com
Complaints / disputes contact@premeets.com
Personal data / GDPR contact@premeets.com
Security (vulnerability, compromise) contact@premeets.com
Judicial requisitions contact@premeets.com
Appeals against a sanction contact@premeets.com
Post Premeets SAS, 7 avenue des Pépinières, 49240 Avrillé, France

The User acknowledges having read these Terms in full before ticking the acceptance box during registration, and declares that they accept all their provisions without reservation.