Privacy Policy

1. Who we are

The controller of your personal data is NOVANC NORBERTH-GABRIEL PERSOANĂ FIZICĂ AUTORIZATĂ, CUI RO33404897, trade register no. F02/672/2014, registered office at Str. Ghioceilor nr. 11, 317280 Sântana, jud. Arad, România ("Bridely", "we").

For anything about your data, write to support@bridely.net. We have not appointed a data protection officer because we are not required to (Art. 37 GDPR): we do not systematically monitor people on a large scale or process special categories of data on a large scale.

2. In short

• We use your data to run your account and the wedding you plan, to take payments and to keep the service secure.
• We do not sell personal data and we do not show advertising.
• Some features send data to service providers, including AI services. Section 6 says exactly what is sent.
• Analytics only runs if you click "Allow analytics" in the cookie banner.
• You can download your data and delete your account yourself, from your profile, at any time.

3. What we collect and where it comes from

From you

• Account: name, e-mail address, password (stored only as a one-way hash), optional phone number, display name and profile photo, language, the Terms and Privacy Policy version you accepted. If you sign in with Google, we receive your name, e-mail address and Google account identifier.
• Your wedding: date, places, budget, expenses and payments, receipts you upload, tasks, notes, timeline, vendors and their contact details, seating, invitation designs, inspiration images, venue preferences, the messages you write to the venue assistant and your conversations with the Ringy assistant (text or voice messages).
• Purchases: what you bought, amounts, billing country, invoice details (name, address, VAT number for businesses) and the consent you gave at checkout. Card details go directly to Stripe; we never see them.
• Messages to us: what you write to support, feedback and data requests.

About other people, from our users

Couples and planners add details about other people: guests (names, e-mail, phone, household, plus-ones, children, table, menu choice, allergies or dietary notes, notes), vendors (contact details, prices), collaborators they invite and, for planners, their clients (the couple's names, e-mail and phone). Section 5 explains how we handle this.

From guests directly

Guests who answer an invitation (RSVP), register through a couple's link, or leave a message or a song request on a guest page give us that information themselves.

Automatically

• Technical data needed to run and protect the service: IP address (kept only as a salted hash for abuse prevention), browser type, country from our network provider, sign-in times, and error reports from which e-mail addresses, identifiers and other personal details are removed.
• Usage events inside the app (for example "opened the guest list"), kept 90 days, and, only with your consent, Google Analytics (section 12).

4. Why we use it and on what legal basis

We do not make decisions about you based solely on automated processing that have legal or similarly significant effects. AI features make suggestions; you decide what to keep.

5. Guests and other people in your wedding

When you add guests, vendors or collaborators, you decide what to add and why. Please add only what you need to organise the wedding. Tell the people concerned that you use Bridely, for example when you ask for their details, and point them to this policy if they ask.

Allergies and dietary notes can reveal health information. The field is optional and is used only to plan the menu. When guests fill it in themselves when they reply, they do so with their explicit consent (Art. 9(2)(a) GDPR), after seeing next to the field what it is used for; they can withdraw that consent at any time by asking for deletion. If you add them yourself, add them only if the guest gave them to you for this purpose, keep them short, and do not add other health details. Only people with access to that wedding see them, plus anyone you send the seating plan to (for example the restaurant).

Children: guest lists may include children. Their details are added by the couple or planner, usually with the parents, and are used only to organise the wedding (seat, menu).

Who is responsible: for weddings couples plan themselves, Bridely is the controller of the guest data hosted in the app and answers guests' requests directly; the couple decides whom to add and uses the data for personal purposes. For wedding planners, the planner is the controller of its clients' and their guests' data, and Bridely processes it on the planner's instructions as a processor (Annex A of the Terms) and helps the planner answer requests.

If you are a guest or a vendor and want your details changed or removed, ask the couple or planner, or use the data request form. We forward the request to the wedding's owner and make sure it is handled.

6. AI features, in plain words

Some features use AI models run by other companies. They only run when you use the feature, and only the data the feature needs is sent:

• The models are not used to identify people in photos and we do not ask them to.
• The results are suggestions: they can be wrong, and nothing is saved until you confirm it.
• We use Google's paid services (Gemini API and Cloud Vision). Under their terms, Google does not use the content we send to improve its products or train its models, processes it as a processor, and keeps it only for a limited time to detect abuse.

7. Who receives data (processors) and transfers outside the EU

We use these service providers. They process data only on our instructions, under data processing terms.

Transfers to the USA (Google, Stripe, Pinterest, Cloudflare) rely on the EU-US Data Privacy Framework, under which these providers are certified, and on the European Commission's standard contractual clauses in their data processing terms. The United Kingdom has an adequacy decision from the European Commission.

We may also disclose data to authorities when the law requires it, and to our accountant for invoices. Other people on a wedding (partner, planner, family you invite) see the wedding data their role allows.

8. How long we keep data

9. Security

We use encrypted connections (HTTPS), hashed passwords, role-based access to each wedding, protected sign-in sessions, bot protection on public forms, limited and audited administrator access, and error reports from which personal data is removed. No system is perfectly secure; if a breach puts your rights at risk we will tell you and the authority as the law requires.

10. Your rights and how to use them

Under the GDPR you have the right to:

• access your data and get a copy — in the app: Profile → Download my data (a ZIP file with readable files);
• rectification — edit your details in the app or ask us;
• erasure — Profile → Delete account, or the data deletion page;
• restriction of processing and objection to processing based on legitimate interest;
• portability — the download contains JSON and CSV files you can reuse;
• withdraw consent at any time (for analytics: the cookie settings link in the footer), without affecting what happened before.

Write to support@bridely.net or use the request form. We answer within one month (extendable by two months for complex requests, in which case we tell you). We may ask you to confirm your identity.

You can complain to the Romanian supervisory authority, ANSPDCP (Autoritatea Națională de Supraveghere a Prelucrării Datelor cu Caracter Personal), B-dul G-ral. Gheorghe Magheru 28-30, Sector 1, București, www.dataprotection.ro, or to the authority in your EU country.

11. Children

Accounts are for adults: you must be at least 18 to create one. Guest lists can include children; their details are added by the couple or planner (section 5). Guest pages and RSVP forms are meant for adults answering for their household.

12. Cookies and analytics

We use one sign-in cookie and the browser's local storage to keep you signed in and remember your settings. Google Analytics only runs after you click "Allow analytics". Details and how to change your choice are in the Cookie Policy.

If you allow analytics, we also note on your account where your visit came from when you signed up: the campaign or kind of site (for example "instagram" or "search") and the page you arrived on, never the full web address. When you create your first wedding we may ask how you heard about Bridely; answering is optional. We use both only to see which channels bring people to Bridely (legal basis: your consent, Art. 6(1)(a) GDPR), and they are deleted with your account.

13. Changes to this policy

When we change this policy we update the version and the date above. If a change is important, we tell you by e-mail or in the app before it applies. Earlier versions are available on request.

14. Contact

NOVANC NORBERTH-GABRIEL PERSOANĂ FIZICĂ AUTORIZATĂ, Str. Ghioceilor nr. 11, 317280 Sântana, jud. Arad, România — support@bridely.net.