Kathā

Your guests' information

Privacy Policy

A wedding website holds real people's names and contact details. Here is exactly what we keep, why, and when it is destroyed.

Last updated 13 September 2026

Who we are

Kathā builds and hosts wedding websites in the Philippines. When a couple books us, we handle their guests' information on their behalf, in line with the Data Privacy Act of 2012.

What we hold about a couple

Your names, wedding date, venues, the content and photos you send us, your email address, and the record of what you have booked. We use it to build your website, send you your preview and your finished website's address, and reach you about your booking.

What we hold about your guests

Their name, and whatever else you give us: an email address, a phone number, a group, a table. When they reply we also hold their answer, any dietary needs they mention, and a note if they leave one. Where a guest asks for a copy of their reply, we hold the address they gave for it.

On packages that include them, a guest uploading a photo picks their own name from your list, and that name is shown with the photo on your website.

Every public form — the reply, a photo, the message on our own contact page — also records a one-way scramble of the sender’s IP address. It cannot be turned back into an address; it exists to stop the same machine flooding your website, and it is destroyed with everything else.

Guest information is never sold, and never used for marketing — not ours, not anyone's. It exists to run one wedding. When a couple lets us show their website as an example, their guests' messages and photos are left off it unless each of those guests has agreed to that separately.

What appears publicly

A wedding website is not indexed by search engines and is left out of sitemaps — it is an invitation, not a page for strangers. But anyone with the link can open it, so treat the address the way you would a printed invitation.

What a visitor can see: a message a guest actively chose to share, and photos a guest sent after agreeing to their public display. Each appears with the name of the guest who sent it; a photo may also carry the caption they wrote. Before anything is shared, we say that anyone with the wedding link can see it. A guest can keep a note private and still send their reply.

To reply, a guest types their name and picks their household from the matches, so the form confirms the names of the people who answer together — the same names already printed on their invitation. It shows nothing else. Who replied, what anyone answered, dietary notes, contact details, a note the guest did not choose to share, and anything you wrote privately about a guest are visible only to us, signed in, and to you: each reply is emailed to you as it arrives, note included, and the notes come to you again in your keepsake.

Where it is kept

On hosting and database services whose servers may sit outside the Philippines: the site runs on Vercel, its records are in a Neon database, photos are stored with Cloudflare, and email is sent through Resend. Each of them holds the data only to provide that service to us.

Writing to us

The inquiry form on this site sends us your names, your email address, your wedding date if you give one, and your message. We keep it as our record of the conversation, and we reply to it — nothing more. Ask us at hello@angkatha.com and we will delete it.

Saved alongside it is where you came in from: if you reached us through an advertisement, the name that advertisement was given, and otherwise the site that linked you — the address of the page, never anything about you. We pay for those advertisements and this is how we tell which ones were worth it. It is carried in the web address as you move between our pages, so nothing is written to your browser to remember it, and it is deleted with the rest of the inquiry whenever you ask.

Before the form sends, Cloudflare Turnstile checks that a person rather than a machine is filling it in. That check sees your IP address and your browser. It runs on our own pages only — never on a wedding website, and never on a page a guest uses.

Who can sign in

Only we can. There is no sign-up: an account exists because we created it, and signing in with Google works only for an address already on our list. From Google we receive the name and email address on that account, and nothing else — no contacts, no calendar, no files. Couples and guests never hold an account and never need one.

While we are signed in, the session record holds our own IP address and browser, so a sign-in we do not recognise can be found. That is about us, not about you or your guests.

How long we keep it

Your website stays live for 12 months after your wedding, and is then archived. For 90 days after that you can request an export of everything.

After the 90 days we destroy it — every photo and every guest’s personal information. This cannot be reversed. We also destroy it earlier if the couple asks us to.

What survives is our own business record of the booking: your names, your wedding date and venue, the package you took and what was paid. We keep that as any supplier keeps their books. It holds nothing about your guests.

If you are a guest

You can ask us for a copy of what we hold about you, ask for it to be corrected, or ask for it to be removed — including a photo or a message. Write to hello@angkatha.com and tell us which wedding it concerns. We will act on it and tell the couple.

You can also raise a concern with the National Privacy Commission at privacy.gov.ph.

Cookies and tracking

Wedding websites set no cookies and carry no analytics or advertising trackers. Our own pages about Kathā count their visits with Vercel's analytics, which sets no cookie and records the page and where the visit came from, not who you are. Our admin uses a single cookie to keep the provider signed in, and the anti-robot check on our inquiry form may leave its own short-lived token in your browser. We do not track who opens an email or clicks a link inside it. Our cookie policy says the same thing at greater length.

Our own pages — the ones describing what we make — count how many people read them, which is how we tell whether an advertisement was worth paying for. The count records the page and where the visit came from, never who you are, and it is made without a cookie and without writing anything to your device. It runs on our pages only, never on a wedding website.

What a guest's browser fetches from elsewhere

A wedding website loads its lettering from Google Fonts, its photographs from Cloudflare, where they are stored, and — on a page showing a venue map — that map from Google Maps. To send those files, each of them necessarily sees the visitor’s IP address and browser, the same as any website that loads a font, a photo or a map. None of them is given a name, an email address or a reply, and none of them sets a cookie on the wedding site; any cookie Google Maps keeps is on Google’s own domain, under Google’s privacy policy.

We say this plainly because it is what leaves your guests’ browsers and goes somewhere we do not run. Nothing else does: a wedding website carries no analytics, no advertising, no embedded video, and no anti-robot check.

Changes to this policy

If we change what we hold or how long we hold it, we update this page and the date at the top. Anything that materially affects a live wedding, we tell the couple directly.