MeetPly
Back to legal documents

COOKIE NOTICE

Effective from 2026.09.25.

Contents

1. Introduction

This Notice provides information about the cookies used on the meetply.com website operated by MeetPly (Provider: SolvePly Kft.), on the public booking interface built on it and on the admin/platform interfaces, in accordance with the GDPR and with Article 5(3) of the Directive on privacy and electronic communications (2002/58/EC, ePrivacy). This Notice is a supplement to the Privacy Notice and its terms are to be interpreted accordingly – with the difference that here the Visitor means exclusively the person visiting the meetply.com website, the public booking interface or the admin/platform interface.

Exception – Section 4.4, which provides transparency information about the booking interface embedded into the Subscriber's own website; there – in the manner detailed in Section 4.4 – the Provider does not place any cookie on the End User's device.

2. Details of the controller

ItemValue
NameSolvePly Kft.
Company registration number08-09-038874
Tax number33119083-2-08
EU VAT numberHU33119083
Registered seat / mailing address9019 Győr, Szent László út 172., Hungary
E-mailinfo@meetply.com
Websitehttps://meetply.com

A small text file that the website places on the Visitor's device – to ensure the operation of the website, to improve the user experience or for statistical purposes. In some cases the browser also uses other, cookie-like storage (e.g. localStorage) for a similar purpose – one entry in Section 4.1 addresses this separately.

4. The cookies used

4.1. Necessary (technical) cookies – the law does not require prior consent for these, because without them the Service cannot be used, or cannot be used securely.

CookiePurposeLegal basisRetention period
admin_sessionMaintaining the logged-in state on the admin (workspace) interfaceArticle 6(1)(f) GDPR15 minutes
admin_refreshRenewing the session without logging in againArticle 6(1)(f) GDPR7 days
ory_kratos_sessionSession cookie of the identity management component performing login, registration, password reset and e-mail confirmationArticle 6(1)(f) GDPRUntil the session expires, at most 24 hours
csrf_token…Protection of the login, registration and password reset forms against cross-site request forgery (CSRF)Article 6(1)(f) GDPRUntil the process is completed
platform_sessionIdentification of the staff member logged in to the operator (internal) interfaceArticle 6(1)(f) GDPR15 minutes
platform_refreshRenewing the sessionArticle 6(1)(f) GDPR7 days
meetply:cookie-consent (not a cookie, but a localStorage entry)Remembering the category choice made on the cookie settings bar, so that we do not have to ask you again on every page loadePrivacy Article 5(3) – strictly necessary for a service expressly requested by the Visitor (for operating the consent management mechanism); not subject to GDPR consent (Opinion 04/2012 of the Article 29 Data Protection Working Party, EDPB Guidelines 2/2023)At most 12 months, after which the cookie settings bar asks you again

Uniform legal basis for the login/security cookies. The workspace user using the admin interface (owner, administrator, staff member) acts on behalf of the Subscriber, but is typically not personally the contracting party — these cookies therefore uniformly rely on Article 6(1)(f) GDPR — legitimate interest — rather than on the performance of a contract. The platform_session/platform_refresh cookies rely on the same basis, but arise exclusively for the Provider's own staff members — they act not on behalf of the Subscriber but on behalf of the Provider, on the basis of an employment relationship. The meetply:cookie-consent entry contains the fact that a decision was made, the enabled or disabled state of the three categories (under Sections 4.1–4.3), the version number of the category set and the time of the decision; it does not contain data identifying you personally, and we do not send it to our server – it remains exclusively on your device.

Attributes. The above login and security cookies are first-party cookies, with the HttpOnly, SameSite=Lax, path=/ settings and, over HTTPS, with the Secure flag. They are not accessible to third parties and do not serve profiling, advertising data collection or cross-site tracking.

Other storage. Apart from the above cookies, the admin and platform interfaces do not store any data on the Visitor's device; on the public booking interface and on meetply.com, only the meetply:cookie-consent entry above is placed in the browser's storage.

4.2. Analytics cookies – meetply.com and the public booking interface currently do not use any analytics (e.g. traffic measurement) cookie or measurement script; the analytics category of the cookie settings bar is reserved for future introduction.

4.3. Marketing cookies – meetply.com and the public booking interface currently do not use any advertising or remarketing cookie; the marketing category of the cookie settings bar is reserved for future introduction (e.g. for a newsletter subscription interface).

An analytics or marketing cookie may be placed exclusively with the Visitor's prior, express consent, with the two-step guarantee described in Section 5.5: before activating a new tool, the Provider asks every Visitor for consent again, and publishes this Notice in a new version, supplemented with the details of the specific cookie(s) (legal basis, retention period).

4.4. Cookies placed on the Subscriber's website by the embeddable booking interface

This Section does not relate to meetply.com, but to the embeddable booking interface (widget) that the Subscriber may place on its own domain so that the End User can book an appointment there.

The embeddable booking interface does not place any cookie on the End User's device, neither on behalf of the Subscriber nor on behalf of the Provider, and does not store data on the End User's device in any other way either – such as in localStorage or sessionStorage storage. The booking process keeps the necessary temporary state (e.g. holding the selected appointment for a short time) exclusively on the Provider's server, not in the End User's browser. Consequently, in connection with this Section, the Subscriber has no own cookie information obligation under the DPA on account of the embedded interface either – the Subscriber remains responsible for the other cookies placed on its own website.

5.1. No prior consent is required for the necessary cookies – including the meetply:cookie-consent entry under Section 4.1.

5.2. Analytics and marketing cookies are placed exclusively with the Visitor's prior, express consent, through the cookie settings bar and the related settings window ("Cookie settings"). The cookie settings bar appears both on the meetply.com website and on the public booking interface. The decision is stored in the browser's storage, per interface (limited to the web address of the server), and the bar may therefore ask you on both interfaces.

5.3. Consent may be withdrawn at any time by reopening the cookie settings interface – using the "Cookie settings" button in the footer of the meetply.com website – or, on any interface, by deleting the meetply:cookie-consent entry stored in the browser; after the latter, the cookie settings bar appears again and you can decide again.

5.4. Refusal or withdrawal does not restrict the basic functions of the website.

5.5. Consent given earlier never silently carries over to a new, not yet known purpose. The category set has a version number, which is also included in the decision stored in your browser. The Provider increments this version number if it introduces a new category, or if the actual content of an existing category changes materially – for example if a measurement script that actually loads is placed behind the analytics toggle. In the event of a version mismatch, the previously stored decision ceases to be valid: the non-necessary categories automatically revert to the disabled state and the cookie settings bar appears again so that you can decide again. The Provider starts actual data collection for measurement or advertising purposes only after (a) it has incremented the version number and has thus asked every Visitor for consent again, and (b) it has published this Notice in a new version – naming the cookie or stored entry actually placed in the category concerned, with its name, purpose and lifetime. Both must take place before the start of data collection, not after.

6. Managing cookies in the browser

The Visitor may restrict or prohibit cookies in the settings of their browser, or delete them; guidance is available on the official help pages of the browsers. A complete prohibition may hinder the operation of certain functions – since the cookies we use are necessary for logging in, if they are disabled it is not possible to log in to the admin/platform interface. The public booking interface works without cookies as well: an appointment can be booked without enabling cookies.

Your category choice made on meetply.com can be modified at any time, just as easily as you made it: by clicking the "Cookie settings" button in the footer of the website, the settings window opens again and the toggles can be changed. On the public booking interface, the choice can be reset by deleting the meetply:cookie-consent entry stored in the browser (Section 5.3).

7. Rights of the data subject

In connection with the data processed by means of cookies, the Visitor is entitled to the rights set out in Section 7 of the Privacy Notice, at the contact details under Section 2.

8. Amendment of the Notice

The Provider may amend the Notice unilaterally, in particular when the set of cookies changes – in the order described in Section 5.5. The version in force is available on the meetply.com website.

9. Governing language

This Notice was drafted in Hungarian, and the Hungarian-language version is the authoritative text. The Provider also publishes this Notice in English and in German; those versions are provided for information purposes only, to assist Visitors who do not speak Hungarian. In the event of any discrepancy or difference of interpretation between the Hungarian version and a translation, the Hungarian version prevails.