This Privacy Notice explains how Liham ("we", "us") handles personal data, following the Philippine Data Privacy Act of 2012 (Republic Act No. 10173).
Business name, address and data protection officer details will be added here once registration is complete.
What we collect and why
| Data | Why | How long we keep it |
|---|---|---|
| Account: name, email address, password (stored only as a secure hash), language, confirmation that you are 18 or older, two-factor settings if you turn them on | To give you an account, sign you in securely and send service emails | Until you delete your account |
| Sign in with Google or Facebook (optional): your name, email address and the account ID that Google or Facebook gives us. We never receive your Google or Facebook password | To sign you in and connect that sign-in to your Liham account | |
| Invitations: event details, text, photos and anything else you add | To build, show and share your invitations | Until you delete the invitation or your account. Photos no longer used in any of your invitations are deleted after 7 days |
| Guest replies (RSVP): name, attending or not, number of guests, optional phone number, email and message; the guest's IP address stored only as a one-way code | Collected for the host, who decides how to use them; the code helps us stop spam replies | Until the host removes them, deletes the invitation or deletes their account |
| Orders and payments: what you bought, amount, dates, receipt number; for manual payments (such as GCash, Maya or bank transfer), the receipt screenshot and any reference number you send | To deliver what you bought, confirm payments and keep accounting records | Order records are kept for the period the law requires for accounting, even after an account is deleted (with your name and email removed). Receipt screenshots are seen only by the team checking payments |
| Editor profiles: display name, photo, city, bio, prices, contact links, sample invitations | Shown to anyone the editor shares their profile link with; not listed on Liham or in search engines | Until the editor changes or deletes the profile or account |
| Reports: the reason and note you give; your IP address stored only as a one-way code | To review reports and prevent abuse | As long as needed to handle the report |
| Contact messages: your name, email, topic and message; your account if you're signed in; your IP address stored only as a one-way code | To answer you, improve Liham (for example template ideas) and prevent abuse | Until handled, then up to 1 year |
| Stories you share: the name, role, template or place and story you send, and the date you agreed to it being shown | To review it and, with your consent, show it on our website | Until you withdraw consent or delete your account; a story already shown is removed when you ask |
| Technical data: IP address, browser type, pages requested, error logs | To keep the service secure, prevent abuse (for example, rate limits on RSVP replies) and fix problems | Up to 90 days, unless needed for a security investigation |
A design you start before signing up stays only in your own browser; nothing is sent to us until you create an account and save it.
We use only the cookies needed to run the site (signing in, security and your language choice). We don't use advertising cookies or sell personal data.
To understand how Liham is used, we count how many times each published invitation is opened and how often its owner shares the link, as daily totals only. This uses no cookies and stores nothing about the person opening it (no IP address, device or location); link-preview robots and the owner's own visits are not counted. Only Liham's team sees these totals.
Who can see your data
- Liham doesn't list or share your invitations, never posts a client's invitation link on social media (its own pages included), and asks search engines not to show them. You decide who receives the link.
- Anyone with an invitation's link can see what you published in it. Preview links show a draft to anyone who has the link until it is turned off.
- The host sees the RSVP replies to their invitation, and anyone the host sends their private RSVP link (for example a client or family) sees them too, including the phone and email a guest chose to add. Guests: only share what you're comfortable giving the host.
- Editors and clients: an invitation an editor makes for a client stays in the editor's account; the client follows the replies through the private RSVP link the editor sends them.
- Liham's team can access data when needed to run the service, review payments and reports, or answer support requests. When an invitation or editor profile is reported, we email its owner the reason, never who reported it.
- Service providers that process data for us, under contracts that require them to protect it: hosting (Railway), storage of photos and payment receipts, and photo delivery (Cloudflare), email delivery (Resend), error monitoring (Sentry, which stores technical error reports in the European Union), and a payment partner once online payment is available. Some of these providers store data outside the Philippines.
- Video and music services: when a guest taps play on a video or a SoundCloud song in an invitation, it loads from YouTube (privacy-enhanced mode), Vimeo (with Do Not Track) or SoundCloud, which receive the guest's device and connection details and may set cookies under their own privacy policies. Nothing loads from them before the guest taps play. Music from Liham's own library plays from Liham.
- Authorities, when the law requires it.
Customer stories
Customer stories and photos on our website are published only with the customer's written consent, and can be withdrawn at any time on request.
Your rights
Under the Data Privacy Act you may ask to be informed about, access, correct, object to the processing of, and erase your personal data, and ask for a copy in a portable format. You can correct most data yourself in Settings, and delete your account there at any time (how to delete your data). For anything else, email privacy@liham.ph and we will reply within a reasonable time. If you are not satisfied, you may complain to the National Privacy Commission (privacy.gov.ph).
Security
We use encrypted connections, hashed passwords, optional two-factor sign-in (required for our admins), access controls and limits on repeated requests. No system is perfectly secure; if a breach affects you, we will notify you and the National Privacy Commission as the law requires.
Changes
We may update this notice. If a change matters for you, we will tell you by email or in the app. If the English and Tagalog versions differ, the English version prevails.