Privacy Policy
Last updated 6 November 2026
What Wishku collects from owners and guests, why, who sees it, where it is kept and how long we keep it.
About this policy
This policy explains what information Wishku collects, why, who sees it, where it is kept and how long we keep it. It follows the Personal Data Protection Act 2010 of Malaysia (PDPA), as amended.
Wishku is the trading name we use. We operate from Malaysia.
We try to say plainly what we do and, where we do not do something, to say that too.
Who is responsible for what
There are two roles. The owner of an event, usually the couple, decides to collect guests' photos, video, voice notes and wishes, and decides what to do with them. For that guest content, the owner is the data controller and Wishku is the data processor: we store and handle it for the owner and follow the owner's choices.
For account and payment information, and for the usage checks below, Wishku is the data controller. If we run an event ourselves with no owner account, we look after its guest content for the customer who asked us to.
In practice, a guest who wants to see, correct or delete what they sent should ask the owner first. You can also ask us to pass the request on. For everything else, ask us.
What we hold about owners
When you sign up and use Wishku, we hold:
- Your account: your email address, and a password if you set one, which we keep scrambled so nobody can read it.
- Your event: its name, the hosts' names, the dates and celebration days, venues, and the texts and cover you choose.
- Settings and PINs: your event settings, and the PINs for your memories page, live wall and kiosk, which we keep scrambled.
- Orders and payments: what you ordered, the amount, how you paid, and the references ToyyibPay and FPX give each payment. When you pay online, the name and phone number of the person paying (that may be you or someone paying for you) and your account email go to ToyyibPay to make the bill, and we keep them with that bill. We never see or store a bank card number, a bank account number or your online banking login.
- What changed: what is changed on your event, by whom and when, so that we can fix problems and spot misuse.
- Money-gift details: if you switch money gifts on, the bank name, account number and account holder name you type, and any e-wallet QR image you upload. They are shown to your guests exactly as you entered them, and we never use them to move money.
- Network details: a coarse version of your network address when you create a free event, so that we can limit free events.
- Sign-in attempts: a scrambled form of your email address for each wrong code, so that we can stop guessing. Our sign-in provider also logs the IP address of sign-in requests.
What we hold about guests
When a guest uses an event's QR code, we hold:
- What they send: photos, video, voice notes and written wishes, with any caption, and the type, size and time of each.
- Name and relationship: a name and how they know the couple, if the event asks and the guest fills them in.
- A device token: a random code kept in the guest's browser, so that we can count what that guest has sent against the event's limits. It is not a password, and it does not say who the person is.
- Network details: the IP address and browser details (the user agent) of each submission, and a coarse version of the network. We use them to stop abuse and to find faults. We never show them to owners or other guests.
- Where they came from: the page a guest came from, when the event link was opened from another page.
- A location result: if the event checks location, the result of that check, as described next.
- Gift notes: if the event offers them, the name, message and amount a guest types. The amount is only what the guest says they gave, and we never see the money.
Location checks
An event can ask guests to share their location, to check that they are at the venue. The owner chooses whether to ask, and whether a guest who cannot be placed at the venue is stopped or only noted.
Your browser asks your permission first. If you say no, the event decides whether you can still send something. When you send something, our server compares your position with the venue. We keep the result of the check, such as verified, outside the area or not given, and not your coordinates.
Our server does the comparison itself. Your position is not sent to any other company for it.
Cookies and what your browser keeps
We keep to what is needed to run the service. You can clear all of these in your browser settings. If you do, you are signed out, and a guest's device token starts again. Here is what each one does:
- Signing in: a cookie that lasts 10 minutes and carries you through the emailed-code sign-in. Scripts on the page cannot read it.
- Staying signed in: a session set by our sign-in provider, which keeps you signed in on your account.
- The memories page: a cookie that lasts 4 hours after you enter the PIN, so that you do not need it again for every photo.
- The device token: the random code described above, kept in the browser's local storage.
Analytics and error reports
We use Google Analytics on our public pages and on guest pages, to see how many people visit and which pages work. It does not run on your dashboard, our staff console, checkout, the admin area or the sign-in page.
On a guest page, Google receives the event's name, the tag of the QR code that was scanned and, if a guest picks one, how they know the couple, such as friend or family. It never receives a guest's name. Google may use cookies for this, and processes the data as described below.
When something breaks we record the error message, the technical trace and the page or route it happened on. Only our staff see these reports.
When you write to us
Our contact page asks for your name, a phone number or an email address (at least one, so that we can reply), the topic and your message.
We use what you send only to reply to you and to deal with what you asked about. We do not use it for marketing.
If you are signed in when you write, we link your message to your account and reply to your account's email address. If you write from a page about an event or an order, we link the message to it as well, so that we know what you mean, but only if it is yours.
Each message is saved in our database (Supabase, Singapore), and a copy is emailed to our support inbox (Gmail, run by Google, including in the United States). We reply by email, or on WhatsApp if you are arranging a payment that way. Cloudflare's Turnstile check runs on the form.
We delete a message 12 months after we close it, together with the copies in our inbox and chats. We do this by hand; there is no automatic job for it yet. If your message leads to an order, the order is kept as described below. You can ask us to delete your message sooner.
Why we use it
We use information to run the service you asked for, to take payments and keep records, to keep owners and guests safe, and to answer you.
We do not sell personal data, and we do not use guests' content for advertising.
- Running the event: receiving, storing, showing and delivering what guests send.
- Payments and records: taking your payment, sending a receipt and keeping the records the law requires.
- Safety and limits: checking uploads, enforcing limits per guest, stopping abuse and checking fair use.
- Understanding visits: counting visits and seeing which pages work.
Automated safety checks
Every event has an automated safety check, which looks for harmful content. An owner can also choose a stricter check, which decides what appears on a screen.
For these checks we send OpenAI, a company in the United States, a photo (reduced to 512 pixels wide) or a still frame from a video, together with any caption the guest wrote. We also send any written wish. OpenAI answers whether the content is safe to show. Voice notes and full videos are not sent.
If the safety check flags something, it is hidden and a person looks at it. Under the stricter check, content that does not pass is hidden from the screen, and the owner can still see it. If that check cannot be completed, the content is held back as well.
The safety check runs on every event and cannot be turned off. An owner's moderation setting changes only the stricter check. If you would rather your content was not checked, please do not send it.
Usage checks
To enforce our Fair Use Policy, we run automatic checks on events. They look at an event's name and host names and how they change, and they read the wishes guests send. A person reviews anything flagged before we act, and nothing is closed automatically.
These checks do not run on events we run ourselves for a customer on an operator plan.
Who else sees it
We use the companies below to run Wishku. We do not sell personal data. Each one gets only what it needs. The owner of an event also sees what its guests send, and we may share information when the law requires it.
- Supabase: our database and sign-in, in Singapore.
- Amazon Web Services, storage: keeps photos, video and voice notes, in Singapore.
- Amazon Web Services, email: sends our emails, such as sign-in codes and receipts, from Singapore.
- Amazon Web Services, hosting: runs our servers, in Singapore.
- ToyyibPay: takes FPX payments, in Malaysia. It receives the payer's name and phone number, your account email and the amount to make the bill, and passes the payment through PayNet's FPX network to the payer's bank. It keeps payment records under its own terms.
- Cloudflare Turnstile: a bot check on the sign-in screens and our contact form, and on guest pages when an event gets a sudden surge of new guests. It collects your IP address, a TLS fingerprint, your user-agent string and our site key, and Cloudflare states it cannot identify individuals from those signals. Cloudflare's handling is set out in its Privacy Policy and in the Turnstile Privacy Addendum at cloudflare.com/turnstile-privacy-policy.
- OpenAI: the safety check described above, in the United States.
- ImprovMX and Gmail: our support inbox. ImprovMX, in the United States and Europe, forwards email sent to our support address and keeps a delivery record, without the message itself, for 7 days. Gmail, run by Google, including in the United States, holds the email.
- Google Analytics: visit statistics, described above, processed by Google, including in the United States.
- WhatsApp: if we reply to you on WhatsApp, your number and our conversation are also held by WhatsApp (Meta), under its own terms and privacy policy.
Where it is kept, and when it leaves Malaysia
Our database, file storage and servers are in Singapore, and our email is sent from Singapore. Email you send us is forwarded by ImprovMX in the United States and Europe, and stored with Google, including in the United States. So although Wishku is operated from Malaysia, the information is stored outside it. Payments are handled by ToyyibPay in Malaysia.
The safety checks send content to OpenAI in the United States. Google Analytics data is processed by Google, including in the United States. The bot check involves Cloudflare, which operates globally.
The PDPA sets conditions on transferring personal data out of Malaysia. We keep the transfers to the providers listed here and rely on the data-protection commitments they publish.
How long we keep it
Each event runs on dates set by its package: a collection period when guests can send, then a retention period when the memories page and downloads stay open. The Terms of Service explain the clock.
When retention ends, the event is archived. Its media is hidden for a safety-net period, and can be restored if the owner upgrades or asks us. After the safety net, where the package provides for it, we delete the files. We email the owner before we delete.
When we delete, we also clear each submission's caption, wish text, guest name and the link between the submission and the guest's session. A record that something was sent may remain, without those words and without the files.
You can ask us to delete your data sooner. The section on your rights explains how.
- Guest content: kept for the collection and retention periods, then archived, hidden during the safety net, and deleted as described above.
- Captions, wishes and names: cleared when the event's files are deleted.
- IP address and browser details: stored with each submission, and cleared 90 days after the event's last celebration day, whatever the package.
- Account details: kept while your account is open. If you ask us to close it, we first hand each event on or close it.
- Free drafts: a draft that is never taken live is deleted after 90 days, with a reminder email before then.
- Payment records: kept for about 7 years, as tax law requires. They hold the order, the amount and the payment references, never a bank card number or a bank account.
- Contact messages: deleted by hand 12 months after we close them, with the copies in our inbox and chats.
- Closed events: if we shut an event, the owner can download what was collected for 30 days.
- Payer details on unpaid bills: the payer's name, email address and phone number on a bill that was never paid stay with that bill. We do not delete them automatically yet. Ask us and we will.
- Things an owner deletes: hidden at once, and can be restored for 7 days. After that the files are deleted where the package provides for deletion.
Your rights, and how to use them
Under the PDPA you may ask for a copy of the personal data we hold about you, ask us to correct it, withdraw the consent you gave, or ask us to limit how we use it. The Act gives us 21 days to answer such a request.
Requests reach us through our contact page or by email at support@wishku.com. If you are a guest, you can also ask the owner of the event: the owner can remove your contribution from their dashboard, and can pass your request on to us.
- See what we hold: tell us which event and the name you used, and we will tell you what is stored.
- Correct it: an owner can edit their event. A guest can ask the owner or us.
- Delete it: ask us and we will delete it. We do this by hand, so allow us a few days.
- Close your account: ask us through the contact page. Before we close it, an admin hands each event to an account you name, or the event follows the closing path, with 30 days to download.
How it is protected
Traffic to Wishku is encrypted. Passwords and PINs are stored scrambled, so we cannot read them.
Guest uploads go from the guest's browser straight to our file storage through signed links that expire, and our server checks each upload afterwards. The memories page is behind the PIN the owner sets.
A small number of our staff can see everything stored here, including guest wishes, because moderating, supporting and confirming payments requires it. No security is perfect.
If a breach of personal data causes, or is likely to cause, significant harm, we notify the Personal Data Protection Commissioner within 72 hours, as the law requires, and tell the people affected no later than 7 days after that.
Children
Wishku is for adults. If you are under 18, do not create an event or pay without a parent or guardian doing it for you.
Celebrations often involve children, and guests may send photos of them. The owner decides what to keep and show. Ask the owner or us and we will take a child's photo or details down.
Changes to this policy
We will update this page when what we do changes. The date at the top is the date of the version you are reading.
If a change materially affects information you have already given us, we will say so at the top of this page rather than change it quietly.
Contact us
Wishku is operated from Malaysia. Use our contact page, or email us at support@wishku.com.
If your question is about a particular event, send us its link. It is the fastest way for us to find what you are asking about.
If you are not satisfied with how we have handled your personal data, you may complain to the Personal Data Protection Commissioner of Malaysia.