Privacy Policy

Last updated: 10/26/2026

This Privacy Policy explains what personal data Belour collects, why we process it and what rights you have. It applies to account holders (hosts) and to guests who open an invitation, confirm their attendance or send photos.

1. Data controller

The data controller is KELICODE, obrt za računalno programiranje, vl. Kristijan Kelić, Fra Grge Martića 10, 21210 Solin, Croatia (“Belour”, “we”). For any privacy question or request, write to support@belour.app.

2. Data we process

  • Account data — full name, email address, preferred language (from which we derive your currency), app preferences such as the theme, and your password, which is stored only as a bcrypt hash. If you request a password reset, we store only a hash of the reset link.
  • Invitation content — event details, texts, design, photos you upload and any contact details (phone number or email) you choose to show on the invitation.
  • Guest data — the RSVP answers described in section 4, and guests you add or edit yourself.
  • Guest photos — if the host added guest photos to an invitation: the photos and videos guests send, stored as sent, with a smaller preview, the file name, type and size, the upload time and the name the guest enters, if any. Photos can contain information the guest’s device adds, such as when and where a photo was taken.
  • Expenses — the costs you record in the expense tracker.
  • Payment data — whether an invitation and guest photos have been paid for, and the Paddle transaction IDs. We never receive your card details; Paddle handles the payment.
  • Technical data — your IP address and browser information, which our hosting provider processes to deliver the website and keep it secure. For rate limiting we use a short-lived hash of this data that is held in memory for a few minutes and never stored. When something breaks, we collect error reports that may include your account ID.

3. Purposes and legal bases

  • Providing the service (account, invitations, RSVPs, guest groups, guest photos, expenses, payments) — performance of our contract with you (Art. 6(1)(b) GDPR).
  • Security, abuse prevention and fixing errors — our legitimate interest in a safe, working service (Art. 6(1)(f) GDPR).
  • Anonymous usage analytics — our legitimate interest in improving Belour (Art. 6(1)(f) GDPR); see section 6.
  • Accounting and tax records — legal obligation (Art. 6(1)(c) GDPR).

We do not sell or rent your data, use it for advertising or make automated decisions about you.

4. Information for guests

When you confirm your attendance, the invitation asks for a family or group name, the full name of each guest and, if the host turned them on, whether you need accommodation, whether you want the vegetarian menu, and a note. The host decides which questions to ask and is responsible for the guest list; we store and display your answers on the host’s behalf. Only the host sees your answers. Write in the note only what you want the host to know; if you mention allergies or other health information, it is used only to plan the event. To change or delete your answers, contact the host or us. Your answers are deleted when the host deletes the invitation or their account.

Anyone who has the link can open an invitation. We ask search engines not to index invitation pages.

If the host added guest photos, you can send them photos and videos through the QR code or link they share. You don’t need an account, and your name is optional. We store the files on the host’s behalf; only the host sees them, not other guests. Photos can show when and where they were taken; if you don’t want to share the location, turn it off in your camera settings. The files are permanently deleted 60 days after the event, or earlier if the host deletes them, the invitation or their account. To have a file removed, contact the host or us.

5. Cookies and local storage

Belour only uses cookies and storage that are strictly necessary for the service to work, so we don’t ask for consent:

  • next-auth.* — keeps you logged in (a session of up to 7 days) and protects forms against forged requests.
  • NEXT_LOCALE — remembers the language of the public pages until you close the browser.
  • sidebar_state — remembers whether the dashboard sidebar is open (7 days).
  • Local storage — temporarily keeps the invitation you are editing so the preview can show it. It never leaves your browser.
  • belour_guest_name (local storage) — on the guest photos page, remembers the name you entered so you don’t have to type it again. It stays in your browser until you clear it.

We do not use cookies for tracking or advertising.

6. Analytics

On public pages and invitation pages we use Umami Analytics (cloud version) to count page views and clicks. Umami does not use cookies, does not identify you and does not follow you across other websites. It processes your browser type, device, country, the page you came from and the pages you view, and shows us only aggregated statistics.

7. Who processes data for us

We use the following service providers to run Belour. They process data only on our instructions (processors):

  • Vercel — hosting and delivering the website
  • Neon (neon.com) — storing the application database on AWS in Frankfurt (eu-central-1 region)
  • Cloudinary — storing and delivering the photos you upload
  • Cloudflare (R2) — storing guest photos and videos in the EU
  • Resend — sending account emails (welcome, password reset, guest photo reminders, security and legal notices) from AWS in Ireland (eu-west-1 region)
  • Sentry — error monitoring
  • Umami — anonymous analytics

Paddle (Paddle.com Market Limited) sells Belour to you as our reseller and Merchant of Record. Paddle processes payment, billing and tax data as an independent controller under the Paddle Privacy Policy.

We may also disclose data when the law requires it.

8. Transfers outside the EU

Some of these providers are based in the United States. When data leaves the European Economic Area, the transfer relies on the EU–US Data Privacy Framework or on the European Commission’s Standard Contractual Clauses.

9. How long we keep data

  • Account data, invitations, the photos you upload, guest data and expenses — for as long as your account exists. You can delete invitations and guests yourself at any time; deleting an invitation also deletes every photo uploaded for it. Everything else is deleted with your account (see section 11).
  • Guest photos and videos — until 60 days after the event, then they are permanently deleted. The host can delete them earlier, and they are deleted with the invitation or the account.
  • Error reports — up to 90 days.
  • Password reset requests — 30 days.
  • Copies of the emails we send you and their delivery status — kept by Resend for 30 days.
  • Payment and invoice records — kept by Paddle for as long as tax law requires.

10. Your rights

Under the GDPR you have the right to:

  • access — get a copy of the data we hold about you
  • rectification — have inaccurate data corrected
  • erasure — have your data deleted
  • restriction — have processing limited, for example while a complaint is being resolved
  • portability — receive your data in a machine-readable format
  • objection — object to processing based on our legitimate interest

To exercise a right, write to support@belour.app. We reply within one month. You can also lodge a complaint with the Croatian data protection authority, Agencija za zaštitu osobnih podataka (AZOP), or with the supervisory authority in the EU country where you live.

11. Deleting your account

You can delete your account yourself at any time in the app, on the Security page, by confirming with your password. Deletion happens immediately and cannot be undone: we delete your account, invitations, uploaded photos, guest photos and videos, guest data and expenses, and your published invitations stop being available. The exceptions are payment records, which Paddle keeps, and error reports and copies of sent emails, which are deleted within the periods in section 9.

12. Security

We protect your data with encrypted connections (HTTPS), hashed passwords and access limited to what is needed to run the service. No system is completely secure, so please use a strong password that you don’t use anywhere else.

13. Changes to this policy

When we change this policy, we update the date at the top of this page. We will tell you about significant changes by email before they take effect. If this policy is translated, the Croatian version prevails in case of any discrepancy.