Cookie
Policy
What we collect in your browser and how you can manage it.
This is a courtesy translation. In case of any discrepancy, the Polish-language version of this document is legally binding.
The doswiftly.pl site stores a single cookie - remembering the selected language version - and runs no analytics or marketing tools. The dashboard (app.doswiftly.pl) and Stores built on our SDK use only essential and functional cookies: for logging in, the cart and remembering preferences. Such cookies do not require consent, so we do not show a consent banner. You can delete or block cookies in your browser settings.
§ 1 What cookies and similar technologies are
Cookies are small text files saved by your browser on your device when you visit websites. They allow us to recognize the device, remember preferences (e.g. dark mode), keep you logged in, measure traffic and personalize ads with your consent.
This policy also covers similar technologies: localStorage, sessionStorage, pixel tags and service-provider headers.
The use of cookies is governed by art. 399-400 of the Electronic Communications Law (which replaced the Telecommunications Law on 10 November 2024) and the GDPR. Cookies other than essential ones require consent.
Data controller
| Field | Details |
|---|---|
| Company | JAKUB GABRYCHOWICZ GameGoods (marka DoSwiftly) |
| Address | ul. Łęczycka 15/1, 99-340 Krośniewice |
| NIP / REGON | 7752647541 / 360765637 |
| Contact | kontakt@doswiftly.pl |
§ 2 Cookie categories in DoSwiftly
2.1. Essential (always on)
Required for the Platform to work - without them logging in, saving the cart and security requirements cannot be met. They do not require consent (art. 399 of the Electronic Communications Law). They include, among others, the login session, the cart and remembering the selected language.
2.2. Analytics
DoSwiftly does not use analytics cookies. Traffic statistics for Stores (the Merchant's dashboard) are collected without cookies - the visit identifier is kept only in the browser's session storage and disappears when the tab is closed.
2.3. Marketing
DoSwiftly does not use marketing cookies or advertising pixels. If a Merchant adds such tools to their Store, the Merchant is responsible for them and for collecting the required consents.
2.4. Functional
Remembering preferences such as language, currency or interface state. Treated as part of the essential category - they keep the user's choices between visits.
§ 3 Table of cookies used
The table below covers cookies used in DoSwiftly - on the doswiftly.pl site, in the dashboard (app.doswiftly.pl) and in Stores built on the DoSwiftly SDK - set only where you actually use the given feature. DoSwiftly does not use analytics or marketing cookies. The list is updated regularly.
| Name | Provider | Category | Purpose | Duration |
|---|---|---|---|---|
| dsw_lang | DoSwiftly (doswiftly.pl) | Essential (functional) | Remembers the selected language version of the site (PL / EN). httpOnly + Secure + SameSite=Lax. | 12 mo. |
| access_token | DoSwiftly (app.doswiftly.pl) | Essential | Session of a logged-in dashboard user (the token inside is valid for 15 min and renewed via refresh_token). httpOnly + Secure + SameSite=Strict. | 30 days |
| refresh_token | DoSwiftly (app.doswiftly.pl) | Essential | Renews the session without logging in again. httpOnly + Secure + SameSite=Strict. | 30 days |
| oauth_session | DoSwiftly (app.doswiftly.pl) | Essential | Handles signing in with a Google or Facebook account. httpOnly + Secure + SameSite=Lax. | 10 min |
| NEXT_LOCALE, sidebar_state | DoSwiftly (app.doswiftly.pl) | Essential (functional) | Dashboard interface language and sidebar state | 12 mo. / 7 days |
| customerAccessToken, customerRefreshToken | DoSwiftly (Stores built on the SDK) | Essential | Session of a logged-in Store end customer. httpOnly + Secure + SameSite=Lax. | 30 days |
| session-expiry | DoSwiftly (Stores built on the SDK) | Essential | Customer session expiry time (no credentials) | 30 days |
| cart-id | DoSwiftly (Stores built on the SDK) | Essential | Cart identifier | 30 days |
| preferred-currency, preferred-language | DoSwiftly (Stores built on the SDK) | Essential (functional) | The Store currency and language chosen | 12 mo. |
| referral-code | DoSwiftly (Stores built on the SDK) | Essential (functional) | Remembers a referral code from a link until the customer signs up | 30 days |
| __cf_bm, cf_clearance | Cloudflare, Inc. | Essential | Security, bot protection | Session - 1 year |
| _GRECAPTCHA | Google Ireland Ltd. (reCAPTCHA on the dashboard sign-in and registration pages) | Essential | Protects forms against bots | 6 mo. |
| Payment operator cookies | PayU S.A., PayPro S.A. (Przelewy24) | Essential | Processing payments - on the operator's pages after the redirect from checkout and in the card form in dashboard billing | Per the operator's policy |
| Pickup point maps | InPost sp. z o.o., ORLEN Paczka sp. z o.o. | Essential | Choosing a parcel locker or pickup point at checkout - loaded only when choosing a point | Per the operator's policy |
Store cookies are set by the Store's code built on the DoSwiftly SDK - toward end customers their controller is the Merchant, who describes them in their Store's cookie policy. The table does not cover cookies from tools the Merchant adds to the Store themselves (e.g. analytics or ads) - the Merchant is responsible for them and for collecting consents.
Besides cookies, DoSwiftly uses browser storage (localStorage, sessionStorage): the dashboard stores interface settings there (e.g. theme, module state), and Stores built on the SDK store the logged-in end customer's profile data (identifier, email, name, phone) and, only for the duration of the visit, a session identifier for Store traffic statistics.
§ 4 How to manage consent
DoSwiftly uses only essential and functional cookies, which do not require consent (art. 399 of the Electronic Communications Law), so it does not show a consent banner. Should DoSwiftly need to use cookies requiring consent, it will ask for consent before storing them.
You can delete or block cookies at any time in your browser settings (§ 5).
If a Merchant uses cookies requiring consent in their Store, the Merchant collects and manages those consents.
§ 5 Cookie settings in your browser
You can manage cookies directly in your browser settings:
§ 6 Consequences of disabling cookies
Disabling essential cookies will make it impossible to use some DoSwiftly features - including logging in and the cart.
§ 7 Changes to the Cookie Policy
The cookie list is updated as the DoSwiftly infrastructure changes. Significant changes are communicated on this page. The current version is available at doswiftly.pl/cookies.
Version: 2.0, in force from 08.10.2026. The previous version 1.0 was in force from 16.05.2026.