Vendor
Terms

When you operate as a vendor on Slipp - selling to attendees at events through the platform - these terms apply.

Last updated: 23 November 2026

Version 2.1.0

Takes effect: 23 December 2026 for Vendors that accepted an earlier version; from acceptance for a Vendor that first accepts these Terms on or after the publication date.

Summary

This summary, in English and in Danish, is not binding and is not part of the Terms. The numbered clauses in English below are the contract. If the summary and the Terms differ, the Terms apply.

  • Customers pay Slipp's service fee on top of your price, and Slipp keeps the whole fee. You pay Stripe's card fee on every order, deducted on your Stripe account.
  • The fee is never more than 20% of what the guest pays, or 10 kr if that is more. On a 100 kr order that is at most 20 kr. Up to that limit we may change it without notice, for example by event, time or demand.
  • You also pay: MobilePay if you switch it on, Stripe's dispute fees, and any negative balance on your Stripe account. Stripe does not return its card fee when an order is refunded.
  • A fee above that limit, and any fee terms made just for you, apply only if you have agreed to them in writing.
  • At a Prepaid Event, covered items are paid for by the organizer or sponsor under your arrangement with them. Slipp does not guarantee that payment.
  • You are the seller: refunds, complaints, food safety, allergens and ID checks are yours.
  • Payouts go from your own Stripe account to your bank, daily by default.
  • We email you every change to these Terms at least 15 days ahead (30 days for material changes), and you can leave.
  • If Slipp is down, we do not pay for lost sales.

Resumé (dansk)

Dette resumé, på engelsk og dansk, er ikke bindende og er ikke en del af Betingelserne. Aftalen er de nummererede punkter på engelsk nedenfor. Er der forskel, gælder Betingelserne.

  • Kunderne betaler Slipps servicegebyr oven i din pris, og Slipp beholder hele gebyret. Du betaler Stripes kortgebyr på hver ordre, og det trækkes på din Stripe-konto.
  • Gebyret er aldrig højere end 20 % af det, gæsten betaler, eller 10 kr., hvis det er mere. På en ordre på 100 kr. er det altså højst 20 kr. Op til den grænse kan vi ændre det uden varsel, fx efter event, tidspunkt eller efterspørgsel.
  • Du betaler også: MobilePay hvis du slår det til, Stripes gebyrer ved indsigelser og en eventuel negativ saldo på din Stripe-konto. Stripe giver ikke kortgebyret tilbage, når en ordre bliver refunderet.
  • Et gebyr over grænsen, og gebyrvilkår, der kun gælder dig, gælder kun, hvis du har accepteret dem skriftligt.
  • Ved forudbetalte arrangementer betales dækkede varer af arrangøren eller sponsoren efter din aftale med dem. Slipp garanterer ikke den betaling.
  • Du er sælgeren: refusion, klager, fødevaresikkerhed, allergener og ID-kontrol er dit ansvar.
  • Udbetalinger går fra din egen Stripe-konto til din bank, som standard dagligt.
  • Vi sender dig enhver ændring af Betingelserne på e-mail mindst 15 dage før (30 dage ved væsentlige ændringer), og du kan opsige aftalen.
  • Er Slipp nede, betaler vi ikke for tabt salg.

1. About these terms

1.1 These terms and conditions (the "Terms") govern your use of the Slipp platform as a vendor. They form a binding agreement between Slipp ApS, CVR no. 46359070, Denmark ("Slipp", "we", "us"), and the legal entity that accepts the Terms (the "Vendor", "you").

1.2 Schedule 1 (Data Processing Agreement) forms part of the Terms and governs Slipp's processing of personal data on the Vendor's behalf. By accepting the Terms, you also accept Schedule 1.

1.3 The Terms are written in English, which is the authoritative language of the contract. The summary at the top of these Terms, in both English and Danish, and any translation are for convenience only: they are not binding and are not part of the contract. The numbered clauses in English are the contract and prevail.

2. Definitions

2.1 "Platform" means the Slipp software, including the vendor app, the attendee app, the supporting backend services and the marketing site.

2.2 "Attendee" means a consumer who places an Order with the Vendor via the Platform, including a guest at a Prepaid Event.

2.3 "Event" means an event, festival, market, venue or similar setting at which the Vendor offers goods to Attendees via the Platform.

2.4 "Order" means an Attendee's binding purchase of goods from the Vendor placed via the Platform, whether the Attendee pays for it, it is covered under an allowance, or both.

2.5 "Connected Account" means the Vendor's Stripe Connect account, onto which Order proceeds are paid.

2.6 "Platform Service Fee" means Slipp's fee to the Attendee for the ordering service Slipp supplies to the Attendee through the Platform, collected together with the Vendor's price for the goods.

2.7 "Prepaid Event" means an Event at which Orders are covered, in whole or in part, by an allowance funded by an organizer, a sponsor or another payer (a "Payer") rather than paid for by the Attendee.

2.8 "Covered Amount" means the part of an Order that is covered by an allowance.

2.9 "Guest-Paid Amount" means the part of an Order that the Attendee pays for themselves. An Order at an Event that is not a Prepaid Event is a Guest-Paid Amount in full.

3. Slipp, the Vendor and the Platform

3.1 Slipp provides the technical Platform through which Attendees order goods from the Vendor and, where payment is due, pay for them.

3.2 The sales contract for each Order is concluded between the Attendee and the Vendor. Slipp is not a party to the sales contract and is not the seller of the goods; its own supply to the Attendee is the ordering service for which any Platform Service Fee is charged. The Vendor is the merchant of record and is responsible to the Attendee for the goods sold.

3.3 The Vendor must be a legal entity or sole trader with the capacity to enter into and perform commercial contracts in its jurisdiction of establishment.

3.4 Slipp may change the Platform, including its features, user interface and integrations with payment providers. A change that materially affects the Vendor's commercial position is notified in advance under section 23. A change that would alter who is the merchant of record, or would route Order proceeds through an account held by Slipp, is a change to these Terms under section 23.2 and is made only through a licensed payment service provider.

4. Onboarding and Stripe Connect

4.1 Slipp creates and administers the Connected Account for the Vendor under Stripe's Connected Account Agreement (full service agreement). Stripe Payments Europe, Ltd. ("Stripe") performs all Know-Your-Customer and merchant verification. Slipp does not collect identity documents independently of Stripe.

4.2 The Vendor completes Stripe's onboarding and verification on pages provided by Stripe. The Vendor has no separate Stripe dashboard: Slipp administers the Connected Account on the Vendor's behalf, and the Vendor manages it through the vendor app.

4.3 The Vendor's relationship with Stripe is governed by Stripe's Connected Account Agreement (including the Stripe Services Agreement), available at https://stripe.com/legal/connect-account, in addition to these Terms. The Vendor accepts that agreement during onboarding and keeps the information in its Connected Account accurate and up to date.

4.4 Payment processing, the Connected Account balance, refunds, reversals and payouts are also governed by Stripe's agreement. On those payment mechanics, Stripe's agreement governs the Vendor's relationship with Stripe if it conflicts with these Terms.

4.5 Slipp may refuse onboarding, or off-board a Vendor, whose Connected Account is restricted, suspended or rejected by Stripe.

4.6 Tax reporting. Slipp is a reporting platform operator under the Danish rules implementing Directive (EU) 2021/514 (DAC7). The Vendor provides the identification and tax information those rules require and keeps it accurate. Slipp reports that information and the consideration for the Vendor's Orders to the Danish Tax Agency (Skattestyrelsen) each year and tells the Vendor what it has reported. Slipp may suspend the Vendor's access to the Platform until required information is provided.

5. Platform Service Fee

5.1 Slipp may charge Attendees a Platform Service Fee on Orders. Where it does, the fee is shown to the Attendee before the Attendee confirms the Order and is paid by the Attendee on top of the Vendor's order total, as part of the single payment for the Order. The Vendor collects the fee on Slipp's behalf: it is never part of the Vendor's turnover, and it is not deducted from the Vendor's proceeds. The amount is as shown at checkout. A change to the fee ceiling in section 5.3, or to any other default fee term that applies to all Vendors, is a change to these Terms: Slipp notifies it by email under section 23.2, with the notice period that section requires, and it applies only to Orders created after it takes effect.

5.2 Slipp retains the Platform Service Fee charged on an Order in full, subject only to section 6.4 on refunds. Stripe's processing fees on the Order are borne by the Vendor under section 7.

5.3 Fee ceiling. The Platform Service Fee on an Order is never more than 20% of the Guest-Paid Amount, or DKK 10 where that is higher. Up to that ceiling Slipp may set and change the Platform Service Fee, including by Event, by time and by demand, and may charge no fee, without notice to the Vendor and without the Vendor's acceptance. Such a change is not a change to these Terms and applies only to Orders created after it is made.

5.4 Individually agreed fee terms. Fee terms agreed with the Vendor individually apply only where agreed in writing (email suffices) and only to Orders created after they take effect. A Platform Service Fee above the ceiling in section 5.3, and any fee payable by the Vendor to Slipp other than under section 10.2, applies only as fee terms agreed under this section.

5.5 Where a Platform Service Fee is charged, it is itemised on the Attendee's receipt, which names Slipp as the supplier of the fee line, and on the per-Order data the Vendor can inspect in the vendor app, so the Vendor sees what the Attendee paid for the goods and what was charged as a Platform Service Fee.

5.6 The Platform Service Fee is Slipp's consideration from the Attendee for the ordering service Slipp supplies to the Attendee. It is inclusive of VAT, which Slipp accounts for on the full fee. The fee is not part of the Vendor's turnover, and the Vendor does not account for VAT on it. Section 9 governs the monthly statement of the amounts Slipp retains.

5.7 Fee terms bind Slipp only where they are set out in a written agreement under section 5.4 or 10.2 that identifies itself as fee terms under these Terms. Other statements, including sales and marketing material, do not vary sections 5 to 10.

6. Payments, merchant of record, refunds and disputes

6.1 Payment for each Order is processed by Stripe on the Connected Account, with the Vendor as merchant of record. The Attendee is charged in the Vendor's name, or in the name shown for the Connected Account.

6.2 Under the payment flow in use, Order proceeds are paid directly to the Connected Account and Slipp does not receive or hold them. Payouts follow section 8.

6.3 Refunds are the Vendor's primary responsibility as merchant of record. The Vendor issues refunds through the vendor app, which is the only place from which the Vendor initiates a refund. Slipp may itself refund an Order where these Terms, the Attendee Terms or mandatory law require it - for example where an Order is cancelled or cannot be delivered and the Attendee is entitled to a refund under section 9 of the Attendee Terms - to correct a duplicate or erroneous charge, or where the Vendor cannot be reached in time and Slipp reasonably considers the Attendee entitled to the refund under section 9 of the Attendee Terms. Before refunding, Slipp tells the Vendor and gives it a reasonable opportunity to respond, unless the Event or the Vendor's trading at it has been cancelled or the Vendor cannot be reached in time. Slipp tells the Vendor of every refund it makes and why. Slipp does not refund an Order because of a complaint about the quality of goods that were handed over; that is a matter between the Attendee and the Vendor. In every case the refunded amount is debited from the Connected Account.

6.4 When an Order is refunded, the Attendee is refunded the Platform Service Fee in proportion to the amount refunded: a full refund returns the full fee, and a partial refund returns it pro rata. Slipp returns the amount it retained on that Order to the Connected Account in the same proportion, so the Vendor does not bear the fee on a refunded Order. Stripe's processing fee on the original charge is not returned (section 7.4). A chargeback or payment dispute is not a refund for the purposes of this section. Slipp does not return the amount it retained on a disputed charge.

6.5 Chargebacks and payment disputes are routed to the Connected Account. The Vendor is the primary respondent and submits evidence through the vendor app. With the Vendor's prior written authorisation, Slipp may submit evidence on the Vendor's behalf; such assistance does not transfer dispute liability to Slipp.

6.6 Refunded amounts, disputed amounts and reversals, Stripe's fees and any negative balance on the Connected Account are borne by the Vendor. Where Stripe recovers any of them from Slipp, the Vendor reimburses Slipp on demand, and the Vendor authorises Slipp to recover them by instructing Stripe to debit the Connected Account or by set-off against amounts Slipp owes the Vendor.

7. Stripe processing fees

7.1 The Vendor bears the payment processing fees charged on Orders on the Connected Account, in accordance with Stripe's pricing in effect for the Connected Account. Stripe deducts per-transaction fees from the gross payment before the proceeds settle to the Vendor's available balance.

7.2 Stripe calculates its processing fee on the full amount charged to the Attendee, including any Platform Service Fee, and at the rate that applies to the card or other payment method used. The Vendor bears that fee in full on every Order, whatever the card type and whatever fee terms apply.

7.3 Payment methods that the Vendor chooses to enable beyond cards, such as MobilePay, may carry further fees, including a per-transaction premium over the card rate and any periodic membership fee Stripe bills to the Connected Account. Those fees are borne by the Vendor.

7.4 Stripe's processing fee on the original charge is not returned when an Order is refunded, and the Vendor does not recover it.

7.5 Stripe's dispute fees, including any fee for countering a dispute, are charged to the Connected Account and borne by the Vendor. They are returned only where Stripe returns them.

7.6 Stripe alone calculates and collects its processing fees. Slipp does not control, mark up or rebate them.

8. Payouts

8.1 Stripe pays out the Connected Account balance to the Vendor's linked bank account on the payout schedule Slipp sets on the Connected Account, as shown in the vendor app. Slipp sets a daily payout schedule on the Connected Account by default; a change to the default is notified under section 23. The Vendor does not select or amend the schedule.

8.2 Slipp may ask Stripe to delay or pause payouts where Stripe requires it or where Slipp reasonably considers it necessary to cover expected refunds, disputes or a negative balance. Slipp tells the Vendor without undue delay. Funds remain on the Connected Account throughout.

8.3 Questions about the payout schedule are addressed to Slipp. Questions about an individual payout - for example a failed or delayed bank transfer - are matters for Stripe and are raised through Slipp's support, which relays them to Stripe.

9. Monthly statement of retained amounts

9.1 Each month Slipp gives the Vendor a statement of the Platform Service Fees charged on the Vendor's Orders in the preceding calendar month and of the amounts Slipp retained on them, net of amounts returned pro rata on refunds. The statement is in DKK unless otherwise agreed in writing.

9.2 The statement itemises the Orders for the period and reflects refunds processed in the same period.

9.3 The statement requires no payment: the retained amounts have already been collected on each Order. It is the record of those amounts for both parties.

10. Prepaid Events

10.1 Sections 5 to 9 (fees, payments, refunds, disputes, processing fees, payouts and statements) apply only to Guest-Paid Amounts, and the Platform Service Fee on a Guest-Paid Amount is calculated on that amount alone. No Attendee payment is taken and no Platform Service Fee arises on a Covered Amount, and Slipp charges the Vendor nothing for it unless the Vendor has agreed a fee in writing under section 10.2. Every other section of these Terms, including the Vendor's responsibility for the goods, applies to the whole of every Order.

10.2 Slipp may charge the Vendor a fee for a Prepaid Event, or for its Covered Amounts, only where the Vendor has agreed in writing (email suffices) to the fee and the basis for calculating it, and only for allowances set up on the Platform after it was agreed. A fee payable by a Payer is governed by Slipp's agreement with that Payer and never obliges the Vendor to pay. Unless otherwise agreed in writing, a fee the Vendor has agreed to pay is invoiced after the Prepaid Event ends, is exclusive of VAT with VAT added at the applicable Danish rate, falls due 14 days from the invoice date, and is settled by transfer rather than deducted from payouts. Section 9 does not apply to it.

10.3 Slipp is not a party to the arrangement between the Vendor and a Payer and takes no position on what it covers, on how the Vendor is paid for Covered Amounts, or on when settlement takes place. The Vendor agrees that an Attendee owes nothing for a Covered Amount and that its claim for Covered Amounts lies against the Payer alone. Slipp does not guarantee, underwrite or collect payment by a Payer, does not receive or hold amounts a Payer owes the Vendor, and is not liable if a Payer fails to pay, including on the Payer's insolvency. A consumption report from the Platform is a record of the Orders placed through it, prepared with reasonable care. It is not a statement of the Vendor's entitlement against a Payer, and Slipp makes no representation as to what the Vendor may charge a Payer. Slipp's liability for an error in setting up or enforcing an allowance, or in a consumption report, is subject to section 19 and does not include the price of goods the Vendor supplied.

11. Vendor warranties

The Vendor warrants to Slipp, on a continuing basis, that:

(a) it operates lawfully in its jurisdiction of establishment and holds all permits, registrations and authorisations required to offer the goods it lists on the Platform;

(b) where it sells food or beverages, it is registered with the Danish Food Authority (Fødevarestyrelsen) or the equivalent competent authority and complies with applicable food safety and hygiene rules;

(c) all product descriptions, prices and stock indications it shows on the Platform are accurate and not misleading;

(d) it complies with EU Regulation 1169/2011 on the provision of food information to consumers, including disclosure of the 14 mandatory allergens where applicable, through whatever channels are appropriate (section 12.1), and remains responsible for that information whatever the channel;

(e) it complies with sector-specific regulation for any restricted goods it sells, including alcohol (Restaurationsloven and the Danish prohibition on alcohol sales to persons under 18) and tobacco (Tobaksforbudsloven), and refuses delivery where statutory conditions are not met;

(f) it owns or has the necessary rights to all content it uploads to the Platform;

(g) its use of the Platform complies with applicable competition, consumer and marketing law, including Markedsføringsloven.

The Vendor will notify Slipp without undue delay if any of these warranties ceases to be accurate.

12. Product information, allergens and restricted goods

12.1 The Vendor is solely responsible for the accuracy of the product descriptions, prices and other information it publishes on the Platform, and for the accuracy and completeness of allergen disclosures to Attendees through any channel - for example in person at pickup, on-site signage, or text or fields on the Platform. Information given through one channel must not contradict information given through another.

12.2 Where the Vendor sells age-restricted goods, age verification at the point of delivery is the Vendor's responsibility. Slipp does not verify age at order intake. Attendees confirm at signup that they are 18 or older, but that confirmation does not relieve the Vendor of its statutory verification obligations at delivery. Where Danish law lets a parent or guardian have an Order placed by a minor reversed, the reversal is against the Vendor as seller.

12.3 If the Vendor lawfully refuses to hand over an age-restricted item at delivery because the Attendee cannot show valid ID or is visibly intoxicated, that item is refunded to the Attendee under section 12 of the Attendee Terms. The Vendor refunds it through the vendor app and bears the refund under sections 6.4 and 6.6. The rest of the Order stands and is handed over as normal.

13. Content licence

13.1 The Vendor grants Slipp a non-exclusive, royalty-free, worldwide licence to host, store, reproduce, display and transmit the content the Vendor uploads to the Platform (including logos, banners, menu item descriptions and photos), solely to operate the Platform, display the content to Attendees and to the organizers of Events the Vendor takes part in, and promote the Vendor's participation in those Events on slipp.app, in the apps and on Slipp's social-media accounts, and for Slipp's own marketing under section 13.4. Slipp may sublicense these rights to its service providers and to Event organizers for those purposes.

13.2 The licence lasts for the Vendor's use of the Platform. After it ends, Slipp may keep the content in backups and records for the retention periods in section 14 and the Privacy Policy, and need not withdraw material published or printed before the end, but will not use the content in new material. The Vendor retains ownership of the content.

13.3 Slipp may resize, recompress or convert uploaded media for delivery via the Platform and its service providers. Slipp does not edit the content.

13.4 Slipp may use the Vendor's name, logo and photos uploaded to the Platform in Slipp's own marketing - on its website, on its social-media accounts and in sales material - to show the Vendor as a vendor on Slipp. The Vendor may opt out at any time by email to support@slipp.app. Slipp then makes no new use of them in its marketing and removes them from its website, its social-media accounts and its sales material within 14 days of the opt-out; printed material already handed out need not be recalled. Slipp never uses Attendee data or Order data in its marketing.

14. Operational audit log

14.1 Slipp keeps an append-only audit log of Vendor-initiated changes that affect Attendee-facing availability or pricing - for example opening and closing, item availability, prices, and menu additions or removals. Each entry records the acting user, the entity affected, the action, the timestamp and the before and after values. Entries are not altered except where the law requires it or to correct a technical error, and any such change is itself recorded.

14.2 Changes to Prepaid Event access control (adding or removing a guest on a guest list, and admitting a guest at the counter) are also recorded. Those entries never carry the guest's email address: in place of before and after values they record a salted hash of the address and the email domain, alongside the acting user, the action and the timestamp.

14.3 The audit log is retained for at least 5 years from the end of the financial year in which the entry was created, to evidence the history of Attendee-facing prices and availability in disputes. Entries are visible to Slipp administrators and to the Vendor in the vendor app, and Slipp provides them on request for dispute support.

14.4 Slipp uses the audit log to support the Vendor in consumer disputes (including before Forbrugerklagenævnet) and to evidence Slipp's role as intermediary, and discloses entries to a third party, including an Attendee or Forbrugerklagenævnet, only with the Vendor's consent or where the law requires it. The log is an operational record; Slipp does not warrant that it is complete for any particular purpose.

15. Platform rules and content moderation

15.1 The Vendor must not list goods that are illegal under Danish or EU law, infringe third-party intellectual property rights, are deceptive or misleading, or breach the warranties in section 11.

15.2 In accordance with Article 14 of the Digital Services Act, Slipp may restrict or remove content that does not comply with the Terms. Slipp then tells the Vendor the specific clause or rule the content was found to breach and the available appeal route. Within an Event, Vendors are presented to Attendees in an order the Attendee can see, by default alphabetically by name. Where the app offers another order (for example by distance from the Attendee's location on a map), the order follows the parameter the Attendee selects, which is named in the app. No Vendor receives preferred placement, and no payment or fee level influences the order.

15.3 Slipp does not apply algorithmic moderation, automated content classification or recommender systems to moderate or rank Vendor content. If Slipp introduces algorithmic decision-making to moderation, the Terms will be updated and the change notified in advance under section 23.

15.4 Appeals against moderation decisions are sent to support@slipp.app. Slipp responds within 14 days of receipt.

16. Reporting illegal content (DSA Article 16)

16.1 Anyone - including the Vendor, an Attendee, a third party or an authority - may notify Slipp of illegal content or illegal goods on the Platform by writing to legal@slipp.app. To allow Slipp to act, the notice should contain: (a) a sufficiently substantiated explanation of why the content or goods are alleged to be illegal; (b) a clear indication of the exact electronic location (for example a URL, order or item reference); (c) the name and email of the submitter (except for notices concerning offences referred to in Articles 3 to 7 of Directive 2011/93/EU); and (d) a statement confirming the submitter's good-faith belief that the information in the notice is accurate and complete.

16.2 Slipp acknowledges receipt of notices with valid contact details within 5 business days and communicates a reasoned decision to the reporter without undue delay, normally within 30 days. Where a notice concerns content controlled by the Vendor, Slipp informs the Vendor and gives it an opportunity to respond before taking any moderation action other than emergency interim measures.

16.3 Slipp's single point of contact for authorities and users under Articles 11, 12 and 16 of the Digital Services Act is Slipp's legal contact, reachable at legal@slipp.app. Notices are accepted in Danish and English.

17. Suspension and termination

17.1 Either party may terminate the Terms for convenience on 30 days' written notice, or as section 23 provides. The Vendor may stop using the Platform at any time without notice; the Terms then end when its termination takes effect. Orders accepted before termination takes effect continue to be processed under the Terms.

17.2 Slipp may suspend the Vendor's access to the Platform, or terminate the Terms, with immediate effect where the Vendor materially breaches the Terms; loses a required permit, registration or authorisation; has its Connected Account suspended or terminated by Stripe; is the subject of repeated, substantiated consumer complaints; where Slipp's own access to a payment provider needed to operate the Platform is suspended or terminated; or where suspension is necessary to protect the safety of Attendees or the integrity of the Platform.

17.3 Where Slipp suspends or terminates the Vendor, Slipp gives a written statement of reasons in accordance with Article 17 of the Digital Services Act, stating the specific clause or rule breached, the duration of any suspension and the route to appeal.

17.4 Unless the agreement under section 10.2 provides otherwise: if the Terms end before a Prepaid Event for which the Vendor has agreed a fee has ended, the part of the fee calculated per Order remains payable for Orders already placed, and any fixed part remains payable in full if the Terms were ended by the Vendor for convenience or by Slipp under section 17.2; if the Prepaid Event does not take place for reasons outside the Vendor's control, no fee accrues for it.

17.5 On termination, Slipp retains audit-log entries and Order records for the periods stated in the Privacy Policy and section 14, and otherwise deletes or returns Vendor personal data in accordance with Schedule 1.

17.6 Sections 6.6, 10.2, 10.3, 13.2, 17.4, 17.5, 19, 20, 21 and 24, and any other provision that by its nature is meant to continue, survive termination.

18. Data protection - Schedule 1 (DPA)

18.1 When Slipp processes the personal data of Attendees in connection with Orders placed with the Vendor, including the email addresses and Order data the Vendor sees in the vendor app, Slipp acts as the Vendor's processor under Schedule 1. That Order data is the only personal data Slipp processes on the Vendor's behalf, apart from Prepaid Event access data under section 18.2.

18.2 Prepaid Event access data (as defined in clause 2.2 of Schedule 1) is controlled by the event owner, which is the organization that owns the Event on the Platform: the Vendor, where it organizes its own Prepaid Event (including guest lists kept for its client Payers), or otherwise the organizer or Payer on whose behalf Slipp keeps the guest list, regardless of who enters the data. Where the Vendor is the event owner, the Vendor is the controller of that data and Schedule 1 applies to it. Where the event owner is an organizer or Payer other than the Vendor, the data is outside Schedule 1, and a Vendor trading at that Prepaid Event cannot see the guest list or add or admit guests: it sees the allowances redeemable at its stall and whether an Order is covered, and guests are added or admitted by the organizer or by Slipp. Guest email addresses, per-guest sign-in and counter-admission records and the payer's billing contact are deleted 30 days after the Prepaid Event ends or is deleted; email domains, the payer's display name and the allowance rules and their usage are kept with the Prepaid Event (clause 15A of Schedule 1).

18.3 For Slipp's own processing of Vendor user account data, and for Stripe's processing of payment data, Slipp and Stripe each act as independent controllers under their respective privacy notices (slipp.app/privacy and stripe.com/privacy).

18.4 Access to data. Slipp has access to all data the Vendor and Attendees provide through the Platform and to the Order and operational data the Platform generates, and uses it to operate, secure and improve the Platform, to prepare the statements under section 9, to invoice fees under section 10.2 and to report under section 4.6. The Vendor has access in the vendor app to its own menu, Order, refund, dispute and payout data and to the Attendee data described in Schedule 1, but not to other Vendors' data or to data aggregated across Vendors. Slipp shares data with third parties only as needed to operate the Platform: payment data with Stripe, the sub-processors listed in Schedule 1, the Order and consumption data described in section 21.3, and the information reported under section 4.6. After termination the Vendor may request an export of its Order records for 30 days; Slipp keeps the records described in section 17.5.

19. Liability

Except where prohibited by mandatory law, the parties' liability under the Terms is allocated as follows:

(a) Each party is liable for direct losses caused by its own breach of the Terms, capped per claim and in aggregate per rolling 12-month period at the higher of DKK 25,000 and the total of the amounts Slipp retained on the Vendor's Orders and any fees the Vendor paid to Slipp under the Terms in the 12 months preceding the event giving rise to the claim.

(b) Neither party is liable for indirect or consequential losses, including loss of profit, loss of business, loss of goodwill or loss of anticipated savings.

(c) The cap and the exclusion of indirect losses do not apply to liability for death or personal injury caused by negligence; liability for fraud or fraudulent misrepresentation; the Vendor's indemnification obligations under section 20, which are capped only as section 20.3 provides; or any liability that cannot be limited under mandatory law (including the Product Liability Act).

(d) Amounts payable under sections 5.4, 6.6, 7 and 10.2 are debts, not losses, and are not subject to the cap in section 19(a).

Each party maintains commercially reasonable insurance for its activities under the Terms.

20. Indemnification

20.1 The Vendor will indemnify and hold Slipp harmless against any third-party claim - including Attendee claims, regulatory action and intellectual-property claims - arising from:

(a) the Vendor's goods, including food safety, product quality and labelling;

(b) the Vendor's breach of the warranties in section 11;

(c) content the Vendor uploads to the Platform;

(d) the Vendor's breach of Schedule 1 or its processing of Attendee Personal Data outside the Platform;

(e) the Vendor's arrangement with a Payer or an Event organizer;

(f) taxes and duties on the Vendor's sales,

except to the extent the claim results from Slipp's breach of these Terms or from a fault in the Platform, including how it displays or transmits the Vendor's information.

20.2 Slipp will notify the Vendor of any covered claim without undue delay, cooperate reasonably with the Vendor's defence at the Vendor's cost, and not settle a covered claim without the Vendor's prior consent, which is not to be unreasonably withheld.

20.3 The Vendor's total liability under section 20.1 is capped, in aggregate per rolling 12-month period, at the higher of DKK 100,000 and three times the amounts Slipp retained on the Vendor's Orders in the 12 months preceding the event giving rise to the claim. The cap does not apply to claims arising from the Vendor's fraud or wilful misconduct, from its breach of food-safety law or of the law on age-restricted goods, or from infringement of intellectual property rights by content the Vendor uploads to the Platform.

21. Confidentiality

21.1 Each party keeps confidential any non-public information of the other party that is marked confidential or that a reasonable recipient would treat as confidential, and uses it only to perform the Terms.

21.2 This does not apply to information that is or becomes public without breach of the Terms, was already known to the recipient without a confidentiality obligation, is independently developed by the recipient, or must be disclosed by law or a competent authority (with prompt notice to the other party where lawful).

21.3 Slipp may disclose to the organizer of an Event, and to any Payer at it, the Order and consumption data for that Event, and may use aggregated data that does not identify the Vendor to operate and improve the Platform.

22. Force majeure

22.1 Neither party is liable for failure or delay in performing its obligations under the Terms (other than payment obligations already accrued) caused by circumstances beyond its reasonable control, including power or network outages, failures of third-party providers such as Stripe, the suspension or termination of Slipp's access to a payment provider, natural disasters, fire, war, terrorism, civil unrest, labour disputes, epidemics or acts of public authorities.

22.2 The affected party notifies the other without undue delay and uses reasonable efforts to mitigate the effects. If a force majeure event lasts more than 30 consecutive days, either party may terminate the Terms with immediate effect by written notice.

23. Changes to these Terms

23.1 Slipp may update the Terms, for example to reflect changes in law, in the Platform or in commercial arrangements. Each version carries a version number and an effective date.

23.2 Slipp notifies every change to the Terms to the Vendor by email to the Vendor's administrators. Material changes - changes that affect the Vendor's commercial position, the allocation of liability or the scope of data processing - take effect no earlier than 30 days after the notice; other changes take effect no earlier than 15 days after the notice. On receiving notice of a change, the Vendor may terminate the Terms by written notice with effect on a date of its choosing within 15 days of the notice or, for a material change, no later than the date the change takes effect. Continued use of the Platform after a change takes effect is acceptance of it. The notice periods do not apply where Slipp must change the Terms at shorter notice to comply with a legal or regulatory obligation, or to address an unforeseen and imminent danger from fraud, malware, spam, data breaches or other security risks (Article 3(4) of Regulation (EU) 2019/1150); Slipp then notifies the change by email as soon as possible.

23.3 A change to the Platform Service Fee up to the ceiling in section 5.3, and fee terms agreed in writing with a Vendor individually under section 5.4, are not amendments of these Terms. A change to the ceiling, or to any other default fee term that applies to all Vendors (section 5.1), is an amendment and is notified under section 23.2. Nothing else in these Terms may be changed by notice outside this section 23.

23.4 This version replaces every earlier version, including versions published but not yet in effect. For a Vendor that first accepts these Terms on or after their publication date, they apply from acceptance. Earlier versions of the Terms are available on request from support@slipp.app.

24. Governing law and jurisdiction

24.1 These Terms are governed by Danish law, excluding its conflict-of-laws rules and the UN Convention on Contracts for the International Sale of Goods.

24.2 Disputes arising out of or in connection with the Terms are subject to the exclusive jurisdiction of the Danish courts, with Retten i Horsens as the agreed venue of first instance, subject to the mandatory rules on appellate jurisdiction.

24.3 If a provision of these Terms is held invalid or unenforceable, the rest remains in force, and the provision applies to the greatest extent permitted.

24.4 These Terms, Schedule 1 and fee terms under sections 5.4 and 10.2 are the entire agreement between the parties on their subject matter. If fee terms conflict with these Terms on a matter they may govern, the fee terms prevail for the Orders they cover.

24.5 Slipp may assign the Terms to a successor to all or part of its business on notice to the Vendor. The Vendor may assign them only with Slipp's written consent.

25. Contact

25.1 Questions about the Terms are sent to support@slipp.app.

25.2 Slipp ApS, CVR no. 46359070, 8700 Horsens, Denmark. The registered address is available in the Central Business Register (CVR).

Schedule 1 - Data Processing Agreement

Last updated: 5 November 2026

Version 2.0.0

Summary

This summary is not part of the DPA. If it and the DPA differ, the DPA applies.

  • You are responsible for your customers' Order data; Slipp handles it for you.
  • Do not use guest emails for marketing without consent.
  • A Prepaid Event guest list belongs to the event owner. If you run your own Prepaid Event, you are responsible and this DPA covers it, including lists you keep for your clients. If an organizer or payer owns the event, they are responsible and this DPA does not cover it. Guest emails are deleted 30 days after the event ends or is deleted.
  • Slipp tells you within 72 hours of a breach.
  • Questions: privacy@slipp.app.

This Schedule 1 (the "DPA") forms part of the Vendor Terms & Conditions between Slipp ApS, CVR no. 46359070 ("Slipp") and the Vendor that accepts the Terms ("Vendor"). It governs Slipp's processing of personal data on the Vendor's behalf in connection with the Vendor's use of the Platform.

If the Vendor Terms and this DPA conflict on personal-data processing, this DPA prevails. Capitalised terms not defined here have the meaning given in the Vendor Terms.

1. Scope and incorporation

1.1 This DPA is entered into under Article 28 of the General Data Protection Regulation (Regulation (EU) 2016/679, "GDPR") and the Danish Data Protection Act (Databeskyttelsesloven). It applies for as long as Slipp processes Attendee Personal Data on the Vendor's behalf.

1.2 By accepting the Vendor Terms, the Vendor accepts this DPA on behalf of the legal entity it represents. No separate signature is required. Slipp records acceptance with version, timestamp and Vendor identifier in the same way as for the Vendor Terms.

2. Definitions

2.1 "Personal data", "processing", "controller", "processor", "data subject", "sub-processor", "personal data breach" and "supervisory authority" have the meanings given in Article 4 GDPR.

2.2 "Prepaid Event access data" means the data that controls who may order at a Prepaid Event: guest email addresses, email domains, per-guest sign-in and counter-admission records, the allowance rules and their usage, and the payer's display name and billing contact (name, email and postal address). The audit-log entries under section 14.2 of the Vendor Terms form part of it. It is not Attendee Personal Data; clause 3.4 sets out when this DPA applies to it.

2.3 "Attendee Personal Data" means the personal data of Attendees that Slipp processes on the Vendor's behalf in connection with Orders placed with the Vendor (Order data), including the personal data about those Orders that the Vendor can see through the vendor app and Platform APIs.

2.4 "Sub-processor" means a third party engaged by Slipp to process Attendee Personal Data on the Vendor's behalf.

2.5 "SCCs" means the Standard Contractual Clauses adopted by the European Commission under Decision (EU) 2021/914.

2.6 "DPF" means the EU-US Data Privacy Framework adopted by Commission Implementing Decision (EU) 2023/1795.

3. Roles of the parties

3.1 For Attendee Personal Data, the Vendor is the controller and Slipp is the Vendor's processor. Slipp processes Attendee Personal Data only on the Vendor's documented instructions under clause 7.

3.2 For its own processing of Vendor user-account data, billing data and platform-operation analytics, Slipp is an independent controller under its Privacy Policy (slipp.app/privacy). Slipp does not use Attendee Personal Data for marketing.

3.3 Stripe is an independent controller for payment data under its own privacy notice (stripe.com/privacy). Stripe is not Slipp's sub-processor for payment data.

3.4 Prepaid Event access data is controlled by the event owner, which is the organization that owns the Event on the Platform: the Vendor, where it organizes its own Prepaid Event (including guest lists kept for its client Payers), or otherwise the organizer or Payer on whose behalf Slipp keeps the guest list, regardless of who enters the data. Where the Vendor is the event owner, the Vendor is the controller of that data, and this DPA applies to it as it applies to Attendee Personal Data, with clause 15A as its retention period. Where the event owner is an organizer or Payer other than the Vendor, Slipp processes that data for it under Slipp's agreement with that organizer or Payer, not on the Vendor's behalf, and this DPA does not apply to it. A Vendor trading at a Prepaid Event organized by someone else cannot see the guest list or add or admit guests: it sees the allowances redeemable at its stall and whether an Order is covered, guests are added or admitted by the organizer or by Slipp, and the Vendor does not become a controller of that data.

4. Subject matter, duration, nature and purpose of processing

4.1 Subject matter: operating the Platform on the Vendor's behalf to receive and fulfil Orders, communicate Order status to Attendees, support pickup, and maintain the operational audit log in section 14.1 of the Vendor Terms; and, where clause 3.4 applies, controlling who may order at the Vendor's own Prepaid Event, admitting guests and recording allowance usage.

4.2 Duration: the term of the Vendor Terms, plus any retention period required by law (in particular Bogføringsloven, which requires Order records to be kept for 5 years from the end of the financial year in which the Order was placed) or by section 14 of the Vendor Terms. Prepaid Event access data under clause 3.4 is kept for the period in clause 15A, except the audit-log entries under section 14.2 of the Vendor Terms, which are kept under section 14.3.

4.3 Nature: collection, storage, organisation, retrieval, transmission, display and deletion of Attendee Personal Data through the Platform's standard functionality, including showing Attendee email addresses to authorised Vendor users in the vendor app.

4.4 Purpose: to enable the Vendor to receive and fulfil Orders, contact Attendees about Order status, respond to consumer complaints under Danish consumer law, and meet the Vendor's own bookkeeping and tax-record obligations, and, where clause 3.4 applies, to control who may order at the Vendor's own Prepaid Event and apply its allowances.

5. Categories of personal data and data subjects

The personal data processed on the Vendor's behalf is limited to:

(a) identifiers of the Attendee who placed the Order - email address, internal account identifier, signup timestamp, age-confirmation flag and language preference;

(b) Order details - items ordered, prices, taxes, timestamps, pickup status, Order identifier, and the Vendor and Event the Order relates to;

(c) communication records - Order status messages sent to the Attendee on the Vendor's behalf;

(d) technical metadata strictly necessary to deliver and secure the Order flow (for example request timestamps, and IP addresses logged for fraud and abuse mitigation);

(e) where clause 3.4 applies, Prepaid Event access data (clause 2.2).

The data subjects are Attendees who have placed an Order with the Vendor through the Platform and, where clause 3.4 applies, the guests on the Vendor's Prepaid Event guest list, guests who sign in through a configured email domain and guests admitted at the counter, whether or not they order, and the payer's billing contact. Slipp does not process special categories of personal data (Article 9 GDPR) or Danish CPR numbers on the Vendor's behalf.

6. Vendor (controller) obligations

The Vendor warrants and undertakes that:

(a) it has, and will keep, a valid legal basis under Article 6 GDPR for processing Attendee Personal Data, including any use of that data outside the Platform;

(b) it gives data subjects the information required by Articles 13 and 14 GDPR for its own processing as controller;

(c) it gives Slipp instructions only through the Platform's standard functionality or in writing to support@slipp.app, and those instructions comply with GDPR and other applicable data-protection law;

(d) it will not use, copy, export, transmit or otherwise process Attendee Personal Data for purposes incompatible with the purpose for which it was collected - in particular, it will not use Attendee email addresses for direct marketing without a separate valid consent or other lawful basis under Markedsføringsloven § 10 and applicable e-privacy rules;

(e) it applies appropriate technical and organisational measures within its own organisation to protect Attendee Personal Data after it is exported from the Platform.

7. Processing on documented instructions

7.1 Slipp processes Attendee Personal Data only on the Vendor's documented instructions, including with regard to transfers to a third country or an international organisation, unless Union or Member State law to which Slipp is subject requires otherwise. In that case Slipp informs the Vendor of the legal requirement before processing, unless that law prohibits it on important grounds of public interest.

7.2 The Vendor's documented instructions are: (a) the Vendor Terms and this DPA; (b) the operations performed through the Platform's standard functionality (for example updating menu items, opening or closing, or refunding an Order); and (c) any further instructions agreed in writing in advance with Slipp.

7.3 Slipp immediately informs the Vendor if, in Slipp's opinion, an instruction infringes GDPR or other applicable data-protection law, and may suspend that instruction until the Vendor confirms or modifies it.

8. Confidentiality of personnel

8.1 Slipp ensures that persons authorised to process Attendee Personal Data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.

8.2 Access to Attendee Personal Data is limited to personnel and contractors who need it to perform their duties under the Vendor Terms and is governed by role-based access controls.

9. Security of processing

9.1 Taking into account the state of the art, the costs of implementation, the nature, scope, context and purposes of processing, and the risks for the rights and freedoms of natural persons, Slipp implements appropriate technical and organisational measures to ensure a level of security appropriate to the risk, in accordance with Article 32 GDPR.

9.2 Appendix B summarises the measures. Slipp may update them to reflect changes in the state of the art, regulatory expectations or risk, provided the overall level of protection is not reduced.

10. Sub-processors

10.1 The Vendor gives Slipp general written authorisation to engage sub-processors. Those authorised when this DPA takes effect are listed, with their purpose, location and transfer safeguard, in Appendix A; a sub-processor added or replaced under clause 11 is authorised from the end of the notice period without a new version of this DPA. The current list is published in Slipp's Privacy Policy.

10.2 Slipp enters into a written contract with each sub-processor imposing data-protection obligations no less protective than those in this DPA, including on security, confidentiality, breach notification and international transfers.

10.3 Slipp remains fully responsible to the Vendor for each sub-processor's performance of its obligations.

11. Sub-processor change notification

11.1 Slipp gives the Vendor at least 30 days' prior notice of any intended addition or replacement of a sub-processor that processes Attendee Personal Data, by updating the sub-processor list in its Privacy Policy and by email to the Vendor's administrators.

11.2 The Vendor may object on reasonable data-protection grounds within 30 days of the notice. The parties will discuss the objection in good faith and seek a workable solution. If none is reached, the Vendor may terminate the Vendor Terms with effect from the date the new sub-processor is engaged; amounts Slipp retained on Orders already placed are not refunded.

11.3 Where Slipp must engage a new sub-processor on shorter notice to respond to a security incident or maintain service continuity, it may do so and informs the Vendor as soon as reasonably practicable afterwards, recording the rationale in its internal records.

12. Assistance with data-subject requests

12.1 Taking into account the nature of the processing, Slipp assists the Vendor by appropriate technical and organisational measures, insofar as possible, in responding to requests from data subjects exercising their rights under Chapter III GDPR (Articles 12 to 22).

12.2 Requests to access, export, correct or delete the Vendor's records of Attendee Personal Data are sent in writing to support@slipp.app, and Slipp responds within 14 days. Any self-service functions in the Platform supplement this written channel and do not replace it. Slipp may charge a reasonable, cost-based fee for materially burdensome requests, communicated to the Vendor in advance.

12.3 Where a data subject sends Slipp a request about processing carried out on the Vendor's behalf, Slipp forwards it to the Vendor without undue delay and tells the data subject that the Vendor is the responsible controller.

13. Assistance with the Vendor's GDPR obligations

13.1 Taking into account the nature of the processing and the information available to it, Slipp assists the Vendor with its obligations under Articles 32 to 36 GDPR, including security of processing, breach notification and communication, data protection impact assessments and prior consultation with a supervisory authority.

13.2 Assistance is given in writing in response to requests sent to support@slipp.app. Slipp may charge a reasonable, cost-based fee for materially burdensome requests.

14. Personal data breach notification

14.1 Slipp notifies the Vendor without undue delay, and in any event within 72 hours, after becoming aware of a personal data breach affecting Attendee Personal Data.

14.2 The notification goes by email to the Vendor's administrators and, where provided, to the Vendor's designated data-protection contact. It includes, to the extent then known: (a) the nature of the breach, the categories and approximate number of data subjects and of personal-data records affected; (b) the contact details of Slipp's privacy contact (privacy@slipp.app); (c) the likely consequences of the breach; and (d) the measures taken or proposed to address the breach and mitigate its possible adverse effects.

14.3 Where the information cannot all be given at once, Slipp provides it in phases without undue further delay. Slipp cooperates with the Vendor as reasonably required for the Vendor to comply with Articles 33 and 34 GDPR. Notification is not an admission of fault or liability.

15. Return or deletion of personal data

15.1 Within 30 days of termination of the Vendor Terms, the Vendor may instruct Slipp to return or delete the Attendee Personal Data. Without an instruction in that period, Slipp deletes the data under this clause.

15.2 The return or deletion obligation does not apply to: (a) Order records that Slipp keeps as its own accounting records, as an independent controller, for 5 years from the end of the financial year under Bogføringsloven; (b) audit-log entries retained under sections 14.1 and 14.2 of the Vendor Terms for the period in section 14.3; (c) anonymised data from which the data subject is no longer identifiable; and (d) data Slipp is otherwise required by Union or Danish law to retain.

15.3 Data retained under clause 15.2 is processed only for the purpose and duration of the relevant requirement, and remains subject to the confidentiality and security obligations of this DPA.

15.4 Slipp confirms the return or deletion in writing on the Vendor's request.

15A. Prepaid Event access data

15A.1 Slipp deletes the guest email addresses and per-guest sign-in records in the Prepaid Event access data, including those of guests admitted at the counter, and the payer's billing contact, 30 days after the Prepaid Event has ended or, where it is deleted without having ended, 30 days after its deletion. Email domains configured for access control, the payer's display name and the allowance rules and their usage are kept with the Prepaid Event. Where the Vendor organizes the Prepaid Event (clause 3.4), this is the retention period for that data under this DPA; otherwise this clause is for information only and reflects Slipp's Privacy Policy and its agreement with the organizer or Payer. Order records and audit-log entries are not affected.

16. Audit rights

16.1 Slipp makes available to the Vendor all information necessary to demonstrate compliance with Article 28 GDPR and this DPA, and allows for and contributes to audits, including inspections, by the Vendor or an auditor it mandates.

16.2 The Vendor's primary audit mode is a written information request, no more than once per calendar year, to which Slipp responds within 30 days. Slipp may meet this obligation with relevant third-party audit reports, certifications or attestations held by Slipp or its sub-processors (for example SOC 2 Type II reports or ISO 27001 certificates).

16.3 Where a written response is insufficient and an on-site audit is required - for example after a personal data breach or on instruction from a competent supervisory authority - the audit is scheduled at mutually convenient times during normal business hours, on at least 30 days' written notice, subject to appropriate confidentiality undertakings, scoped reasonably to minimise disruption to Slipp and its other customers, and at the Vendor's reasonable cost.

16.4 Audit rights do not extend to information about other Slipp customers, Slipp's commercially sensitive information unrelated to the processing of Attendee Personal Data, or sub-processor premises beyond what the sub-processor permits under its own audit programme.

17. International transfers

17.1 Slipp processes Attendee Personal Data within the EU/EEA wherever practicable. Where Attendee Personal Data is transferred outside the EU/EEA - for example through a sub-processor with US-based corporate functions - the transfer is protected by an appropriate transfer mechanism under Chapter V GDPR.

17.2 In particular: (a) where the recipient is certified under the DPF, the transfer relies on the DPF adequacy decision; (b) otherwise, it relies on the SCCs (Module Two, controller-to-processor, or Module Three, processor-to-processor, as applicable), supplemented where appropriate by additional technical, organisational and contractual measures.

17.3 The Vendor authorises Slipp to conclude the SCCs on its behalf with each affected sub-processor where required. A copy of the relevant SCCs and any supplementary measures is available on written request to privacy@slipp.app.

18. Liability

18.1 The liability allocation in section 19 of the Vendor Terms applies to this DPA. Nothing in this DPA limits or excludes either party's liability where mandatory law prohibits it, in particular Article 82 GDPR.

18.2 Where a data subject is awarded compensation under Article 82 GDPR, each party is liable as between the parties in proportion to its responsibility for the damage, in accordance with Article 82(5) GDPR.

19. Term and survival

19.1 This DPA takes effect with the Vendor Terms and remains in force for as long as Slipp processes Attendee Personal Data on the Vendor's behalf.

19.2 Clauses 14 (for events relating to the term), 15, 15A, 16 (for the retention period of records retained under clause 15), 17 (for any continued retention) and 18 survive termination of the Vendor Terms to the extent necessary to give them effect.

20. Governing law and jurisdiction

20.1 This DPA is governed by Danish law and is subject to the jurisdiction provisions in section 24 of the Vendor Terms.

20.2 Nothing in this clause prevents either party from seeking interim or injunctive relief from any competent court, or restricts a data subject's right to bring proceedings under Article 79 GDPR.

Appendix A - Authorised sub-processors

The following sub-processors are authorised to process Attendee Personal Data on the Vendor's behalf. Changes follow clause 11, and the same list is published in Slipp's Privacy Policy.

Sub-processor Purpose Location Transfer safeguard
Cloudflare, Inc. Content and image storage and delivery, bot protection and DDoS mitigation for the Platform. US, with EU edge processing. DPF + SCCs. Sub-processor disclosures 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 all categories of personal data in clause 5. Hosted on AWS eu-central-1 (Frankfurt, Germany). EU Standard Contractual Clauses; EU-US Data Privacy Framework 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. EU Standard Contractual Clauses; EU-US Data Privacy Framework where certified.
Resend Transactional email on the Vendor's behalf (for example order confirmations and pickup-ready notifications) and sign-in emails. US. DPF + SCCs.
BetterStack Error and performance monitoring, uptime monitoring, log management, status page and on-call alerting under Slipp's legitimate interest, and session replay only where the Attendee has explicitly consented. None of these is Vendor-instructed processing. EU. EU hosting; DPA in place. See betterstack.com.
PostHog Product analytics in the apps, limited to events emitted after Attendee statistics consent. Operational funnel telemetry that does not depend on consent is processed under Slipp's legitimate interest and is not Vendor-instructed processing. EU. EU hosting; DPA in place. See posthog.com.
LaunchDarkly, Inc. Feature-flag evaluation in the apps and on the backend, strictly necessary to serve the right product surface. Receives the user ID and email of signed-in users for targeting rules only; no display name is shared. US, with a global edge. DPF + SCCs; DPA in place. See launchdarkly.com.

Stripe Payments Europe, Ltd. is not a sub-processor of Slipp. Stripe is an independent controller for payment data under its own privacy notice and contracts directly with the Vendor under the Stripe Connected Account Agreement.

Appendix B - Technical and organisational measures (Article 32 GDPR)

Slipp implements and maintains the following measures, taking into account the state of the art and the Platform's risk profile. The list is illustrative, not exhaustive; Slipp may update specific measures provided overall protection is not reduced.

Access control and identity

  • Role-based access control on the principle of least privilege; access to Attendee Personal Data is limited to personnel and contractors with a documented need.
  • Multi-factor authentication for Slipp personnel access to production environments and sub-processor consoles where supported.
  • Periodic review of personnel access rights and prompt revocation on role change or departure.

Encryption and key management

  • Encryption in transit using TLS 1.2 or higher for all external network traffic, including between the apps, the backend and sub-processors.
  • Encryption at rest for production databases and object storage, with provider-managed keys and periodic rotation.
  • Secrets and credentials kept in dedicated secret-management systems, never in source code or version control.

Network and infrastructure security

  • Production runs in environments separated from development and staging by network and identity boundaries.
  • Edge protection, including DDoS mitigation, bot management and TLS termination.
  • Regular patching of base images, runtime dependencies and managed-service components.

Application security

  • Mandatory code review for all backend changes; automated dependency scanning and static analysis in CI.
  • Secure-by-default frameworks for input validation, output encoding, authentication and session management.
  • Passwordless sign-in; passwords are not stored.
  • Audit logging of administrative and Vendor-initiated operational changes (section 14 of the Vendor Terms).

Backup, resilience and recovery

  • Automated database backups with retention sufficient to recover from operational incidents.
  • Documented incident response covering detection, triage, containment, eradication, recovery and post-incident review.
  • Periodic verification of backup integrity and restore procedures.

Personnel and organisational measures

  • Confidentiality undertakings binding all personnel with access to Attendee Personal Data.
  • Security and privacy awareness for personnel with access to production data, including secure handling during incident response.
  • Documented sub-processor due diligence with periodic review.

Data minimisation and retention

  • Attendee Personal Data is limited to what the order flow needs (clause 5).
  • Retention periods are enforced in line with Slipp's Privacy Policy and the Vendor Terms; data is deleted or anonymised when retention obligations expire.
  • No CPR numbers and no Article 9 GDPR special categories of data are processed on the Vendor's behalf.