Who this covers and our role
This policy covers this website (noiva.ai), the planning app at app.noiva.ai, and each wedding’s website, guest portal and personal guest links on its own address (for example camila-mateo.noiva.ai). “noiva”, “we” and “us” mean the people who run the service.
- Your account. For the details you give us to sign up and sign in, we decide how they are used, and this policy explains how.
- What you put into a wedding. The couple or planner who runs a wedding decides what goes into it, such as the guest list, and who on their team can see it. We store and process that information on their behalf and only to run the service for them.
If you are a guest and want your details changed or removed, the couple or their planner can do it in a moment. You can also write to us at [email protected] and we will help.
Information we collect
When you sign up and sign in
- Your email address and, if you add them, your name and profile color.
- Your display settings (light, dark or system theme) and app preferences, and when you last signed in.
- At sign-up: the account and wedding name, the plan you picked and roughly how many guests you expect.
- For planner accounts: the account name, the people on your team and their roles.
- For a planner account opened through another planner’s referral link: which account referred it and the referral’s status. The referring planner sees only your account’s name (as you entered it at sign-up) and that status, never your weddings, your team or any email address.
Sessions and security
- We never ask for a password. We email you a sign-in link, and store only a scrambled (hashed) form of it, never the link itself.
- For each signed-in device we keep the browser’s description (user agent), its IP address and when it was last used, so you can see your sessions in your profile and sign any of them out.
- IP addresses are also used to limit repeated requests, and appear in our server logs.
What you plan
Everything you and your team enter: guests and households, seating, menus and meal choices, vendors, payments and budget, tasks, the schedule, and your wedding website’s text and links. Each wedding also keeps a log of recent changes (who changed what), which its team can see. Only the newest 5,000 entries are kept.
The noiva assistant
When you use the assistant, we keep your conversations in your account: your messages, its answers and the changes it made or proposed. Only you can see your conversations, and they are not part of the wedding’s backup. We also record how many AI credits each answer used and who asked, to charge them to the account that owns the wedding.
Payments
Payments go through Stripe’s own checkout and billing pages. We never see or store your card number: we keep only Stripe’s customer reference for your account and the state of your plan.
What we don’t collect
There are no analytics, advertising or tracking scripts on this site, in the app or on wedding websites, and we don’t sell or rent anyone’s information.
How we use it
- To run the service: sign you in, keep your wedding in sync for everyone on the team, and show guests their invitation.
- To send the emails the service needs: sign-in links, invitations, and a notice a week before a wedding is archived.
- To bill paid plans and apply their limits.
- To answer your questions in the noiva assistant and make the changes you ask it for.
- To keep the service secure, prevent abuse and fix problems.
- To answer you when you write to us.
We don’t use your wedding’s content to advertise to you or to anyone on your guest list, or to train AI models.
Guests’ information
A guest list can hold names, nicknames, email addresses, phone numbers, which side a guest is on, whether they are an adult or a child, RSVPs, meal choices, and notes on dietary needs, allergies and accessibility. Households can hold a postal address for invitations. Some of this, like allergies or accessibility needs, is sensitive, so couples and planners should add only what they need to host their guests well.
Guests never need an account. Each household gets a personal link to RSVP and update their own details; we store only a hashed form of that link, and the couple can turn it off at any time. When a guest opens their link we keep the same session details as for team members (browser, IP address, last use).
If a planner connects a webhook, details of changes in a wedding, which can include guest information, are sent to the address the planner chooses, and a log of those deliveries is kept in the wedding.
Sharing and service providers
Inside a wedding, information is visible to its team according to their roles, and to guests only as far as their own household. Outside it, we share information only with the companies that help us run noiva, only for that purpose, or when the law requires it.
| Provider | What they do for us |
|---|---|
| DigitalOcean | Hosting: the servers and the database that store everything in noiva. |
| Cloudflare | Domain names, secure connections and protection in front of every noiva address. |
| Resend | Delivering our emails (sign-in links, invitations, notices), sent from [email protected]. |
| Stripe | Payments, invoices and subscription management for paid plans. |
| Amazon Web Services | Storing the service’s own configuration secrets. No user data is kept there. |
| OpenRouter | Routing the noiva assistant’s requests to the AI model provider of the level you chose. |
| AI model providers (through OpenRouter) | Running the models that write the assistant’s answers. Today these are GMICloud (Fast), Google (Smart) and Anthropic, directly or through Amazon Web Services, Google Cloud or Microsoft Azure (Expert). |
To answer, the assistant sends OpenRouter your message, the conversation so far and the wedding information it needs, which can include guests’ details. Every request tells OpenRouter to use only providers that don’t collect that data to store it or to train their models. If you don’t use the assistant, nothing is sent to OpenRouter.
An image a couple links to from elsewhere, such as their wedding’s cover photo, loads from the site that hosts it, and that site sees the visitor’s IP address as usual.
Cookies and local storage
We use only what the service needs to work. Because none of it is for tracking, there is no cookie banner.
- Sign-in cookie (
__Secure-noiva_session): keeps you signed in on the app and on your weddings’ addresses, for 30 days after you last used noiva. Page scripts can’t read it. Because it is set for noiva.ai and its subdomains, your browser also sends it when you visit this website, which doesn’t use it. - Guest cookie (
__Host-noiva_guest): keeps a guest’s personal link working on that one wedding’s address only. - Browser storage: your light or dark theme choice (on this website too), the account you last chose on this device, recent searches, whether the side menu is collapsed, and a random id for each open tab. These stay in your browser; the only one we receive is the tab id, which keeps your open tabs in sync and identifies the tab, not you.
- Referral code (
wp.ref, browser storage on this website and in the app): when you arrive through a planner’s referral link, its code is kept for 30 days so the sign-up can credit that planner. It names the referring planner’s account, not you, and leaves your browser only when you sign up. The “Planned with noiva” link on wedding pages carries such a code, never anything about the guest who follows it.
Security
- Every connection is encrypted (HTTPS).
- Each wedding is kept apart at the database level, so one wedding’s data can’t be read from another.
- No passwords to leak: sign-in links expire after 15 minutes, and only their hashes are stored.
- You can review your signed-in devices and sign out of all others from your profile.
No system is perfectly secure. If something goes wrong that affects your information, we will tell you.
How long we keep it
- Sessions end 30 days after their last use and are then deleted, as are sign-in links once they expire.
- A wedding is archived 60 days after its date (or 18 months after it was activated, when it has no date). Archived weddings are read-only and kept so you can look back at them and download them. A couple can always open their own; a planner can while their workspace subscription is active. Wedding websites stay up for 12 months after the date.
- When an owner deletes a wedding, everything in it is deleted from the service.
- Conversations with the assistant are kept until you delete them or the wedding they belong to is deleted. The record of AI credits used stays with the account’s billing.
- Your account stays until you ask us to close it.
Your choices: export and deletion
- Export: download a full backup of a wedding, the guest list as CSV, or any report as CSV, from the app.
- Correct: change your name and preferences in your profile; change wedding details in the wedding itself.
- Delete a wedding: its owner can delete it from the app (you’ll be asked to type its name to confirm).
- Close your account, or anything else: to close your account, get a copy of what we hold about you, or object to how we use it, write to [email protected]. We may need to confirm the request comes from you.
Where your data is stored
noiva runs on servers operated by the providers listed above, which may be in a different country from where you live. We choose providers that protect the information they handle for us.
Children
noiva is for adults planning a wedding, and accounts are not meant for children. A guest list may include children as guests; that information is added by the couple or planner, who are responsible for it.
Changes to this policy
When we change this policy we update the date at the top. If a change matters to how your information is used, we will tell account holders by email before it takes effect.
Contact
- Privacy questions and data requests: [email protected]
- Legal notices: [email protected]
- Everything else: [email protected], and we reply within 24 hours.