Privacy
How we handle your personal data when you buy a ticket, use proptechsummit.no and use our event tools.
Oslo Proptech Summit is organised by Proptech Norway AS (organisation number 923 190 198), the data controller for the personal data described here. Our registered address is Møllergata 6, 0179 Oslo, Norway. Questions? Contact us at [email protected].
Tickets are sold through Tickster, our ticketing provider (based in Sweden, within the EEA). To process your order, Tickster handles your name, email, billing details and, where you provide it, your company. We receive the information needed to manage your registration and admission. We use it to fulfil your purchase, send your ticket and practical event information, and meet our accounting obligations. Legal basis: performance of a contract, and a legal obligation to keep accounting records. See Tickster's own privacy policy for how it processes payment data.
On the programme page you can choose to have your personal schedule sent to you. If you enter your email address, we send it through Resend (our email provider). If you enter your phone number, we send it through Twilio (our SMS provider). We use your email or phone number only to send the message you asked for. We do not use it for marketing and do not keep it for that purpose. Legal basis: your request (consent).
If you hold a ticket and opt in, your name, title and company are included in an attendee list shared with other attendees roughly seven days before the event, to help you connect. The list excludes anyone who has not opted in or who has asked to be left out, and you can withdraw at any time by contacting us. Legal basis: your consent.
We collect anonymous usage statistics (page visits, approximate country, device type and time on page) to understand and improve the site. Your IP address is not stored for this. The badge generator is the one exception, and it is described below.
Depending on the activity, we rely on: performance of a contract (ticket purchases), your consent (the attendee list, getting your programme by email or SMS, LinkedIn sign-in), our legitimate interest in running and improving the event and the site, and legal obligations (keeping accounting records). You can withdraw consent at any time.
We use a small number of trusted providers who process data on our behalf: Tickster (ticketing and payment, Sweden/EEA), Resend (email), Twilio (SMS), Montage AS (the badge generator, Norway) and LinkedIn (only when you sign in or publish a badge). We do not sell your personal data.
Most processing takes place within the EU/EEA. Some providers (Resend, Twilio and LinkedIn) are based in the United States. Where data is transferred outside the EEA, it is protected by appropriate safeguards such as the EU Standard Contractual Clauses or the EU-US Data Privacy Framework.
We keep ticket and order data for as long as needed to run the event and to meet our legal and accounting obligations (Norwegian accounting law requires accounting records to be kept for several years). Email addresses and phone numbers entered to receive your programme are used only to send that message and are not kept afterwards for other purposes. The attendee list is kept until shortly after the event. Badge data is kept for the duration of the event and deleted within 90 days afterwards.
You have the right to access, correct or delete your data, to withdraw consent, and to object to processing. To exercise these rights, contact us at the address above. You may also lodge a complaint with the Norwegian Data Protection Authority (Datatilsynet).
On the badge page you can make a personal conference badge, download it and, if you want to, publish it on LinkedIn. The paragraphs below cover the whole tool.
The generator was built by Montage AS (organisation number 929 445 139), which also runs the LinkedIn app, "Badge Generator by Montage", that you give access to if you sign in.Proptech Norway AS, the organiser, is responsible for this campaign and for the usage statistics described below. Ask us at[email protected], or Montage at [email protected].
The photo you upload, and any company logo, are processedentirely in your own browser. So is the optional AI background removal, which runs on your own machine. The picture isnever uploaded to or stored on our servers, and the file you download is put together in the browser. There is one exception: if you publish the badge straight to LinkedIn, the finished badge image passes through our server on its way there. That happens only in the moment you press Publish, and the image is not kept.
To understand how the campaign is doing, the organiser storespseudonymous usage statistics: a random identifier that is not your name, approximate country, device type, how long you stayed on the page and which page you came from. When you complete a badge (download or share it), we also store thename and company written on the badge, so the organiser can see who is taking part in the campaign.Legal basis: our legitimate interest in running and measuring the campaign, with this notice; the name and company you type are given by you for exactly that purpose.
Your IP address is used to limit abuse of the service, and for that it is stored only as an irreversible hash that cannot be turned back into the address. In addition, this organiser keeps aninternal visit log in which the IP address is stored in the clear, so that individual visits can be reviewed (time, IP address, approximate country and time on page). Stored addresses are removed automatically 90 days after the visit; the statistics built from them remain, without the address.
You can use the generator without signing in at all. If you do sign in with LinkedIn, we fetch your name and profile photofrom LinkedIn to pre-fill your badge, and we are able to publish the finished post on your profile. We publishonly when you press Publish and confirm: never automatically, and never anything other than the post you have seen in the preview.
We ask for as little access as possible: name, profile photo and the right to share posts. LinkedIn shows its own description of that sharing permission on the consent screen, and that description also mentions editing and deleting posts. It is LinkedIn's combined label for the permission; the generator creates posts and does nothing else.
Your sign-in is kept in an encrypted cookie in your own browser (AES-256-GCM, see the cookie table below), which is sent only to the badge service's own API and lasts up to 60 days. During the sign-in itself a ten-minute security cookie is set as well. Neither your access token nor your profile photo is stored on our servers. Legal basis: your consent, given when you sign in.
You can sign out with one click in the generator, which deletes the cookie immediately. To remove the app's access from your LinkedIn account altogether, do it in your LinkedIn settings. If you do nothing, the access expires by itself. LinkedIn (Microsoft) is an independent controller of your LinkedIn account and of the post you publish there; transfers to the United States are covered by the EU-US Data Privacy Framework.
The statistics are stored by the organiser and deleted once the campaign is over and the purpose is met, and in any case no later than90 days after the event. The organiser can delete all of it at any time, and stored IP addresses go automatically on the 90-day schedule above. Your rights of access, correction and deletion apply here as they do everywhere else on this page.
Strictly necessary cookies, including the one that remembers your cookie choice, are always on. Analytics and marketing cookies are set only if you accept them, and you can change your choice any time:
Needed for the site to work and to remember your cookie choice. These are always on and do not require consent.
| Cookie | Provider | Purpose | Duration |
|---|---|---|---|
| cc_consent | Oslo Proptech Summit | Remembers your cookie consent choices so we do not ask again. | 6 months |
| badge_li_s | Oslo Proptech Summit | Holds your LinkedIn sign-in for the badge generator, encrypted, so we can fetch your name/photo and publish the post you approve. Set only if you sign in; removed when you sign out. | 60 days |
| badge_li_o | Oslo Proptech Summit | Short-lived security token (CSRF protection) during the LinkedIn sign-in redirect for the badge generator. | 10 minutes |
Help us understand how the site is used so we can improve it. Set only if you accept. Off by default.
| Cookie | Provider | Purpose | Duration |
|---|---|---|---|
| _ga | Google Analytics | Distinguishes unique visitors. | 2 years |
| _ga_* | Google Analytics | Persists session state for GA4. | 2 years |
| _clck | Microsoft Clarity | Persists the Clarity user ID and preferences for the site. | 1 year |
| _clsk | Microsoft Clarity | Connects multiple page views by one user into a single session. | 1 day |
| CLID | Microsoft Clarity (clarity.ms) | Identifies the first time Clarity saw a visitor. | 1 year |
| MUID, ANONCHK | Microsoft | User identification and verification used by Clarity. | Up to 1 year |
Let us measure whether our LinkedIn ads lead to ticket sales, and show the summit to people who have visited this site. Set only if you accept. Off by default.
| Cookie | Provider | Purpose | Duration |
|---|---|---|---|
| li_sugr | Browser identifier used to match ad views and site visits to a LinkedIn member. | 90 days | |
| UserMatchHistory | Syncs the LinkedIn Ads ID with the visitor for ad measurement. | 30 days | |
| AnalyticsSyncHistory | Remembers when a sync with the LinkedIn Insight service last happened. | 30 days | |
| bcookie, lidc, ln_or | Browser and routing identifiers LinkedIn sets alongside the Insight Tag. | Up to 1 year |
