Last updated: 23 October 2026
This Privacy Policy describes how Slipp ApS ("Slipp", "we", "us") processes personal data when you use our marketing site (slipp.app), our attendee app, our vendor app, or any related services (together, the "Services").
We process personal data as a data controller under Regulation (EU) 2016/679 (the "GDPR") and the Danish Data Protection Act (Databeskyttelsesloven). This policy fulfils our duty to inform you under GDPR Articles 13 and 14.
One category works differently. A prepaid-event guest list described in section 4 is controlled by its event owner: the organizer or payer whose event it is (the organization that owns the event on the platform), or a vendor running its own prepaid event. This holds whoever enters the data, including Slipp support acting on behalf of the owner. Slipp processes the list on the event owner's behalf as its processor, and the Articles 13 and 14 duty for that data is the event owner's. A vendor that only trades at someone else's event is neither controller nor processor of it. We describe it here so you can see what we hold and for how long, and section 2 explains where to take a request about it.
Slipp ApS, CVR no. 46359070, is the data controller for personal data processed through the Services.
One category is different: a prepaid-event guest list described in section 4 is processed on behalf of its event owner, as their processor, and the event owner is the data controller for it. The event owner is the organizer or payer whose event it is (the organization that owns the event on the platform), or a vendor running its own prepaid event (the data processing agreement in our Vendor Terms then applies), whoever enters the data, including Slipp support acting on behalf of the owner. Slipp remains the controller for your Slipp account and your orders, as described in the rest of this policy. If your request concerns the guest list, we forward it to the event owner as the responsible controller and confirm to you that we have done so.
Registered office: 8700 Horsens, Denmark.
Privacy contact: privacy@slipp.app. General support: support@slipp.app.
DSA single point of contact (Articles 11–12 of Regulation (EU) 2022/2065): Jesper Halborg, legal@slipp.app. We accept communications from authorities and users in Danish and English. Notices of illegal content or illegal goods under DSA Article 16 should also be sent to legal@slipp.app - see the Vendor Terms § 16 for the notice-and-action procedure.
Slipp has not appointed a Data Protection Officer. We are not required to appoint one under GDPR Article 37(1): we do not carry out large-scale systematic monitoring of data subjects, we do not process special categories of data on a large scale, and we are not a public authority.
For any data-protection question or request, contact privacy@slipp.app.
We try to keep what we collect to a minimum. The categories are:
What: Email address. Optionally a display name if you set one.
Why: To authenticate you (one-time codes), to send order confirmations, and to give vendors a way to contact you about your specific order.
What: Items ordered, prices, vendor, event, timestamps, pickup status.
Why: To process and deliver your order, to keep your order history available to you, and to comply with Danish bookkeeping law.
What: For prepaid events: the guest email addresses and email domains the event owner (the organizer or payer whose event it is, or a vendor running its own prepaid event) sets up to decide whose orders an allowance covers, a record of each guest who signs in with a matching address or is admitted at the counter, the allowance rules and which guests drew on them, and the payer's display name and billing contact (name, email and postal address). Guests are covered whether or not they go on to place an order.
Why: To let the event owner decide whose orders an allowance covers, admit guests at the counter, see what was consumed and be invoiced for it. Slipp processes this on the event owner's behalf as its processor; the event owner is the controller for it. A vendor that only trades at someone else's event is neither.
What: Versions of the Terms and pickup-or-forfeit clause you have accepted, timestamp, and IP address at the moment of acceptance.
Why: To document your consent for legal-basis purposes and to be able to demonstrate consent if challenged.
What: Your choices in our cookie banner (statistics, app-improvement recording), stored in your browser on your device.
Why: To respect your choices on subsequent visits without asking again every session.
What: IP address, user-agent, request timestamps, error traces, and performance traces (request timings and spans from our backend).
Why: To operate the service, detect abuse, debug issues, monitor performance and availability, and protect the platform.
What: Operational events such as "checkout initiated", "acceptance recorded", "payment succeeded", tagged with device class and connection type. Not joined to advertising profiles.
Why: To detect drop-off and fix the order flow. Treated as a legitimate-interest, operational signal - not consumer analytics.
What: For vendor users: email address, optional display name, organisation details (legal name, CVR number, contact details) and Stripe Connect account status. Stripe collects KYC identity documents directly under its own controller responsibility; Slipp does not receive them.
Why: To operate the vendor dashboard, prepare statements of the amounts Slipp retains, invoice any fee agreed in writing, meet bookkeeping obligations and, where the DAC7 rules apply to Slipp, report seller information to the Danish Tax Agency (Skattestyrelsen).
We do not collect or process Danish CPR numbers (Personnummer). Slipp does not require CPR for any service.
Each category of processing has a lawful basis under GDPR Article 6:
| Purpose | Lawful basis | Reference |
|---|---|---|
| Creating your account, authenticating you, processing orders | Performance of a contract | Art. 6(1)(b) |
| Bookkeeping records (orders, invoices, payments) for 5 years | Legal obligation (Bogføringsloven) | Art. 6(1)(c) |
| Security logs, fraud prevention, error monitoring, performance and availability monitoring, operational funnel telemetry | Legitimate interests in operating a secure, reliable platform | Art. 6(1)(f) |
| Cookies / trackers that are not strictly necessary (analytics, session replay) | Consent | Art. 6(1)(a) |
| Deciding whose orders an allowance covers at a prepaid event, and admitting guests at the counter | Legitimate interests of the event owner as controller in covering the guests it approves, whether from the guest list, a configured domain or at the counter (Slipp processes this on its behalf as its processor) | Art. 6(1)(f) |
| Invoicing the event owner of a prepaid event, from aggregated counts such as the number of guests who drew on an allowance | Legitimate interests in invoicing our business customer under our agreement with it | Art. 6(1)(f) |
| Reporting vendor seller information to the Danish Tax Agency under the DAC7 rules, where they apply to Slipp | Legal obligation (DAC7, Council Directive (EU) 2021/514) | Art. 6(1)(c) |
| Marketing emails | Not applicable - Slipp does not send marketing emails | - |
We share personal data only with parties that need it to provide the Services. The recipients are:
We use a small number of vetted providers. International transfers outside the EU/EEA rely on the EU-US Data Privacy Framework ("DPF") and/or Standard Contractual Clauses ("SCCs").
| Provider | Role | Location | Safeguard |
|---|---|---|---|
| Stripe Payments Europe, Ltd. | Payments, KYC, fraud prevention. Independent controller. | Ireland (EU); group transfers to US. | DPF + SCCs. See stripe.com/privacy. |
| Cloudflare, Inc. | CDN, image delivery, bot protection, DDoS mitigation. | US, with EU edge processing. | DPF + SCCs. Sub-processor list at cloudflare.com. |
| Fly.io, Inc. | Application hosting. | Primary region Frankfurt (EU); company in US. | DPF + SCCs. |
| Neon Inc. (USA) | Managed PostgreSQL database holding the platform's records, including account, order and guest-list data. | Hosted on AWS eu-central-1 (Frankfurt, Germany). | SCCs; DPF where certified. |
| Upstash Inc. (USA), provisioned via Fly.io | Redis in-memory store for rate-limit and session-support keys; rate-limit keys contain email addresses. | Frankfurt, Germany. | SCCs; DPF where certified. |
| Resend | Transactional email delivery (order confirmations, pickup-ready notifications and sign-in emails). | US. | DPF + SCCs. |
| BetterStack | Error monitoring across our backend and apps, backend performance monitoring (APM/tracing), and operational uptime monitoring, log management, status page, and on-call alerting - all under our legitimate interest in a reliable, secure service (error context may include personal data where needed for diagnosis). With your "App improvement" consent, it also records a sample of app sessions (session replay) to debug user-experience issues. | EU. | DPA in place. See betterstack.com. |
| PostHog | Product analytics in the apps (only after Statistics consent) and aggregated page-view analytics on the marketing site (cookieless, no persistent identifier). | EU. | EU hosting; DPA in place. See posthog.com. |
| LaunchDarkly, Inc. | Feature flag evaluation both client-side in the apps and server-side on our backend (strictly necessary; flags must resolve in order to render and serve the right product surface). Receives your user ID and email when you are signed in, used only for targeting rules. No display name is shared. Not used on the marketing site. | US, with a global edge. | DPF + SCCs; DPA in place. See launchdarkly.com. |
Some of our sub-processors are based outside the EU/EEA, primarily in the United States. Where transfers occur, they are protected by the EU-US Data Privacy Framework (where the recipient is certified) and/or by the European Commission's Standard Contractual Clauses, with supplementary measures where appropriate.
You can request a copy of the transfer safeguards by writing to privacy@slipp.app.
We keep personal data only for as long as needed for the purpose it was collected for, plus any period required by law:
| Category | Retention period | Basis |
|---|---|---|
| Order records (invoices, transaction data) | 5 years from end of the financial year | Bogføringsloven (Danish bookkeeping law) |
| Account data for active users | For as long as you keep your account | Performance of contract |
| Account data for dormant accounts (no orders) | 24 months, then deleted | Data minimisation |
| Security and application logs | 30 to 90 days | Legitimate interests (security) |
| Cookie consent records | 12 months, then re-prompted | ePrivacy + cookie guidance |
| Records of withdrawn consent | 2 years | Documenting compliance with withdrawal |
| Prepaid-event guest list (guest email addresses, per-guest sign-in and counter-admission records, and the payer's billing contact) | 30 days after the event is marked as ended, or 30 days after it is deleted, the guest addresses and per-guest records are deleted and the billing contact's name, email and postal address are erased. Kept after that: the email domains authorised for the event, the payer's display name and the allowance rules, which identify an organisation rather than a person. An event that is never marked as ended or deleted keeps its guest list. Which guests drew on an allowance stays in the order records, kept for 5 years from the end of the financial year (Bogføringsloven). Audit log entries keep only a salted hash and the email domain, and are retained with the rest of the audit log (5 years). | Data minimisation (processed for the event owner, which is the controller) |
| Audit log of vendor operational changes | Same as order records (5 years) | Legal obligation + dispute support |
Under the GDPR you have the following rights:
To exercise any of these rights, write to privacy@slipp.app. We will respond within one month, in line with GDPR Article 12(3). We may need to verify your identity before acting on a request. Where your request concerns the prepaid-event guest list described in section 4, the event owner (see section 2) is the controller and decides it: within that same month we forward the request to the event owner without undue delay and confirm to you that we have done so, rather than deciding it ourselves.
If you believe our processing of your personal data infringes the GDPR, you have the right to lodge a complaint with the Danish Data Protection Authority - Datatilsynet (datatilsynet.dk).
We would appreciate a chance to address your concern first - please reach out to privacy@slipp.app.
Slipp is intended for users aged 18 and over. We require an 18+ confirmation at signup. The age threshold is set on the basis of Danish contractual capacity (Værgemålsloven §§ 1, 42), not as a special-category processing matter.
Restricted-goods enforcement (alcohol under Restaurationsloven, tobacco under Tobaksforbudsloven) is the responsibility of the vendor at the point of delivery.
If you become aware that someone under 18 has created an account, please contact privacy@slipp.app and we will close it.
Slipp does not make decisions producing legal or similarly significant effects about you based solely on automated processing within the meaning of GDPR Article 22.
Stripe may run automated fraud checks as part of its payment processing under its own controller relationship; Stripe's privacy policy applies.
Slipp does not collect, process or store Danish CPR (Personnummer). Processing CPR is restricted under Databeskyttelsesloven § 11 to specific scenarios that do not apply to Slipp.
Slipp does not send marketing emails. The only emails we send are transactional (order confirmations, authentication codes, service notices). We will not opt you in to marketing communications without separate, explicit consent.
We may update this policy from time to time. The "Last updated" date at the top reflects the most recent change. For material changes that affect your rights, we will give reasonable notice and, where required, ask for renewed consent.
Previous versions are available on request from privacy@slipp.app.