Privacy notice
Last updated
This notice explains what we collect when you plan a wedding with Blissful Tomorrow, visit this site or open a page a couple has shared with you. It also says why, who helps us handle it, and the choices you have.
1. Who we are
We are Blissful Tomorrow, registered in Singapore. This notice covers the Blissful Tomorrow website at blissfultomorrow.com, the wedding planner you sign in to, the pages your guests open from the links you share, and our mobile apps.
As a Singapore organisation, we follow the Personal Data Protection Act 2012 (Singapore), called the Act in this notice, and Singapore law governs this notice. If you live elsewhere, the law where you live may give you rights as well, and nothing here takes them away.
The Act asks us to have a data protection officer and to publish how to reach them. Write to ours at support@blissfultomorrow.com.
2. What we collect and why
What we hold depends on how you use Blissful Tomorrow. Here is each kind and what we use it for.
- Your account. Your email address, your name and, if you add one, your phone number. We use them to sign you in with a magic link, to run your account and to contact you about it.
- Your wedding. The couple’s names, the date, your events, your country and currency, and the answers you give when you set the wedding up, such as how many guests you expect, the kind of venue, the feel you want and your traditions. We use them to run the planner for you.
- Your guests. Their names and contact details, dietary needs, RSVP answers, seating and arrival on the day. You and your guests enter them, to run your events.
- Budget and tasks. Your budget, your expenses and the people contributing to them, your tasks, and the receipts and files you attach.
- Your microsite and save-the-dates. What you write and upload for them, including anything you choose to publish on a public page.
- Memories. The photos and videos guests upload to your memories page. Guests upload with no account and no name. The upload page keeps a random id in the guest’s browser and sends it with each upload, so that you can hide everything one device sent.
- Your conversations with the microsite’s chat assistant. We keep them so that a conversation can carry on where it left off.
- Gifts. The contributor’s name, the amount and the message of each gift you record or a guest sends you.
- Payments. Which wedding was paid for, who paid, what was paid and in which currency, the region the price was set for, and Stripe’s references for the payment. Your card details go to Stripe and never reach us.
- Changes in a wedding. A log of who changed what, kept as the wedding’s history. We also count, across all weddings and never per person, how couples use Blissful Tomorrow, such as how far new weddings get in their first weeks, to improve it. None of it goes to Google Analytics.
- Analytics, only with your permission. Analytics events and the attribution cookie, described in section 5 and section 6.
- Server logs. Each request to our servers is logged with its internet address and a description of the browser that sent it, which we use to keep the service running and secure. Our hosting provider also tells us which country a request comes from, so that we can show you the price for your region.
3. Your guests and the people you invite
You decide what to enter about each guest, and you are responsible for what you enter. We handle it on your instructions, to run your events, and we email your guests only when you send them something from the planner, such as your save-the-dates.
If you are a guest, what we hold about you is what the couple entered and what you sent us yourself: your RSVP answers and plus-ones, your email and phone if you gave them, a gift’s message and the photos and videos you upload. You can ask the couple about it, or write to us at support@blissfultomorrow.com.
Guests reach their RSVP page, the memories page and the couple’s microsite through links the couple shares. A memories upload carries no name and no account, only the random id described in section 2.
When you invite someone to help you plan, we email them your invitation. Once they accept, they have an account of their own, and this notice applies to them as it does to you.
4. Who helps us run the service
These providers do part of the work of running Blissful Tomorrow for us.
| Provider | What it does for us | Where it keeps data |
|---|---|---|
| Google Cloud | Hosts the service: our servers, our database and the files you upload. | Singapore; backups and service logs elsewhere in Google Cloud |
| Resend | Sends our emails: sign-in links, invitations, save-the-dates and task reminders. | Outside Singapore |
| Stripe | Takes payments, on its own checkout pages. | Outside Singapore, including the United States |
| Google Fonts and Google Maps | Serve the typefaces of our pages, and find a venue as you type it in the planner. Your browser fetches both from Google directly. | Google’s servers worldwide |
| jsDelivr | Serves one language file that the seating plan’s image scan needs, fetched by your browser. | Its servers worldwide |
| Anthropic, Google and OpenAI | Answer AI help (section 8). They receive the wedding details and the text you ask it to work from, and from your guest list only counts and standard categories, never the names on it or your uploads. | Outside Singapore, including the United States |
| Google Analytics | Measures how people find and use this site, only if you allow it (section 6). | Outside Singapore, including the United States |
Several of these providers keep data outside Singapore, including in the United States. Google Cloud, Resend, Stripe, the AI providers, Google Analytics and Google Maps, which the planner uses through our key, work for us under our accounts with them and are bound by their contracts with us, as section 9 explains. Your browser fetches Google Fonts and the jsDelivr language file directly from those providers, under their own terms and with no account of ours.
5. Cookies and similar storage
These are the cookies and the browser storage our pages use. None of them is for advertising.
| Name | What it is for | How long |
|---|---|---|
| Cookies | ||
__session | Keeps you signed in. Only our server can read it. | 30 days |
__csrf | Protects the forms you send us, so that another site cannot send them as you. | 30 days |
bt_ | Remembers your answer about analytics. | 1 year |
bt_ | Remembers which page and link brought you here. Set only after you allow analytics, and sent with your sign-in so that your account’s first visit can be credited. | 30 days, renewed when you sign in |
_ga and _ga_ | Google Analytics, set only after you allow analytics. If you later say No, we stop them and remove what we can, and the rest expire on their own. | 2 years |
std_ | Remembers that a save-the-date has played, on that save-the-date’s page alone. | 90 days |
| Local storage in your browser | ||
std_ | Remembers whether you muted the music on a save-the-date page. | Until you clear it |
memories: | The random id the memories upload page keeps, so that the couple can hide everything one device sent. | Until you clear it |
bt_ | The date of the privacy notice whose change you closed on your overview, so the line doesn’t show again in this browser. | Until you clear it |
| Session storage, while the tab is open | ||
blissful: | A save-the-date design the free plan could not save, kept so that it comes back after you pay. | Until the tab closes |
bt_ | The price of a payment you started. Set only after you allow analytics. | Until the tab closes |
bt_ | A mark that a payment was counted. Set only after you allow analytics. | Until the tab closes |
| IndexedDB in your browser | ||
eng.traineddata | The English language file the seating plan’s image scan uses, kept after a scan so the next one need not fetch it again. It holds no personal data. | Until you clear it |
6. Analytics: your choice
We ask before we measure anything. Until you answer, and if you answer No, we load no analytics, set no analytics cookie and send Google Analytics nothing.
If you allow it, we use Google Analytics to learn how people find and use this site. We measure:
- the pages of this site and the sign-in page you visit
- the buttons and links you press, whether you reach the pricing section, and which questions you open in the FAQ
- whether you ask for a sign-in link, sign in or sign up, create a wedding and pay
- the page and link that brought you here
Allowing it also lets us keep the attribution cookie described in section 5, which remembers that page and link and goes with your sign-in, so that your account is credited to them.
Inside your wedding we send only the sign-in, sign-up, wedding-created and payment events, with the page’s address and title fixed to the wedding’s front door. The one thing those events say about how you use the planner is which part of it, or which limit of the free plan, led you to unlock the wedding. Google Analytics itself also records that a visit happened, whether it was a first one, and how long the page stayed open.
We never send Google Analytics your email, your name, your guests, any link token or any id of ours. We do not use it for advertising, and Google signals, which links visits to signed-in Google accounts, is off.
If your browser sends Global Privacy Control, we treat it as No without asking, for analytics and for the attribution cookie alike.
We remember your answer for a year, then ask again. You can change it here at any time. A No stops analytics at once, in every tab you have open, removes our attribution cookie and removes Google’s cookies as far as we can; the rest expire on their own.
Analytics: not asked yet
7. Payments
When you unlock a wedding, you pay on Stripe’s own checkout pages, and your card details go to Stripe, never to us. We keep the payment record described in section 2. Stripe keeps its own records under its privacy notice.
8. AI help
AI help drafts things for you when you ask it to:
- your day-of timeline, and a check of it for gaps, which sends your events’ titles, times and venues
- a suggested checklist for an event
- your task checklist
- the how-to for a task
- your microsite’s text, from its editor or its chat
Each sends the text you type for it and the wedding details named in section 2, as you wrote them. From your guest list it sends only counts and the standard categories, such as how many guests are on the A-list or in the bridal party, so the names on your guest list are never sent. Any other text you enter reaches the model as you typed it. AI help never sends your budget or your uploads.
The provider that answers, Anthropic, Google or OpenAI, receives it to produce the answer and keeps it under its own API terms. We never use it to train a model, and under the API terms we use, neither do the providers. What comes back is a draft for you to edit.
9. Where your information is kept
We keep your information in Google Cloud’s Singapore region, asia-southeast1: our servers, our database and the files you upload. Google keeps the database’s backups in its Asia multi-region, and our service logs, which can include your email address, in its global logging store. Where Google, or another of the providers in section 4 that we hold an account with, keeps data outside Singapore, it does so under a contract that meets the Act’s transfer limitation obligation: your information must be protected to a standard comparable to the Act’s. Google Fonts and the jsDelivr language file are fetched by your browser directly, under those providers’ own terms.
10. How long we keep it
We keep your information for as long as the wedding it belongs to is being planned and run and we have a business or legal need for it. After that, we delete it or make it anonymous.
Today that means:
- a wedding’s information stays while the wedding exists in your account, archived weddings included
- payment records are kept for as long as the law requires
- sign-in links and invitations expire on their own
- backups of our database roll off on our hosting provider’s schedule
11. Your rights and how to ask
Under the Act, you can ask us:
- for a copy of your personal data, and for how it has been used or disclosed in the past year
- to correct it
- to stop using it, by withdrawing your consent: for analytics, with the buttons in section 6; for anything else, by email
Write to us at support@blissfultomorrow.com. We reply within 30 days, and if we need longer, we tell you within those 30 days when we will reply.
If you withdraw consent for information the service needs, we can no longer run the service for that wedding.
You can also ask us to delete your information. We delete what we no longer need to keep, and tell you what must stay and why.
You can download much of it yourself: your guest list, budget, seating plan and gifts each have an export.
12. Changes to this notice
Each version of this notice is dated, and the date at the top is this version’s. When we change it in a way that matters, we tell you in the product.
13. Contact
For anything about your privacy or this notice, write to our data protection officer at support@blissfultomorrow.com.