Privacy Policy
Last updated: October 18, 2026
This policy explains what personal data RSVBee collects, why, and the choices you have. It covers two groups of people: account holders, usually the couple or their planner, and guests, who receive an invitation but never sign up.
1. Who is responsible for your data
A3 Group LLC ("A3 Group", "we", "us"), 30 N Gould St, Ste R, Sheridan, WY 82801, USA (a3grouphq.com), operates RSVBee and is the controller of the personal data described in this policy.
Questions or requests: info@myrsvbee.app.
2. What we collect
| Category | Examples | Where it comes from |
|---|---|---|
| Account data | Email address, password (stored hashed by Amazon Cognito), sign-in records | You, or Google if you choose to sign in with Google |
| Wedding pages | Couple names, date, venue and location, your story text, dress code, and any photos or videos you upload or link | You |
| Guest data | Name and email address of each household, invitation and reminder status, whether each guest is attending, plus-ones, meal choices and dietary notes, and when they replied | The account holder adds names and emails; guests give their replies themselves |
| Billing data | Plan purchased, amount, Stripe payment and invoice references, billing name and address | You and Stripe. We never receive or store full card numbers. |
| Usage and device data | IP address, browser and device type, request, error and email-delivery logs | Collected automatically when you use RSVBee |
| Communications | Support requests and feedback | You |
Dietary notes can sometimes reveal health information or religious belief. We collect them only so the couple can plan the meal, and we use them for nothing else. We do not intentionally collect any other sensitive data.
3. How we use it and our legal bases
| Purpose | Legal basis (EU/UK GDPR) |
|---|---|
| Create and run your account and wedding page | Performance of our contract with you |
| Send invitations and reminders to guests, and record their replies | Contract with the account holder; our and the account holder's legitimate interest in delivering an invitation the guest was meant to receive |
| Process payments and send receipts and invoices | Contract; legal obligation for tax and accounting records |
| Provide support and send essential service messages | Contract; legitimate interests |
| Keep RSVBee secure, prevent fraud and abuse, fix bugs | Legitimate interests |
| Understand how RSVBee is used, with analytics, and improve it | Legitimate interests for cookieless analytics; your consent for analytics cookies |
| Comply with law and respond to lawful requests | Legal obligation |
Account holders are responsible for having a lawful basis to share their guests' details with us. We do not sell personal data, we do not share it for cross-context behavioural advertising, and we never use guest data for marketing, ours or anyone else's.
4. Who we share it with
We share personal data only with service providers that help us run RSVBee, under contracts that limit their use of it to our instructions:
- Amazon Web Services: hosting, database, file storage, sign-in (Amazon Cognito) and email delivery (Amazon SES).
- Stripe: to process payments, issue invoices and prevent fraud.
- Google: sign-in if you choose it, and maps and address search when a wedding page shows a venue.
- YouTube or Vimeo: only if an account holder adds one of their videos to a wedding page.
- PostHog: product analytics, hosted in the US. It receives the pages viewed, links clicked (not their text), your browser and device type, approximate location, and your IP address. Unless you accept analytics cookies, it tells visits apart without storing anything on your device. Invitation links are stripped of their private token before anything is sent, and we do not record sessions. If you accept analytics cookies and sign in, your visits are linked to your account by an internal ID (never your email or name).
Guests' replies are shared with the account holder who invited them, because that is what an RSVP is for. Anyone holding an invitation link can see that invitation and the wedding page it belongs to.
We may also disclose data to comply with the law, to protect the rights and safety of our users or others, or as part of a merger, acquisition or sale of assets, in which case this policy continues to protect your data.
5. Where your data is stored and international transfers
RSVBee's database, files and email sending run in the AWS Europe (Frankfurt) region. A3 Group is based in the United States, and some providers, such as Stripe and Google, may process data in the US and other countries. When we transfer personal data out of the EU, the UK or Switzerland, we rely on adequacy decisions such as the EU–US Data Privacy Framework where the recipient is certified, or on the European Commission's Standard Contractual Clauses and the UK addendum.
6. How long we keep it
- Wedding pages, guest lists and replies: until the account holder deletes them or closes their account. Deleting a guest removes their record straight away.
- Account data: while your account is open. After you close your account, we delete or anonymise it within 30 days, except copies in backups, which are overwritten within 90 days.
- Billing and transaction records: as long as tax and accounting laws require, usually up to 7 years.
- Logs: usually up to 12 months, longer only to investigate security incidents.
- Support messages: up to 3 years after the conversation ends.
7. Your rights
Depending on where you live, you may have the right to access, correct, delete or export your personal data, to object to or restrict certain processing, and to withdraw consent at any time. Account holders can do much of this from the dashboard, including exporting and deleting guest lists. For anything else, email info@myrsvbee.app. We will reply within one month, or the time your local law requires.
If you are a guest and want your details removed from a wedding list, you can ask the couple who invited you, or email us and we will remove your record.
If you are in the EU or UK, you can also complain to your local data protection authority.
US residents: residents of California and other US states with privacy laws can request access to, correction of, or deletion of their data, and will not be treated differently for doing so. We do not sell or share personal data as those laws define it.
8. Cookies and similar technologies
RSVBee does not use advertising cookies, and we do not track you across other sites. Our analytics (PostHog, see section 4) are cookieless unless you accept analytics cookies in our cookie notice; say no and they store nothing on your device. . Besides that optional cookie, we use only the storage needed to make the Service work:
| What | Why | How long |
|---|---|---|
| Sign-in tokens (Amazon Cognito), kept in your browser's local storage | Keep you signed in to the dashboard. Guests are never signed in. | Until you sign out, or up to 30 days |
| Short-lived session flags and cookies set during sign-in | Complete sign-in with Google securely | Until you close the tab |
| Your cookie notice choice, kept in local storage | So we do not show you the notice again | Until you clear your browser data |
| Analytics cookie (PostHog), only if you accept it | Recognise a returning visitor so our usage numbers are accurate | Up to 1 year, or until you change your choice |
Content from other services. Wedding pages can show a Google map of the venue, fonts from Google Fonts, and a video from YouTube (in its privacy-enhanced mode) or Vimeo. To display these, your browser connects to those providers, which receive your IP address and may set their own cookies under their own privacy policies. The dashboard also uses Google's address search. You can block third-party cookies in your browser settings; RSVBee will keep working.
9. Security
Data is encrypted in transit and at rest on AWS. Each wedding page and guest list can be changed only by the account that created it. Invitation links contain a random, unguessable token; anyone holding the link can view and answer that invitation, so guests should not forward theirs. No system is perfectly secure; if a breach affects your personal data, we will notify you and the authorities as the law requires.
10. Children
Accounts are not available to children under 16, and we do not knowingly collect their personal data from them. Couples sometimes add children to an invitation as part of a household; we handle those names only to deliver that invitation. If you think a child has given us personal data, contact info@myrsvbee.app and we will delete it.
11. Changes to this policy
We may update this policy as RSVBee changes. For material changes we will notify account holders by email or in the Service before they take effect. The date at the top shows when it was last updated.
RSVBee is operated by A3 Group LLC, 30 N Gould St, Ste R, Sheridan, WY 82801, USA. Questions: info@myrsvbee.app.