Dev.Cooking is an independent crypto publication at dev.cooking. This policy describes the website implementation reviewed on October 5, 2026. The public newsletter signup has been removed; reading articles does not require an account or wallet connection.
Information used to operate the website
Our hosting provider, Netlify, may process technical request information such as IP addresses, browser information, requested URLs and timestamps to deliver and protect the site. Hosting controls and provider retention practices are separate from the article code. See Netlify's privacy policy for its description of processing.
The search interface downloads the first-party article index and matches your query in your browser. The current application does not send the text you type into search to a separate search or analytics service. Ordinary page and index requests still reach the hosting provider.
Market data and external references
The browser requests market snapshots from a Dev.Cooking server endpoint. That server retrieves public quotes from CoinGecko, with a Binance public-data fallback. The application does not forward a visitor's email, search query or wallet address to these providers. Their own websites have separate policies when you follow an external link.
Articles link to primary documentation. Following those links leaves Dev.Cooking and may expose your request information to the destination website. We do not control that site's collection practices.
Cookies and browser storage
The reviewed site code does not set advertising cookies, install an analytics tracker or persist search queries in local storage. Fonts, editorial artwork and optimized coin icons are served from this site. Coin marks are credited to their respective issuers and the image provider; they are not claimed as exclusive Dev.Cooking artwork. The hosting platform or a protected deploy preview may use necessary access-control or security mechanisms. See our cookie policy for the scope of this statement.
The optional market watchlist stores selected coin IDs in your browser’s localStorage. It is not sent to our server or synchronized to an account. Market search text is filtered locally and is not persisted. Clearing site data removes the saved watchlist.
Email enquiries
When you email Hello@dev.cooking, your email address, message and any information you choose to include are used to respond to your enquiry, address corrections or rights requests, and maintain necessary correspondence records. Do not include wallet credentials or unnecessary sensitive information. Email service providers may process the correspondence to deliver and secure it.
Previous newsletter records
Earlier signup functionality stored an email address, creation time, consent state, consent version and a hashed removal-token verifier in private Netlify Blobs storage. Production and preview records are separated. Newsletter email delivery is not connected. The public signup interface is no longer present.
If you saved your secure removal link, it remains available. A successful removal clears the email field and marks that record unsubscribed; a hashed identifier and record metadata can remain. It is not a promise to erase every hosting log or backup. No automatic expiry for historical records is currently configured. Access is limited by the hosting account and application controls; we do not claim that these make any system immune to a breach.
Requests and policy changes
Email Hello@dev.cooking for privacy enquiries and access, correction or deletion requests. See Contact for reporting guidance. Do not post private personal information in a public issue. Access, correction or deletion requests may require proportionate identity verification so that another person cannot obtain your information. Any applicable rights depend on the circumstances and law; this page does not waive them.
If the website introduces accounts, advertising, analytics or other data collection, this policy must be updated before describing those features as active. We do not sell newsletter records or use them as public article content.