Copyright © 2026 Cloud Native Bergen. All rights reserved.
Powered by Konf
We collect your information to organize conferences and manage speaker applications, using privacy-friendly analytics to improve our website. We're committed to protecting your data and never sell your personal information to third parties.
This policy explains what data we collect, how we use it, and your rights under GDPR. We only gather information necessary for conference operations, speaker coordination, and providing you with the best possible event experience.
Last updated: September 28, 2026
Cloud Native Days Norway is a conference organizer based in Bergen, Norway. This notice covers the personal data we process in connection with Cloud Native Day Bergen 2024.
We process your personal data based on the following legal grounds under GDPR:
Managing speaker applications, scheduling, and logistics
Sending updates about the conference, speaking arrangements, and travel
Sanity.io
Content management and database services (EU-based)
Shared platform infrastructure
Vercel.com
Website hosting, infrastructure, content delivery, file storage for uploaded attachments, and privacy-friendly analytics (Vercel Analytics & Speed Insights; cookie-less)
Some of our service providers may be located outside the EU/EEA. When we transfer your data internationally, we ensure appropriate safeguards are in place:
Standard Contractual Clauses (SCCs) with service providers
The following providers may process data outside the EU/EEA: Vercel.com (United States), Resend.com (United States), Slack (United States), WorkOS (AuthKit) (United States). We rely on Standard Contractual Clauses and other safeguards required by GDPR for such transfers.
WorkOS processes workshop authentication data in the United States. We rely on:
We retain personal data for different periods depending on its purpose and legal requirements. Where the table says not deleted automatically, nothing in our systems removes that data on a schedule: it stays until you ask us to delete it, or until the conference deletes its data.
| Data Type | Retention Period | Legal Basis & Reason |
|---|---|---|
| Active Speaker Profiles | Not deleted automatically Kept until you ask us to delete it or the conference deletes its data | Legitimate Interest: Future conference invitations and speaker outreach |
| Archived Speaker Profiles |
You have comprehensive rights regarding your personal data. Here’s what you can do:
Request a copy of all personal data we hold about you, including how it’s processed.
Correct any inaccurate or incomplete personal data we have about you.
We implement comprehensive security measures to protect your personal data from unauthorized access, alteration, disclosure, or destruction:
All data is encrypted in transit (HTTPS/TLS) and at rest using industry-standard encryption protocols.
Role-based access controls with organizer-only admin functions and multi-factor authentication.
Age Restriction: Our services are not intended for individuals under 13 years of age. We do not knowingly collect personal data from children under 13. If you become aware that a child has provided us with personal data, please contact us immediately and we will delete it.
We may update this privacy policy from time to time. When we make changes, we will:
Update the date
Update the “Last updated” date at the top of this policy
Notify active users
Send email notifications about significant changes
Request renewed consent
For significant changes, we may request renewed consent where required by law
For privacy-related questions:
📧contact@cloudnativedays.noSubject line: Please include “Privacy Policy” in your email subject
Response time: We will respond within 30 days and may request identity verification for security purposes
This privacy policy complies with the EU General Data Protection Regulation (GDPR) and Norwegian data protection laws.
Purpose: Keeping speakers and organizers informed of proposal and conference activity. Legal Basis: Legitimate interest in conference coordination. These notifications are automatically deleted 90 days after they are created, except an unread new-message notification, which is kept until you read it.
Visibility: Messages in a proposal thread are visible to that proposal's speakers and all conference organizers; messages in a general thread are visible to their author and all conference organizers; messages in a sponsor portal thread are visible to that sponsor's contacts (via the portal link) and all conference organizers. Purpose: Coordinating proposals, sponsorships and conference logistics. Legal Basis: Legitimate interest in conference coordination. Messages and conversations are retained for 24 months after the conference ends, then permanently deleted.
Legal Basis: Legitimate interest for event documentation and community engagement. You can untag yourself at any time through your speaker profile or by contacting us.
Legal Basis: Legitimate interest in promoting the conference and its programme.
Legal Basis: Legitimate interest in promoting the conference and its programme. The accounts we tag are the links you gave us for your public speaker profile and for promotional material, and tagging is a use of those same links. Because it is a more visible use than displaying them, you can object to it on its own with the checkbox above, without changing anything else about your profile.
If you ask us for a letter of invitation to support a visa application, you send us your passport details and an organizer enters them to produce the letter.
These are never stored in our systems and never written to our logs. They exist only for as long as it takes to render your letter, and the letter itself is not stored either.
We keep this so we can confirm to you — or to a consulate that contacts us — that a specific letter is genuine.
When an organizer invites someone to join the organizing team, they enter that person's email address — so we hold an address belonging to someone who may never have used this site. We use it for one thing: to send the invitation and to check who is accepting it.
Nothing happens. An invitation you never accept expires by itself, and once it has expired the whole record — including your email address — is deleted by a daily clean-up. No account and no profile is ever created for you. An organizer can also withdraw an invitation, which stops it working immediately; the record is then removed on the same clean-up once its original expiry date passes. Accepted invitations are kept, because they record who was given access to the event and when.
An invitation on its own grants nothing, and forwarding one passes nothing on: accepting requires signing in with a link we email to the invited address, which is also the moment a speaker profile is created or matched. Accepting never changes the name, email or login details on an existing profile.
A speaker on a proposal, or an organizer, can invite someone to present with them. They type that person's email address and, if they choose, their name — so we hold a record about someone who may never have visited this site and has no account here. We use it to send the invitation, to send a reminder if it goes unanswered, and to record the answer.
No account and no profile is created for you. The link stops working after 14 days. Ninety days after you decline, or after the link lapses unanswered, a daily clean-up deletes the whole record — your email address, your name and any reason you gave for declining. If an organizer later adds you to the proposal directly (see below), the invitation is marked cancelled and is removed on the same clean-up, ninety days after its original expiry date. An invitation you accepted is kept, because it records who asked you to present and when — and it stays kept even if you are later taken off the proposal.
Accepting requires signing in, and that is the moment a speaker profile is created or matched; from then on the Speaker Information section applies. You do not need an account to ask about an invitation: email contact@cloudnativedays.no from the invited address and we will tell you what we hold and delete the record if you ask.
An organizer can also put a co-speaker on a proposal without an invitation, by creating a speaker profile for that person directly. This is meant for someone who will not act on an invitation. The organizer types the person's name and email address, and may add a professional title and a biography. An email address is required, so we can always tell the person they were added. The person named does not take part in this and learns of it from that email.
We send the address the organizer entered one email saying who added you and to which proposal, with the conference contact address to reply to if it is wrong. The profile cannot be created without an address, so this email is always sent to it. If the send fails, the organizer is told to reach you another way.
The profile is treated like any other speaker profile: organizers and the proposal's other speakers can see it, and if the talk is accepted and published, the name, title and biography appear in the public programme. It is kept as long as any other speaker profile (see section 7) and is not removed on its own. To see, correct or delete it, email contact@cloudnativedays.no; you do not need an account.
If you are a speaker and your conference ticket was bought under an email address we do not already hold — a work address, or one an employer used — your ticket looks unclaimed to the organizers. An organizer can then search this event's tickets and record the address yours was bought under on your speaker profile. They do this from their own pages, and you are not asked first.
You can sign in with that address from then on. It becomes a full login identity for your speaker profile, exactly like an address you signed in with yourself — because whoever bought the ticket had to receive it at that address. We only accept an address a ticket for this event was actually registered to, and we refuse it if it already belongs to another account.
An organizer can unlink it again: the address and the record of who added it are removed, and the sign-in goes with them. If the address is wrong, or you do not want it to sign in to your profile, ask the organizers to unlink it or email contact@cloudnativedays.no. Until it is unlinked it is kept as part of your speaker profile (see section 7), and it is deleted with the profile if you ask us to erase it.
Purpose & Legal Basis: Platform administration and service provisioning (contract performance / legitimate interest). This data describes the organization's account and is retained for as long as the organization uses the platform. The plan tier, feature configuration and administrative notes are visible only to platform operators.
A Template's version history, including who saved each version, is visible to the organizers of that organization, so a version can be traced to the person who made it. It is kept until an organizer deletes the Template, which removes every version.
Purpose: Volunteer coordination and event logistics. Legal basis: Legitimate interests for coordination and operations; explicit consent for special category data (dietary restrictions).
See your GDPR rights in section 8 (Your Rights Under GDPR).
Handling travel reimbursements and expense management
Registration management, access control, and sharing participant lists with venue partners for security
Displaying speaker profiles and bios on the conference website (with consent)
Privacy-friendly analytics by PostHog (EU): anonymous by default, one optional cookie if you accept it.
Analyzing feedback to improve future conferences
We record conference sessions and may publish talks on our official online video channels/platforms. For speakers, the legal basis is our speaking agreement and our legitimate interest in documenting and sharing the event. For attendees, our legitimate interests allow incidental capture; we provide no‑filming areas and will honor reasonable requests for removal or blurring where feasible.
Shared platform infrastructure • Location: United States • Protected by Standard Contractual Clauses
Resend.com
Email delivery for conference communications Sent through this organizer’s own Resend account.
Shared platform infrastructure • Location: United States • Protected by Standard Contractual Clauses
Checkin.no
Ticket sales, ticket management and event check-in
Selected by the event organizer
PostHog Inc. (EU Cloud)
Website analytics, hosted in Frankfurt (EU): pageviews, clicks on marked buttons, arrival campaign parameters, outbound link URLs, host and conference; anonymous by default (a daily-changing hash, no IP retained), one optional cookie if you accept it
Selected by the event organizer
Slack
Internal organizer notifications for operations (e.g., speaker proposal updates)
Selected by the event organizer • Location: United States • Protected by Standard Contractual Clauses
GitHub/LinkedIn
Authentication for the Call for Papers (when you choose to sign in)
Shared platform infrastructure
WorkOS (AuthKit)
User authentication and identity management for workshop signups (email, name, user ID, authentication sessions)
Shared platform infrastructure • Location: United States • Protected by Standard Contractual Clauses
• Participant registration lists - Names and basic contact information shared for venue access control and security
• Speaker information - Names and session details for event coordination and technical setup
• Logistics coordination - Information necessary for event management and facility access
Legal Basis: Legitimate interest for event security, access control, and venue management. Data sharing limited to information necessary for venue operations.
• Sponsors for networking opportunities (only if you opt in during registration)
• Photography/videography vendors for event documentation (with prior notice)
• Catering and hospitality providers for dietary requirements and service coordination
We never sell your personal data to third parties.
| Indefinitely With option to request removal |
| Public Interest Archiving (Art. 89): Historical documentation of technology community events and speakers.Legitimate Interest: Maintaining public archives of past conferences for community and historical value. |
| Banking & Financial Information | At least 5 years after payment; not deleted automatically after that Bank details on an unpaid request are deleted if you ask for erasure | Legal Obligation: Norwegian accounting and tax law requirements for financial records |
| Travel Receipts & Documentation | At least 5 years after reimbursement; not deleted automatically after that | Legal Obligation: Financial record keeping and audit requirements |
| Email Communications | Not stored by this site We keep no copy of sent emails; the email provider listed in section 5 holds delivery records under its own terms | Legitimate Interest: Conference documentation and operational continuity |
| In-App Notifications (Content, recipient, acting user, related proposal, read status) | 90 days after creation Except an unread new-message notification, which is kept until you read it | Legitimate Interest: Keeping speakers and organizers informed of proposal and conference activity |
| Reminder Delivery Log (Speaker reference, reminder type, send count and timestamps) | Not deleted automatically Deleted with your profile if you ask for erasure | Legitimate Interest: Operational bookkeeping so a scheduled speaker reminder is not delivered twice |
| Ticket Address Links (An address linked from a ticket, the ticket it came from, and the organizer who linked it) | Not deleted automatically Removed as soon as an organizer unlinks the address; deleted with your profile if you ask for erasure | Legitimate Interest: Matching a ticket to the right speaker, and keeping a trail so a wrong link can be traced and undone |
| Messages (Content, author, timestamps, conversation preferences) | 24 months after conference ends | Legitimate Interest: Speaker↔organizer coordination of proposals and conference logistics |
| Co-Speaker Invitations (Invited email and name, status, decline reason, timestamps) | 90 days after the invitation is resolved Declined invitations are deleted 90 days after you declined; withdrawn and expired ones 90 days after their original expiry date. An invitation you accepted is kept. The link itself stops working after 14 days | Legitimate Interest: Recording who was asked to present a proposal and what they answered |
| Attendee & Participant Data (Registration, check-in, preferences) | Not deleted automatically | Legitimate Interest: Event management, security, future event planning, and attendee experience improvement |
| Workshop Registration Data (Signups, experience levels, system preferences) | Not deleted automatically Cancelling moves you to the waitlist; the record is deleted when a workshop organizer removes it or you ask us to | Legitimate Interest: Workshop planning and speaker preparation for future events, capacity planning, and participant experience improvement |
| Marketing Consent & Preferences | Until you withdraw it The record of when you gave and withdrew consent stays on your profile; not deleted automatically | Consent: Active consent management and preference tracking |
| Volunteer Applications & Information (Contact details, availability, preferences, assignments) | Not deleted automatically Deleted when an organizer removes your application or you ask us to | Legitimate Interest: Volunteer coordination, event operations, and safety management. Consent for special category data (dietary restrictions) |
| WorkOS Authentication Data (User ID, email, name, authentication sessions) | Not deleted automatically | Legitimate Interest: User account management, audit trail for capacity management, and preventing duplicate registrations. Contract Performance: Authentication required to access registered workshops |
We maintain archived versions of conference programs with speaker information for historical and community purposes. This information was previously published with consent and serves the public interest of documenting our technology community’s history. You can request removal of your information from archives at any time by contacting us.
Request deletion of your personal data in certain circumstances (right to be forgotten).
Limit how we use your personal data in certain situations while keeping it stored.
Receive your personal data in a machine-readable format to transfer to another service.
Object to processing based on legitimate interests or for marketing purposes. This includes the right to object to analytics based on our legitimate interests.
Remove yourself from event photos at any time. Once you untag yourself, the system prevents re-tagging you in that photo, permanently respecting your choice.
Where we process your data based on consent, you can withdraw that consent at any time. This won’t affect the lawfulness of processing before withdrawal.
Contact us at contact@cloudnativedays.no to exercise any of these rights. We will respond within 30 days and may request identity verification for security purposes.
Secure OAuth-based authentication through trusted providers (GitHub, LinkedIn).
Continuous security patches, system updates, and vulnerability monitoring.
We only collect and process data that is necessary for our stated purposes.
Regular privacy and security training for all organizers and team members.
Website analytics is provided by PostHog (EU Cloud, hosted in Frankfurt). It records page views, clicks on marked buttons, the campaign parameters you arrived with, outbound link URLs, and the site and conference you visited. Without your consent you are counted with a hash that changes daily and your IP address is not stored. If you accept, PostHog sets one cookie for one year, alongside its browser storage, so that your visits can be recognised as the same browser. Whichever you choose, the choice itself is kept in a small cookie for one year.
Your analytics choice: not available — analytics is not running in this browser (it may still be starting, or it is blocked), so there is nothing to change.
No advertising cookies: We do not use cookies for advertising or cross-site tracking. Our analytics are aggregated and, unless you accept the cookie above, anonymous.
localStorage: We use your browser’s localStorage to save personal bookmarks on your device. This isn’t sent to our servers.
Opt-out: Decline the cookie above (or in the bar shown on your first visit) to stay anonymous; you can also object to analytics by contacting us or using tools that block analytics requests. We will respect your choice.
If you believe we have not handled your personal data properly, you have the right to lodge a complaint with the data protection authority:
Norwegian Data Protection Authority (Datatilsynet)
Website: www.datatilsynet.no
Email: postkasse@datatilsynet.no