Privacy Policy

Wedivo is operated by PT. Wedivo Digital Solution, a company incorporated in Indonesia with its registered address at Jl. Sunan Kalijaga Gg. I No.06, Berkoh, Purwokerto Selatan, Banyumas, Jawa Tengah 53146, Indonesia.

In this policy, “we” and “us” mean PT. Wedivo Digital Solution. “The service” means the Wedivo marketing site at wedivo.id, the Wedivo dashboard, and the guest-facing invitation pages we publish on your behalf.

For privacy questions, write to us at the address above or email privacy@wedivo.id.

Account holders — couples and their collaborators who sign in to Wedivo. We are the data controller for account data.

Guests — the people an account holder invites. Guest details are uploaded by the couple, not collected by us directly. For that data we act as a processor on the couple's instructions: we store and process it so their invitation, RSVP, seating, check-in and souvenir features work, and we do not use it for our own purposes.

If you are a guest and want your details corrected or removed, the fastest route is to ask the couple who invited you. You can also contact us and we will help.

Account identity: your name, email address, and profile photo, as provided by Google when you sign in. Wedivo uses Google sign-in only — we never receive or store a password.

Wedding details you enter: both partners' names and nicknames, parents' names, wedding date and time, venue, and the photos and prewedding video you upload.

Content you create: invitation designs and their code, AI prompts and the reference images attached to them, greeting-screen settings, seating layouts, planner entries, and support conversations.

Billing records: what you bought, when, the amount, and the payment status. Card numbers and bank credentials are handled by our payment provider and never reach Wedivo's servers.

Technical data: log records needed to operate and secure the service, including timestamps of significant actions taken in your account.

Usage data: which parts of the dashboard you open and the actions you take there, recorded against your account identifier. See “Analytics and marketing” below for what this is used for.

Names and phone numbers, and optionally an email address, a guest group, which side of the family they belong to, and how many people their invitation covers.

Responses guests give themselves: RSVP status, pax count, any message left with the reply, and wishes or comments left on the invitation.

Wedding-day records: check-in status and time, an optional check-in selfie, the seat assigned to them, and souvenir assignment and pickup state.

Where the couple's plan includes face matching for wedding photos: a numeric face measurement derived from that check-in selfie. This is biometric data, which Indonesian law treats as a specific category of personal data — “Face matching and biometric data” below sets out exactly what we do with it and what a guest can ask for.

Gift records, where the couple has enabled digital gifts: the amount sent, any message, and the time.

To provide the service you asked for: publishing your invitation, delivering invitations to your guests, recording RSVPs, running check-in, seating, souvenirs, the venue screen, and the planner.

To operate and secure the platform: authentication, abuse prevention, backups, debugging, and keeping records of significant account actions.

To handle payments, issue records of them, and apply the plan you bought.

To answer your support requests, including through the in-product chat assistant.

To understand how the service is used and improve it, by measuring which features are opened and where people get stuck.

To measure whether our own advertising works and to build audiences on advertising platforms, using account holders' email addresses in hashed form. Guest data is never used for this.

To meet legal and accounting obligations that apply to us in Indonesia.

Most of what we do with your data, we do because you asked us to: publishing your invitation, delivering it to your guests, running check-in and seating, taking your payment. That is processing necessary to perform our agreement with you.

Some of it we do because Indonesian law requires it of us — keeping payment and tax records, and the identity verification that has to happen before anyone can receive digital gifts.

A narrower set rests on our own legitimate interest in running a service that stays up and is not abused: authentication, abuse prevention, backups, audit logs, and understanding in aggregate how the product is used.

Two things are optional and rest on consent: the face matching described below, and the advertising audiences described under “Analytics and marketing”. You can withdraw either one, and doing so costs you nothing else in your account.

For guest data, the couple is the controller and we act on their instructions. A guest's own basis for being on a guest list is the couple's to explain, and we ask couples to hold one.

Some features send content to third-party AI providers to do their work: generating an invitation design from your prompt, generating prewedding imagery from photos you upload, reading a vendor quote you upload in the Wedding Planner, drafting budget suggestions, and answering questions in the support chat.

What is sent is limited to what the feature needs — your prompt and attached reference images, the document you uploaded, or the specific wedding figures the assistant was asked about.

We do not send guest contact details to AI providers as training data, and we do not use your content to train our own models.

The support assistant can read your wedding data to answer your questions. It cannot change it: it never adds a guest, edits a budget, or alters your invitation.

Face matching is an optional feature on some plans. It exists for one purpose: to hand a guest the photos they actually appear in, out of a gallery of several hundred.

It works from the selfie a guest chooses to take at check-in. From that selfie we derive a numeric representation of facial features and store that representation, then compare it against the faces found in that couple's own wedding photos. Indonesian data protection law treats biometric data as a specific category of personal data, and we handle it on that footing.

The representation is not a photograph and cannot be turned back into one. It belongs to that one wedding: it is never compared across weddings, and it is never used to identify anyone for any other purpose — not security, not advertising, not anything we do with our own business.

The check-in selfie is optional. A guest who declines it is checked in normally and simply is not matched to photos.

A guest can have it removed. Ask the couple to reset your responses, or write to privacy@wedivo.id and we will do it — the selfie and the derived representation are both deleted.

Google Firebase — authentication, database, and hosting infrastructure.

Our AI providers — for the generation and document-reading features described above.

Our payment provider — to take payments, run the identity verification required before you can receive digital gifts, and process withdrawals to your bank.

Our messaging provider — to deliver WhatsApp invitations to the numbers you supply.

Google Maps — to display a venue map inside an invitation.

Our hosting provider — to serve the sites and store uploaded media.

Google Analytics — to measure how the service is used.

Google Ads — to measure our advertising and to hold the hashed-email audiences described in the next section.

We do not sell personal data. We do not share guest data with advertising platforms, and nobody we share data with is permitted to use it for their own purposes.

We use Google Analytics to see how Wedivo is used — which pages and features get opened, and where people get stuck. Inside the dashboard those events carry your account identifier, so one person's session can be told from another's; on the marketing site they do not.

We also advertise Wedivo, and we upload account holders' email addresses to Google Ads as audiences: one of everyone who has signed up, one of everyone who has paid. They let us measure whether our advertising works and reach people similar to our existing customers.

Addresses are hashed with SHA-256 before they leave our servers, so what is uploaded cannot be read back as an email address. Nothing else goes with them — no name, no phone number, no wedding details.

Only account holders are included. We never upload guest data, and a guest who was invited through Wedivo is not put into an advertising audience by us.

If you would rather not be included, email privacy@wedivo.id and we will take you out of those audiences. It changes nothing about your account, your plan, or what you have already bought. Deleting your account removes you from them too, automatically.

Wedivo is operated from Indonesia and your account and wedding data are stored on Google Firebase infrastructure.

Several of the providers listed above process data outside Indonesia — our AI providers, Google Analytics and Google Ads, and our messaging provider among them. Where that happens we send only what the feature needs, and we rely on those providers' own contractual data-protection commitments.

If you want to know where a particular feature sends data before you use it, ask us at privacy@wedivo.id and we will tell you.

If you enable digital gifts, you will be asked for a photograph of a government ID and a short liveness selfie. This is a requirement of Indonesian payment regulation, not a Wedivo policy.

Those documents are submitted to and reviewed by our payment partner. Wedivo does not retain a copy of your identity document.

A published invitation is a public web page. Anyone with the link can open it, and links pasted into WhatsApp or social media generate a preview card with the photo and details you configured.

Wishes left on an invitation are visible on that invitation and, if you enable it, on the greeting screen at your venue.

A design you choose to publish to the community design library becomes visible to other Wedivo users. Your couple details are not published with it — designs resolve those values live from whoever is using them.

Account and wedding data are kept while your account is open. Deleting your account from Settings erases your wedding data, your guest list and every file you uploaded immediately, not on a schedule; a deletion you ask us to carry out for you is done within 30 days. Two things are kept either way and are listed before you confirm: financial records, below, and designs you published — a published design holds none of your wedding details, and other couples may have started their own invitation from one. Unpublished designs go with everything else.

Payment and tax records are retained for as long as Indonesian law requires.

Backups are rotated on a rolling schedule, so a deleted record may persist in an encrypted backup briefly after removal from the live system.

Data is encrypted in transit. Access to production data is limited to personnel who need it to operate the service.

Access to every record is enforced at the database layer by rules that check who is asking, not only by the application interface. A collaborator only ever reaches the wedding they were invited to, at the level of access they were given.

You can ask us to give you a copy of your data, correct it, delete it, or stop a particular use of it. Much of this you can do yourself: guest lists are editable and exportable from the dashboard, collaborator access can be revoked at any time, and Settings has a Delete account and data control that erases everything and closes your account without going through us at all.

You can also object to a particular use, withdraw a consent you gave, or ask to be taken out of our advertising audiences. Withdrawing consent for something optional does not affect anything else in your account.

Write to privacy@wedivo.id and we will respond within 30 days. If you think we have handled your data wrongly, tell us first and we will try to put it right — you may also complain to the competent Indonesian authority.

Wedivo is not directed at children and we do not knowingly create accounts for anyone under 18.

If we change this policy materially we will update the date at the top and, where the change affects you meaningfully, tell you in the product before it takes effect.