Privacy policy
Effective: · The Vietnamese version is authoritative. This English text is a translation. · Tiếng Việt
zuey.me is the personal site of Duy Nguyen (Zuey): profile, Knowledges articles, the Zuey AI assistant, memberships, the community and business consulting. This page explains what data is collected, why, who processes it and what rights you have.
Key commitments
- Your personal data is NOT used for any purpose other than those described in this policy.
- Personal data is never sold, rented or traded.
- Your data is not used for targeted advertising.
- Your content (including chats with Zuey AI) is not used to train AI models without your explicit consent.
- Data is isolated per user: each account can only see its own data.
Data collected
- Account: email, display name and avatar from Google or GitHub when you sign in; email verification status; a session cookie.
- Membership and payments: chosen plan, term, status and transaction reference. Card and bank details are handled by the payment providers; zuey.me does not store card numbers.
- Personal API keys: key name, scopes and usage details so you can manage and revoke keys.
- Zuey AI: the questions you send and the generated answers, stored per account so you can see your history.
- Consultation booking: name, email, the context you provide and the meeting time.
- Telegram community (Community plan): single-use invite links, your Telegram user ID once you join through such a link, and membership status so access follows your plan.
- Weather (only if you turn it on): a city name or coordinates rounded to 1 decimal place (about 11 km). The choice is stored in your browser only; the server just forwards the query to Open-Meteo and does not link it to your account.
- Browser storage: a locale cookie (zuey_locale) and localStorage for the companion position and state, dismissed notices, recent commands and weather preference. You can clear these at any time in your browser settings.
- Usage analytics: page views and some interaction events (such as link clicks and language changes) via PostHog.
- Technical logs: IP address, user agent and request details recorded by Cloudflare to operate the service and prevent abuse.
How data is used
- To provide the account, paid content, Zuey AI, MCP/API, booking and community features you choose to use.
- To process payments, renewals and refunds and send transactional email (verification, receipts, reminders).
- For security, fraud and abuse prevention, and rate limiting.
- To understand aggregate usage and improve the product.
- To meet legal obligations.
Per-user isolation and administrator access
Every API and MCP request is authorised against your own session or API key; one account’s data is not shown to another account.
The administrator (Duy) has technical access to stored chats and account data. It is used only to provide support you ask for, to investigate security incidents or abuse, or when required by law. Administrator access to chats is recorded in an audit log.
Zuey AI and model providers
To generate answers, your question and relevant content excerpts are sent through the Dewee gateway to an AI model provider. These parties process the data to answer and may retain it under their own policies; zuey.me does not promise that providers never retain data.
Do not enter passwords, secret keys or other sensitive information in the chat.
Processors
zuey.me relies on the services below. Each receives only the data its function needs.
| Processor | Purpose | Data involved |
|---|---|---|
| Cloudflare | Hosting, database (D1), CDN, security | All stored data, request logs |
| Resend | Transactional email | Email address, transactional email content |
| SePay | Vietnamese bank-transfer payments | Amount, transfer memo, transaction reference |
| Polar | International card payments | Email, payment details collected by Polar |
| Dewee gateway and AI model provider | Generating Zuey AI answers | Questions, relevant content context |
| Sign-in; Google Calendar/Meet for consultations; Google Fonts | Basic sign-in profile; booker name and email; IP address when fonts load | |
| GitHub | Sign-in; showing public activity of @mrgoonie | Basic sign-in profile. The activity section uses public events only, not your data |
| Telegram | Community plan groups | Invite links, Telegram user ID, membership status |
| Open-Meteo | Weather for background effects (optional) | City name or rounded coordinates |
| PostHog | Usage analytics | Page views, interaction events, device identifier |
If a new payment provider or processor is added, this list is updated before that service handles your data.
Retention, backups and deletion to be finalised
- Account, membership and chat history data are kept while your account is active or until you ask for deletion.
- Specific retention periods for each data type (chat history, technical logs, analytics) are to be finalised and will be published here.
- Infrastructure backups may still contain deleted data for a period before being overwritten; the exact period is to be finalised.
- Payment records may need to be kept longer to meet accounting and tax obligations.
- You can request deletion of your account and data by emailing hi@zuey.me. A self-service deletion flow is to be finalised.
Your rights
- Ask to access, export or correct your personal data.
- Ask for deletion or withdraw consent (for example turn weather off or clear browser data).
- Revoke API keys and sign out sessions from your account page.
- Complain to the competent data protection authority.
Contact and changes
Send any privacy request to hi@zuey.me. When this policy changes materially, the effective date above is updated and the change is announced on the site.