StoryWall Privacy Policy
Version 2026-11-11
1. Who we are
StoryWall is a digital platform for private social spaces for events. For the processing this Policy describes, the controller is:
- Legal name: Georgios Christos Tsourdiou, trading as CodeGetIt, operator of Storywall
- Address: Thessaloniki 54639
- VAT number: 168646261
- Privacy email: support@storywall.gr
For details a Host enters about other people (for example guests' details on an invitation), the Host is responsible for using them lawfully and only for their event.
2. Who this applies to
This Policy covers everyone whose data we process through StoryWall: Hosts, Co-hosts, Guests, people who receive an invitation, people who upload through QR Photo Upload without an account, people who appear in other people's photos or videos, website visitors and people who contact us.
3. Basic principles
We process only the data we need, for specific purposes, and we keep it no longer than needed.
4. Account data
When you create an account with email, we process your first name, last name, email, password, language and, if you add one, profile photo.
We store your password only as a BCrypt hash. Nobody can read it.
We also record when you confirmed your email, which versions of the Terms of Use and the Community Guidelines you accepted and when, your confirmation that you are 18 or over, and when you were last active.
When you create an account, with email or with Google or Apple, we also save where the visit that led to it came from:
- the channel, such as an ad, social media, a search engine, an email, a partner, an invitation or a gift,
- 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,
- the first StoryWall page you opened, under its general address, without the codes that identify an event, an invitation or an order.
We use these details only for our own statistics on which channels bring new accounts, events and purchases. Only StoryWall administrators can see them, and we do not share them with anyone. They are saved once, when the account is created, and never changed.
If you turned on Analytics cookies, the details come from the sw_src cookie (see the Cookie Policy). If you didn't, nothing is stored on your device: we keep the details only in the open page and, when you go from our public pages into the app, pass them along in the page address. In that case they are saved only if you create the account during the same visit.
5. Signing in with Google or Apple
You can sign in with "Continue with Google" or "Sign in with Apple". We never receive your Google or Apple password.
- Google: we receive your account identifier, your email, whether Google has verified it, your first name, last name and profile photo. We copy the photo once, when the account is created.
- Apple: we ask for your name and email. We receive your account identifier and email, which may be an Apple relay address.
6. Sessions and account security
For each sign-in we store the IP address and your browser or device (user agent), to protect your account. An account has one active session at a time. Changing or resetting your password ends all sessions.
7. Event details
The Host enters details such as title or names, dates and times, time zone, venue, address, map link, cover photo, description and schedule. Members of the StoryWall can see them.
8. Invitations and third-party data
On a personal invitation, the Host can enter the guest's first name, last name and email. In that case we receive the data from the Host, not from the person themselves.
We use it to create and send the invitation and for joining the StoryWall.
9. Co-hosts
A Host invites a Co-host by email. The invitation is tied to that email and only an account with the same email can accept it.
10. RSVP
When you answer an RSVP we process whether you are coming, the number of adults and children, the phone number and message you write, and your answers for specific schedule items.
Hosts see these answers with your name and can export them as PDF. Once a Host downloads a PDF, we cannot recall that copy.
11. Content you create
We process what you post: posts, text, photos, videos, links, stories, comments, reactions, wishes, song suggestions and votes, and the role label you pick in the StoryWall. Members of the StoryWall can see this content.
A story is shown for up to 24 hours. After that it is not shown, but it stays stored until the StoryWall is deleted. We record who viewed each story; its author and the Hosts can see the list.
For each reaction we record which member left it. The app does not show this to others.
12. Photos and videos
Before storing a photo we remove its location data (GPS) and other metadata. We resize photos to at most 2560 pixels on the longest side and convert videos to at most 1920 pixels, without their metadata.
If the StoryWall has the keep-originals add-on, we also keep the original, also without location data. Only Hosts and the person who uploaded it can download the original.
If the StoryWall's plan includes the members' Gallery download, about a day after the event ends we also prepare the Gallery's photos and videos, in their display version, as zip files, and every member of the StoryWall can download them. We rebuild these files when the Gallery changes, take a removed file out of them, and delete them with the StoryWall. Whoever uploads to such a StoryWall is told so when uploading.
Files are kept in private storage. The app shows them through temporary links that expire within one hour.
Photos may show other people, including minors. Whoever uploads is responsible for doing so lawfully and respecting others' rights.
13. QR Photo Upload without an account
When you upload through QR Photo Upload, we process the files and, if you type one, the name you give, which is shown with your uploads. We do not ask for an email.
To limit abuse, we briefly count requests per IP address. The count is kept only in the server's memory and is not stored.
14. Wishbook and song suggestions
Your wish is shown to members with your name. Hosts can export the wishbook as a PDF with names and wish texts.
A song suggestion has a title, artist, YouTube or Spotify link and an optional comment. Suggestions are visible to members.
15. Gift Account
The main Host can publish a bank name, account holder, IBAN and note, which members can see. We never use the IBAN for any transaction.
16. Reports and moderation
When a report is made we process details about who made it, the content or member it concerns, the StoryWall, the reason, the dates and the decision. If you send a notice without an account, we process the details you give in the form.
When we decide about content or an account, we email whoever is affected.
Every administrator access to content and every moderation action is logged with the administrator, time and IP address. We also record which Host changed the event date or the Gift Account.
17. Payments
Payments go through Stripe Checkout. You enter your card details on Stripe's page and we never see them.
From Stripe we receive and store:
- payment, checkout session and customer identifiers,
- amount, currency, tax and payment status,
- the card's issuing country and the billing country,
- a card identifier (fingerprint) that does not reveal the card number,
- Stripe's fraud risk assessment,
- receipt number and link,
- refunds and chargebacks.
We also record the version of the withdrawal terms you accepted at checkout and when you asked for the service to start immediately.
If you turned on Analytics cookies and the sw_campaign cookie holds a link we made, we save that link's campaign details (utm_source, utm_medium, utm_campaign) with the order when you go to pay to activate or upgrade a StoryWall (see the Cookie Policy). We use them only to count sales and revenue per link. Only the StoryWall team can see those totals, and we do not share the details with anyone. They are saved once and never changed.
18. Business purchases
If you buy as a business, we process the legal name, country, VAT number and address. We check the VAT number in the European Commission's VIES system, which returns the name and address it has on record.
19. Withdrawals and fraud checks
When you withdraw, the system works out the refund automatically. Some signals, such as earlier withdrawals from the same account or card, a very new account, or a StoryWall with many members or files, may put the refund on hold for a member of our team to check. A hold does not cancel the withdrawal. If no decision is made, the refund is paid automatically after a few days.
20. Technical data
When an error happens in the app while you are signed in, we send our server the error type and message, the page and the app version, with your account.
We also use Sentry to find and fix errors and slow pages. When an error happens on our website or our web server, Sentry receives:
- the error type, message and where in our code it happened,
- the page address and the steps just before the error, such as pages opened and buttons pressed,
- your browser, device type and operating system,
- your IP address, which Sentry uses to estimate your country but does not store,
- your account identifier, if you are signed in, but not your name or email,
- timing details for a small share of page loads, to measure speed.
We do not send Sentry your password, payment details or anything you post.
If you turn on Analytics cookies, Sentry also records a replay of the page when an error happens: the page's layout and your clicks and scrolling just before the error. All text, everything you type, photos and videos are hidden in the replay, so it does not show your content. If you leave Analytics off, no replay is recorded.
If you send a problem report from the app, we process the description, page, browser, screen size, language, time zone, recent errors and, if you attach one, a screenshot.
21. Traffic measurement and advertising
We use Vercel Web Analytics to count visits to each page. It stores no cookies or identifiers on your device and does not tell us who you are.
When you open one of our public pages from a link in one of our own campaigns (a link we made, with utm_source, utm_medium and utm_campaign), we also count the visit ourselves, without cookies or anything else stored on your device. We also count whether you then tap the button to create a StoryWall, open the plans or pick a plan. To count each visitor once a day, we combine your IP address, your browser details (user agent) and the link with a random code that changes every day, and keep only the result. We do not store your IP address or browser details. The result and that day's code are deleted after the day ends (Greek time), so the count can't be linked to you or from one day to the next. What we keep is only the count: the campaign, what happened, when, whether it was a phone, tablet or computer, and the page language. Only StoryWall administrators can see it.
We use Google Analytics to see how many people visit our public pages, such as the home page and the wedding page, which pages they open and where the visits come from, only if you turn on Analytics cookies. It also runs on the purchase confirmation page. It never runs inside a StoryWall or on sign-in, account or event management pages. Google then receives:
- the pages you open, under their general address and without the codes that identify an event, an invitation or an order,
- the campaign details of the link that brought you, such as utm_source or gclid,
- the site you came from or, if you came from another of our pages, only our site's address,
- your IP address, from which Google estimates your approximate location, and details of your browser and device,
- the Google Analytics cookies described in the Cookie Policy.
We do not send Google your name, email, payment details or anything you post.
Our Google Analytics is linked to our Google Ads account, so we can see which ads lead to visits and purchases. 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.
We use Google Ads to show ads for StoryWall and to measure which ads lead to a purchase, only if you accept advertising cookies. Google then receives the ad you clicked, the pages where the tag runs (our public pages and the purchase confirmation page), your IP address, browser details and the Google Ads cookies described in the Cookie Policy. We do not send Google your name, email or payment details.
We use the Meta Pixel to measure which of our ads on Facebook and Instagram lead to visits and purchases, only if you accept advertising cookies. It runs only on our public pages and on the purchase confirmation page. Meta then receives the address of the page you open, the ad you clicked, your IP address, browser details and the Meta cookies described in the Cookie Policy. On the purchase confirmation page Meta also receives the order number, the amount and currency, and the email of your StoryWall account in coded form (hashed), created in your browser before it is sent, so Meta can match the purchase to an ad. We do not send Meta your name, payment details or anything you post. For collecting and sending this data, StoryWall and Meta Platforms Ireland Limited are joint controllers; what Meta does with it afterwards is covered by Meta's own privacy policy.
You can withdraw either consent at any time from Cookie settings, at the bottom of the home page or on the Cookie Policy page. When you switch a category off, we delete its cookies and the measurement stops from then on; withdrawing does not affect measurement done before. We do not use Google Tag Manager or other measurement tools.
22. Purposes and legal bases
- Account and sign-in (name, email, password, sessions): performance of a contract.
- Running the StoryWall (event details, content, RSVP, Gallery): performance of a contract.
- Payments and withdrawals (payment data, consents): performance of a contract and legal obligation.
- Accounting and tax records (purchase data, business details): legal obligation.
- Security and abuse prevention (IP, sessions, fraud checks, logs): legitimate interest.
- Sign-up statistics (where the visit that led to an account came from): legitimate interest in knowing which channels bring us customers.
- Finding and fixing errors (error reports, page speed, Sentry): legitimate interest in keeping the service working.
- Error replays (Sentry replays with hidden text and media): consent.
- Reports and moderation: legitimate interest and legal obligation.
- Service emails: performance of a contract.
- Newsletter: consent.
- Cookieless traffic measurement (Vercel Web Analytics, visits and clicks from our campaign links): legitimate interest.
- Visit measurement with Google Analytics (Analytics cookies, pages visited, campaign details): consent.
- Sales statistics by campaign link (Analytics cookies, the campaign link saved with an order): consent.
- Ad measurement (Google Ads and Meta cookies, ad clicks, purchases from ads, the hashed email sent to Meta with a purchase): consent.
23. Service emails
We send emails needed to run the service: email confirmation, welcome, password reset and change, invitations, the StoryWall deletion code, payment and withdrawal confirmations, moderation decisions and, to Hosts, notices about their StoryWall, such as storage limits and coverage ending.
24. Newsletter
You join the newsletter only if you choose to, at sign-up or from your profile. Joining is complete once you confirm your email. We record the email, language, when you joined and confirmed, and the IP address and browser at the time of consent. Your email is added to our mailing list in Brevo.
If you are subscribed, we may also email you offers for your StoryWall, such as a discount on a plan upgrade. If you are not subscribed, we send you no offers.
You can unsubscribe at any time from the link in every newsletter or offer, or from your profile. Unsubscribing does not affect processing done before.
25. Providers that process data
We share data only as needed to run the service, for a legal obligation or to protect rights. We use these providers:
- Railway: hosting of the server and database.
- Vercel: hosting of the website, image optimisation and traffic measurement.
- Cloudflare (R2): storage of photos, videos and other files.
- Brevo: sending emails and the newsletter list.
- Stripe: payments, receipts and refunds.
- Sentry (Functional Software, Inc.): finding errors and slow pages on our website and web server, and error replays only if you turn on Analytics cookies.
- Google and Apple: signing in with your account there, only if you use it.
- Google (Google Ads): measuring our ads, only if you accept advertising cookies.
- Meta Platforms Ireland Limited (Meta Pixel): measuring our ads on Facebook and Instagram, only if you accept advertising cookies.
- Google Ireland Limited and Google LLC (Google Analytics): measuring visits to our public pages, only if you turn on Analytics cookies.
- European Commission (VIES): VAT number checks for business purchases.
26. Where data is stored and transfers outside the EEA
Our providers store data here:
- Railway: the server and database, in the Netherlands.
- Vercel: the website runs in France. Vercel also delivers pages and images from servers around the world, near each visitor.
- Cloudflare (R2): photos, videos and other files, in Europe.
- Brevo: emails and the newsletter list, in the EU.
- Stripe: payments, through Stripe Payments Europe in Ireland.
- Sentry: error reports, in Germany.
Some data may still leave the European Economic Area (EEA):
- Railway, Vercel, Cloudflare and Sentry are US companies, and their staff may access data from the United States. Stripe also shares payment data with Stripe, Inc. in the United States. These transfers rely on the European Commission's Standard Contractual Clauses in each provider's data processing terms.
- Google may process sign-in, Google Ads and Google Analytics data in the United States, and Apple may process sign-in data there. Google LLC and Apple Inc. are certified under the EU-US Data Privacy Framework, and Google's data processing terms also include the Standard Contractual Clauses.
- Meta may process Meta Pixel data in the United States. Meta Platforms, Inc. is certified under the EU-US Data Privacy Framework.
27. How long we keep data
- StoryWalls and content: while coverage runs. When a StoryWall's coverage ends or it is deleted, Hosts have 30 days to download their files, and then the event, its content and files are deleted for good.
- Content you delete: removed from the StoryWall at once. Photo and video files are deleted for good within about one day.
- Account: until you delete it (see section 28).
- Sign-in sessions: a session lasts up to 30 days. Its IP address and browser details are deleted 30 days after it ends.
- Where your sign-up came from: with the account, and deleted with it.
- Campaign link counts: the daily code and the result made from your IP address and browser are deleted after the day ends. The counts, which do not identify anyone, are kept for our statistics.
- Purchase records: for as long as tax law requires. After an event is deleted we keep only its title with the purchase.
- The campaign link saved with an order: with the purchase record.
- Errors: error reports, speed data and Sentry replays are deleted after 90 days.
- Problem reports: what you send, with any screenshot, is deleted after 90 days.
- Server logs: deleted after 30 days.
- Backups: database backups are kept for up to 3 months. Data deleted from StoryWall stays in them until they are deleted.
- Google Analytics: Google keeps the visit data linked to the Analytics cookies for 14 months, then deletes it. Reports that show only totals, such as visits per month, may be kept longer.
- Moderation and administrator logs: not deleted, since they are evidence for decisions that may be challenged.
28. Deleting your account and content
You can delete your own content and your account in the app. You delete your account from your profile, by confirming a code we email you. If you are the main Host of a StoryWall, first delete it or hand your role to a Co-host (see section 29).
When you delete your account:
- you are signed out at once and can no longer sign in,
- you are removed from the newsletter,
- after 30 days we erase your name, email and profile photo,
- what you posted in other people's StoryWalls stays and is shown as "Deleted user",
- we keep purchase records for as long as tax law requires (see section 27).
Content that stays is not necessarily anonymous: a photo may still show you. You can delete it before you delete your account.
29. Deleting a StoryWall
The main Host can delete a StoryWall without deleting their account. For 30 days the deletion can be cancelled, and then it is final.
The main Host can hand their role to a Co-host. A StoryWall bought as a gift passes to the recipient when they redeem the gift card, and the buyer stays on as a Co-host.
30. Security
We take technical and organisational measures to protect data. Among them:
- connections use HTTPS only,
- passwords are stored only as hashes,
- sign-in cookies cannot be read by page scripts,
- one active session per account,
- files are kept in private storage and shown through temporary links,
- each member sees only the StoryWalls they belong to,
- deleting a StoryWall is confirmed with a code sent by email.
31. Minimum age
StoryWall is for people aged 18 or over, and the same applies to QR Photo Upload. We do not ask for a date of birth.
This does not mean children cannot appear in photos or videos of family events uploaded by adults.
32. Cookies
The cookies and similar technologies we use are described in the Cookie Policy.
33. Your rights
Depending on the case, you have the right to information, access, correction, erasure, restriction of processing, portability and objection. Where processing relies on consent, you can withdraw it.
These rights are not absolute. In some cases the law requires or allows us to keep certain data.
34. How to use your rights
Write to support@storywall.gr. We may ask for details to confirm your identity before we act.
35. Complaints
If you think the processing of your data breaks the law, you can complain to the Hellenic Data Protection Authority (www.dpa.gr).
36. Automated decisions
We do not make decisions based solely on automated processing that have legal or similarly significant effects on you. The automatic checks on withdrawals (section 19) only delay a refund for a human to review.
37. Third-party content and links
StoryWall shows Spotify and YouTube previews inside the page for song suggestions, and a Google Maps map for a schedule item's venue. When you open those pages, your browser connects to these services, which process data under their own policies.
The same applies when you follow a link to a third-party service or use the Gift Account details at your bank.
38. Changes to this Policy
We update this Policy when the service, our providers or the law change. Each version is dated at the top of the page. For material changes we let you know.
39. Contact
For any question about personal data, write to support@storywall.gr or to Thessaloniki 54639.