Crypto Wallet Basics
Cookie and Cache Policy
Crypto Wallet Basics uses a small set of cookies and may cache pages so they load quickly.
Cookies we use
- A comment or login cookie only if you are an editor signed in to WordPress. Readers do not need an account.
- A form nonce, stored as a cookie or hidden field, so the contact form can reject a forged submission.
- A short-lived rate-limit marker after you submit the form.
Cache
Our host may cache HTML so repeat visits are faster. Policy pages are sent with cache-bypass headers so a confirmation message on the contact form is not stored as the public page.
What you can do
You can block cookies in your browser. The public guides still load. The contact form may fail if the browser drops the nonce cookie. Clearing your browser cache does not delete a message already stored in the reader inbox.
Advertising cookies
Editorial pages load Google Ad Manager. Google may set or read cookies on those pages to choose and measure ads. Policy pages do not load the ad tag, so they do not request those advertising cookies. If you watch a rewarded ad, this site sets cryptowalletbasics_access for 6 hours. That cookie only records that the unlock was granted. It is not sent to sign you in.