Privacy Policy

The data controller is Jiří Pařízek, a sole trader registered in the Czech Trade Licensing Register, company ID (IČO) 11725851, registered seat Mlýnská 218/50, 602 00 Brno – Trnitá (“we”). We build and run the Portál Svatebčana wedding app for Android, iOS and the web at app.portalsvatebcana.cz.

For anything concerning personal data, write to hello@parez.dev.

The app is multi-tenant: every wedding has its own separate data, and the content is entered by the wedding couple. What the couple records about you, and who they show it to, is their decision; we process it on their behalf and provide the technical platform. To exercise your rights regarding one specific wedding, contact that couple, or write to us and we will put you in touch.

This policy covers the Portál Svatebčana mobile and web app, and the marketing site at portalsvatebcana.cz.

You do not create an account and you do not choose a password. You sign in with a six-character code from your paper invitation, or with a link that carries the code. One code belongs to one guest at one wedding.

So that you are not asked for it on every launch, the app stores the code on your device. The code is the only credential — whoever has it can open that wedding. Treat it like a password, and on a shared device sign out when you are done (Profile → Sign out), which erases the code from the device.

We use no Firebase Authentication or other sign-in service for guests, so no persistent user account exists that could link you across weddings.

a) Entered about you by the couple — first and last name, the invite code, optionally an e-mail address, your table number and seat, the room assigned to you, whether you may bring a guest, and whether you may remove song requests.

b) Entered by you in the app — whether you are attending, the name of your plus-one, whether you are staying overnight, your choice of accommodation, dietary preference, allergies and food restrictions, and answers to any extra questions the couple defines (the couple chooses those, so the content can be any free text).

Allergy information can reveal something about your health and is therefore a special category of personal data under the GDPR. Filling it in is entirely optional — you may leave the field empty and tell the couple another way.

c) Content you upload — photos in the wedding gallery and in the photo bingo, their captions, song requests, and votes on other guests’ requests. Each item records which guest created it and when, and several of them display your name to the other guests.

d) Technical data — if you allow notifications, we store a Firebase Cloud Messaging registration token together with the platform (android, ios, web) and your name, so we can remind you about an upcoming part of the programme. The app also keeps the invite code, the wedding identifier and your appearance settings in the device’s own storage, and caches the data it has loaded so it keeps working without a signal.

e) What we never collect — the app contains no analytics, advertising or crash-reporting SDK. We collect no advertising identifiers, do not track your location, do not read your contacts or calendar, set no cookies, and build no profiles or automated decisions. On Android the app asks only for internet access and notification permission; you pick photos through the system photo picker, so the app never gets access to your whole gallery.

You can withdraw consent at any time — by turning notifications off in your device settings, by clearing the value in the app, or by writing to hello@parez.dev. Withdrawal does not affect processing carried out beforehand.

We do not sell personal data and never use it for advertising. It reaches only these recipients:

• The wedding couple and anyone they authorise — their admin dashboard shows every detail about their guests, including your answers, allergies, photos and song requests, and lets them export it.
• Other guests at the same wedding — the gallery, photo bingo, song requests and seating plan are shared. Your name is shown next to your photos, requests and votes.
• Google Ireland Limited / Google LLC — the technical backbone: Cloud Firestore database, Cloud Storage, Firebase Cloud Messaging for notifications, Cloud Functions and hosting. Data is processed in Google’s infrastructure; transfers outside the EU rely on the European Commission’s standard contractual clauses.
• Google Photos — if the couple connects their wedding to a Google Photos album, then alongside the resized copy kept in the app we also send the original full-quality photo, including its metadata, which can carry the capture time and, for camera photos, the location, and we attach your name to it. The album belongs to the couple and we have no access to it. If you would rather not, do not upload the photo, or strip its metadata first.
• Spotify AB — when you search for a track, your search term is sent through our server to Spotify’s public API. It carries neither your name nor your code. Album artwork is loaded straight from Spotify’s servers, so they always learn your IP address and browser or device type when the request list is displayed.
• Vercel Inc. — hosting for the marketing site portalsvatebcana.cz.
• Web3Forms — only the contact form on the marketing site, which sends the name, e-mail and message you type into it. The app does not use that form.

We may also disclose data where the law requires it or a public authority asks for it within the limits of the law.

The web version at app.portalsvatebcana.cz sets no cookies. It keeps the invite code, the wedding identifier and your appearance settings in the browser’s localStorage, and a local copy of loaded data in IndexedDB so it works offline. Both are removed by signing out or by clearing site data in your browser.

It also registers a service worker, which is what delivers notifications while the page is closed.

The loading screen of the web version fetches two typefaces from Google Fonts and the Firebase library from Google’s servers, which tells Google your IP address and browser details when the page loads. The mobile apps download no fonts or scripts — everything is bundled inside them.

Wedding data is kept until the couple deletes the wedding. Deleting it removes the guest records, photos, song requests and photo bingo. There is no automatic deletion deadline — a wedding gallery is usually a keepsake that couples and guests want to reach years later.

The invite code and settings stored on your device disappear when you sign out or uninstall the app. The notification token is deleted when you sign out.

We keep database backups against disaster. A backup may, for a limited time, still contain data that has already been deleted in the app.

Under the GDPR you have the right to:

• know what data we hold about you and receive a copy,
• have inaccurate data corrected,
• have your data erased,
• have processing restricted,
• object to processing based on legitimate interest,
• receive your data in a portable format,
• withdraw any consent you have given,
• lodge a complaint with the supervisory authority, which is the Úřad pro ochranu osobních údajů (Czech Data Protection Authority), Pplk. Sochora 27, 170 00 Praha 7, uoou.cz.

The app has no user accounts, so there is no account to close. To have your data removed from a wedding you have two routes:

• Ask the couple who runs the wedding — their dashboard can delete a guest and individual photos.
• Write to us at hello@parez.dev. Include the couple’s names and your own so we know which wedding to look for. We answer within 30 days at the latest and confirm the outcome.

Inside the app you can yourself remove your vote on a song request, turn off the photo bingo reminder, and — by signing out — erase the invite code and the notification token from your device.

The app is not directed at children and we do not target them with content or advertising. Where a child is a wedding guest, their details are entered by the couple in agreement with the child’s legal guardian. If we learn that we hold data about a child under 15 without a guardian’s consent, we delete it.

All traffic between the app and our servers is encrypted with HTTPS. Data is stored in Google’s infrastructure, which also encrypts it at rest. The admin dashboard is protected by a username and password.

A guest’s access to a wedding is protected by the invite code alone. That is a deliberate trade-off — wedding guests should not have to create accounts. It does mean that anyone who obtains the code or the sign-in link can see that wedding’s content, so do not publish or forward it.

No security is absolute. If you find a vulnerability, please tell us at hello@parez.dev.

We may update this policy, for instance when a feature is added or a provider changes. The current version always lives at this address, with the date of the last change at the top. Your couple will tell you in the app about any substantial change.