This policy explains what Native Cook knows about you, why, who else handles it, and what you can ask us to do with it. It applies to the site at nativecook.dev. The short version: we keep the little we need to run your account, we measure how the site is used and you can turn that off, we run no ads, and we never sell data.
Native Cook is run by Ngoc Le, an individual based in Vietnam.
Email: support@nativecook.dev
1. What we collect
Account. Your email address, a display name, which sign-in method you use (email link, GitHub or Google) and when you signed in. If you sign in with GitHub or Google, they send us your email and name; we never see your password for those services. Email sign-in links are sent through Cloudflare on our behalf.
What you do on the site. The blocks you save. Your choices of theme and platform tab are kept in your browser only (see section 5).
Requests about a design. If you ask us to correct a credit or take a block down through the form on the credits page, we store what you send: your name, your email address, the block, the link to your original work and your message. You don’t need an account for that.
Technical records. The companies that host the site keep ordinary server logs (IP address, browser, pages and videos requested) for a short time for security and reliability, and that includes the requests to your account.
Visit statistics. To see how many people visit and which pages they use, we use Cloudflare Web Analytics. A small script on each page reports the page viewed, the site that linked to it, the type of browser and device, the country and how fast the page loaded. It sets no cookies, stores nothing in your browser and does not follow you across other sites, and we only see totals, never an individual visitor.
Usage analytics. To understand how the site is used and fix what breaks, the site sends usage events to PostHog, in its EU region: the pages you open, actions such as copying a prompt or saving a block, your browser and device, the country worked out from your IP address (the address itself is not stored), and errors with their technical details. For a search we send only the number of results, never what you typed, and addresses go without their query. It records no sessions. When you’re signed in, events are linked to your account’s ID, and PostHog keeps your email on that user. Our admins can read that account’s events, including those from before you signed in on that browser, to help you when something goes wrong. If your browser asks sites not to track it (Do Not Track), nothing is sent. Sharing is on by default; you can turn it off here at any time, and the choice applies to this browser:
Google Analytics. The site also uses Google Analytics 4 to see which pages and blocks people find useful, and asks first in a cookie banner. If you press Accept, it records the pages you view, the site that linked to them, your browser and device, and your approximate location worked out from your IP address; Google Analytics 4 does not store the IP address itself. Until you accept, or if you decline, it sets no cookies and keeps no identifier for your browser: Google only receives a cookieless signal that a page was viewed, which it uses for anonymous totals. Advertising and personalisation signals are always off. You can change your answer at any time with “Cookie settings” at the bottom of every page.
We don’t use advertising trackers.
2. Why we use it
- To run your account, show you the right content and keep your saves: this is needed to provide the service you asked for.
- To count visits and see which pages are used and how fast they load, from anonymous totals: our legitimate interest in improving the site.
- To order Popular blocks using aggregated views, saves, prompt copies and code fetches.
- To measure use with Google Analytics cookies: only with your consent, given in the cookie banner and withdrawn through “Cookie settings”.
- To keep the site secure, prevent fraud and answer your emails: our legitimate interest in running the site properly.
- To act on a request about a design and keep a record of what was changed or removed and why: our legitimate interest in crediting people correctly.
We only email you about your account. We don’t send marketing emails and we don’t sell or rent personal data.
3. Who else handles it
These companies process data for us, each only for the purpose listed:
- Cloudflare (hosts the site and our database, so your account, sign-in and saves; stores and streams the preview videos, counts visits through Web Analytics, sends our sign-in emails, and receives email sent to our support address; data stored primarily in the Asia-Pacific region) — privacy policy
- PostHog, Inc. (usage analytics and error reports, unless you turn them off; EU region) — privacy policy
- GitHub (sign-in provider if you choose it) — privacy statement
- Google LLC (Google Analytics, with cookies only if you accept them in the cookie banner; sign-in provider if you choose it; our support mailbox is a Gmail account, so email you send us is kept there and our replies go out through it) — privacy policy
Some of them are outside your country, mainly in the Asia-Pacific region and the United States. They commit to safeguards such as standard contractual clauses for that data, and to processing it only on our instructions.
4. How long we keep it
Your account and saves stay until you delete your account, which you can do yourself on the account page or by emailing us from the address on the account. Server logs are kept for short periods and then discarded.
A request about a design is kept as the record of that decision. Ask us to delete yours and we will, once it has been dealt with.
5. Cookies and browser storage
The site sets one cookie of its own, only once you sign in: your sign-in session, which it needs to know it is you. The only other cookies are Google Analytics’ (_ga and _ga_ followed by an ID), and only after you press Accept in the cookie banner; the visit statistics and the usage analytics in section 1 set none. Your answer to the banner is kept in your browser’s local storage (nc-consent), so it is asked only once; “Cookie settings” in the footer asks again, and declining there turns Google Analytics off and removes its cookies. The site also keeps a few other things in local storage: your theme and platform choices, whether you share usage data, the page to return to after signing in, and, unless you turn usage data off, PostHog’s random identifier for your browser. Signing out ends the session; clearing site data in your browser removes all of them.
6. Your rights
You can ask us for a copy of your data, to correct it, to delete your account, or to object to how we use it. Email support@nativecook.dev from the address on your account; we answer as soon as we can and within the time the law gives us. If you live in the EU or the UK you can also complain to your data-protection authority. Residents of Vietnam have the rights set out in Decree 13/2023/ND-CP on personal data protection.
7. Children
Native Cook is for people aged 18 and over. We don’t knowingly keep data about anyone younger.
8. Security
Everything travels over HTTPS and our server only lets you read your own records. No method is perfect; if we learn of a breach that affects you, we will tell you.
9. Changes
When this policy changes we update the date at the top, and for meaningful changes we email account holders. Our terms live alongside this page.