Privacy Policy

01Who we are

The service operator identified in our Legal Notice is the data controller for the account data and website data processed through this platform. For questions about this policy or your data, write to us at contacto@tudiadeblanco.com.

Where the GDPR applies, the organiser determining the purposes of guest-data processing acts as controller, and we process that data on their documented instructions under our data processing agreement. Roles depend on the circumstances, including whether a planner acts for a couple; purely personal or household activities may fall outside the GDPR.

02Data we collect

Account data — when you register an account as a couple member or a wedding planner: name, email address, password (stored only as a secure hash), and your role and permissions on each wedding.

Wedding content — information you add to your workspace: the couple's story and details, schedule, news updates, budget figures, seating plans, documents, and chatbot knowledge base.

Guest data — added by the people running a wedding or submitted by guests through an RSVP: guest names, contact details, invite codes, RSVP responses, plus-one nominations, dietary and accessibility needs, and private letters to the couple.

Conversation data — questions asked to Concierge on an invitation website, used to answer doubts and improve the knowledge base.

Technical data — security and service logs needed to operate the platform; optional usage and performance measurements (Vercel Web Analytics and Speed Insights) are sent to Vercel only with your permission.

Registration origin and onboarding — when a couple registers: the promotional code or QR campaign used, if any; the campaign parameters of the link that brought you (such as utm_source) and the website that referred you, when your browser shares them; and milestones in setting up the workspace (for example, when the trial started, the first guest was added or the website was published). We use them to know which channels work and to improve onboarding, never for advertising.

03iPhone and iPad app

The native app accesses the same account and wedding workspace as the web. Email-and-password sign-in sends those credentials securely to our token endpoint. The app stores its session credentials in the device Keychain; its Share extension and widgets use the app's shared storage to provide their features. Signed-in device names and notification tokens are used for session management and requested notifications.

If you connect Sign in with Apple, we verify Apple's identity token and store its account identifier as an additional sign-in method. We do not request your Apple name or email, do not merge accounts by Apple email, and keep your existing account email unchanged. You can disconnect it at any time in the app under Settings → Account.

Before uploading a document for AI processing or using the private document assistant in the app, you are asked to agree to sharing the document or conversation and relevant content with OpenRouter and its selected model providers. You can decline and continue using the other workspace features. Provider processing is described in Concierge and AI below.

04Photo pool and Google Drive

When the couple connects Google Drive, we access the connected email and the folder and files created through Tu Día de Blanco with drive.file, without access to unrelated Drive files. We create the wedding folder, arrange guest uploads and check folder availability and free storage to warn the couple.

We store an encrypted refresh token, connected email, folder id and link, storage and connection health, and upload metadata (file name, type, size and uploader name). Access tokens are held temporarily in server memory. Photos and videos go directly from the guest’s browser to the couple’s Google Drive; TDB does not receive or store their contents.

The couple controls access, sharing and deletion in Drive under Google’s applicable terms. Guests should upload only content they are entitled to share and inform people shown where required. Contact the organisers or contacto@tudiadeblanco.com for access or deletion requests.

Disconnect in the Workspace to delete our stored connection and request revocation, or revoke Google access at https://myaccount.google.com/permissions. Existing files remain in the couple’s Drive. Upload metadata follow the wedding-data retention terms; disconnecting alone does not delete these records.

Tu Día de Blanco’s use and transfer of information received from Google APIs adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements. This information is used only to provide the Photo pool, not for advertising, sale or AI model training.

05Workbook tasks in Google Calendar and Google Tasks

A member of a wedding can connect their own Google account and choose individual Workbook tasks to copy to Google Calendar, Google Tasks or both. We request openid and email to identify the connected account, calendar.app.created for Calendar (a calendar Tu Día de Blanco creates and its events, without access to your other calendars) and tasks for Google Tasks. Google offers no narrower Tasks permission; we only create, update and delete items in the task list Tu Día de Blanco created, and never read or change your other lists.

Each copy contains only the task's title, due date, whether it is done and a link back to the task. Notes, assignees, sharing and other wedding data are not sent. Copies are updated when the task changes and removed when you stop syncing a task, can no longer see it, or leave the wedding. Nothing is read back from Google.

We store an encrypted refresh token, the connected Google account id and email, granted permissions, the ids of the calendar, task list and copies we created, and sync status. Access tokens are held temporarily in server memory. Only the member who connected can see or manage their connection.

Disconnect in the Workbook and choose whether to keep the copies in Google or have us remove the copies we created; the calendar and list we created remain so anything you added yourself is kept. Disconnecting deletes our stored connection and requests revocation unless the same Google account is still connected elsewhere in Tu Día de Blanco. You can also revoke access at https://myaccount.google.com/permissions; copies already in Google then remain until you delete them.

Tu Día de Blanco’s use and transfer of information received from Google APIs adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements. This information is used only to provide task sync, not for advertising, sale or AI model training, and no person at Tu Día de Blanco reads it except with your permission, for security or where the law requires.

06The planner's Agenda in calendar apps and Google Calendar

A wedding planner can turn on a private calendar address for their Agenda and subscribe to it from Google Calendar, Apple Calendar, Outlook or another calendar app. The app then fetches the planner's dated Agenda entries of the kinds they choose (wedding dates, requested dates, fee payments due, enquiry follow-ups, wedding tasks and business tasks), each with its name, day and a link back. Notes, amounts, assignees and contact details are not included, and every fetch only returns what the planner may see at that moment. Anyone holding the address can read these entries, so the planner should keep it private; making a new link or turning it off stops the old address. Once fetched, the entries are held by the calendar provider under its own terms.

A planner can also connect their own Google Calendar to see their appointments in the Agenda. We request openid and email to identify the connected account and calendar.events.readonly to read events. We read only the main calendar, only for the days on screen while the planner uses the Agenda, and only each event's title, times, location and link. Events are shown to that planner and are not stored, logged, shared with the wedding, used by the Concierge or sent to other services. We never change anything in Google Calendar.

We store an encrypted refresh token, the connected Google account id and email, the granted permissions and the connection status. Access tokens are held temporarily in server memory. Disconnect from the Agenda to delete our stored connection; to withdraw the permission in Google as well, revoke it at https://myaccount.google.com/permissions.

Tu Día de Blanco’s use and transfer of information received from Google APIs adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements. Calendar information is used only to show the planner their own appointments in the Agenda, not for advertising, sale or AI model training, and no person at Tu Día de Blanco reads it except with your permission, for security or where the law requires.

07Moodboard Chrome extension

When you choose to save a clip, the extension sends the selected image, text or link, its source URL and title when available, and your chosen collection to your wedding's moodboard. You can also explicitly upload or paste an image from your device. It does not send a general browsing history. Website access is used to identify and download the content you choose and show save confirmations.

OAuth credentials, the registered client, server preference and a collection cache are stored locally in the extension. Sign-in takes place on Tu Día de Blanco; the extension does not receive your password. Its authorisation permits adding clips and reading collection names, without access to guests or budget data. Disconnecting in the extension clears its local session; revoke server access through Settings → Connected apps. Disconnecting does not delete saved clips: manage them in your moodboard or request deletion at our contact email.

Extension data are used to provide the moodboard function, not for advertising or sale. Saved clips are handled as wedding content under the sharing and retention terms in this policy.

08How we use your data

We process personal data to:

• create and secure accounts, and manage memberships and roles on each wedding;
• build, host and serve invitation websites and run workspace modules (guests, seating, budget, updates, documents, chatbot);
• handle RSVP responses, invite codes and guest sessions;
• power Concierge so it can answer guest questions;
• send transactional emails such as access codes, confirmations and service notices;
• process payments and provide customer support;
• keep the platform secure and prevent abuse;
• measure which channels bring couples and where onboarding gets stuck (registration origin and milestones), based on our legitimate interest in improving the service.

09Legal bases

Dietary and accessibility information can reveal health or religious beliefs. Providing these details is optional. Where explicit consent is required, it must be obtained separately and may be withdrawn by clearing the details or contacting the wedding organisers. No marketing consent is bundled with account registration.

Where the GDPR applies, we rely on: performance of a contract (to provide accounts and the service you signed up for); your consent (for optional communications and certain guest-provided details); our legitimate interests (to secure, maintain and improve the service); and compliance with legal obligations (such as accounting).

10Concierge and AI

Concierge answers guest questions from a knowledge base the couple controls. Questions, conversation history and relevant wedding context are sent through OpenRouter to the configured model provider. Uploaded documents and knowledge-base text may also be sent for extraction and embeddings. Avoid unnecessary sensitive data. Provider retention, training and processing locations depend on the selected model and provider settings; contact us for the current configuration.

11Sharing and service providers

We do not sell your personal data. We share it only with providers who help us run the service, under contracts that limit them to that purpose, including:

• Vercel (web hosting and optional performance measurements), Supabase (database, authentication and file storage), and Heroku (backend hosting);
• Resend (transactional email delivery);
• OpenRouter and configured downstream model providers (AI answers, document processing and embeddings);
• Stripe (subscription payments and billing);
• Google Identity Services, when you choose Google sign-in; Notion, if configured for handling wedding offer requests.

We may also disclose data where required by law or to protect our rights and the safety of users.

12International transfers

Providers may process data outside the EEA. The applicable processing locations and transfer mechanism depend on the provider contract, region and selected AI model. Contact us to obtain the current locations, safeguards and how to request a copy. We must establish a valid transfer mechanism before transferring personal data; this policy does not itself establish those safeguards.

13Cookies and local storage

We use necessary session cookies and browser storage for authentication, language and theme. Optional Vercel performance measurements remain disabled until you allow them and can be disabled through Cookie preferences. Our Cookie Policy describes storage names, purposes, durations and controls. We do not use advertising cookies.

14Data retention

Account and wedding data are held while needed to provide the active service. Wedding data processed on a customer’s behalf follow their documented return/deletion instructions under the data processing agreement. Public website expiry limits access but does not automatically delete records or cancel billing. Billing records are retained for applicable tax/accounting obligations; security records only as needed to investigate abuse and protect the service. Any recovery or backup period must be confirmed for your service. Request an export, deletion, or the applicable retention criteria at our contact email; we will identify any legal reason preventing deletion.

15Your rights

Subject to applicable law, you may request to access, correct, delete, restrict or port your personal data, and object to certain processing. You may also withdraw consent at any time without affecting prior processing. To exercise these rights, email contacto@tudiadeblanco.com. You also have the right to lodge a complaint with your local data protection authority (in Spain, the Agencia Española de Protección de Datos).

If you are a wedding guest and want your data corrected or removed, contact the couple or planner running the wedding, or write to us and we will pass your request to them.

16Security

We protect data with encryption in transit, hashed passwords, access controls scoped by membership and role, and least-privilege access for our team. No system is perfectly secure, but we work to keep your information safe and to notify you of serious incidents where required.

17Children

The service is intended for adults. It is not directed at children, and accounts may not be created by anyone under the age required by local law.

18Changes to this policy

We may update this policy as the service evolves. We will revise the date above and, for material changes, give notice through the service. A policy update does not create consent for new processing; we will request consent separately where required.

19Contact

Questions about privacy? Write to contacto@tudiadeblanco.com.