Privacy and data processing
This page explains what data processing may happen when you use this website and when external services are loaded.
Last updated: 2026-10-21
What this notice covers
- This notice covers this website and the third-party services integrated in it.
- The exact data that each provider receives depends on your interaction and your cookie preferences.
- When you follow external links, the destination site handles your data under its own policies.
Legal basis in short
- Essential technical processing is based on legitimate interest to operate the site securely.
- Optional analytics and marketing scripts are loaded only after your consent in cookie settings.
- You can change your choices any time from the footer's Cookie settings link.
Third-party services used
These providers may receive technical metadata (for example IP address, browser details, and interaction events) when enabled or used.
Scheduling
- Google Calendar (calendar.google.com, calendar.app.google): used on the contact pages to book calls.
- Cloudflare Turnstile (challenges.cloudflare.com): spam protection. It loads only when you pick a time and the booking form appears, or when you click "Show e-mail address" on the contact page, not when you open the page. Your browser sends Cloudflare technical data (such as IP address and browser details) to run the check, and we send Cloudflare the check token and your IP address to verify it. It is not used for tracking and does not depend on cookie consent.
- What you enter in the booking form (name, email, company, message, how you heard about us) is stored only in the Google Workspace calendar event of the call, which Google processes for us. We do not keep it in a database or in logs.
- To limit abuse we count booking attempts per email address and per IP address. Only a keyed hash (HMAC-SHA256 with a secret salt) of them is stored, never the plain values, in our AWS DynamoDB table, and each counter is deleted automatically when its time window ends (IP: about one hour, email: about seven days).
- Our contact e-mail address is not in the page code. When you click "Show e-mail address" on the contact page, the Turnstile check runs and our AWS Lambda returns the address. The IP address is only used for the check and for a per-IP counter (stored as a keyed hash, deleted after about one hour), to limit abuse.
Newsletter / waitlist signup
- AWS Lambda Function URL (lambda-url.eu-central-1.on.aws): used for the training waitlist signup form and for requesting the PDF edition of the State of AI Dev report. Email and first name are sent in a JSON request when you subscribe.
- Signup data is processed by a backend workflow operated by Letscode Solutions.
Analytics
- Google Analytics (googletagmanager.com): page view and usage analytics.
- Hotjar (static.hotjar.com): behavior analytics and session insights.
Measurement without consent
- If you decline analytics cookies, we still count page views in an anonymous, aggregated form. This is based on our legitimate interest in understanding how many people visit the site and where they come from.
- What we measure: the page path, the page language, the domain you came from (not the full address) and campaign (UTM) parameters if the link had them. We also record how far you scroll (25, 50, 75 and 90% of the page), how long the page was visible in your browser, a coarse device type (mobile, tablet or desktop), the browser family and your country. We also count a few key clicks (workshop buttons, Slack join, checkout redirect, report download, booking intent) with the button's position or topic.
- Nothing is stored on your device: no cookie, no localStorage and no sessionStorage. The visit ID that groups the pages of one visit lives only in the browser's memory and is a new random value on every page load.
- We do not store your IP address or your browser's User-Agent, and we do not pass them on: the server only derives the device type, browser family and country from them. Known bots are ignored. The data is sent to our own server endpoint (letscode.hu/collect), which forwards the page view to Google Analytics 4. Google acts as our data processor.
- These records are marked as collected without consent and cannot be linked to you or across visits. Choosing to accept analytics cookies in the cookie settings stops this measurement right away, with one exception described next.
- If you accept analytics cookies but your browser or an ad blocker prevents Google's analytics script from loading or working, we measure your visit in the same anonymous, cookieless way instead, so that it is counted only once and not by both. These records are marked as collected in a fallback mode. If you withdraw analytics consent, the rules for visitors who declined apply.
Marketing
- Google tag / Google Ads (googletagmanager.com): ad measurement and remarketing.
- Facebook Pixel (connect.facebook.net): marketing and campaign performance measurement.
- LinkedIn Insight Tag (snap.licdn.com): campaign and conversion measurement.
- If you accept marketing cookies, we also pass your booking intent (when you start booking a call) to Meta on the server side, through our own endpoint (letscode.hu/collect) and Meta's Conversions API. The purpose is advertising measurement. This works even if your browser blocks the Facebook Pixel, and Meta uses a shared event ID to count it once.
- What we forward: your IP address, your browser's User-Agent, Meta's own cookie identifiers (_fbp, _fbc, or the Facebook click ID from the link) and the event itself (booking intent, its value and topic, the page). We do not store the IP address or the User-Agent and we do not write them to logs; they only pass through our server to Meta. Nothing is sent to Meta this way if you have not accepted marketing cookies.
- If you subscribe while marketing cookies are accepted, your email address is also passed to Meta, only in hashed form (SHA-256, after trimming and lowercasing), for the same advertising measurement. The plain address is never sent to Meta, and our endpoint (letscode.hu/collect) neither stores nor logs it.
Embedded media
- YouTube embeds (youtube.com): conference talk videos.
- Vimeo embeds (player.vimeo.com): conference talk videos.
External links and profiles
- Sessionize links (sessionize.com): public conference sessions profile.
- Credly links (credly.com): public certification badges.
AI adoption quiz
- When completing the quiz, your email address and answers are stored.
- Data is forwarded to a Letscode Solutions AWS Lambda backend and used to send the aggregated benchmark report.
- The legal basis for processing is the explicit consent you give before submitting.
- We do not share data with third parties; it is used solely for producing and sending the report.
Cookie controls
You can accept all optional cookies or choose categories (analytics, marketing). Preferences are stored locally so your choice is remembered.
Questions
If you have questions about data processing on this site, please use the Contact page.
