Privacy Policy

Aurea is a wedding planning application, available at planwithaurea.com. This policy explains how we handle information about the people who use Aurea and the people invited through it. For any privacy question, write to ola@planwithaurea.com.

Aurea is an early-stage project based in Maputo, Mozambique. If and when the responsible entity changes, this page will be updated before that change takes effect.

We store only what the application needs in order to work. Specifically:

Your account

Your email address and, if you sign up with a password, an encrypted version of that password — never the password itself. If you sign in with Google, we receive your email, name and profile picture from Google, and we never have access to your Google password.

Your wedding

Names, date, location, venue, budget estimates, priorities, and the presentation preferences you choose.

Guests

The names you enter, and optionally phone numbers and notes, grouped into invitations and households. Also the replies guests give to your invitation.

Budget and suppliers

Expenses, recorded payments, the suppliers on your team and the contact details you save.

Documents and photographs

The files you upload — contracts, receipts, invitation photographs.

Tasks and the day

Your planning tasks and the run of show for the wedding day, including who you name as the person to look for at each moment.

Notifications

A record of what has happened in your account, so we can show you what changed.

We do not run advertising, we do not build behavioural profiles, and there is no third-party analytics tool installed in this application at all.

Most of the personal information in Aurea does not belong to the person who typed it. When a couple enters their guest list, those guests have no account with us and have given us nothing directly.

In those cases the couple decides what is stored and for how long, and Aurea holds it on their behalf. A guest who wants to know what exists about them, correct it, or ask for its removal can speak to the couple or write to us at ola@planwithaurea.com — we will pass the request to the couple responsible and help resolve it.

When a guest replies to a public invitation, we store the reply (who is coming, and anything written in the message or dietary field, if the couple asked for those) and the date of the reply. We do not ask for or store the IP address of the person replying.

Almost everything in Aurea is private and reachable only by the people you give access to. That is enforced by the database rather than only by the interface: every row belongs to a wedding, and access is checked server-side on every request.

There is one exception, and it is deliberate: the invitation. When you publish yours, it becomes available at a public address (planwithaurea.com/w/…) so guests can open it without an account or a password. What you wrote in the invitation is visible there — names, date, venue, your words and the photographs you chose.

Your guest list is never public. Someone opening the invitation can look up their own name in order to reply, but cannot see the list.

While an invitation is unpublished, the address returns nothing. Photographs are the exception: so that any guest can see them once you publish, they are held in publicly readable storage. Treat a photograph you upload as something that can be opened by anyone who reaches its address, even before you publish the invitation.

We do not sell personal information and we do not share it for advertising. We use the following providers to run the application:

Supabase

Database, authentication and file storage. This is where your wedding's information is held.

Vercel

Hosting and delivery of the application.

Google

Only if you choose to sign in with Google. In that case Google confirms your identity to us; we send it no information about your wedding.

Google (Gemini)

When you use assisted features — for example asking for help writing your invitation — the text needed to answer is sent to this service. We do not send it your guest list or your documents, and these features are optional.

Resend

Sending notification emails, when configured. While it is not, email notifications are recorded as not sent rather than pretending to have been sent.

These providers may process information outside Mozambique. We may also disclose information where we are legally required to.

Aurea uses no advertising or tracking cookies. We use:

• A session cookie, to keep you signed in. Signing in is not possible without it.
• A language cookie, which remembers whether you prefer Portuguese or English.
• Local storage in your browser, for visual preferences such as your chosen palette and whether the sidebar is collapsed.

We keep your wedding's information for as long as your account exists. If you ask us to delete it, we delete the account and the associated wedding data, including uploaded files.

To be honest about where we are: deletion is done by us on request, and there is not yet a button that does it on its own. A request sent to ola@planwithaurea.com is handled within 30 days. When automatic deletion exists, this page will say so.

You can ask us, at any time, for:

• A copy of the information we hold about you.
• Correction of anything wrong — most of it you can correct directly in the application.
• Deletion of your account and wedding.
• That we stop using your information for a particular purpose.

Write to ola@planwithaurea.com. We reply from the same address.

Access to data is checked in the database on every request, not only in the interface: a request that does not belong to your wedding returns nothing. Documents you upload are held in private storage and served through temporary addresses. Traffic is encrypted in transit.

No system is perfectly secure. If you find a security problem in Aurea, please write to ola@planwithaurea.com before making it public — we will respond and fix it.

Aurea is intended for people aged 18 or over. We do not create accounts for minors. A guest list may include children, marked as such by the couple; in that case we store only their name and which invitation they belong to.

If we change this policy significantly, we will say so in the application before the change takes effect. The date at the top of this page always indicates the version in force.