Privacy Policy

PoSHOP AI có thể lưu dữ liệu tài khoản, đơn hàng/thanh toán, lịch sử chat nếu bật lưu trữ, thông tin tuyến nhà cung cấp, sự kiện đồng ý và sự kiện chính sách nội dung.

Yêu cầu AI có thể được xử lý bởi nhà cung cấp API bên thứ ba hoặc API chính thức tùy sản phẩm được chọn. Dữ liệu có thể được xử lý ngoài quốc gia của bạn tùy tuyến cung cấp.

Người dùng có thể yêu cầu xuất dữ liệu hoặc xóa lịch sử chat nếu hệ thống hỗ trợ, nhưng một số dữ liệu có thể cần giữ lại vì lý do thanh toán, bảo mật, pháp lý hoặc kiểm toán.

We may collect account data such as email, name, password hash, role, account status, plan, credit balance, and account timestamps.

We may collect payment/order data such as top-up amount, payment method, submitted reference, deposit date, approval status, and administrator review records.

If chat history is enabled, we may store chat titles, messages, selected product/model, selected agent, usage cost, token estimates, provider route metadata, and task/status information.

We may store consent events, provider route disclosures, content policy events, short prompt excerpts when needed for safety review, and user data requests. We should avoid storing raw IP addresses and raw user agents where hashing is supported.

We use data to operate accounts, provide chat responses, manage credits and plans, process payment requests, prevent misuse, satisfy legal/compliance needs, and improve support.

Third-party API providers may process requests depending on the selected route. Data may be transferred across borders depending on the provider, hosting location, and route selected.

Retention periods may vary by data type, such as chat history, payment records, audit logs, consent events, and content policy events.

Administrators should configure retention settings before production and review them regularly.

Where supported, users may request export of account data, deletion of chat history, or deletion of account data. Some records may need to be retained for payment, fraud prevention, legal, tax, security, or audit reasons.

We may reject or limit requests that conflict with legal obligations, active disputes, abuse prevention, or security needs.

We use reasonable technical and organizational measures, including password hashing and backend-only API keys. No system can be guaranteed completely secure.

For privacy questions or data requests, contact the administrator through the support link shown on the website.