Privacy Policy

1. Who handles your information

lyv is software for Philippine Facebook live sellers. It records product claims, creates orders and payment requests, and manages seller-specific buyer lists. Operator identity and contact details are on our contact page.

For account administration, support and service security, lyv acts as a personal information controller (PIC). For buyer records handled on a seller’s instructions, lyv acts as a personal information processor (PIP); the seller is the PIC. Any processing for lyv’s own purposes requires its own lawful basis and notice.

2. Information processed

• Seller identity: Facebook user ID and display name; email if Meta supplies it; phone and business details you provide. Sign-in uses Facebook. lyv does not ask for your Facebook password.
• Business records: products, prices, stock, orders, delivery notes, GCash/Maya/bank payment instructions and seller notes.
• Facebook integration: user and Page access tokens, granted permissions, Page identifiers and metadata, live video details, comment text, commenter names and IDs, timestamps and webhook payloads.
• Buyer records: name, Facebook identifiers, contact and delivery details, order history, private block/allow entries and reasons. Payment submissions can include amount, method, reference, proof URL or uploaded proof image.
• Technical information: authentication cookies, temporary sign-in browser storage and request/security logs where the deployment records them. See our Cookie Policy.

Facebook sign-in requests public_profile and email. Page connection requests pages_show_list, pages_read_engagement, pages_read_user_content, pages_manage_metadata, pages_messaging and business_management as configured. Meta controls permission availability. These allow authorized Page features and invoice replies; they do not give lyv unrestricted access to private conversations.

Do not put government IDs, health details, passwords, PINs, OTPs or unrelated financial information in comments, notes or payment proofs. Crop proofs to the minimum transaction details. Sensitive information requires a separate lawful basis under Section 13 of RA 10173; legitimate interest alone is insufficient.

3. Purposes and lawful bases

Account operation and requested support use information necessary for the seller’s service agreement (Section 12(b), RA 10173). Required legal records rely on applicable legal obligations (Section 12(c)). Proportionate security processing may rely on legitimate interests (Section 12(f)), following a documented assessment.

The seller must establish a lawful basis for buyer claim matching, fulfillment, payment verification and list management. A contract with the seller alone does not authorize processing every commenter’s information. Public comments remain personal data. Sellers must provide a buyer notice and assess necessity and fairness before using legitimate interests; consent, when needed, must be specific and withdrawable.

Claim matching and block/allow rules automate order handling. A blocked claim or stock mismatch can prevent an order. Ask the seller for human review or correction. lyv does not maintain a shared buyer blacklist or credit score.

4. Recipients and transfers

Authorized sellers receive their own buyer records. Meta receives integration requests and invoice messages. Service providers may host databases, files, logs and support communications under documented processing arrangements. Legally required disclosures must be limited to the lawful request.

Depending on the features a seller turns on, buyer information also goes to:

• Meta, for Messenger and Instagram replies, the seller's chat inbox, auto-replies and broadcasts, and, when the seller adds them, the Meta Pixel on their store and bills and Conversions API purchase events (with phone and email hashed before sending).
• PayMongo, when a buyer pays a bill online: the checkout runs on the seller's own PayMongo account and the money goes to the seller, not to lyv.
• Semaphore, an SMS provider, for order-update texts to the buyer's phone number, on the seller's Business plan.
• Couriers such as Lalamove and Ninja Van, the buyer's name, phone and delivery address, when the seller books a delivery from lyv.
• The seller's staff, who work in the seller's shop under the seller's instructions.

We do not sell buyer lists or use them for advertising. The production provider names, services and processing countries must be confirmed and published on the Data Processing Terms page before real personal data is accepted. Cross-border processing requires appropriate safeguards and continued accountability.

Invoice links grant access to the information shown on the invoice to anyone with the link. Send links privately, verify the recipient, and avoid public posting.

5. Retention and deletion

Service records remain in the current application until removed through applicable record controls or an authorized support process. A daily automatic sweep deletes comment text and buyers' payment screenshots 12 months after they were received, and raw webhook payloads after 90 days; the claim and payment record (amount, method, reference) stay with the order. Expiry of logs and backups is not implemented or verified in this review version. We do not promise a seven-day purge or a fixed backup expiry.

A seller can erase a buyer's information on request. Erasure deletes that buyer's unpaid orders and blanks their comments; orders already paid stay as the seller's sales records with the buyer's name, phone, address and payment screenshots removed. A seller may keep the buyer's Facebook id alone on their own blocklist so the block still works. Blocklists are never shared between sellers.

Before production, the operator must approve and implement purpose-based retention periods, legal holds, file deletion and backup expiry. Records needed for a legal obligation or dispute must be minimized and restricted, with the reason and expected period explained to the requester. See data deletion instructions for the current process and callback limits.

6. Security and incidents

Application controls include seller-scoped access and signed Meta webhook verification outside mock mode. Hosting security, HTTPS, encryption, access reviews and backup recovery must be verified for the deployed environment; no security certification is claimed.

For a breach requiring notification, the responsible PIC must notify the NPC and affected people within the applicable 72-hour period, based on knowledge or reasonable belief, subject to lawful exceptions. lyv as PIP must promptly assist the seller PIC. Investigation must not postpone a required initial notification.

7. Your rights and requests

Under RA 10173, subject to legal conditions, you have rights to information, objection, access, correction, erasure or blocking, data portability, damages and complaint. Contact privacy@lyv.ph with the relevant account or seller Page and request. We may seek proportionate identity verification; do not send an ID unless a secure, necessary method has been agreed.

Buyers can contact their seller or lyv. We coordinate processor-held requests with the seller and address requests within our own controller role. We explain any lawful restriction or delay. You may complain directly to the National Privacy Commission; contacting us first does not waive that right.

8. Children and changes

Seller accounts are for adults aged 18 or above with authority to operate their business. Incidental child data in comments or proofs requires prompt assessment, minimization and an appropriate lawful basis. Report it to our privacy contact.

Material changes will be explained through available account or service channels before new processing begins where required. A notice update or continued use is not blanket consent to a new purpose.