1. Who we are
Mangkol ("we", "our" or "us") is a bilingual invitation platform for weddings and other ceremonies, based in Phnom Penh, Cambodia. The legal name and registered address of the company behind Mangkol will be shown here once confirmed (proposed). This policy explains what personal data we collect when you use mangkol.com, how we use it, and what choices you have.
2. Data we collect
We collect only what is necessary to operate the platform:
- Account data — your name, the phone number and/or email address you sign up with, your password (stored only in hashed form) and your language preference.
- Google or Facebook sign-in — if you sign in this way, we receive your name, your account ID with that provider, your profile photo and, if the provider shares it, your email address. If it does not, we ask you for a phone number or email address and confirm it with a one-time code before creating your account.
- Event data — ceremony details (names, dates, venue, programme, seating) and the photos and other media you upload for your invitation.
- Voice greeting and music — if you add a voice greeting or upload background music, we store the recording, the greeting text, the music file and any AI voice lines we make from your text (such as a greeting that says each guest's name). We ask for your consent on that invitation first.
- Your own voice for thank-yous — if you and your partner both agree, we store each partner's voice sample and a recording of the consent sentence, the voice made from them, the thank-you messages you write and their spoken versions, and who agreed and when.
- Guest data — names of the guests you add (by typing, importing a file or, if you choose, reading a photo of a list) and, if you enter them, their phone numbers and email addresses, plus the details you manage for them, such as their group, how many people they may bring, a personal message, their table, their check-in time and any cash gift you record. You are the data controller for your guests; we process this data on your behalf.
- Team members — the phone number or email address of anyone you invite to help manage your invitation.
- RSVPs, messages and photos — the responses guests submit through your invitation link, their answers to your RSVP questions, their messages and any photo they upload with their RSVP.
- Guests' voice replies and blessings — if you turn these on, a guest who agrees to their own notice can record a voice reply or a blessing. We store the recording and the text written from it with your invitation, so you can listen to it and read it.
- Live screen — if you turn on a live screen for your event, the name a guest signed with, their wish and their photo are shown to anyone who has the screen link, but only the ones you approved.
- Recordings we do not keep — speaking to the AI setup assistant, speaking gifts at the reception, the audio for live captions, a spoken design brief, a call recording used by our managed-service team and the photo of a guest list are processed once and not kept. What they produce, such as the guests you import or a gift you confirm, is kept like any other data you enter.
- Payment records — your orders (Event Passes, AI credit packs, premium templates and custom designs), their price, any promo code and the payment status. If our team marks an order paid after a payment made outside the site, we note how. Card and bank details are entered on ABA PayWay's own payment page; we never receive or store them.
- AI credits — your balance, each batch of credits with its expiry date, bonuses and referral rewards, and a history of what each credit was used for. We also log each AI request (which feature, when, for which invitation, how many credits and whether it worked), but not the text, audio or photos you sent.
- Referrals — your referral code, who joined with it and whether the reward was paid. To catch abuse we keep a scrambled code (a keyed hash) made from the device ID and the IP address, never the raw IP address or device ID.
- Custom design orders — your brief, any files you upload, the messages and proofs exchanged with our design team, the quote and the status of your order.
- Invitation activity — when a guest first opens their personal invitation link and when they are checked in at the event, shown to you on your invitation dashboard.
- Anonymous usage counts — to see where sign-ups and RSVPs get stuck, we count steps such as a page view or an opened invitation against a random ID that lives only in that browser tab (not a cookie). If you then create an account or reply to an invitation in that tab, those steps are linked to it. These counts contain no names, phone numbers, email addresses, IP addresses or browser details, and are never used for advertising.
- Technical data — your IP address is used to limit repeated requests and to protect the sign-in and RSVP forms from abuse.
3. How we use your data
- To provide and operate the invitation and guest-management service.
- To send one-time codes and service messages by SMS or email (sign-in and verification codes, password resets, team invitations).
- To send event reminders to your guests by email, when you turn reminders on for your invitation.
- To email a guest their personal invitation link, when you send it from your guest list or when the guest asks for it on your invitation page. It only goes to the email address you saved for that guest, never by SMS.
- To display invitation analytics on your organiser dashboard.
- To run the AI features you choose to use, as listed under service providers below.
- To give you support, handle orders, refunds and reports of abuse, and keep the service secure and fair (including limiting repeated requests and checking referrals for abuse).
- To improve the platform and fix bugs using aggregated usage counts.
- We do not sell your data or your guests' data to anyone.
4. Guest data and your responsibilities
When you add guests to Mangkol, you are acting as the data controller for that personal information. You are responsible for ensuring you have a lawful basis to share your guests' names and contact details with us (for example, that they have agreed to receive your invitation). We only use guest data to power the features you use for your invitation, such as RSVPs, reminders, seating, check-in (including offline check-in on your staff's devices), the message wall, the live screen and voice replies. Guests can stop reminder and link emails with the unsubscribe link in each email. If a guest asks us about their data, we refer them to you, the host, unless the law says otherwise (proposed).
5. Who at Mangkol can see your data
A small team of our staff uses an internal admin console to give support, look after orders and refunds, review templates and designs, take down invitations that break our terms and handle account requests. Staff have one of three roles (super admin, admin or support), and each role can only do what it needs: for example, support staff can look up accounts, invitations and orders, but cannot refund or delete. Every change staff make in the console is written to an audit log that records who did what and when.
6. Service providers
We share data only with the providers that help us run the service, and only what each of them needs:
- DigitalOcean hosts our servers and database, and stores uploaded files (photos, recordings, music) in DigitalOcean Spaces.
- Cloudflare sits in front of mangkol.com: all traffic to the site passes through it, and it may check that a form is being sent by a person rather than a bot.
- An SMS provider in Cambodia delivers one-time codes and team invitations by text message.
- An email delivery service sends verification emails, password resets, team invitations and reminders.
- ABA PayWay processes payments for Event Passes, AI credit packs, premium templates and custom designs.
- Google and Facebook, if you choose to sign in with them.
- Smean AI, our partner in Cambodia, turns text into speech and speech into text. It receives data only for the voice features you choose: the greeting text for an AI voice greeting; the names, date, venue and programme on the invitation when a guest taps "Listen to the invitation", if voice features are on; each guest's name when that guest opens their link, if you turn on greeting guests by name; and voice messages you record for the AI setup assistant, after you agree.
- Google Gemini, Google's AI service, writes text and speech for the optional AI features, and only when you ask. Text it receives: the details on your invitation (names, date, venue, programme and its current wording) for the invitation text, wording suggestions and reminder drafts; one guest's name and group for a suggested personal message; your conversation with the AI setup assistant; questions typed into the help assistant (signed-in users only); after your event, the invitation's totals (guests, replies, arrivals and gift totals) and up to 20 of your guests' wishes, without their names, for the wedding summary; and the text of announcements and thank-you messages you write, to be read aloud. Your guest list and gift details are not sent for writing.
- Google Gemini also receives sound, only for the feature you use: a guest's voice reply or blessing (to type it out and, for a blessing, translate it into English); each partner's voice sample (to make the voice for spoken thank-yous); audio for live captions; gifts spoken at the reception, together with the names on your guest list (names only); a design brief you speak to our design team; and, when our managed-service team writes notes from a call, the call recording, which the family has agreed to. On an invitation these features need the owner's consent first; the AI setup assistant asks for your own consent before your first typed or spoken message; both partners agree before a voice is made; and guests see their own notice before they record.
- A photo of a guest list, including the names, phone numbers and groups written on it, goes to Google Gemini only when you upload it to import guests.
We do not use third-party advertising or analytics services.
7. Where your data is processed (proposed wording)
Our servers and file storage are run by DigitalOcean outside Cambodia. Google (Gemini) and Cloudflare also process data in other countries, and sign-in with Google or Facebook is handled by those companies. By using Mangkol you understand that some of your data and your guests' data is processed outside Cambodia by these providers. We share only what each feature needs, as described above.
8. Cookies and device storage
We use only cookies that are strictly necessary for the service:
- Sign-in cookies (access_token, refresh_token) keep you signed in. Scripts on the page cannot read them. If you choose to stay signed in, they last up to 30 days; otherwise they end when you close your browser.
- A small flag cookie (sambok_session) tells the app that you may be signed in. It contains no personal data.
- During Google or Facebook sign-in, two short-lived cookies (oauth_state, oauth_pending) protect the sign-in and remember it for 10 to 15 minutes while you finish.
We also keep a few things in your browser's own storage rather than in cookies: your language choice, display settings such as larger text, an unsaved invitation draft and your place in the invitation editor, a guest's unfinished RSVP and invitation link, announcement banners you dismissed, the random visit ID described above, and, for the referral programme, the referral code you arrived with and a random device ID. Items kept for a single tab are cleared when you close it. We do not use advertising or cross-site tracking cookies. You can block cookies in your browser settings, but you will then not be able to sign in.
9. Check-in on a staff device
So that check-in keeps working when the internet drops, the check-in page of an invitation saves a copy of the guest list on the device of the staff member who is signed in:
- What it holds: each guest's name, group, table, party size, whether they are checked in and a scrambled fingerprint (a hash) of their invitation code. It never holds phone numbers, email addresses, gift amounts or personal messages.
- Check-ins made offline wait on the device until the connection returns, and are dropped if they cannot be sent within 3 days.
- The copy is erased when the staff member signs out, and 12 hours after the event ends.
Anyone who can use that device while it is signed in can see these names, so staff should sign out of shared devices and keep their phones locked.
10. Data retention
We keep your account and event data for as long as your account is active. In addition:
- When you delete an invitation, it is taken offline for guests straight away. Its records are not yet erased automatically; contact us if you want them permanently deleted.
- You cannot yet delete your account from your account page. To delete it, contact us and our team will do it for you. We then erase your sign-in details and profile and sign you out everywhere. Your invitations are taken offline straight away and their records are kept like those of a deleted invitation (above). AI credits left on the account can no longer be used. Records of your purchases are kept, without your name or contact details, because we must keep financial records.
- When you withdraw consent for voice and AI features on an invitation, the voice recording, guests' personal greetings, uploaded music, guests' voice replies, blessings and announcement audio are removed from the invitation and their files are deleted from our storage straight away. Voice messages for the AI setup assistant are never kept.
- If you or your partner withdraw consent for your voice, new thank-you messages stop at once and your voice sample and the voice made from it are deleted, straight away or, if Google cannot be reached, within 30 days. Messages already sent to guests stay.
- A guest's voice reply or blessing is kept with the invitation until the hosts (or, for a blessing, the guest) remove it, consent is withdrawn or the invitation is deleted. A voice reply that a guest records but does not send is deleted within about a day.
- Live captions are not recorded. The captions on your display link are deleted when you turn them off, or after 12 hours.
- AI credits expire 1 year after they are bought or given and are then removed from your balance. The record of what you bought and your credit history are kept as financial records.
- Photos that guests upload but never send with an RSVP are deleted automatically within about a day.
- The audit log of changes our staff make, and the log of AI requests (which hold no text, audio or photos), are kept as security and cost records. We have not set an automatic deletion period yet (proposed: to be decided).
- Individual usage counts are deleted after 13 months; after that we keep only daily totals.
11. Security
Passwords are hashed and never stored in plain text. All data travelling between your device and mangkol.com is encrypted with HTTPS (TLS), and access to our servers and storage is restricted. Despite these measures, no internet service is 100% secure — please use a strong, unique password and never share your one-time codes.
12. Your rights
You have the right to:
- Ask us for a copy of the personal data we hold about you: contact us and our team will send it to you.
- Correct inaccurate data — you can edit most of it yourself in the app.
- Ask us to delete your account and its data: contact us and our team will do it for you.
- Withdraw your consent for voice and AI features at any time, on the invitation itself; your consent for the AI setup assistant (typed and voice messages) on that screen; and your consent for your own voice in the voice settings.
To exercise any of these rights, write to us through our Contact page.
13. Age and children
Mangkol accounts are for adults: you must be at least 18 (proposed: the minimum age is still to be confirmed). Guests and family members of any age can appear on an invitation, so if you add a child's name, photo or voice, you are responsible for having the permission of a parent or guardian.
14. Contact
Questions about this policy? Reach us through our Contact page.