Privacy policy
What data Duetto keeps, why, on what basis, where, for how long, and what you can do about it. Written to be read, not ticked.
Last updated: 12 October 2026
Who is responsible for what
For your account and for how the platform works, Duetto is the data controller: we decide what data we ask for and how we use it, and this policy describes exactly that. For a wedding's guest list, the controllers are the couple: they decide who goes on the list and what data they enter. For a vendor's client list, the controller is the vendor. In these two cases Duetto is a processor: we keep the data on their behalf, under their instructions, and never use it for anything else. The rules of that processing are in the Terms, under “Processing data on your behalf”. This policy covers the duetto.ro website, the app and the emails we send.
What data we keep
Your account: name, email address, password (stored only as a hash; we cannot read it), language, notification preferences and, if you add them, your phone number and the link to Telegram or browser notifications. The wedding: the couple's names, the date and place, the guest count, the budget and payments, tasks, the vendors you talk to, quote requests, offers, contracts, messages, the invitation (texts, photos, godparents and parents), tables, the schedule, the files you upload and the people you have given access to the wedding. Vendors: company details (tax ID, legal name, legal form, trade register number and registered office, taken from the public ANAF registry), brand name, public contact details, packages and prices, portfolio, calendar, billing details, colleagues invited into the account and everything the vendor keeps in their client list. Signing a contract or an addendum: the signer's name, the moment, the IP address it was signed from, the browser used and the document's fingerprint. These are the proof of signing and both parties can see them. Using the platform: which pages of the app you open, marketplace searches (category, county, wedding month, number of results) and profile views, without recording who made them; a security log of sensitive operations (for example signing in, deleting the account, support-team searches), with the account and the moment; your IP address, as a hash, for traffic limits. We do not ask for or keep data about health, religion or other special categories. If a guest notes an allergy or the couple chooses a religious ceremony, that information reaches only the couple, or stays in their wedding plan, and we never use it in any other way.
Guests
The guest list is entered by the couple, who decide what data goes in it (usually the name, the household the guest belongs to, phone, email). Guests have no account: they open their invitation through a personal link they receive from the couple and answer only for their household. Answers (attending or not, how many people, the chosen menu, allergies, whether they need accommodation or transport, a song request), the table they sit at, guestbook messages and photos uploaded to the wedding gallery reach only the couple and the people the couple has given access to the wedding, and are used only to organise that wedding. The wedding page and the gallery open only for whoever has their link, and the couple can put a code on the page. We do not list them in search engines. The invitation records whether it was opened (not from which device) and when it was answered, so the couple knows whom to ask again. A guest who wants to see, correct or delete their data asks the couple, who can change it at any time from their list, or writes to us. Guest data disappears together with the wedding.
Clients kept by vendors
A vendor can keep their client list in Duetto, including couples who have no account on the platform: name, phone, email, wedding date and place, guest count, agreed amounts, instalments, their notes, the answers to questionnaires they send and the files they upload for that client. For this data the vendor is the controller; they are responsible for its lawful basis and for informing their clients. Duetto only stores it for the vendor, shows it only to them and to the colleagues they have invited into the account, never uses it for anything else, never contacts those couples and never creates accounts for them. An offer sent by link opens without an account, only with the address received from the vendor; the answer and the name of whoever accepts reach only the vendor. A contract sent by link is read and signed without an account too; the signer's name, the moment and the IP address stay in the signing log, visible to the vendor and to whoever has the link. A questionnaire sent by link is answered once, and the answers reach only the vendor. A vendor's public request form sends the data you type (name, phone, email, wedding date and place, message) only to that vendor. The calendar the vendor subscribes their phone to receives only the couple's names, the day, the place and the guest count of booked weddings; the calendar address is secret and the vendor can change it at any time. Invoices the vendor issues from Duetto include the client's name and address and, if the vendor enters them, the personal or company tax ID. Only the vendor sees them; reporting them to ANAF is done by the vendor, not by Duetto. Couples who want to see, correct or delete their data from a vendor's list ask the vendor or write to us, and we pass the request on and make sure it gets an answer.
Why we use it and on what basis
So that the platform works (the wedding plan, the invitation, the link between couples and vendors, offers, contracts, invoices, in-app notifications): performance of the contract between you and us, i.e. these Terms (art. 6(1)(b) GDPR). To send you notifications by email, Telegram or in the browser: by email, as part of the service, about your account and wedding; by Telegram and in the browser only if you switch them on, and you can switch them off at any time from the Account page (consent, point (a)). To verify vendors before they go public, keep the platform safe (traffic limits, the security log, blocking abuse), moderate reviews and reports and understand how the platform is used, from figures that do not record who did what: our legitimate interest in offering a safe and trustworthy service (point (f)). You can object to this processing by writing to us; we will weigh your request against these interests. To keep what the law requires (for example a contract's signing log, the records tax law requires about our own activity): legal obligation (point (c)). We do not sell or rent data, do not build advertising profiles, do not make automated decisions that affect you and do not send commercial messages without your consent. The emails you receive are about your account, your wedding or your clients.
Who else sees the data
Other users, exactly as far as you decide: the colleagues you invite into the wedding or the vendor account; the vendor you send a request to (who sees the couple's names, date, place and guest count as they were when the request was sent, and your messages); the couples a vendor answers (who see their profile, offer and contract); the public, for a vendor's approved profile and for published reviews (the name chosen by the couple, the rating, the text, photos and the vendor's reply). Service providers that process data on our behalf, under processing agreements per art. 28 GDPR: Supabase (database, files and authentication; servers in the European Union, in Frankfurt), Vercel (hosting and delivery of the app), Resend (sending emails). If you switch them on: Telegram (Telegram messages) and your browser's notification service (Apple, Google or Mozilla, as the case may be), which receive only the notification text. Public authorities, only when the law obliges us or on a reasoned legal request. The ANAF registry: when a vendor types their tax ID, we look it up in the public registry to fetch the company details; ANAF receives nothing else. We use no third-party analytics or advertising tools: everything we measure lives in our own database.
Where it is kept and how it is protected
Data and files are kept in the European Union, in Frankfurt. Some of our providers are US companies; with them we rely on the European Commission's standard contractual clauses and, where applicable, their certification under the EU–US Data Privacy Framework, and the actual processing stays in Europe. Access to data is enforced in the database, not only in the app: everyone sees only their own wedding, their own vendor account and what they were explicitly given. Everything travels encrypted (HTTPS), passwords are stored only as hashes, and passwords known to have leaked are refused at sign-up. Private files open only through signed, expiring links. The Duetto team accesses data only for support and verification, and its searches are written to the security log. No measure is perfect. If we learn of a security breach that concerns you, we will tell you and, where the law requires it, notify the supervisory authority within 72 hours.
Cookies
We use only the cookies without which the platform does not work, so the law requires no consent for them and we have no cookie banner. These are all of them: • the account session (cookies starting with “sb-”): keeps you signed in; expires when you sign out or after a period without activity; • the chosen language (“NEXT_LOCALE”): one year; • the wedding and the vendor account you are working in, when you have several (“duetto_wedding”, “duetto_vendor”): one year; • what you filled in a public tool and want to carry into your wedding setup (“duetto_start”): 14 days, deleted when used; • the code from the forgotten-password link, while you choose a new password (“duetto_recovery”): 15 minutes; • the message of an action that failed (“duetto_notice”): a few seconds. We use no advertising, analytics or third-party cookies, do not use the browser's local storage for tracking and do not track what you do on other sites. Browser notifications use a push subscription that you create and remove yourself from the Account page.
How long we keep it
Your account and wedding: until you delete them. You can delete your account at any time from the Account page; the weddings only you own disappear with it, including guests, files, messages and unsigned contracts. A contract signed through the platform stays with the vendor after the couple deletes their account, detached from the wedding (the parties, the text, the signatures, the signing log and its file), because it is their proof in case of a dispute; likewise, a contract signed by the couple stays in their account if the vendor deletes theirs. A signed contract is kept as long as the other party has an account, and at least three years from the wedding date (the general limitation period). A vendor account: until you delete it, with the exception described for contracts; while a contract is in force for an upcoming wedding, the account cannot be deleted. Its client list, questionnaires, files, invoices and billing details disappear with the account, so the vendor keeps the copies accounting law requires. Read notifications are deleted after 12 months; usage figures (searches, views) after 24 months; Telegram linking codes after a day; team invitations not accepted within 30 days. The security log is kept as long as needed for the platform's safety and for any legal obligations, as a rule no longer than three years. Database backups rotate within 30 days at most; what you delete disappears from them within that time.
Your rights
You have the right of access, rectification, erasure, restriction, portability and objection, and the right to withdraw your consent at any time where processing is based on it, without affecting what was done before. Most of these you can do yourself: see and correct your data in the platform's pages; download all your data, in a file you can read and take elsewhere, and delete your account from the Account page, section “Your data”; switch Telegram and browser notifications off from the same page. For the rest, write to us at the address below. We answer within a month at most; if the request is complex, we will tell you and may extend by two further months. We do not charge for this. If you believe your data is not being handled properly, you can complain to the Romanian supervisory authority (ANSPDCP), B-dul G-ral Gheorghe Magheru 28-30, Bucharest, www.dataprotection.ro, or to the courts. As we are established in Estonia, our lead authority is the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon, www.aki.ee); a complaint filed with ANSPDCP reaches it through the European one-stop-shop mechanism, with nothing more for you to do. We would appreciate it if you wrote to us first, so we can fix it.
Age
The platform is for people aged 18 or over. We do not create accounts for minors and do not ask for their data. If the couple adds children to the guest list (for example for the children's menu), that data belongs to the couple, like any guest data.
Changes
When we change something important in this policy (what data we keep, why, whom we give it to), we tell you in the platform or by email before it applies. Small changes (wording, adding a provider in the same role) appear only here, with the update date at the top.
Operator and contact
The Duetto platform is operated by GTO Business OÜ, registrikood 17489502, Sepapaja tn 6, 15551 Tallinn, Estonia (“Duetto”, “we”).
For any question about your data or these terms, write to hello@duetto.ro