Privacy Policy
Amore Invite (https://amoreinvite.com) lets couples build an interactive wedding invitation website and collect RSVP replies from their guests. This policy explains what personal data is processed, why, who else sees it, and what your rights are. It applies to two groups of people: customers (the couple who buy and use the service) and guests (people who open an invitation and reply to it).
1. Who is responsible
Customer account data — we are the controller: [Operator legal name — TODO], [Operator address and registration number — TODO]. Contact for all privacy matters: [contact e-mail — TODO].
Guest RSVP data — the couple who created the invitation decide why and how their guests’ replies are used, so the couple is the controller of that data and we process it on their behalf, only to provide the service.
2. What we collect and why
| Data | Why (legal basis) |
|---|---|
| Customer e-mail address (sign-in, order and activation e-mails) | To provide the service you bought (contract) |
| Order data: plan, payment session reference, activation code. We never see or store your card number — payment is handled by Stripe. | Contract; keeping accounting records (legal obligation) |
| The invitation content you enter: names, wedding date, venues and addresses, story, schedule, dress code and Guest Dress Colors, music link, photos and videos you upload | To build and publish your invitation (contract) |
| Guest RSVP replies: name, attending yes/no, party size, number of children, meal preference, dietary needs, accommodation need, and an optional note | Carrying out the couple’s instructions (we are their processor) |
| Simple usage events about an invitation (for example: preview viewed, shared, RSVP submitted) with no free text and no personal identifiers | Improving the service and showing the couple how their invitation is used (legitimate interest) |
| Technical data: your IP address is used briefly to limit abuse (for example repeated RSVP submissions) and appears in our hosting provider’s standard server logs | Security and preventing abuse (legitimate interest) |
Guests may write dietary needs or notes that reveal health or religious information. Guests should share only what they are comfortable with; the couple should use it only to plan the event.
We do not sell personal data, and we do not use advertising or third-party tracking cookies.
3. Cookies
We use only strictly necessary cookies: one that keeps you signed in, and one that carries your activation code between the activation page and your account. They do not track you across websites, so no cookie banner is required.
4. Who else processes data for us
- Supabase — database, sign-in and file storage (our project runs in the EU).
- Vercel — website hosting and delivery.
- Stripe — payments.
- Resend — sending sign-in and order e-mails.
- OpenAI — only if a customer uses the optional AI wording feature. What is sent is the couple’s own invitation details (names, venues, story text, and similar); guest RSVP data is never sent.
Some of these providers are based in, or may process data in, the United States. Where personal data leaves the EU/EEA it is protected by the provider’s approved safeguards, such as the EU Standard Contractual Clauses or the EU–US Data Privacy Framework. We share data with authorities only when the law requires it.
5. Who can see an invitation and its replies
A published invitation is visible to anyone who has its link (the couple decides who receives it). RSVP replies are visible only to the signed-in customer who owns the invitation, in their guest dashboard.
6. How long we keep data
We keep invitation and guest data while the invitation is active, and delete it when the customer deletes the invitation or asks us to. Order records are kept as long as accounting law requires. If we introduce a time limit on hosting, we will tell customers well in advance and allow them to export their guest list.
7. Your rights
You may ask us for access to your data, correction, deletion, restriction, a portable copy, or object to processing based on legitimate interest, and withdraw any consent you gave. Write to [contact e-mail — TODO]; we answer within one month. Guests can also ask the couple who invited them, since they control the reply data. You may complain to the Data State Inspectorate of Latvia (Datu valsts inspekcija, dvi.gov.lv) or your local data protection authority.
8. Security
Traffic is encrypted (HTTPS), access to each customer’s data is restricted to that customer at the database level, and secrets are kept out of the code. No system is perfectly secure; if a breach affects you we will notify you and the authority as the law requires.
9. Children
The service is for adults planning a wedding. We do not knowingly collect data directly from children; a reply may state how many children are attending but not their names.
10. Changes
We will update this page when our practices change and show the date at the top.