50% off all plans. See plans

StoryWallStoryWall

StoryWall Cookie Policy

Version 2026-11-11

1. What cookies are

Cookies are small files a website stores on your device, such as a computer, phone or tablet. They are used, for example, to keep you signed in or to remember your choices.

This Policy also covers similar technologies, such as the browser's local storage and session storage.

2. Who uses them

StoryWall is provided by Georgios Christos Tsourdiou, trading as CodeGetIt, operator of Storywall, Thessaloniki 54639. For personal data, see the Privacy Policy.

3. In short

  • We use the cookies and storage StoryWall needs to work.
  • With your consent, we use Google Analytics cookies to see how many people visit our public pages and which pages they use (section 7). They are off until you turn them on.
  • With the same consent, we keep a note of where your visit came from in our own sw_src cookie, so that if you create an account we know which channel brought you (section 7).
  • With the same consent, we keep the latest campaign link that brought you in our own sw_campaign cookie, so that if you buy we know which link led to the sale (section 7).
  • With the same consent, Sentry keeps a replay identifier in session storage, so it can record a replay with hidden text and media when an error happens (section 7).
  • With your consent, we also use Google Ads and Meta Pixel cookies to measure which of our ads bring people to StoryWall (section 8). They are off until you accept.
  • Some pages show content from Spotify, YouTube and Google Maps, which may set their own cookies (section 9).

4. StoryWall cookies

All of these are needed for the service to work and do not require consent.

  • storywall_at: keeps you signed in. Page scripts cannot read it. Lasts 15 minutes.
  • storywall_rt: renews your session so you don't have to sign in every time. Page scripts cannot read it. Lasts 30 days or until you sign out.
  • NEXT_LOCALE: remembers the language you picked. Lasts 1 year.
  • storywall_active_event: remembers which StoryWall you opened last. Lasts 1 year.
  • site_notice_dismissed: remembers which notices you closed, so they stay closed. Lasts 1 year.
  • sw_consent: remembers your cookie choice, separately for Analytics and for Advertising. Lasts 6 months, then we ask again.

5. Browser storage

These items stay on your device only and are never sent to us. The exceptions are the discount code and the create form below: they are sent when you apply the code at checkout or submit the form, just like anything you type.

Local storage (kept until you clear it in your browser, unless a shorter time is given):

  • storywall.eventDescriptionViews.(id): how many times you saw an event's description, so it doesn't keep opening.
  • sw.rolePrompt.(id): that we already asked you to pick a role in a StoryWall.
  • countdown-celebrated:(id): that you already saw the countdown celebration.
  • storywall.crashReportTimes: when recent error reports were sent, so not too many are sent.
  • storywall:demo:… and storywall:demo-act-as:…: your changes in the demo event.
  • storywall.partnerCode: the discount code from a partner's link you followed, so it is filled in at checkout. Deleted after 30 days, when you close the discount code field, or if the code can't be used.
  • pending_create_event_path: the plan you picked before confirming your email, so you can go back to it afterwards. Deleted when you go back to it with your email confirmed, and not used after 7 days.
  • storywall.createEventWizard: your answers while creating a StoryWall, so a reload, signing in or confirming your email doesn't lose them. Deleted when you go on to the payment page or sign out, and not used after 7 days.

Session storage (cleared when you close the tab):

  • storywall.pendingCheckout.(id): the purchase you started, so you can continue when you come back from the payment page.
  • storywall.createEventCheckout.(id): the StoryWall you went on to pay for, so going back from the payment page opens it.
  • storywall.emailCodeSentAt.(id): when we last sent you an email code, so a reload doesn't send another one or restart the wait.
  • storywall:landing-motion-paused: whether you paused the home page animations.

6. Traffic measurement

We use Vercel Web Analytics to count visits to each page. It stores no cookies or other data on your device and does not recognise you from one visit to the next.

When you arrive from a link in one of our own campaigns, we also count the visit ourselves. This stores no cookies or other data on your device either (see section 21 of the Privacy Policy).

With your consent, we also use Google Analytics on our public pages (section 7). We do not use Google Tag Manager or other measurement tools. Google Ads and the Meta Pixel are described in section 8.

7. Analytics cookies

We use Google Analytics to see how many people visit our public pages, which pages they open and where the visits come from, for example a search or one of our ads. This happens only if you turn on Analytics in the cookie banner.

Google Analytics runs only on our public pages, such as the home page and the wedding page, and on the purchase confirmation page. It never runs inside a StoryWall or on sign-in, account or event management pages.

If you turn it on, Google sets these cookies on storywall.gr:

  • _ga: tells one visitor from another. Lasts up to 2 years.
  • _ga_(id): keeps track of your current visit. Lasts up to 2 years.

We send Google each page under its general address, without the codes that identify an event, an invitation or an order. From the address we keep only the campaign details that show which ad or link brought you, such as utm_source or gclid. We do not send Google your name, your email or anything you post.

Our Google Analytics is linked to our Google Ads account, so we can see how visitors who came from our ads use the site. Google uses Analytics data for advertising only if you have also accepted advertising cookies. Google signals is off, so Analytics data is not linked to your Google account.

If you turn on Analytics, StoryWall also sets its own cookies, on any of its pages:

  • sw_src: remembers where your visit came from: the campaign details of the link that brought you (utm_source, utm_medium, utm_campaign), whether you came from an ad (yes or no, without the ad's click code), the name of the site you came from (such as instagram.com, without the full address) and the first StoryWall page you opened, under its general address. A later visit does not replace it, except a visit to a gift page. Lasts 30 days.
  • sw_campaign: remembers the campaign details (utm_source, utm_medium, utm_campaign) of the latest link that brought you. A later campaign link replaces it, except the link on the offer card inside a StoryWall. Lasts 30 days.

We use sw_src only if you create an account: the details are then saved with your account for our sign-up statistics (see section 4 of the Privacy Policy). They are not sent to Google or anyone else.

We use sw_campaign only when you go to pay to activate or upgrade a StoryWall: if it is a link we made, it is then saved with that order for our sales statistics (see section 17 of the Privacy Policy). It is not sent to Google or anyone else.

If you turn on Analytics, Sentry, which we use to find and fix errors, also keeps this item in session storage, on any StoryWall page:

  • sentryReplaySession: an identifier for your visit, so that when an error happens Sentry can record a replay of the page just before it, with all text, everything you type, photos and videos hidden (see section 20 of the Privacy Policy). Cleared when you close the tab.

If you leave Analytics off, Google Analytics does not run on StoryWall, and sw_src, sw_campaign and sentryReplaySession are not set.

You can change your choice at any time from Cookie settings at the bottom of the home page or on this page. If you switch Analytics off, we delete the Google Analytics cookies above, sw_src, sw_campaign and sentryReplaySession, and Sentry stops recording replays.

8. Advertising cookies

We use Google Ads to show ads for StoryWall and to see which ads lead to a purchase. This happens only if you turn on Advertising in the cookie banner.

If you accept, Google sets these cookies on storywall.gr:

  • _gcl_au: links your visits to our ads. Lasts 90 days.
  • _gcl_aw: remembers the ad you clicked to reach us. Lasts 90 days.

Google may also use its own cookies on its own domains, under its own policy. When you complete a purchase, the checkout confirmation page tells Google Ads that the ad led to a purchase.

We also use the Meta Pixel to see which of our ads on Facebook and Instagram lead to a purchase. It runs only on our public pages and on the purchase confirmation page, and only if you turn on Advertising.

If you accept, Meta sets these cookies on storywall.gr:

  • _fbp: tells one visitor from another, so Meta can link your visits to our ads. Lasts 90 days.
  • _fbc: remembers the Facebook or Instagram ad you clicked to reach us. Set only when you arrive from one. Lasts 90 days.

Meta may also use its own cookies on its own domains, under its own policy. When you complete a purchase, the checkout confirmation page tells Meta about the purchase, with your email in coded form (hashed), so Meta can match it to an ad (see section 21 of the Privacy Policy).

If you leave Advertising off, neither Google Ads nor the Meta Pixel runs on StoryWall.

You can change your choice at any time from Cookie settings at the bottom of the home page or on this page. If you switch Advertising off, we delete the Google Ads and Meta cookies above.

9. Third-party content inside StoryWall

  • Spotify and YouTube: song suggestions show a preview of the song. For YouTube we use privacy-enhanced mode (youtube-nocookie.com).
  • Google Maps: the venue page of a schedule item shows a map.

When you open those pages, your browser loads content from these services, which may set their own cookies under their own policies.

10. Signing in with Google or Apple

The sign-in and sign-up pages load the Google and Apple sign-in buttons. When you use them, you deal directly with those services, which may use their own cookies for signing in.

11. Payments through Stripe

You pay on Stripe's page, not on StoryWall. There Stripe may use its own cookies, for example to prevent fraud, under its own policy.

12. Browser settings

You can delete or block cookies and storage in your browser settings. If you block StoryWall's cookies, you won't be able to sign in.

13. Changes

We update this Policy when we add or remove technologies. Each version is dated at the top of the page. Before we add any other cookies that are not strictly needed, we will ask for your consent first, and you will be able to change it at any time.

14. Contact

For questions about cookies, write to support@storywall.gr.