1. Who is responsible for this website
ADCOMM CENTURY, S.L. is the data controller for the personal data processed through cookies and equivalent technologies on this site.
- Legal name: ADCOMM CENTURY, S.L.
- Spanish Tax ID (NIF): B-86414786 (VAT: ESB86414786)
- Registered address: C/ Telegrafía 1, Bajo E, 28044 Madrid, Spain
- Contact email: info@adcommcentury.com
This policy covers cookies and the storage of information on your device only. The personal data you provide when registering for a specific congress is processed by the organizer of that congress, which sets out the details in the privacy policy of the event itself.
2. What cookies are
A cookie is a small text file that a website downloads onto the terminal equipment of the person visiting it — computer, tablet or phone — and which that same website can later access to retrieve the stored information.
Article 22.2 of Spanish Act 34/2002 on information society services and electronic commerce (LSSI-CE) applies the same legal regime to any other technology that stores information on a device or accesses information already stored there: local storage (localStorage and sessionStorage), tracking pixels, device identifiers or fingerprinting techniques. For convenience, this policy refers to all of them as "cookies", and every one of them is listed in section 4.
Cookies are usually classified as follows:
- By who manages them: first-party (set by the site owner) or third-party (set by another entity).
- By duration: session cookies (deleted when the browser closes) or persistent cookies (kept for a set period).
- By purpose: technical or strictly necessary, preference or personalisation, analytics or audience measurement, and behavioural advertising.
3. Which cookies this site uses, and which it does not
This site uses strictly necessary technical cookies only: those required to authenticate users, keep sessions alive, ensure security, remember your chosen language, and allow the payment process to be completed securely.
We do not use, directly or through third parties:
- analytics, statistics or audience measurement cookies;
- advertising or behavioural advertising cookies;
- profiling or cross-site tracking cookies;
- social media plugins or fingerprinting techniques.
Nor do we sell, transfer or otherwise make available to third parties any information obtained through cookies for advertising or profiling purposes.
For that reason, this site does not display a cookie consent banner. Article 22.2 LSSI-CE exempts from prior consent those cookies that are strictly necessary to provide a service expressly requested by the user. According to the Spanish Data Protection Agency's Guidance on the use of cookies, asking for consent to cookies that will be installed in any event would amount to apparent consent and could be misleading. Section 7 describes the consent and rejection mechanism that will apply should any non-exempt cookie be introduced in the future.
4. Detailed list of cookies
4.1 First-party cookies
-
sb-<project-reference>-auth-token(may be split into…-auth-token.0,…-auth-token.1)
Purpose: keep the person signed in to the private area (organizer dashboard or administration) authenticated, so that credentials do not have to be entered on every page.
Type: technical, authentication. First-party, managed through the authentication service of our database provider, which acts as a processor.
Duration: persistent. Renewed automatically while the session remains active and deleted on sign-out. -
sb-<project-reference>-auth-token-code-verifier
Purpose: securely complete the credential exchange during sign-in (PKCE protocol), preventing interception of the authorisation code.
Type: technical, security.
Duration: temporary, a few minutes. Deleted as soon as authentication finishes. -
portal_session
Purpose: allow a registered attendee to view and manage their registration from the access link received by email, without creating a password. The cookie is cryptographically signed and server-only (HttpOnly).
Type: technical, authentication and security.
Duration: 8 hours. Deleted on sign-out from the portal. -
register_locale_<event-identifier>
Purpose: remember whether you chose to view that congress's registration form in Spanish or in English, so you are not asked again.
Type: technical, interface personalisation.
Duration: 12 months. -
NEXT_LOCALE
Purpose: remember the language selected for the site's general interface.
Type: technical, interface personalisation.
Duration: 12 months. -
profile_locale_synced
Purpose: record that the dashboard language has already been aligned with the preference saved in your profile, avoiding repeated redirects on access.
Type: technical, functional.
Duration: 12 months.
4.2 Local storage (technology equivalent to cookies)
sinkro_register_draft_<event-identifier>— stored insessionStorage, not as a cookie
Purpose: preserve the draft of the registration form — current step, selected tickets and data already entered — so it is not lost if you switch language, reload the page or go back.
Type: technical; falls within the "user-input" category exempt from consent.
Duration: deleted automatically when the browser tab is closed and, in any case, expires after 24 hours. It is never transmitted to third parties nor stored on our servers. Acceptance of the general terms and conditions is not saved in this draft: it must always be given expressly before submitting the registration.
4.3 Third-party cookies
The following cookies are set by Stripe, our payment service provider (Stripe Payments Europe, Ltd., Ireland), and only when you reach the card payment step. They are necessary to process the charge and to prevent fraud, an obligation imposed on payment providers by law.
-
__stripe_mid
Purpose: persistently identify the browser in order to detect and prevent fraudulent transactions.
Duration: 12 months. -
__stripe_sid
Purpose: link actions performed within the same payment session, for fraud prevention purposes.
Duration: 30 minutes. -
m(set on them.stripe.comdomain)
Purpose: fraud risk assessment during payment processing.
Duration: up to 24 months.
Stripe acts as a processor when executing the payment and as an independent controller as regards fraud prevention and compliance with its own legal obligations. You can read its cookie policy at stripe.com/legal/cookies-policy and its privacy policy at stripe.com/privacy.
No third-party resources, tags or scripts are loaded on this site for advertising, statistical or measurement purposes.
5. Legal bases for the processing
Storing and reading cookies. All the cookies and equivalent technologies described above are exempt from the prior consent requirement under the second paragraph of Article 22.2 LSSI-CE, as they are strictly necessary to provide an information society service expressly requested by the user. They fall within the user-input, authentication or identification, security, and interface personalisation categories recognised by the Spanish Data Protection Agency.
Processing of the associated personal data. This relies on the following legal bases under Article 6(1) of Regulation (EU) 2016/679 (GDPR), read together with Spanish Organic Act 3/2018 (LOPDGDD):
- Performance of a contract or pre-contractual measures (Art. 6(1)(b) GDPR): keeping the session open, processing the registration and completing the payment.
- Legitimate interests (Art. 6(1)(f) GDPR): ensuring the security of the platform and preventing payment fraud, a legitimate interest expressly recognised in recitals 47 and 49 GDPR. This interest has been balanced against your rights and freedoms, with an outcome favourable to the processing given its minimal, indispensable and non-intrusive nature.
- Compliance with a legal obligation (Art. 6(1)(c) GDPR): fraud prevention and anti-money-laundering obligations borne by the payment service provider.
Cookies are not used to process special categories of data, nor to make automated decisions producing legal or similarly significant effects, nor to build profiles.
6. Recipients and international transfers
The information associated with these cookies is processed by the technology providers essential to delivering the service — hosting and database, authentication, transactional email and payment processing — which act as processors under a contract compliant with Article 28 GDPR and may not use the data for their own purposes.
Where any of these providers processes data outside the European Economic Area, the transfer relies on a European Commission adequacy decision or, failing that, on Standard Contractual Clauses together with any supplementary measures required. You may request information about these safeguards at the contact address given in section 1.
7. Prior consent and rejection mechanism
This site currently sets no cookie subject to consent, which is why no notice is displayed. Should any non-exempt cookie be introduced in the future — analytics, advanced personalisation or advertising — a consent notice will be displayed before it is installed, meeting the criteria of the Spanish Data Protection Agency and EDPB Guidelines 03/2022 on deceptive design patterns:
- No non-exempt cookie will be installed before you give consent through a clear affirmative action.
- A first layer stating the controller's identity, the purpose of the cookies, the types of data collected and whether third parties are involved, plus a link to this policy.
- A reject button equivalent to the accept button: "Accept all" and "Reject all" will appear in that same first layer, at the same visual level and with identical size, format, colour, contrast and legibility. Rejecting will never require more clicks or more effort than accepting.
- A settings panel by category, with every non-exempt category switched off by default and no pre-ticked boxes.
- Neither scrolling, nor continuing to browse, nor closing the notice will be treated as acceptance: closing the notice means rejection.
- No cookie walls: access to content will not be conditional on acceptance.
- Proof of consent: a record will be kept of when and on what terms consent was given, and consent will be requested again at appropriate intervals and in any case after 24 months.
- A permanent "Cookie preferences" link available at all times to change or withdraw consent as easily as it was given.
8. How to delete or block cookies
Even though these cookies are exempt from consent, you can delete them or prevent them from being set at any time:
- By signing out of the private area or the attendee portal, which deletes the authentication cookies.
- By closing the browser tab, which clears the form draft held in
sessionStorage. - From your browser settings, where you can view, delete and block cookies from this and any other site:
- By browsing in private or incognito mode, so that cookies are deleted when the window closes.
9. What happens if you block them
Because these are strictly necessary cookies, blocking or deleting them will prevent the site from working normally: you will not be able to sign in or stay signed in, the attendee portal will no longer recognise you, your selected language will be lost, and card payments may be declined by the payment provider's anti-fraud systems.
10. Your rights
You may exercise your rights of access, rectification, erasure, objection, restriction of processing and portability, and withdraw consent where consent is the legal basis, by writing to the contact address given in section 1 and proving your identity. We will reply within one month, extendable on the terms set out in Article 12(3) GDPR.
If you believe the processing does not comply with the applicable rules, you may lodge a complaint with the Spanish Data Protection Agency (C/ Jorge Juan 6, 28001 Madrid — www.aepd.es), without prejudice to contacting us first.
11. Updates to this policy
This policy will be reviewed whenever the cookies used, the applicable law or the criteria of the Spanish Data Protection Agency change. We recommend consulting it from time to time.
Last updated: 3 August 2026.