Cookie Policy

Last updated: 09 April 2026

1. What this Cookie Policy covers

This Cookie Policy explains how Swipe uses cookies, similar technologies, and browser-side storage in the web application. It supplements the Privacy Policy and describes in particular which technologies are used for login, session management, security, and certain convenience features.

This Cookie Policy applies to the use of the Swipe web application under the domains swipe-service.de and swipe-service.ae. Browser cookies do not apply in the same way to the native mobile apps; those apps use app-specific token and device-storage mechanisms instead.

2. What are cookies and similar technologies?

Cookies are small text files stored on your device by your browser. Similar technologies include Local Storage, Session Storage, and other browser-side storage mechanisms that can keep information available for later requests.

These technologies may either apply only to the current session or remain stored beyond the session until they expire automatically or are deleted by you.

3. Which technologies we currently use

3.1 Required login, session, and security cookies in the web application

In the web application, Swipe currently uses required cookies in particular for authentication, session management, security, and protection against abusive requests. This includes in particular an authentication or access cookie, a refresh cookie for session continuation, and the CSRF protection cookie XSRF-TOKEN.

These cookies help us recognize logged-in users on the web, secure protected requests, renew sessions, and associate realtime features with the correct authenticated user.

3.2 Browser-side storage in the web application

In addition, the web application uses browser-side storage such as Local Storage or Session Storage where this is necessary for certain product features. According to the current product setup, this includes in particular language settings, public return and scroll position handling, temporary drafts, and market-related development or staging settings.

3.3 Native mobile apps

According to the current product setup, the native iOS and Android apps do not use browser cookies for login or session management. Instead, they use app-specific token and storage mechanisms that are technically different from browser cookies.

4. Why we use these technologies

We use cookies and similar technologies in particular for the following purposes:

• providing and securing the login process in the web application
• recognizing users who are already signed in on the web
• continuing and refreshing existing sessions
• protecting the platform against CSRF and similar abuse attempts
• supporting technical convenience features such as language settings and temporary drafts
• supporting internal navigation and return behavior in the web application

5. Which types of cookies we currently do not use

According to the current product setup, Swipe does not currently use optional analytics, marketing, or retargeting cookies in the web application that are not necessary for operating the platform.

If we introduce optional cookies or similar tracking technologies in the future, we will update this policy accordingly and, where legally required, provide an appropriate consent or preference mechanism.

6. Legal bases

Where the General Data Protection Regulation (GDPR) applies, we generally rely on Article 6(1)(b) and (f) GDPR for required cookies and similar technologies, insofar as they are necessary to provide the requested web functions, manage sessions, and protect the security and integrity of the platform.

Where applicable data protection law in the United Arab Emirates applies, required technologies are used within the legally permitted processing cases thereunder, in particular to provide the requested services, perform contractual obligations, and protect our platform and users.

7. Retention periods

The exact retention period depends on the relevant technology and function:

• Required authentication and security cookies are generally stored only for as long as needed for the relevant session or its technical continuation, or until you log out.
• Refresh-related session information may remain valid longer depending on the web session setup and features such as “remember me,” until it expires or is revoked.
• The CSRF cookie XSRF-TOKEN is retained for as long as it is needed to secure the web session.
• Entries in Local Storage or Session Storage generally remain until they are overwritten technically, removed automatically, or deleted by you or your browser.

8. Third parties and technically integrated services

Some functions of the web application may establish technical connections to third parties, for example Stripe for payment functions or Google for font or icon resources. Whether and to what extent such third parties use their own cookies or similar technologies is governed by their own privacy and cookie notices.

This Cookie Policy primarily describes the cookies and browser-side storage mechanisms for which Swipe is responsible within its own web application.

9. Management and disabling

You can manage, restrict, or delete cookies in your browser. You can also clear Local Storage and Session Storage through your browser settings.

Please note, however, that disabling or deleting required cookies and storage mechanisms may prevent login, session continuation, security functions, or other parts of the web application from working properly.

10. Contact

If you have any questions about this Cookie Policy, you can contact us using the support options in the app or on the website. The provider responsible for the market you are using, together with its contact details, is listed in the imprint (legal notice).

11. Currency and changes to this Cookie Policy

We update this Cookie Policy if the technologies used in the web application, the product functions, or the legal requirements change. The current version published on the platform shall apply.