Politique de confidentialité

What an organiser gives us

A name, an email address, and a password if one is used. If a workspace is created, its name. Nothing else is required to run an event.

Payment details are never held by Winglark. When payments are enabled they will be handled by a payment provider, and Winglark will hold only the record of what was bought.

What a guest list contains

Whatever the organiser puts in it: usually a name and an email address, sometimes a phone number, a company, a category, a table, a dietary note or an accessibility need.

The organiser decides what to collect. Winglark asks for the minimum needed to send an invitation and count an arrival.

A QR code carries an opaque token and nothing else — no name, no email, no event. A screenshot of one reveals nothing about the person holding it.

Photos and videos sent from an event’s QR code

Where an organiser switches on MomentFlow, guests can send photos and videos from a QR code at the event without an account. A name and an email address are optional; without them a contribution is anonymous.

Before anything is sent the guest answers two separate questions: whether the organiser may keep it in the event’s collection (needed to send), and whether the organiser may also use it in their own promotion (optional). Both answers are stored with the time, the language and the version of the wording.

Nothing a guest sends is public until the organiser approves it, and then only on the event’s display screen or gallery if the organiser has opened them. Copies shown anywhere are re-rendered without location or camera data; the original file is kept privately for the organiser.

Files are stored in a private store in Frankfurt, reached only through short-lived signed links. Each guest receives a private link to see what they sent and take any of it back; a taken-back file is removed from view at once and its files are deleted within days.

Non tranchéThe organiser’s and Winglark’s respective roles for guest media, the legal basis for each use, and the retention period after an event need legal review.

Joining a venue’s audience through AudiencePass

Where an organisation uses AudiencePass, a visitor can scan its QR code and ask to hear about its future events. The page asks for a first name and an email address, optionally a last name, a phone number and interests the organisation has listed, and a tick against one sentence. Nothing is stored without that tick.

The organisation’s contacts are its own. Winglark processes them on the organisation’s behalf to keep its list, confirm the address and send what the organisation chooses to send through Winglark. Winglark does not use them for its own marketing, does not add them to any Winglark list or advertising audience, and does not show them to any other customer. The same address joining two organisations makes two separate records, and neither organisation can see the other’s.

By default a person is on the list only after pressing the link sent to their email address. The record keeps the wording they agreed to and its version, the time, the language, and which of the organisation’s codes they used; it does not keep an IP address or a device fingerprint. Where it is certain, it also notes the event that was running when they joined.

Every message carries a link to a page Winglark runs, from which the person can leave in one press, and mail apps receive a one-click unsubscribe. Leaving is enforced by Winglark: the organisation cannot add the person back by hand, by importing a list or by asking them to scan again. The decision is kept as a keyed digest of the address, which differs for every organisation, so it can be enforced without keeping the address itself. Only the person can rejoin, from their own link.

An organisation can delete a contact. When someone asks to be deleted, their details are removed and only that keyed digest remains, so they are not added back by mistake.

Non tranchéThe organisation (controller) and Winglark (processor) roles for audience contacts, the legal basis for each organisation’s use, retention after an organisation stops using AudiencePass, and imported lists attested by the organisation need legal review.

What we do with it

Send the invitations the organiser asks us to send, record the replies, admit people at the door, and produce the report afterwards.

Winglark does not sell data, does not share guest lists between organisers, and does not use a guest list to market anything to the people on it.

Visits to the public website

If you agree to it in the consent panel, Winglark measures how its public pages are used — pages read, where visitors came from, which buttons are used — with PostHog in the United States, without cookies and without identifying visitors. If you do not agree, nothing is measured. The cookies page describes exactly how, and “Cookie preferences” in the footer changes your answer at any time.

Separately, and only if you agree to advertising in the same panel, the Google Ads tag runs on the public pages. It lets Google record that one of Winglark’s own adverts brought you to the site, count a contact message, an access request or a completed sign-up as the result of that advert, and lets Winglark show its adverts again to people who have read these pages. Google receives the pages you read and the language of the site, never your name, your email address or what you typed into a form. Google processes this data under its own privacy policy; the cookies page lists the cookies it sets.

When you ask for access, the request records how you found Winglark: the campaign, the referring site, the page your visit started on and the page you sent the request from. The team uses it to see which sources bring useful requests. It is never used to market anything to you and is not shared. The page your visit started on and the page you came from are kept in your browser only while analytics is switched on; otherwise the request records just what the request page itself knows.

The early-access list on the home page is separate from a request for access. Joining it stores your email address, the language you used, the time, the wording of the consent you gave (with its version), the same attribution as above, and one confirmation link. Nothing is sent to the address until you have opened that link; product updates and launch news then come only while you are on the list, and every message carries an unsubscribe link that works without an account. If you join while the introductory offer is open, the offer is noted against that address once — it is never issued twice for the same address — and its state (noted, issued, used) is kept with the record so the team can honour it. The list is never shared, sold or used for advertising audiences, and it is not passed to Google Ads.

How long it is kept

An event and its guest list stay in the account until the organiser deletes them. Deleting an event deletes its guest list and its replies.

Non tranchéRetention after account closure, and whether report data is anonymised rather than deleted, are not decided yet.

Getting it out, or getting it deleted

An organiser can export every guest list as CSV or Excel at any time, on any tier including the free one, and can delete an account and its data.

A guest who wants their details removed should ask the organiser who invited them, because it is the organiser who holds the list. If that is not possible, contact us and we will reach the organiser.

Where it is processed

Winglark runs on infrastructure in the European Union, and guest data is stored there.

Non tranchéThe full list of processors, and the legal basis under GDPR for each category of data, needs to be written and reviewed.