Emialiko

Privacy Policy for the Emialiko wedding apps and related services — mobile team app, invitation dashboard, and digital invitation cards.

Effective date: 20 July 2026 Last updated: 20 July 2026 Package: co.emialiko.app

1. Who we are

Emialiko (“we”, “us”, “our”) provides software for wedding hosts and their teams to manage guests, invitations, check-in, messaging, and contributions. This policy explains what personal data we process and why.

Controller contact: privacy@emialiko.co

2. Scope

This policy covers:

  • the Emialiko mobile app for wedding owners, editors, and door scanners;
  • the operations / invitation dashboard used by organisers;
  • public digital invitation cards opened by invitees via personal links;
  • our APIs and related backend services that power those products.

3. Data we collect

We collect only what is needed to run wedding workspaces, deliver invitations, and support the team on the day. Categories include:

Account & team identity Phone number (primary login), optional display name, role on a wedding (owner, editor, scanner, viewer), and authentication session tokens.
One-time passwords (OTP) Temporary verification codes sent by SMS to confirm phone ownership. Codes are hashed when stored and expire quickly.
Wedding event details Partner names, event date/time, church and reception venues, contact person name/phone, notes, contribution goals, and invitation card URL.
Guest / invitee data Title, full name, phone and/or email (if provided), party size, RSVP status, invitation code, card status, and optional notes.
Invitation & check-in activity Whether a card was sent/opened/scanned, check-in timestamps, seats checked in, and scan method (QR or manual).
Messaging SMS message content you compose, recipient phone numbers, delivery status, credit balances, and purchase/payment references for SMS top-ups.
Payments (SMS credits) Mobile-money phone number used for USSD approval, amount, provider payment/intent IDs, and payment status. We do not store full card numbers or mobile-money PINs.
Contributions Contributor name, amount, currency, method (e.g. cash, mobile money), and notes recorded by the wedding team.
Device & technical data App version, device/OS type, crash/diagnostic logs where enabled, IP address and basic request metadata for security and reliability.
Camera (on-device) Camera access is used locally to scan invitation QR codes at the door. We do not upload continuous camera video or store photos from scanning.

We do not sell personal data. We do not use guest lists for unrelated advertising. Precise GPS location is not required for core features.

4. How we use data

  • Authenticate team members with phone OTP and keep wedding workspaces secure.
  • Create and personalise invitation cards and invitation SMS for guests.
  • Track RSVPs, card status, and door check-ins for the wedding host and scanners.
  • Send operational SMS (invites and verification codes) via SMS providers.
  • Process SMS credit purchases via mobile-money payment providers.
  • Record contributions and show totals against wedding goals.
  • Provide support, prevent abuse, and improve reliability and security.
  • Comply with legal obligations where applicable.

5. Sharing & processors

We share data only with service providers that help us operate the product, under instructions limited to those purposes:

  • SMS delivery providers (e.g. SmartAlert) — phone numbers and message content needed to send OTP or invitation SMS.
  • Payment providers (e.g. Snippe / mobile money rails) — phone number and amount to complete SMS credit purchases.
  • Hosting / database infrastructure — encrypted storage and processing of wedding workspace data.
  • Wedding team members you invite — owners/editors/scanners can see guest and event data according to their role.

Invitees who open a personal invitation link see the wedding details and their own guest information shown on that card. We may disclose information if required by law or to protect rights, safety, and integrity of the service.

6. App permissions

  • Camera — to scan invitation QR codes for check-in.
  • Network access — to sync guests, messages, payments, and stats.
  • Notifications / audio (limited) — optional short feedback sounds (for example after a successful scan). Microphone recording is not used for wedding features.

7. Retention

We keep wedding workspace data for as long as the wedding account remains active or as needed to provide the service. OTP codes expire within minutes. Message and payment records are retained for operational history, accounting, and dispute resolution. You may request deletion of a wedding workspace or personal account data subject to legal retention needs.

8. Security

We use industry-standard measures appropriate to the sensitivity of the data, including encrypted transport (HTTPS), access controls by wedding membership role, hashed OTP storage, and restricted server access. No method of transmission or storage is 100% secure; please protect devices used by your wedding team.

9. Your rights

Depending on applicable law, you may request to:

  • access the personal data we hold about you;
  • correct inaccurate data;
  • delete data or close a wedding workspace;
  • object to or restrict certain processing;
  • receive a portable copy of data you provided, where feasible.

Wedding hosts are often the primary contact for guest-list corrections. Guests may also contact us directly at privacy@emialiko.co.

10. Delete user data

You can ask us to delete your Emialiko account and related personal data. Wedding hosts can also request deletion of an entire wedding workspace (including guest lists managed in that workspace).

How to request deletion

  1. Email privacy@emialiko.co with the subject line Delete my Emialiko data.
  2. Include the phone number used to sign in, and (if relevant) the wedding couple names or wedding ID so we can locate the correct records.
  3. Confirm whether you want account deletion only, removal from a wedding team, and/or full wedding workspace deletion.

What we delete

  • Your user account profile (phone number, display name, roles).
  • Authentication sessions and unused OTP challenges tied to your phone.
  • For workspace deletion requests from an authorised host: guests, invitation codes, check-ins, messages history, contribution records, and wedding settings for that wedding.

What we may retain

We may keep limited records where required for security, fraud prevention, accounting, SMS/payment dispute resolution, or legal compliance (for example payment references and timestamps). Where we retain such records, we minimise what is kept and do not use it for marketing.

Timing

We aim to acknowledge deletion requests within 7 days and complete deletion within 30 days, unless a longer period is required by law or to resolve an outstanding payment/security issue. After deletion, you will need a new invitation to a wedding workspace to use the app again.

Guests who are not app users can ask the wedding host to remove their details from the guest list, or contact privacy@emialiko.co with enough information for us to identify the invitation entry.

11. Children

Emialiko is intended for wedding organisers and adult team members. We do not knowingly create accounts for children. Guest lists may include children’s names only when provided by the host for invitation/check-in purposes.

12. Changes

We may update this policy from time to time. The “Last updated” date at the top will change when we do. Material changes will be highlighted in-app or on this page where practical.

13. Contact

Questions, privacy requests, or data deletion:
Email: privacy@emialiko.co
Product: Emialiko wedding apps (co.emialiko.app)