What information the shop uses and what your browser saves.
Version 2026-11-13
Who is responsible for your data
The personal data controller is the seller named in the details below. Contact the seller’s email about access, corrections, deletion or any privacy question. We use your information to provide the shop, process orders and respond to you, rather than treating a purchase as permission for advertising.
What we process and why
Orders use your name, surname, phone, delivery destination, selected pieces, payment status and correspondence. Email at checkout is optional; it helps link orders to your account. An account uses your email, authentication credentials and details you choose to save. We process what is needed to enter into and perform the contract, meet accounting and fiscal duties and deal with claims. Optional marketing would require a separate choice.
A connection to the shop necessarily involves technical information such as an IP address, browser information and requests. Technical error and security logs may contain this information. We do not use it to build advertising profiles. Do not put banking passwords, PINs or full card details in shop forms or messages; mono processes card authorization on its own payment page.
For a contact-form request, we use your email, message and optional name to respond. The message is delivered to the workshop and recorded in the email delivery history. To limit spam and duplicate delivery, the shop temporarily stores keyed fingerprints of the network address and request, alongside sending counters; the anti-spam record does not contain the message or email address itself.
Who receives information
Only the information needed for the chosen service is shared: recipient and destination details with Nova Post or Ukrposhta; order and payment details with mono; receipt details and contact information with Checkbox and its receipt-delivery services when fiscal processing applies. Authorized technical providers may process data to operate and protect the shop. Public authorities receive information when required by law.
Email correspondence is received in iCloud Mail (Apple). Delivery from the contact form uses Resend; Instagram correspondence is processed by Meta. These services may process correspondence outside Ukraine under their own privacy rules. Following external links or opening a payment provider’s page also involves that provider’s rules. For an individually agreed international shipment, the destination country, recipients and applicable data safeguards must be clarified before ordering.
Retention and your rights
We retain order and payment records for performing the contract and for the accounting, fiscal and claims periods required by law. Account information is needed while the account is used; you can request its deletion. A deletion request does not erase records that must legally be retained. Cookie lifetimes are listed below; they are different from the retention period of an order in the shop’s database.
You may ask what data we hold, access it, correct inaccuracies, object to unlawful processing or request deletion where the law allows. Consent can be withdrawn for processing that depends on it, without invalidating earlier lawful processing. We may need to verify that a request concerns your data. You can also complain to the Ukrainian Parliament Commissioner for Human Rights or seek protection in court. These rights also apply under other applicable data-protection laws.
Cookies and browser storage
The shop uses service cookies for the cart, sign-in, temporary registration details and cache, and stores language and theme choices. These functions are separate from optional analytics. Accepting the purchase terms does not enable analytics or advertising. Removing site storage may empty the local cart, sign you out or reset preferences; it does not cancel an order or delete its server records.
Only after permission, our own analytics records views of selected public pages and product pages, successful additions from a product page to the cart, opening checkout and workshop story video milestones. Each event includes its time, a random tab-session identifier, a public page path, a general traffic source, campaign labels and a screen-width category. Account pages, order pages and payment-return or verification links are excluded. With renewed permission under the current notice, we also associate the checkout session with its cart and a subsequently created order to measure conversion and sales sources. We do not join visits across devices or create advertising audiences. Overall order and payment statistics remain available from Medusa operational records independently of analytics permission.
Analytics events are stored in the shop database, with access limited to the seller and technical providers needed to operate the shop. Contact details, addresses, account or order identifiers, full URLs, query strings, IP addresses and user-agent strings are not written into these analytics events. A short-lived hash of the connection address is used in server memory to limit incoming requests and is cleared each minute; this is separate from analytics records and ordinary technical logs. Analytics history is not automatically deleted because of its age. We keep it while the shop operates and the history is needed for long-term comparisons of product interest, traffic sources and the path to checkout. We review this need when the purpose or operation of the shop changes; data that is no longer needed must be deleted or anonymised. Renewing or withdrawing browser permission does not automatically erase history already received. Privacy rights and requests remain available using the contact details on this page. We do not use session recordings.
Optional analytics remains off until permission is given through the analytics controls. The current notice asks for renewed permission before linking sessions to orders; an older refusal remains effective until it expires. Shopping and payment work without permission. Withdrawing permission, browser exclusion, Do Not Track or Global Privacy Control stops future collection and new associations. A later checkout submission without permission excludes an unfinished cart association from the new order even if optional cleanup is unavailable. History already received and associations attached to existing orders are not automatically erased; the analytics retention and privacy-request rules on this page continue to apply.
After permission, sessionStorage groups events in one tab using a random identifier, the first traffic source and campaign labels, a screen category and the last recorded activity time. After 30 minutes without a recorded event, the next event starts a new session. The record is not automatically removed at the 30-minute mark; it is replaced when a new session starts, removed on withdrawal or cleared when the browser ends that tab session. Browser restoration can restore a tab session. A session is not a unique person. Do Not Track and Global Privacy Control signals disable collection. If browser storage is unavailable, analytics remains off.
This choice applies only to the shop’s own analytics described here. Google Analytics, Meta Pixel, advertising audiences and other third-party tracking are not connected. If we introduce them, we will describe the services, purposes and data recipients and offer a separate choice before enabling the relevant tracking. Fonts are served with the shop, and Instagram links do not embed tracking widgets.
After analytics permission, we also record the start, halfway point and completion of individual videos in the workshop stories gallery opened from the homepage. Each event uses a stable public video identifier and the same tab session, page path and general attribution described above. Background video previews and product galleries are excluded. Each milestone is counted once per video per gallery opening; reopening the gallery can count another view. These events help compare interest in workshop videos. They do not include video URLs, viewer names, contact details or recordings of interactions.
An operator can exclude their own browser from shop activity analytics. A local browser preference stops future activity events without changing analytics permission, existing history, orders or payment records. It applies only to that browser and is removed when the preference or site storage is cleared.
The optional checkout association stores the cart identifier, random tab-session identifier, general source and campaign labels, permission notice version and permission and association times in the shop database. Medusa's server-side cart-to-order relation confirms an order; a browser payment return is not proof of a purchase or captured funds. The association is pseudonymous rather than fully anonymous: staff with access to operational orders can connect the session to the corresponding order. Names, contact details, addresses and payment credentials are not copied into analytics events or the association. It uses the first traffic source in the session that submits checkout, not a cross-device or multi-touch history. Existing orders and older permissions are not retrospectively linked.
Each checkout confirmation stores a server-generated attempt reference and a yes/no analytics-permission flag with the order's operational snapshot. Without permission, this guard contains no analytics session or traffic source. It prevents an older permitted attempt from being reused after a refusal or a failed analytics request. The optional association includes the matching attempt reference and is used only when the created order confirms that same permitted attempt.
Browser storage
_medusa_cart_idCookie
Keeps your cart between visits and during a payment return.
Storage duration: Up to 7 days
_medusa_jwtCookie
Keeps you signed in after authentication.
Storage duration: Up to 7 days
_medusa_pending_customerCookie
Temporarily keeps signup contacts when email verification is required.
Storage duration: Up to 24 hours
_medusa_cache_idCookie
Separates service cache updates for your cart and account.
Groups permitted tab activity by a random session, first traffic source, campaign labels, screen category and last activity time. With renewed permission, the session can also be associated with checkout and its subsequently created order.
Storage duration: Browser tab session; the next event after 30 minutes of inactivity starts a new analytics session. Removed on withdrawal.