Privacy commitment and Meta requirements
We place a high priority on customer and user privacy. We are committed to following the Meta Platform Terms, Developer Policies and applicable Meta data and privacy requirements for the integrations and permissions we use. Meta information is used only for authorized purposes described in this policy and within granted permissions. Publishing this policy does not mean Meta has certified the app or approved every permission.
We do not sell, rent or disclose personal information to outside companies, individuals or organizations for their marketing or purposes unrelated to the service. External processing or disclosure is limited to necessary providers described below, such as Meta, Cloudflare and delivery or payment providers when those services are used, with information limited to what the purpose requires. Other purposes require consent or another legally permitted basis. Legally required disclosures are assessed for lawfulness and the necessary scope of information.
See the Meta Platform Terms and Meta Privacy Policy. This app policy also covers information you provide directly to the app.
Responsibility and scope
CF First is operated by Somphong CHANTHAMIXAY. For privacy requests, contact the store owner through the Facebook channel you used to contact the store or place an order. Stores using the service manage their own customer and order data within their assigned permissions. This policy covers information processed for account access, shopping, store operations and authorized Meta connections. The service is under development and testing; some integrations are not enabled.
How the service works and where data comes from
Customers choose products on the website or submit comment orders on posts/live sessions configured by a store. Eligible requests create or update an order, check available quantities and produce an order summary. Customers provide recipient details for delivery. Stores handle payment verification and shipping through enabled workflows; returning from a payment page alone is not proof of payment.
Store owners separately authorize eligible Meta Pages/accounts. Connected channel events, including messages and comments, reach the inbox or order workflow. Authorized staff can reply, associate orders, assign conversations, add internal notes and create follow-up tasks. Store, channel and permission scope are checked. Meta messaging is subject to granted permissions and provider messaging windows, not unrestricted outreach to any person.
Sources include information you submit, authorized Meta information, store-entered records and technical usage information. Reading this policy does not require a store connection.
Information and purposes
- Facebook Login: name, app-scoped user ID and profile picture information for identification, account display and access checks. We do not receive your Facebook password. Ordinary login requests public_profile, not email, friends or private posts.
- Orders: products, quantities, order-related payment information and recipient name, phone and address that you provide, to manage orders, contact you and arrange delivery.
- Messages and comments: content, provider IDs, channel account identifiers, timestamps and supported attachment information to handle inquiries, comment orders and customer support. Website attachments are private files accessed after authorization.
- Store connections: selected Facebook Page or Instagram account information, granted permissions and API tokens for connections authorized by the store owner. Connection consent is separate from ordinary login. Tokens are stored server-side and encrypted in the current system.
- Operations: assignment history, order states, audit records and request information needed for troubleshooting, security and store reports.
Instagram and provider attachment processing depend on enabled capabilities and granted permissions. Signing in does not grant access to every Page or account.
Store records and generated information
Stores may record product information/images, selling channels, order records, payment checks, shipping details and necessary customer information. Inbox records may include labels, assigned staff, internal notes, follow-up tasks, response deadlines and read/reply states. The system creates record IDs, timestamps, audit history and delivery results for duplicate prevention, troubleshooting and store reports. Reports/exports may contain customer information and are permission-controlled. Internal notes are for authorized staff and are not automatically sent to customers. Assignment and operational reminders organize store work; they are not customer credit or legal decisions.
Storage and hosting
Account, connection, order, task and audit records are stored in the server database. Product media and private website chat files are stored separately. Chat downloads require store/conversation authorization; they are not public media links. Channel tokens are encrypted server-side. Temporary caches improve performance, but are not the source of truth for inventory, payment or authorization. Clearing caches does not erase underlying records.
At the current development stage, the main app and database run on equipment/servers managed by the operator, accessed through Cloudflare Tunnel. This policy page is part of the CF First website and does not itself store account or order data. Material changes in hosting or data use will be reflected in this policy.
Cookies and device storage
The app uses cookies for login sessions and login request validation. Carts, order links and interface preferences may be stored in your browser. Clearing browser data does not erase server records. This policy document has no forms, tracking scripts or application cookies. You can manage site data through browser settings; blocking necessary cookies may prevent login or some features. Network providers may process IP addresses, request times/URLs and browser information for delivery and security.
Access, providers and international processing
Store owners and authorized team members access data within their store and permission scope. Necessary providers, including Meta and Cloudflare, process information for login, messaging and network services. Delivery or payment providers may receive the information needed when those services are used. Infrastructure may process information in other countries depending on provider locations. We do not sell personal information.
When Cloudflare is used to deliver this website, it may receive network request information such as IP addresses and browser information for delivery and security. This page does not access store account, chat or order databases. Meta services are also governed by Meta's own policies.
Security and retention
Measures include store-scoped authorization, restricted file access and token protection. Retention depends on purpose and data type; there is no automatic universal deletion schedule.
- Accounts, orders and transaction evidence: retained for service, purchase history, verification and dispute handling, subject to appropriate deletion/correction actions and applicable requirements.
- Website messages and linked files: remain in conversation records subject to authorized actions. Unsent pending uploads expire after 24 hours and are handled by cleanup jobs; physical deletion is not guaranteed at the exact expiry second.
- Messenger: history is loaded from Meta with short caching, minimizing permanent storage of ordinary chat text. Newly processed terminal content enters a short cleanup cycle of approximately 15 minutes. Pending processing, unresolved delivery payloads and necessary accepted comment/order evidence may remain longer. Message IDs, read states, delivery results and order links are retained for operations.
- Instagram: when enabled, content and events have type-specific expiry/cleanup. This does not mean all records or information held by Meta are erased together.
- Backups and audit records: backups may include database records, product media and private chat files. Main-system deletion does not immediately erase older backups; the operator must consider backup cycles and relevant restrictions.
These measures reduce risk but cannot guarantee absolute security. Contact the operator if you identify a data concern.
Access, correction and deletion requests
Contact the store owner through the Facebook channel you used to contact the store or place an order, and include the subject “CF First — Data deletion request”. Include your account name, the channel used and an order reference if applicable. The same contact accepts access and correction requests.
Do not send passwords, OTPs or access tokens. We verify identity and request scope before processing and explain the result or any necessary retention for ongoing orders or applicable obligations. This is a manual request process, not an immediate automatic deletion service.
You may revoke the app in Facebook Settings → Apps and websites. Revocation alone does not erase order records held by the store system.
Choices and data rights
You may withhold optional information, though recipient/contact details are needed for delivery. You may request access, a copy, correction, deletion, restriction/objection information or withdrawal of channel authorization under applicable rights. We assess identity, request scope, ongoing transactions and relevant requirements. Do not send sensitive identity documents in the first message. Stores cannot freely access other stores' customer records. Export recipients must safeguard downloaded files; deletion in the app does not automatically erase copies held outside it.
Marketing and information to avoid sending
Information is used for the service and store operations described here. A Meta connection is not blanket consent for advertising. New marketing purposes or features will be explained and permission obtained where necessary. Do not send passwords, verification codes, full payment-card details or unnecessary sensitive information in chat or attachments. This policy does not announce use of customer chats for AI model training.
Updates
We update this document and its revision date when services or data use change. Contact the operator with questions about this policy. Meta, shipping, payment and other services you use directly may have their own policies governing their processing.