This Cookies Policy explains how Novelle uses cookies, local storage, consent signals, pixels, tags, and similar technologies on https://novelle.wedding.
The website is operated by Nova Group Sp. z o.o., Tax ID / VAT ID PL7011215529, KRS 0001117840, REGON 529224431, registered address Żurawia 6/12 Lok. 745, 00-503 Warszawa, Poland. Contact: support@novelle.wedding.
1. What cookies are
Cookies are small files or identifiers stored on your device. Similar technologies include local storage, session storage, pixels, tags, SDK identifiers, and consent signals.
Some technologies are necessary for the website to work. Others are used for analytics, advertising, remarketing, conversion measurement, authentication, payment security, fraud prevention, and service improvement.
2. Consent
Strictly necessary cookies may be used without consent because they are required to provide the website, security, payments, consent management, or account access.
Analytics, marketing, remarketing, and similar non-essential technologies are used according to your consent choices where consent is required. You can change or withdraw your cookie consent at any time by reopening the cookie settings widget available on the website.
3. Cookie categories
| Category | Purpose |
|---|---|
| Strictly necessary | website operation, security, payments, consent records, account access |
| Preferences | remembering selected choices such as language or consent state |
| Analytics | understanding traffic, page usage, conversions, and product performance |
| Marketing | ad measurement, remarketing, campaign attribution, conversion tracking |
| Authentication | account sessions, login state, protected partner or customer areas |
| Payment and security | payment-session security, fraud prevention, transaction integrity |
4. Cookie and technology table
| Provider | Cookie / storage name or pattern | Category | Purpose | Typical retention | Consent required | Notes |
|---|---|---|---|---|---|---|
| Cookiebot CMP / Usercentrics | CookieConsent, CookieConsentBulkTicket | Strictly necessary | Stores consent choices and consent proof | 12 months | No | Required to remember and apply consent settings |
| Google Consent Mode v2 | consent signals such as ad_storage, analytics_storage, ad_user_data, ad_personalization | Consent signaling | Communicates consent choices to Google tags | session to 24 months depending configuration | Follows consent choice | Consent Mode is not a banner; it works with the consent widget |
| Google Analytics 4 | _ga | Analytics | Distinguishes users for analytics and reporting | 24 months | Yes, where required | Used only according to consent configuration |
| Google Analytics 4 | _ga_* | Analytics | Stores GA4 property/session state | 24 months | Yes, where required | Name varies by GA4 property |
| Google Analytics / Google tag | _gid | Analytics | Distinguishes users for short-term analytics | 24 hours | Yes, where required | May be present depending configuration |
| Google Analytics / Google tag | _gat, _gat_* | Analytics | Throttles request rate | 1 minute | Yes, where required | May be present depending configuration |
| Google Ads | _gcl_au | Marketing | Conversion linker and ad attribution | 90 days | Yes | Used for Google Ads measurement where enabled |
| Google Ads | _gcl_aw | Marketing | Stores ad click attribution | 90 days | Yes | Used when Google Ads auto-tagging or conversion tracking is enabled |
| Google Ads | _gcl_dc | Marketing | Stores campaign attribution for Google marketing integrations | 90 days | Yes | May be present depending tag setup |
| Google advertising services | IDE, test_cookie, NID | Marketing | Ad delivery, fraud prevention, personalization, and measurement on Google domains | session to 13 months | Yes for marketing use | May be set by Google services or embedded content |
| Plausible Analytics | usually cookieless | Analytics | Privacy-friendly traffic measurement | no cookie by default | Consent depends on configuration and local law | Plausible is usually cookieless unless configured otherwise |
| PostHog | ph_*, posthog_*, local storage identifiers | Analytics / product analytics | Product analytics, event measurement, feature analysis | session to 12 months | Yes, where required | Exact names depend on PostHog configuration |
| Clerk | __session, clerk_* | Authentication | Account login, session management, protected pages | session to 12 months | No for necessary authentication | Used where account or partner/customer areas are enabled |
| Stripe | __stripe_mid | Payment and security | Fraud prevention and payment security | 12 months | No where necessary for payment security | Used by Stripe payment services |
| Stripe | __stripe_sid | Payment and security | Short-term payment session security | 30 minutes | No where necessary for payment security | Used by Stripe payment services |
| Stripe | m, stripe.csrf, Stripe local storage identifiers | Payment and security | Payment security, fraud prevention, and checkout integrity | session to 24 months | No where necessary for payment security | Exact identifiers may vary by Stripe integration |
| Worldline | Worldline payment session cookies | Payment and security | Payment session, authentication, fraud prevention, transaction security | session to 24 months | No where necessary for payment security | Exact names depend on Worldline integration |
| Novelle website | session and CSRF cookies | Strictly necessary | Security, form submission, account protection, service continuity | session | No | Required for safe website operation |
| Novelle website | preference cookies or local storage | Preferences | Remembers interface preferences such as language or consent state | 6 to 12 months | Depends on purpose | Used only where relevant to website functionality |
| Email and campaign links | UTM parameters, referrer data | Analytics / marketing | Campaign attribution and conversion measurement | session to 90 days | Yes, where required | Stored only if configured through analytics or marketing tools |
5. Google Ads and analytics compatibility
The website may use Google Consent Mode v2 so that Google tags adjust behavior based on consent choices. When analytics or marketing consent is denied, Google tags should respect that choice according to the configured consent mode.
Conversion measurement, remarketing, and personalized advertising are used only where permitted by law, platform policy, and consent settings.
6. Third-party cookies
Some cookies may be set by third parties whose services are embedded or integrated into the website, including payment providers, authentication providers, analytics providers, advertising platforms, consent tools, and security services.
Third-party providers may process data under their own policies. Novelle uses these providers to operate the website, protect transactions, measure performance, and provide services.
7. Managing cookies in your browser
You can also block or delete cookies through your browser settings. Blocking strictly necessary cookies may affect website features, payment flows, account access, consent storage, and security functions.
8. Contact
For questions about cookies or consent, contact privacy@novelle.wedding or support@novelle.wedding.