Back

Last updated: 16 May 2026

Privacy Policy

Note: This is an English translation of the legally binding German version of the privacy policy (datenschutzerklaerung). In case of any discrepancy, the German version shall prevail.

1. Controller

The controller within the meaning of the General Data Protection Regulation (GDPR) and other national data protection laws of the EU member states is:

Anne Speerschneider
trading as "Lille Loppe"

Conrad-Röntgen-Straße 72
25524 Itzehoe
Germany

Email: datenschutz@pladsly.app
General contact: contact@pladsly.app
Contact form: pladsly.app/contact

Data protection officer

We have not appointed a data protection officer, as the legal prerequisites for this under § 38 BDSG (German Federal Data Protection Act) and Art. 37 GDPR are not currently met. For data protection questions, please use the email address above.

2. Scope and general principles

This privacy policy applies to the following services we operate (together "Pladsly" or "the platform"):

  • Marketing website: pladsly.app
  • Shop dashboard: dashboard.pladsly.app for operators of flea market and second-hand shops who use Pladsly as a software solution (hereinafter "shop operators" or "shops")
  • Renter and visitor portal: portal.pladsly.app, including
    • the public shop pages under portal.pladsly.app/shop/{slug},
    • the booking wizard under portal.pladsly.app/wizard/{storeId}, and
    • the logged-in areas for renters (hereinafter "renters").

We process your personal data exclusively in accordance with the applicable data protection regulations, in particular the GDPR and the German Federal Data Protection Act (BDSG). We adhere to the principles of data minimisation, purpose limitation, storage limitation, and transparency.

3. How Pladsly is built — identity layer and business layer

Pladsly is B2B software that helps flea market shops manage shelf rentals to private individuals. To make the roles around your data understandable, we briefly explain the two data layers between which Pladsly separates technically and legally:

Identity layer (technical identity and login data). When you create an account on Pladsly, we store the data required for login and platform security at the Pladsly level. This includes in particular the email address as login identifier, magic-link tokens, security logs, and the technical information about which shops your account is linked to. For this data, Pladsly is the controller within the meaning of Art. 4(7) GDPR.

Business layer (business data per shop). When you, as a renter, book a shelf at a shop, list products, or conclude a rental agreement with the shop, business data is created that belongs to the respective shop (e.g. address for the rental agreement, bank details, uploaded products, sales history). This data lives technically in a shop-bound data structure (so-called "contact entity"). For this data, the respective shop is the controller; Pladsly processes it as a processor on behalf of the shop on the basis of a data processing agreement (Art. 28 GDPR).

Why this matters: Some data fields, such as your email address, appear in both places — once as a login at Pladsly (identity layer) and once as a contact address for the rental agreement with a specific shop (business layer). Even though the data may look identical, it is processed for different purposes and under different controllership. The following sections make this distinction visible.

4. Marketing website (pladsly.app)

4.1 Visiting the website (server logs)

Each time the marketing website is accessed, our hosting provider automatically records technical data temporarily in server logs:

  • IP address of the requesting device
  • Date and time of access
  • Requested URL and HTTP status code
  • Amount of data transferred
  • Submitted user agent (browser, operating system)
  • Referrer URL (if transmitted)

Purpose: Provision and delivery of the website, ensuring IT security (e.g. detecting and defending against attacks), error handling.

Legal basis: Art. 6(1)(f) GDPR (legitimate interest in the secure operation of the website).

Storage period: Short-term, as required for IT security and error handling; typically no longer than 30 days.

4.2 Reach measurement with Vercel Analytics

We use Vercel Analytics to collect statistics on how our website is used. Vercel Analytics works without cookies and without individual user trackers. Only aggregated, anonymised statistics are collected (e.g. page views per URL, approximate geographical region at country level, device type). We cannot derive any personal reference from this data.

For this reason, we do not use a cookie banner. No consent is required from you.

Legal basis: Art. 6(1)(f) GDPR (legitimate interest in privacy-friendly reach measurement), § 25(2)(2) TDDDG (German Telecommunications Digital Services Data Protection Act — no consent required because no end-device access takes place).

4.3 Contact form and email contact

If you use our contact form at pladsly.app/contact or send us an email, we process the data you provide (name, email address, content of the message) to handle your enquiry.

Legal basis: Art. 6(1)(b) GDPR (pre-contractual measures) or Art. 6(1)(f) GDPR (legitimate interest in responding to your enquiry).

Storage period: Until your enquiry is fully handled, plus a reasonable period for evidence purposes. Where retention obligations (e.g. under German commercial or tax law) apply, these take precedence.

The email is sent via our sub-processor Resend (see section 9).

5. Shop dashboard (dashboard.pladsly.app)

The shop dashboard is intended exclusively for shop operators who subscribe to Pladsly as a software solution. Pladsly is the controller for the processing operations described in this section.

5.1 Registration and account creation

For the creation of a shop operator account, we process the following data:

  • Name and address of the shop operator
  • Trade name of the shop
  • Contact details (email, phone)
  • Login data (email, magic-link token)
  • Evidence of acceptance of terms of service and data processing agreement (timestamps)

Purpose: Provision of the SaaS service, performance of the contract, authentication.

Legal basis: Art. 6(1)(b) GDPR (contract).

5.2 Shop verification pursuant to Art. 30 Digital Services Act (DSA)

If you, as a shop operator, want to activate the booking wizard, we are required to verify you under Art. 30 of Regulation (EU) 2022/2065 (Digital Services Act). For this we process:

  • Name, postal address suitable for service, phone, email
  • VAT identification number or tax number
  • Commercial register extract or comparable identification document
  • Bank details (verification via Stripe Connect)
  • Self-certification that you offer only services compliant with EU law

We verify the information through manual sample checks.

Purpose: Fulfilment of our obligations as a provider of an online platform for consumer-to-business distance contracts under Art. 30 DSA.

Legal basis: Art. 6(1)(c) GDPR (legal obligation under Art. 30 DSA).

Storage period: For the entire duration of the wizard's use, followed by the statutory retention periods (typically up to 10 years under § 257 HGB (German Commercial Code) and § 147 AO (German Fiscal Code)).

5.3 Stripe Connect integration

If you use the booking wizard, you connect your own Stripe account to Pladsly via Stripe Connect (direct charges). Pladsly only stores the Stripe account ID and references to transactions, but not payment or account data. Payments from your renters are settled directly by Stripe to your account; Pladsly is at no point the recipient of funds.

For the processing of payment data, Stripe is its own controller. See the Stripe Privacy Policy.

5.4 Configuration and usage data, audit logs

When using the dashboard, we process configuration data (shelves, packages, prices, wizard settings) and audit logs (which account holder made which changes at what time).

Purpose: Provision of the service, traceability of critical changes, abuse prevention.

Legal basis: Art. 6(1)(b) GDPR (contract), Art. 6(1)(f) GDPR (legitimate interest in security and traceability).

Storage period: For the duration of the active business relationship. After termination, we retain audit logs only for as long as is required for security, evidence, or statutory purposes.

6. Renter and visitor portal (portal.pladsly.app)

6.1 Public shop pages (visit without account)

When you, as a visitor, access a public shop page at portal.pladsly.app/shop/{slug}, we process only the following data:

  • Server logs as described in section 4.1 (same purposes, same legal basis, same storage period).
  • Vercel Analytics as described in section 4.2 (cookieless, anonymous).
  • LocalStorage in your browser for the wishlist, language, and theme preferences. This data is stored exclusively locally in your browser and is not transmitted to our servers. You can delete it at any time via your browser settings. This storage is technically necessary to provide the function you have requested and does not require consent under § 25(2)(2) TDDDG.

There is no cross-shop personal profiling.

6.2 Booking wizard

The booking wizard allows you, as a renter, to book a shelf at a specific shop online and conclude the rental agreement with the shop digitally.

Who is responsible for what? Three parties meet in the wizard:

Data categoryControllerPladsly role
Contract data for the rental agreement (name, address, date of birth if requested by the shop, contact details, booking details)The respective shopProcessor of the shop under Art. 28 GDPR
Pladsly account data (email as login identifier, magic-link token, link to the shop)PladslyController
Payment data (credit card, SEPA, etc.)Stripe Payments Europe Ltd.Pladsly has no access to this data

The entry of your payment data takes place via an input field embedded directly by Stripe (Stripe Elements). We do not see your card number or account data at any time.

Conclusion of contract and confirmation email. After successful conclusion of the contract, we send a confirmation email to your email address from the wizard via our sub-processor Resend. The email contains the content of the contract, the right-of-withdrawal notice (if applicable), the mandatory information under Art. 246a EGBGB (Introductory Act to the German Civil Code), and a magic link with which you can activate your Pladsly account.

Legal bases:

  • For the processing of your contract data to perform the rental agreement with the shop: Art. 6(1)(b) GDPR (contract with the shop), acting as processor.
  • For the processing of your account data to create and manage your Pladsly account: Art. 6(1)(b) GDPR (contract with Pladsly regarding the use of the renter portal).
  • For sending the confirmation email: Art. 6(1)(b) GDPR and Art. 6(1)(c) GDPR (statutory obligation under § 312f(2) BGB (German Civil Code)).

Storage period: Contract data is stored for the duration of the rental relationship and subsequently in accordance with the statutory retention periods (typically up to 10 years under § 257 HGB and § 147 AO). Account data is stored until you delete your Pladsly account.

6.3 Logged-in renter area

Once you have activated your Pladsly account, you can manage your data in the portal. We process:

At the Pladsly level (identity layer), Pladsly as controller:

  • Email address, login status, magic-link token
  • Security and login logs
  • List of shops linked to your account (technical linking information)

At the shop level (business layer), the respective shop as controller, Pladsly as processor:

  • Per linked shop: master data (address, bank details if applicable), booking history, uploaded products, sales history, rental agreement documents
  • When accessing your portal: the actively selected shop context (no automatic merging across shops)

If you are a renter at multiple shops, your business data is kept separately per shop. Pladsly does not aggregate this data into a cross-shop profile. You can dissolve the link to a shop at any time in your portal settings.

Legal basis identity layer: Art. 6(1)(b) GDPR (contract regarding the Pladsly account), Art. 6(1)(f) GDPR (security).

Legal basis business layer: Art. 6(1)(b) GDPR (contract with the shop, processed on behalf).

6.4 Product images and AI-supported data enrichment

When you, as a renter, upload product images for your items, we process these images using automated procedures to categorise the products, generate descriptions and price suggestions, and assign the images to your items. This AI processing takes place via Google Cloud's "Vertex AI" service, configured in an EU region (Frankfurt or the Netherlands).

According to our Acceptable Use Policy, product images may not show any persons. If, in individual cases, persons should nevertheless appear in an image, we take technical and organisational measures to ensure that no independent insights about these persons are derived from the AI processing.

Controller: The respective shop. Pladsly processes the images as a processor.

Legal basis: Art. 6(1)(b) GDPR (contract with the shop).

Storage period: Until deletion by the renter or until the images are no longer required for the sales process.

The AI pipeline is orchestrated internally via the "Vercel Workflows" service. We have designed this orchestration step technically so that no personal data flows through it — only image references and product-related analysis results (e.g. detected product category, price suggestion). No personal data is transmitted into this system. See sections 9 and 10 for further details.

6.5 Notice-and-action under Art. 16 DSA

If you report allegedly unlawful content to us via the "Report content" function on a product page, we process your information (description of the content, URL, justification, optionally your contact details for follow-up questions).

Purpose: Review and, where applicable, removal of the content; fulfilment of our obligations under Art. 16 and 17 DSA.

Legal basis: Art. 6(1)(c) GDPR (legal obligation under Art. 16 DSA).

Storage period: At least 6 months from receipt of the notice in order to fulfil DSA obligations; longer where required for ongoing proceedings.

7. Processing on behalf of the shops — what this means for you as a renter

When Pladsly processes data as a processor of a shop (in particular contract data, bookings, products, sales history), the following applies:

  • The controller for this data is the respective shop. Please address data protection requests regarding this data (access, rectification, erasure) primarily to the respective shop. The shop's contact details can be found in the "About this shop" section of the respective shop page.
  • Pladsly acts only on the shop's instructions on the basis of a data processing agreement under Art. 28 GDPR.
  • If you contact Pladsly directly, we will forward your request to the responsible shop and support them in handling it.

Beyond this, Pladsly remains the controller for the processing operations described in sections 5 and 6 (identity layer, server logs, verification under Art. 30 DSA, our own security measures).

8. Cookies and similar technologies

We do not use tracking cookies or third-party advertising cookies on our services.

We use only:

  • Strictly necessary cookies for authentication (login session) and, where applicable, CSRF protection. These are essential for the operation of the logged-in areas (§ 25(2)(2) TDDDG, no consent required).
  • LocalStorage in your browser for language and theme preferences, and for the wishlist on public shop pages (see section 6.1).
  • Vercel Analytics in cookieless, anonymised mode (see section 4.2).

For this reason, we do not use a cookie consent banner.

9. Recipients and processors (sub-processors)

To provide our services, we work with the following sub-processors. With all sub-processors we have concluded data processing agreements under Art. 28 GDPR and, where required, standard contractual clauses under Art. 46 GDPR.

Sub-processorLocation / configurationData processedPurpose
Vercel Inc. (Hosting)Primary Frankfurt (EU), USA as failoverHosting content, server logsPlatform delivery
Vercel Inc. (Workflows)USA (region not configurable)Exclusively product-related data and image references, no personal dataOrchestration of the AI pipeline for product images
Vercel Inc. (Analytics)EU-awareAggregated, anonymous usage statisticsReach measurement (cookieless)
Vercel Inc. (Blob Storage)Frankfurt (EU)Uploaded images (product images)Image storage
MongoDB Inc. (Atlas)Frankfurt (EU)Database contents (all identity- and business-layer data)Database hosting
Resend (Resend Inc.)USAEmail content and recipient addressesSending transactional emails (e.g. magic link, confirmation emails)
Google LLC (Vertex AI)Frankfurt or the Netherlands (EU region)Product images and derived analysesAI-supported data enrichment
Stripe Payments Europe Ltd. / Stripe Inc.Ireland / USAPayment and identity data of Stripe end customersPayment processing (Stripe is independently responsible for the payment data)

A continuously updated list of sub-processors is available at pladsly.app/subprocessors.

10. Transfer to third countries (outside the EU/EEA)

With some of our sub-processors, transfers to third countries occur, particularly to the USA. We take the following safeguards:

  • EU region where available: With Vercel Hosting, MongoDB Atlas, Vercel Blob, and Vertex AI, data processing takes place primarily in the EU.
  • EU-US Data Privacy Framework (DPF): Vercel, Resend, Google Cloud, and Stripe are certified under the EU-US Data Privacy Framework. There is therefore an adequacy decision of the European Commission under Art. 45 GDPR.
  • Standard contractual clauses (SCCs): In addition, we have concluded standard contractual clauses under Art. 46(2)(c) GDPR with all US providers.
  • Data minimisation by architectural design:
    • The "Vercel Workflows" service (USA, region not configurable) is used by us exclusively for orchestrating the AI pipeline for product images. No personal data flows through this step; only product references and analysis results. No third-country transfer of personal data takes place via Vercel Workflows.
    • Resend (USA) processes only email recipients and transactional email content; we do not use it for marketing or extensive profiling.
    • For Vercel Hosting, the primary region is Frankfurt; USA processing only occurs in failover.
  • Stripe is an independent controller for payment data. Data is sent directly from your browser to Stripe; Pladsly never sees card data.

A copy of the respective safeguards can be requested via the email address listed in section 1.

11. Storage period and deletion concept

We store personal data only for as long as is necessary for the respective purposes or as required by statutory retention obligations. We follow these principles:

Data categoryStorage period
Server logs (IP, user agent)Short-term, as required for IT security; typically not longer than 30 days
Audit logs (account actions)During the active business relationship, thereafter as required for security and evidence purposes
Pladsly account master data (active)Until you delete the account
Pladsly account master data (inactive)After prolonged inactivity, anonymisation or deletion may take place under our data minimisation principle
Shop-bound contract and booking dataUntil the end of the rental relationship, followed by statutory retention periods (in particular up to 10 years under § 257 HGB / § 147 AO)
Renter product imagesUntil deletion by the renter or until the images are no longer required for the sales process
Notices under Art. 16 DSAAt least 6 months from receipt, longer where required for ongoing proceedings
Dissolved shop-renter linksFor a reasonable audit period, then deletion
Closed or terminated shop accountsWithin a reasonable period after the end of the business relationship, subject to statutory retention obligations
Database backupsRolling retention of up to 30 days

After the respective period has expired, data is deleted or anonymised, unless statutory retention obligations preclude this. You can at any time request deletion of your data (see section 12).

12. Your rights as a data subject

In relation to us as controller for the data described in the identity layer and other own Pladsly processing operations, you have the following rights (for business-layer data, please address such requests to the respective shop, see section 7):

  • Right of access (Art. 15 GDPR): You can request information about the personal data we process concerning you.
  • Right to rectification (Art. 16 GDPR): You can request the correction of inaccurate data.
  • Right to erasure (Art. 17 GDPR): You can request the deletion of your data, unless retention obligations preclude this.
  • Right to restriction of processing (Art. 18 GDPR).
  • Right to data portability (Art. 20 GDPR): You can receive your data in a structured, commonly used, and machine-readable format.
  • Right to object (Art. 21 GDPR): You can object to the processing of your data where processing is based on a legitimate interest.
  • Right to withdraw consent (Art. 7(3) GDPR): Where processing is based on consent, you can withdraw it at any time with effect for the future.

To exercise your rights, a simple email to datenschutz@pladsly.app is sufficient. We typically process requests within one month of receipt. In individual cases we may request additional information to verify your identity.

In the logged-in area of the portal, you can additionally delete your account yourself.

13. Right to lodge a complaint with a supervisory authority

Without prejudice to other remedies, you have the right to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR). The authority responsible for us is:

Independent State Centre for Data Protection Schleswig-Holstein (ULD)
Holstenstraße 98
24103 Kiel
Germany
Phone: +49 431 988-1200
Email: mail@datenschutzzentrum.de
Web: datenschutzzentrum.de

You may also contact the supervisory authority responsible for your place of residence.

14. Obligation to provide data

You are not required by law or contract to provide personal data. You are not obliged to provide us with data. However, without the data marked as mandatory in the respective input form, we cannot provide certain functions — in particular, signing up, completing a booking, or creating a shop account is technically not possible without the data required for these.

15. Automated decision-making

Automated decision-making within the meaning of Art. 22 GDPR which produces legal effects concerning you or significantly affects you in a similar way does not take place. In particular, the AI-supported product analysis (section 6.4) produces only product-related results (category, price suggestion), not personal decisions.

16. DSA contact points

For matters under Regulation (EU) 2022/2065 (Digital Services Act), we have set up separate contact points. These are listed in the legal notice (imprint) and can be reached via the following email addresses:

17. Data security

We use technical and organisational security measures to protect your data against accidental or intentional manipulation, partial or complete loss, destruction, or unauthorised access by third parties. These include in particular:

  • Encryption of data transmission via TLS
  • Encryption of stored data ("at rest")
  • Access controls and rights management at the application and database level
  • Tenant isolation at the database and application level, so that shops can only access their own data
  • Architectural separation of the AI pipeline such that no personal data flows through the orchestration step (Vercel Workflows, USA)
  • Regular security updates and patch management
  • Logging of security-relevant events

Our security measures are continuously adapted in line with technological developments.

18. Changes to this privacy policy

We reserve the right to adapt this privacy policy so that it always complies with current legal requirements, or to reflect changes to our services, e.g. when new features are introduced. The current version applies to your next visit. The current version is available at any time at the URLs listed in section 2.

For material changes that affect your rights as a data subject, we will additionally inform you actively (e.g. by email to the address stored in your account).