Privacy Policy

The data controller is Trailbits SRL, with its registered office at Sat Feleacu, Comuna Feleacu, Nr. 677C, Jud. Cluj, registered with the Trade Register under no. J2026042527004, fiscal code RO55107625. For any request regarding your data, write to us at contact@loomia.ro.

For most of the processing described below, we are the controller. There is one exception, marked as such wherever it appears: where a professional customer runs their own events, their own client list, their own Marketplace inbox or the answers to their own questionnaires on Loomia, that professional is the controller and we handle the data on their behalf, as their processor. The next section says which is which.

• Account holders: couples, wedding planners, event venues and vendors.
• Wedding guests — who have no account: they receive a personalised link and can RSVP, choose menus, send a message or a gift. Their contact data is initially entered by the couple (or, for events managed entirely by a professional, by that professional).
• Visitors of the public pages (marketplace, landing pages) and people who submit an inquiry through a public contact form.
• People who fill in a feedback form received from a couple.

If you are a guest and your data was entered by the couple, this policy — reachable from the invitation — also constitutes the information required by Art. 14 GDPR for data we did not collect directly from you.

For events managed entirely by a professional (a wedding whose couple has no Loomia account, with the guest list entered by the wedding planner or the venue), as well as for the clients in a professional's pipeline, the inquiries they receive through the Marketplace and the answers to the questionnaires they send to couples, the controller of that data is the professional: they decide why and how it is processed. We process it on their behalf, as a processor, under the Data Processing Agreement accepted when the professional account is created. Informing the persons concerned is, in that case, the professional's responsibility.

A wedding managed entirely by a wedding planner can move into the couple's account. The planner buys the couple Premium tied to that wedding and sends them an account sign-up link; if the couple create their account through it and do not already have a wedding on Loomia, they take over the wedding the planner prepared, with the guest list, the menu choices and the notes for the kitchen, the seating, the schedule, the vendors and the budget. The handover is made on the instruction of the planner, who is the controller of this data until that moment and is responsible for having a basis to disclose it to the couple. From the takeover onwards the wedding is the couple's, and its data is processed as for any wedding a couple created: we are the controller, under this policy, and we received the guests' data from the planner. The planner stays connected to the wedding and sees only what the couple allow through the sharing options; tasks it has not made visible to the couple, its documents, notes and client records stay its own and do not reach the couple. Other professionals already connected to the wedding stay connected, and the couple can see them and remove them at any time. If you are a guest at such a wedding, from the takeover onwards this policy — reachable from the invitation — is the notice required by Art. 14 GDPR, and you can exercise your rights directly with us; for the period before, informing you was the planner's responsibility.

Sometimes we receive data about you from someone else: a couple adds you to their guest list, a professional enters you as a guest or as a client in their own records, another member of your household fills in the RSVP and the menu choice for everyone named on the invitation, a couple mentions you in their answers to a professional's questionnaire (as a godparent, for example, or on the list for the family photographs), or you appear in a photograph or a video message someone else uploaded. In those cases we process the data to provide the service the person who gave it to us asked for, on the bases described below, and you have exactly the same rights as if you had given it to us yourself — including the right to object. Whoever enters data about another person is responsible for being entitled to do so.

Account and authentication — email address, password (stored only cryptographically, as a hash), name, chosen role, business name (professionals). Purpose: creating and securing the account. Basis: performance of a contract (Art. 6(1)(b) GDPR).

Emails about the service — besides the account messages (address confirmation, password reset, payment confirmations, the warning before videos are deleted), which are part of the service and always arrive, we may send couple account holders, now and then, an email with what to do at the next stage of the wedding and what is new in Loomia. For that we use the account's address, the wedding date and a few numbers about it (how many guests are on the list, whether the invitation has gone out) — no other data about guests or gifts. Professional accounts (wedding planner, event venue, vendor) receive, on the same terms, a welcome email and, if the Marketplace profile is not published in the first few days, one reminding them of it; for these we use the account's address, the account type, the day the trial ends and whether the profile is published. Basis: Art. 12(2) of Romanian Law no. 506/2004 — the address was obtained when the account was created, the messages concern only the Loomia service, and the refusal was offered to you on the sign-up form itself (an unticked box) and is offered again in every email, through a link that works without signing in. You can change your mind at any time, either way, from the account page or from the link in the email; we keep the choice, its moment and the version of the text shown to you at sign-up, as well as which such emails we sent you, so none is sent twice. Accounts created before that box existed receive a single such email, the welcome, with the same opt-out link, and no other unless they choose to receive them from the account page.

Acceptance of the unusual clauses (professional accounts) — when the account is created, professionals tick a separate box expressly accepting the clauses covered by Article 1203 of the Romanian Civil Code. We keep a record of each acceptance: the version of the Terms, the moment, a cryptographic fingerprint of the accepted text and, as evidence of the circumstances, the IP address and browser identifier the acceptance came from. We use those for nothing else and never tie them to your activity on the Platform. Purpose: so we can show which text you accepted and when. Basis: performance of a contract and our legitimate interest in establishing and defending legal claims (Art. 6(1)(b) and (f) GDPR). Couple accounts are not asked for this checkbox and no such record is created for them.

Wedding/event data — the couple's names, date, venues, day schedule, invitation texts, seating plan, budget, vendor list and, if the couple enables the digital gift, the receiving details they enter themselves: a payment link generated by the couple's own banking app and/or the IBAN together with the account holder name. We store these exactly as entered, show them to guests on the gift page, and use them for nothing else. Basis: performance of a contract.

The guest list — household/person names, headcounts (including children), phone, email, preferred language, RSVP status. This data is entered by the couple to manage their own event. Basis: the Operator's legitimate interest in providing the service the couple asked for (Art. 6(1)(f) GDPR) — an interest we have weighed against the guests' rights and which is confined to running this one event. Separately from our own basis, the couple is responsible for having a lawful basis of their own for giving us their guests' data and for making sure that doing so complies with the law. Guests may object at any time (see 'Your rights').

The RSVP — attendance, headcount, per-person menu choice, accommodation needs, a message to the couple. Basis: steps taken at the data subject's request and the legitimate interest described above. Choosing a menu is required if you confirm attendance: the venue needs the exact number of portions of each type, and the event cannot be catered without it. You may pick any option on the list. An option can hint at a health or religious reason — “gluten-free” is the obvious one — but we never ask what the reason is and we do not record it: to us the choice is a portion count and nothing more. We process it on the legitimate interest of organising the event (Art. 6(1)(f) GDPR) rather than on consent — precisely because the choice is required, and consent you cannot submit the form without would not be freely given. The free-text “other” field is optional and is never a condition of replying: you can confirm your attendance without writing anything there. If you do write an allergy or an intolerance, that is health information, and its basis is your explicit consent (Art. 9(2)(a) GDPR) — given through a separate tick that appears beside the field, not by the act of filling it in. We keep the moment of that tick and the version of the wording you read, so we can show what you agreed to. You can change your mind at any time: untick and re-submit, and the detail is deleted along with the consent. You are never required to give a medical reason, and you may leave the field blank.

The digital gift — the pledged amount, currency, message, transfer reference and, optionally, a video greeting recorded by the guest; the receipt confirmation, entered by the couple. This data is visible exclusively to the couple. Basis: performance of the service requested by the guest and by the couple respectively. Important: the actual payment happens outside the Platform, directly between guest and couple — we never see or store guests' banking details.

The wishlist — reservations made by guests. The reserver's name is visible only to the couple; other guests see only "Reserved".

Marketplace — the professional's public profile (data they choose to publish) and inquiries received from prospective clients (name, phone/email, event date, message). Basis: performance of a contract (professional), respectively pre-contractual steps at the request of the person sending the inquiry (Art. 6(1)(b) GDPR).

Professionals' questionnaires — a wedding planner, an event venue or a vendor may send you the link to a questionnaire they have put together, with questions about the day's schedule, songs, family photo groups, the godparents' names, addresses and the like. To answer, you need to sign in to your couple account. The link is taken by the first couple account that opens it and presses “Start”, and it can no longer be used from any other account. We process the answers you write, the photos you upload (up to 10 per question) and the moment you send them. Your answers save as you type, but the professional sees them only once you have sent them for the first time. After sending, you can change them only if the professional unlocks them; while they are unlocked, the professional sees your changes as you make them. In the couple's dashboard you can view them at any time, but not change them. When you send them, the professional receives an email saying that the answers have arrived; the email does not contain the answers. Alongside the answers, the professional sees the couple's names and the wedding venue (its name and address), as they appear on your invitation. The venue appears only if you chose to show it on the invitation. No other information about your wedding, such as guests, gifts or messages, reaches the professional through a questionnaire. The professional decides what to ask and what to do with the answers. That is why, for the answers and photos, the controller is the professional who sent you the link, and we process them on their behalf, as a processor, under the Data Processing Agreement. For your account and for passing your names and venue to the professional, we remain the controller; we pass them on at your request, when you press “Start”. Basis: performance of a contract (Art. 6(1)(b) GDPR).

Professionals' contracts — a wedding planner, an event venue or a vendor may send you the link to one of their contracts, so that you fill in the blanks left for you in it (your names, address, the wedding date and, if the professional asked for it, a personal identification number (CNP) or the series and number of an identity card, for example). To fill it in you need to sign in to your couple account; the link stays tied to the first couple account that opens it. Only the professional who sent it and your account can read the contract. Everything typed into the contract is stored encrypted and appears only on the contract's screen and in the documents the two parties download, which are generated on request and not kept. Signing happens outside Loomia: you download the contract, sign it, and you or the professional upload the signed copy (a PDF or a photo). When it is uploaded, the values typed in are deleted from the database; only the signed copy remains, and both of you can download it. Nothing on the Platform is a signature. The contract's text is written by the professional, and Loomia is not a party to the contract. For the contract, the values typed in and the signed copy, the controller is the professional, and we process them on their behalf, as a processor, under the Data Processing Agreement. Basis: performance of a contract (Art. 6(1)(b) GDPR).

Reviews (feedback) — the rating and comment a couple leaves about a professional. Only aggregates are shown publicly (average + count); individual comments remain with the professional. Basis: legitimate interest (operating the review system).

Payments for Loomia plans — processed by Stripe; we receive payment confirmation and transaction identifiers from the processor, never card details. Stripe's checkout page collects every buyer's name and billing address, and for professional accounts the tax identification number as well — the data an invoice requires. These stay with Stripe and are passed to our invoicing software (SmartBill), which issues the invoice and files it in the e-Factura system; they are not stored in the Platform. Basis: performance of a contract and legal obligations (invoicing, accounting).

Referrals — if a Couple account is created through a professional's referral link, or enters that professional's code, we record the link between the two accounts, the discount applied and, after payment, the credit given to the professional. The professional sees only the number of accounts created and of those that bought Premium through its link — never the couple's names, wedding or any other data. If it sent the link to only a few people, the professional may be able to work out from these numbers who created an account or bought Premium. We receive no data from the professional about the people it sends the link to. Purpose: applying the discount and granting the credit, under the Terms. Basis: performance of our contract with you, for the discount (art. 6(1)(b) GDPR), and our legitimate interest in giving the professional the credit we promised (art. 6(1)(f) GDPR).

Messages sent through the contact form — your name, email address, the subject you chose and the text of your message. These are emailed to us and stay in our correspondence; they are not stored in the Platform and are never used for marketing. Purpose: so we can reply to you. Basis: steps taken at your request prior to entering into a contract, and our legitimate interest in answering enquiries we receive (art. 6(1)(b) and (f) GDPR).

Ad measurement — if you accepted "Advertising" in the cookie banner: the public pages you visited and, when an account is created, the fact that it was, with the account's e-mail address and identifier irreversibly hashed, the IP address and the browser type, sent to Meta. Purpose: to learn what an account that came from an ad costs us, and to show our ads to people they may interest. Basis: consent (Art. 6(1)(a) GDPR), which you can withdraw at any time without affecting processing carried out before the withdrawal.

Where an account came from — when an account is created we record, on that account, the campaign label of the link the visitor came through (utm_source, utm_medium, utm_campaign), the domain of the site they came from (the domain only, not the page address) and whether the link came from a Facebook or TikTok ad (we do not keep the click identifier). No cookie is used for this and nothing is saved in your browser: the labels stay in the page address until the account is created. They are deleted with the account and used only to count which channels bring new accounts, and are not passed on to anyone. Basis: our legitimate interest in understanding how people reach the Platform (Art. 6(1)(f) GDPR).

Technical data — server logs, IP address (also used for abuse prevention — rate limiting), browser type. Basis: our legitimate interest in keeping the Platform secure and functional.

Menu choices may indirectly indicate health information (allergies, intolerances) or, in some cases, religious beliefs (e.g. fasting preferences). We process them exclusively to organise the event catering and share them only with those involved in preparing the catering: the couple and, if the couple chooses to share, the venue and the planner — never in the form of the guest's free-text message to the couple. The same choices also appear on the event sheet the couple can send to their venue through a unique access link, described in the next section. There they appear next to the person's name, and if you chose the free-text “other” option when you replied and wrote a detail (an allergy, for instance), that detail appears beside your name: the kitchen has to know which plate it is and who it goes to.

Picking a menu from the list is required if you confirm attendance, so it cannot be a voluntary disclosure: consent you cannot submit the form without would not be freely given. We use it strictly as a portion count, we never ask you for the reason and we do not record it. What is voluntary is the detail written under “other”, and for that we ask separately for your explicit consent.

That same detail can reach us by two other routes, on which you are not present and no consent can be taken at the time: when the couple or their planner records an answer given over the telephone, and when a professional enters the guest list of an event they run on their own. On both we ask the person entering it to confirm that you gave the information knowing it reaches the people preparing the meal, and we keep that confirmation; without it the detail is not saved at all. For an event run entirely by a professional, that professional is the controller of those data and we process them on their behalf.

Professionals' questionnaires have no field meant for health data, and we do not ask you for any. The questions, however, are written by the professional, so a question may ask for, or an answer may contain, information about someone's health, religion or family situation, for example an allergy the cake-maker has to allow for. Write only what the professional needs for the service they provide to you. About other people (godparents, parents, guests), write only what you know they are happy for the professional to have. If you cannot see why such information is being asked for, ask the professional before you answer. For these answers the professional is the controller, and establishing the legal basis for processing them is up to them. Unlike the detail written under “other” in an RSVP, these answers are not deleted automatically after the wedding.

Children's names on the guest list are entered by their parents or by the couple, exclusively for portion counts and seating. The Platform is not directed at minors and does not create accounts for them.

• The gift ledger (amounts, givers, messages) is visible exclusively to the couple. Professionals connected to a wedding cannot see it, by construction of the Platform.
• The couple controls, through explicit share toggles, what the venue and the planner see (guest list, seating plan, schedule, vendor list).
• Guests' private messages to the couple never appear on the sheets intended for the venue or the planner.
• Public Marketplace profiles and the other public pages are built on strict field allowlists: they expose no guest data, no amounts, no login email addresses.
• The answers to a professional's questionnaire, and the photos uploaded in it, are accessible only to the professional who sent the questionnaire and the couple who filled it in. The photos have no public address: the Platform shows them only after checking that the request comes from one of those two.
• The event-sheet access link the couple sends to their venue never carries the gift ledger, guests' private messages to the couple or the couple's login email address. It does carry the portion counts and the per-person menu choices — with the guest's name, the table they are seated at and, where they chose “other”, the detail they wrote. The names are on the sheet deliberately: they are what ties a plate to a place card, and an allergy with no name cannot be served safely. The sheet also lists the meals for the crews working the wedding (photographer, band and others): a role or a name, entered by the couple, the planner or the venue, and the menu type.
• The event sheet opens with no password, on the strength of the link alone. The couple choose who receives it and are required by the Terms to send it only to the professionals working on the event. The link closes automatically 14 days after the wedding date: past that point the address shows nothing at all, no matter who it reached in the meantime. The couple can generate a fresh link from the app at any time — at which point the old address stops working immediately — and deleting the wedding or the account closes the link too. A professional who receives the sheet is required by the Terms to treat it as a confidential document: to use it solely to prepare the event, make it available only to the members of their own team who need it, and neither publish it nor pass it on. Separately, the couple or their planner can send their vendors a day-of link — the schedule, the venue and the planner's and venue's phone numbers — which carries no guest, no menu choice and no gift, can be switched off or replaced at any time, and closes on the same date.
• Guest links and connect codes are generated cryptographically at random — practically impossible to guess.

In short, who sees what:

• The invitation — the guest who receives the link, and the couple, who created it.
• The RSVP and the menu choice — the couple; the venue and the planner if the couple chooses to share.
• The detail written under “other” — the couple, the venue and the planner, and the event sheet, beside your name.
• A private message to the couple — the couple alone.
• Gifts, amounts and the ledger — the couple alone.
• Greetings and video messages — the couple alone.
• The guest list — the couple; the venue and the planner if the couple chooses to share.
• The event sheet — anyone who opens the access link, until it closes.
• That your Premium was offered by a wedding planner — you, in your account, and the planner who bought it, who sees only whether and when the link was used.
• That you created your account through a professional's link — that professional, as a number, without your name. If it sent the link to only a few people, it may be able to work out from the numbers who created an account or bought Premium.
• A Marketplace profile — public.
• An inquiry sent to a professional — the professional it is addressed to.
• The answers to a professional's questionnaire, and the photos uploaded in it — the couple who filled it in and the professional who sent it; the professional also sees, alongside them, the couple's names and the wedding venue as they appear on the invitation.
• A rating and its comment — the rated professional; publicly, only the average and the count.

Data reaches four kinds of recipient, each described in detail elsewhere in this policy: the professionals a couple chooses to connect to their wedding, sends the event-sheet access link to, or answers a questionnaire for; the service providers we use to run the Platform, listed below; the public, for whatever a professional chooses to publish on their own Marketplace profile; and public authorities, only where the law requires it.

We do not sell personal data. We use it for advertising in one case only, described below under Meta: only with your consent, and only to measure our own ads. We work with a small number of providers. Most of them handle data only on our behalf and on our instructions, as processors, under contracts that meet Art. 28 GDPR. A few of them are, for some of that processing, controllers in their own right: they pursue their own purposes under their own privacy policy. What each one does is set out below:

• Stripe Payments Europe, Ltd. (Ireland) — payment processing for Loomia plans. For payment data Stripe also acts as an independent controller, for its own fraud-prevention and regulatory purposes (their privacy policy).
• Intelligent IT SRL — SmartBill (Romania) — issuing the invoices for Loomia plans and filing them in the e-Factura system, from the billing data received from Stripe (their privacy policy).
• Railway Corporation (USA) — application and production database hosting, in the EU-West region (Amsterdam, Netherlands) (their privacy policy).
• Cloudflare, Inc. (USA) — storage of uploaded files (photos, videos, documents) in European-Union-jurisdiction storage, and the domain's DNS service (their privacy policy).
• Resend, Inc. (USA) — sending account emails (for example, password reset) and the emails about the service described above (their privacy policy).
• Google Ireland Limited (Ireland) — signing in with your Google account, only if you choose the "Continue with Google" button. Google passes us the stable identifier of your Google account, your e-mail address (as verified by Google) and your display name; we neither receive nor keep your profile photo, your Google password or anything else from the account, and we access nothing in your Google account after sign-in. For this sign-in Google acts as an independent controller under its own terms (their privacy policy).
• PostHog, Inc. (USA) — usage statistics and session replay, hosted in the EU (Frankfurt); active only with the consent you give through the cookie banner (basis: Art. 6(1)(a) GDPR). We have configured it to mask all on-page text and all form fields in recordings, so a recording shows the page structure and the actions rather than the content, and not to build person profiles — we never send it your identity. On the signed-in pages (the couple’s dashboard and the professional portal) we have also switched off automatic interaction capture entirely, because that transmits the text of whatever you click; only page views remain there. We do not load it at all on guest pages or on any other page opened through a personal link — the invitation, the RSVP, the gift page, the event sheet, the feedback form, a professional's questionnaire and password reset are neither tracked nor recorded (their privacy policy).
• Meta Platforms Ireland Limited (Ireland) — measuring the ads we run on Facebook and Instagram, only if you choose "Advertising" in the cookie banner (basis: Art. 6(1)(a) GDPR and Art. 4 of Romanian Law no. 506/2004). We use two channels, both off without that consent: the Meta pixel, a script that loads only on the public pages and the sign-up pages and tells Meta which page you visited, your IP address, your browser type and the identifiers in Meta's cookies; and, when an account is created, a message sent directly by our server (the Conversions API) reporting the sign-up, containing the account's e-mail address and identifier, both irreversibly hashed (SHA-256), the IP address, the browser type and the account type chosen. We never send Meta your name, your phone number, or anything about a wedding, its guests or its gifts. The pixel never loads on guest pages, nor in the couple's dashboard or the professional portal. For collecting and transmitting this data we are joint controllers with Meta; Meta's further processing is its own, as an independent controller under its own policy (their privacy policy). You can withdraw consent at any time from "Cookie settings" in the footer of the public pages.
• Functional Software, Inc. (Sentry) (USA) — monitoring of technical errors in the Platform, hosted in the EU (Germany). We have configured it to receive only the technical information an error diagnosis needs — the error message, the page it occurred on, and the browser or server context — and to exclude form contents, request headers and cookies, and anything identifying you: we set no Sentry cookies, record no sessions, and attach no IP address to error events. Personal links (invitation, event sheet, feedback form, a professional's questionnaire, password reset) have their token stripped before anything is sent. Unlike analytics, error monitoring stays active on guest pages too: an invitation that fails to open on the wedding day is the most expensive failure this Platform has. Basis: our legitimate interest in keeping the Platform working (Art. 6(1)(f) GDPR) (their privacy policy).

The WhatsApp and email send buttons open your own local apps with a pre-filled message — through these buttons the Platform transmits no data to WhatsApp/Meta; the message is sent from your device and your account. Public Marketplace profiles may embed a video hosted on YouTube (Google), exclusively in the player's privacy-enhanced mode — when such a profile is displayed, your IP address is visible to YouTube, to which Google's privacy policy applies (details in the Cookie Policy). Data may be disclosed to authorities only where the law requires it.

Some of our providers are US companies, even where your data is hosted in the European Union (Railway — Amsterdam; Cloudflare — EU-jurisdiction storage; Sentry — Germany; PostHog — Frankfurt); Meta also processes data in the United States, through Meta Platforms, Inc. Where a transfer outside the European Economic Area does take place, it relies on the EU–US adequacy decision (the EU–US Data Privacy Framework) while the provider is certified under it, and otherwise — or if that certification ends — on the standard contractual clauses approved by the European Commission, which are part of our contract with each provider. We will tell you on request which mechanism applies to a given provider.

• Account and event data: for as long as the account exists. Deleting the account permanently deletes the wedding, guests, gift ledger and associated files; standalone events left without an owner are deleted as well. If a wedding planner or a venue was connected to the wedding, it keeps a copy of the event in its own account, which it needs for its work: the couple's names, the date, the number of guests, the day's schedule, the vendors, the contact details it already holds, its own notes and the rating you gave it. The guest list, gift ledger, messages and wishlist are never copied and are deleted with the account. Answers sent through a professional's questionnaire are not deleted with the account (see below).
• Video messages left by guests: videos are deleted automatically 3 months after the wedding date, so the couple can download them until then; the couple is emailed 7 days beforehand. Written messages stay in the account for as long as it exists.
• The gift ledger is designed as a long-lived record — it remains available to the couple for as long as they keep their account; they can export it (CSV) or delete it at any time.
• Guest links stay active until 3 months after the wedding date, after which they no longer open at all. The RSVP and wishlist reservations close earlier — the day after the wedding itself; the gift page stays open to the end, because gifts keep arriving after the event.
• Marketplace inquiries: until deleted by the professional or until that professional's account is deleted.
• The referral link between a Couple account and the professional that referred it: for as long as the Couple account exists; credit already given stays in the billing records for the period the law requires.
• Answers to a professional's questionnaire, and the photos uploaded in it: until the professional deletes the link, the questionnaire or their own account; the photo files are then deleted from storage too. For as long as the professional keeps them, you can view them too, but not change them; once the professional deletes them, they disappear from your account as well. Deleting your couple account does not delete them: the answers were sent to the professional and stay with them, like any other document you sent them. Only their link to your account is removed, and the label the professional gave the link appears in place of the couple's names. If you want the professional to delete them, address the request to them, or write to us and we will pass it on (see “Your rights”). A photo you delete before sending is removed from storage straight away.
• Professionals' contracts: the values typed in are deleted when the signed copy is uploaded or when the professional cancels the contract, and if you delete your account before then, they are deleted with it. The signed copy stays in the professional's storage until the professional deletes it or their account; while it exists, you can download it too. Keeping it is the decision of the professional, who is its controller.
• Messages sent through the contact form: they stay in our email correspondence for at most 12 months after the matter is settled.
• Records of acceptance of the unusual clauses (professional accounts): for as long as the account exists, plus the period in which a right arising from the contract can still be pursued; deleting the account deletes them with it.
• The detail you write under “other” (an allergy, an intolerance): deleted automatically 14 days after the wedding date, together with the event-sheet link that carried it. It serves no purpose once the meal has been cooked, and the menu choice itself stays.
• The event-sheet access link: closes automatically 14 days after the wedding date (details under “Who can access the data”).
• Financial-accounting documents (invoices): the statutory archiving periods under Romanian tax law.
• Password-reset links: they expire after 60 minutes and can be used only once.
• Unconfirmed accounts: an account created with an email and password whose address is not confirmed within 7 days is deleted automatically, together with its confirmation links (valid for 24 hours, single use). Accounts created through Google have a confirmed address from the start.
• Technical logs: short periods, as needed for security.

We may keep some data beyond the periods above where we need it to meet a legal obligation or to establish, exercise or defend a legal claim. Where that happens we keep only the data that purpose needs, only for as long as it needs it, and we use it for nothing else.

Deleting your account does not affect invoices already issued: those are accounting documents, they are held by our invoicing and payment providers for the period Romanian tax law sets, and they cannot be deleted on request.

Deletion does not reach the backups instantly, though: once you delete a file, the wedding or the whole account, the data can remain for a limited period in the copies described below under "Data security", until those are rotated and overwritten. Throughout that period it stays protected by the same security measures as the live data and is not used for any other purpose.

Cookie lifetimes are detailed in the Cookie Policy.

We apply technical and organisational measures appropriate to the risks of the processing. We review them and may change them, provided the level of protection does not drop. At present they include: encrypted connections (HTTPS), passwords stored as hashes, encrypted sessions, server-side access checks on every operation, cryptographically generated links and codes, login rate limiting, and strict data separation between accounts.

If data we control is involved in a security breach that puts your rights at risk, we notify the Romanian supervisory authority within 72 hours of becoming aware of it, and where the risk is high we tell you as well. Where the controller is a professional customer — their own events, their own clients, their own inquiries, their own questionnaires — notifying the authority and informing the people affected is their responsibility; we alert them without undue delay and give them what they need, as set out in the Data Processing Agreement.

We keep backups, so that a fault or a deletion made by mistake does not mean the data is gone for good. Every night we copy both the database and the uploaded files (photos, video messages, documents) into private storage, separate from the infrastructure the Platform runs on and hosted in the European Union. We keep the last 30 nightly copies of the database and one copy per month for 12 months, and the copy of a deleted file survives for at most 30 days before it leaves the backups too. The copies are protected by the same measures as the live data, are used for nothing else, and the restore procedure is one we test rather than merely document.

Under the GDPR you have the right of access to your data, the right to rectification, to erasure, to restriction of processing, to data portability, the right to object (in particular to processing based on legitimate interest) and the right to withdraw consent at any time, without affecting prior processing. Guests may exercise these rights directly with us where their data was entered by the couple — there, the controller is us. Where the event is run entirely by a professional, that professional is the controller: we still take the request, tell you who the controller is, pass it on within three working days, and follow it up so that you get your answer within the period the law allows. The same applies to your answers to a professional's questionnaire: their controller is the professional, whom you can ask directly to give you access to them, rectify them or erase them. If you write to us instead, we pass the request on within the same period.

We take no decisions based solely on automated processing that produce legal effects concerning you or similarly significantly affect you (Art. 22 GDPR), and we do not use profiling for that purpose. Our analytics tool builds no person profiles: we never send it your identity and we do not tie activity to your account. The Platform does run routine automated checks — it limits how many times a login can be attempted, it checks that the domain of the email address given at signup actually exists, and it closes portal access when a business account's subscription has expired — but those look at the request or at the state of the account, never at your personal characteristics.

The order Marketplace listings appear in is set by published criteria, identical for everyone, and is described in full in the Terms and Conditions under “How Marketplace listings are ordered”. Briefly: the average and number of ratings a professional has received from couples, the filters you choose on the page, and a share of first-page slots kept for recently published profiles. A paid plan decides whether a profile is in the list, never where in it. Nothing about you as a visitor is used to order the results, and no position is for sale.

To exercise your rights, write to us at contact@loomia.ro; we answer within the period the GDPR sets — as a rule within one month, and where a request is complex or several arrive at once, within three months at the outside, in which case we tell you within the first month that we are extending and why. Account holders can delete their account at any time, together with the associated data and files (with the exceptions set out under “How long we keep the data”), from the account page. You also have the right to lodge a complaint with the Romanian supervisory authority (ANSPDCP), B-dul G-ral. Gheorghe Magheru 28-30, Bucharest, dataprotection.ro.

The Platform uses strictly necessary cookies (the authentication session, a marker telling the public pages that you are signed in, the language preference, the record of your choice in the consent banner and, where relevant, the questionnaire we take you back to after you create your account) and, only with your consent given in the banner, the PostHog analytics cookies and, with a separate consent, the Meta advertising cookies, both described above. Details in the Cookie Policy.

We may update this policy; the current version and its last-updated date are permanently published on this page, and significant changes will be announced in the Platform. Questions: Trailbits SRL, contact@loomia.ro — or through our contact page.