1. Who is responsible
- For your account and your own details: SayJa (see the Terms), contact ryan@sayja.se. We are the "controller", which means we decide why and how that data is used.
- For your guests' details: you (the couple) are the controller and SayJa is your processor. Section 4 explains.
2. What data we hold
| Whose data | What we hold | Where it comes from |
|---|---|---|
| You and the people you invite (owner, partner, planner, helper, viewer) | Name, email, login, role, language, country, who changed what (activity log), technical data (IP address, browser, error logs) | You |
| Your wedding | Names of the couple, date, venue, schedule, budget, notes, website content, plan | You |
| Your guests | Name, email and/or phone, household, postal address if you ask for it, tags, plus-ones and children (name or slot, kids' meal), reply per event, meal and dietary needs, table, arrival and travel details, song requests, optional profile photo | You and your guests' own answers |
| Messages and files | Chat messages, photos, documents and voice notes in the guest app, and messages you send to guests. For each message: whether it was delivered and, only for guests who agreed, when it was opened or a link clicked | You and your guests |
| Location (only if you switch the feature on) | A guest's shared location, off by default, per guest, time-limited and pausable | The guest |
| Payments | Name, email, country, amount, date, VAT, and your VAT number and address if you give them. Stripe handles your card; we never see the number | You, through Stripe |
| Support | Your question, a reference number, and page, plan, guest count and browser only if you tick the box. Never guest names | You |
| AI writing help | The text you give it and the draft it returns | You |
Dietary and access needs are extra sensitive. Things like halal, kosher, coeliac or wheelchair access can reveal religion or health, which the law calls "special category" data. So we store only what the caterer needs, guests agree to it when they answer, it is used only for catering and access planning, and only people who need it can see it. We never use it in analytics.
Children: we store the minimum, a name or slot and a kids' meal flag. Children have no accounts, and photos of children need a guardian's consent.
3. Why we may use data (legal basis)
The law says we need a reason for each use. Ours:
| What we do | Whose data | Reason (legal basis) |
|---|---|---|
| Run your account and wedding, send messages you set up | You and helpers | Contract: you asked for it |
| Collect RSVPs and use guest answers for your wedding | Guests | The couple's reason, on their instructions (see section 4) |
| Use dietary and access needs for catering | Guests | Explicit consent |
| Show photos of people in the guest album | Guests | Consent: guests can remove themselves and delete their own uploads |
| Take payment and keep receipts | You | Contract, and legal duty (accounting law) |
| Service emails: receipts, deletion warnings, security | You | Contract; this is not marketing |
| Tell the couple when a guest opens a message or clicks a link | Guests | Consent: guests choose, can say no, and can change their mind at any time |
| Keep SayJa secure, stop abuse, fix bugs | Everyone | Legitimate interests (keeping the service safe) |
| Answer your support questions | You | Contract |
| Marketing to you | You | Only with your consent |
4. Guests' data: the couple is in charge
When a guest answers an RSVP, the couple decides what to ask and what to do with it. SayJa stores it and runs the tools on the couple's instructions. In legal terms the couple is the controller and SayJa is the processor. As processor, we promise:
- We use guest data only to run the couple's wedding, on their instructions.
- Our people who can reach it are bound by confidentiality and only see it when needed.
- We keep it secure: encryption in transit and at rest, access controls and backups.
- We use only the providers in section 6. We email the owner at least 30 days before adding or swapping one, and the couple can object.
- We help the couple answer guests' requests, and forward any guest request that reaches us within 5 working days.
- We tell the couple without undue delay, and within 48 hours, if we learn of a breach affecting guest data.
- When the wedding is deleted, the guest data goes with it (section 8). The couple can download it first.
- We give the couple the information they need to check we follow this, and allow reasonable checks, for example by questionnaire.
- We never sell guest data, use it for advertising, or use it to train AI models.
- We move data outside the EU/UK only with the safeguards in section 7.
Couples: tell your guests what you do with their details (we give you a short notice below), ask only for what you need, and use it only for the wedding.
We are a controller ourselves for a small amount of guest data: security logs and what we need to defend a legal claim.
5. For guests: the short version
6. Who else handles your data
These companies process data for us. We have a data processing agreement with each one.
| Provider | What for | Where | Status |
|---|---|---|---|
| Supabase | Database, login, file storage | EU | In use |
| Vercel | Runs the app and wedding website | EU region | In use |
| [Email provider] | Account emails and guest messages | [EU region] | In use |
| [SMS provider] | Text messages to guests | [EU region] | When switched on |
| Stripe | Payments and fraud checks | Stripe's EU entity for EU customers | From launch |
| [Error logging provider] | Finding and fixing errors; personal data removed from reports | [EU region] | In use |
| [AI writing provider] | Drafts text when you ask | [ ] | Later |
Stripe also acts as a controller for its own fraud and legal checks, and its privacy policy applies to that. The AI provider will be named here before the feature is switched on. It will only receive what you choose to send, and we require that it does not train its models on your data. We use no other tools that see personal data, and no advertising or analytics tools.
7. Moving data between countries
We store your data in the EU. UK couples' data stored in the EU is allowed by UK rules, and EU data sent to the UK is covered by the European Commission's renewed UK decision, valid until 27 December 2031.
Some providers are based outside the EU or UK, or their staff can reach data from there (for example a US company). In those cases we rely on approved safeguards: the EU's Standard Contractual Clauses or the EU–US Data Privacy Framework, and for the UK the UK addendum or the UK–US data bridge.
8. How long we keep data
| What | How long | Why |
|---|---|---|
| Wedding, guest details, messages, photos | Until the wedding date, then read-only for 30 days, then deleted | The wedding is over; we keep as little as possible |
| Your account | Deleted with the wedding, or sooner if you delete it | No longer needed |
| Backups | Roll off within 30 days of deletion | Disaster recovery |
| Receipts and accounting records | 7 years after the end of the financial year | Accounting law |
| Support requests | 24 months | To help you again |
| Security logs and activity logs | 90 days | Security |
Receipts hold only your name, email, country, amount, date and VAT, and your VAT number and address if you gave them. They never include your wedding or guest details.
We may keep anonymous numbers (for example, weddings per month) that cannot identify anyone.
9. Your rights
You can ask us to show you your data, correct it, delete it, limit how we use it, move it to another service, or stop a use you object to. If you gave consent (for dietary needs or photos), you can take it back at any time. We make no automated decisions that affect you.
Most of this you can do yourself in the app:
| Button | What it does | Who can use it |
|---|---|---|
| Download my details | A file with your own details and activity: account, role and what we hold about you | Everyone with an account |
| Download everything | The whole wedding: guest list, replies, meals, messages, photos and budget, in common file formats | Owner and partner |
| Delete my account | Removes your login and details. If you are the owner, it also deletes the wedding. Immediate and final | Everyone with an account |
| Delete this wedding | Removes the wedding and all guest data. Everyone loses access. Immediate and final | Owner |
Deleting is final: we ask twice, give a last warning, and ask you to type DELETE and your password. There is no grace period. Receipts are kept as the law requires (section 8). Anything else, email ryan@sayja.se. We answer within one month, free of charge, and may ask you to log in to confirm it is you.
Guests: you can see what the couple sees about you, opt out of the attendee list, choose whether the couple see when you open their messages, remove yourself from photos and delete your own uploads. For anything else, ask the couple first, since they decide how the details are used. Couples can edit or delete a guest at any time. If a guest writes to us, we pass it to the couple within 5 working days.
10. Cookies
SayJa uses essential cookies only: they keep you logged in, remember your language, and protect forms and logins. Stripe's checkout page may set its own cookies to stop fraud. We use no analytics, advertising or tracking cookies, and no social media pixels. In emails to guests who agreed to it, we add a small invisible image and tracked links so the couple can see when a message was opened or clicked. Guests who have not agreed get plain emails with no tracking, and can change their choice at any time. We do not track the couple or helpers this way. Essential cookies do not need your consent, so there is no cookie banner.
11. Keeping data safe
Data is encrypted in transit and at rest, each role sees only what it needs, personal links to guest pages are unguessable and can be revoked, and we back up regularly. If a breach puts your data at risk, we tell you without undue delay and tell the data authority where the law requires, within 72 hours.
12. Complaints
Write to ryan@sayja.se first, and we will reply within 30 days. You can also complain to the data authority:
| Country | Authority | Website |
|---|---|---|
| Sweden | Integritetsskyddsmyndigheten (IMY) | imy.se |
| UK | Information Commissioner's Office (ICO) | ico.org.uk |
| Denmark | Datatilsynet | datatilsynet.dk |
| Norway | Datatilsynet | datatilsynet.no |
You can complain where you live, where you work, or where you think the problem happened.
13. Changes and contact
We post new versions here with the date. For important changes we email you 30 days ahead. Questions: ryan@sayja.se, Buskvägen 3, 281 36 Hässleholm, Sweden.