Privacy & Cookies

Last updated 2026-10-27. Weekly Delight is run by one person, Turab.

The short version

There is no account, no login and no database. This is a static site.
What you save — favourites, your theme, your reviews — stays in your own browser and never reaches me.
There is no consent banner. Analytics and advertising load with the page. A content blocker stops the analytics and may stop the ads, but the ad network serves them from addresses that change to get past blockers, so I cannot promise it will — the links further down turn each one off at the source.
The contact form is the only thing that sends anything to me, and only what you type into it.
Nothing on the site depends on either: if the analytics or the ads are blocked or fail to load, every recipe, the search and the timers work as before.

Cookies, and how to refuse them

This site does not ask before loading its analytics and advertising scripts: they run when the page does. I would rather say that plainly than imply a choice you were not given.

If you do not want them, a content blocker is the usual way to stop them, and the site works perfectly without either — every recipe, the search, saved recipes, cook mode and the timers are unaffected. I would rather be plain about the ads, though: the network serves them from addresses that change, which is how it gets past some blockers, so a blocker may stop them or may not. The Analytics and Advertising sections below also link to the opt-outs Google and Adsterra provide, which work across every site that uses them, not just this one.

The things this site stores for itself — your theme, your saved recipes, your reviews — are a separate matter. They never leave your device and exist only because you asked for them.

What stays on your device

The site keeps four things in your browser's local storage. They never leave the machine you are reading on, are not sent anywhere, and I cannot see them.

Your saved recipes — the hearts you tap, kept under cv:favourites.
Your theme — light or dark, under cv:theme.
Reviews you write — under cv:reviews: and the recipe name. Reviews on this site are private notes to yourself. Nobody else sees them, including me.
An old newsletter entry — under cv:newsletter, if you used the signup box before it was removed. Nothing was ever sent anywhere; you can clear it with your browser data.

Clearing your browser data clears all four, and you will lose your saved recipes. There is no copy anywhere else.

The contact form

This is the one place the site collects anything about you, and only because you chose to type it. When you send the form, your name, email address, subject and message are posted to a small script on this site's server, which emails them, with the time they were sent, to the site owner's inbox. Nothing is saved in a database on the website. The message then exists wherever the owner's email lives: on Hostinger's mail systems if the mail is sent through them, and with the owner's own email provider.

Your address is used to reply to you and for nothing else. It is not added to any list, not passed to anybody, and not used for advertising. Messages stay in the inbox until the owner deletes them; if you would like a message of yours removed, say so in a reply. Hostinger's own privacy policy covers what they do with it while it is on their systems.

What the script keeps to limit abuse. For each message it records the time and a salted hash of the IP address it came from, in a small file on the server that nothing else reads. A hash like this is pseudonymous, not anonymous: it is still personal data, because someone with the site's secret could check an address against it. An entry stops counting after an hour and is deleted the next time the form, or its set-up check, is used. If nobody uses the form, an expired entry stays in the file until the next use, so it is not guaranteed to be gone after exactly an hour. The same file keeps a count of messages in the last day, as timestamps only. Separately, the server's ordinary access logs record your IP address for every request, as described under Hosting below.

The form also carries a hidden field that people never see. If it arrives filled in, the submission came from a bot and is dropped without being sent. It collects nothing about you.

If the contact form has not been switched on, the page says so and nothing you type leaves your browser.

Problem reports

The report a problem form sends what you write to a program on this site's server, which stores it as a file outside the public part of the site, where only the person running the site can read it. It stores the recipe and version you were reading, your answers, the time, and a salted hash of your IP address used only to stop floods of reports. Your name and email address are stored only if you give them, and are used only to reply to that report. Reports are kept while the correction is dealt with and deleted within a year. To have a report you sent deleted sooner, quote its reference through the contact page.

If the page says reports are not switched on, nothing you type is sent or stored.

There is no newsletter and no mailing list, and no page asks for your email address for one. The weekly plan is a page you can visit, not an email.

Analytics

Google Analytics 4 counts visitors and shows me which recipes get read. It sets cookies, records your approximate location from your IP address, and notes your device, browser and the pages you open. It does not tell me who you are, and I never see an individual reader — only totals.

Google is the data controller for what it collects. Its own explanation is in how Google uses data from sites that use its services, and you can opt out everywhere at once with the Google Analytics opt-out add-on.

Grow by Mediavine

The site loads Grow, a script from Mediavine that offers its own tools for saving recipes and following the site. Mediavine runs it, not me: it may set cookies or use your browser's storage, and like any script fetched from another server it receives your IP address and basic details of your device and browser. If you create a Grow account or sign up for anything through it, what you give is held by Mediavine, not by this site.

Mediavine's Legal & Privacy Center explains what Grow collects and how to ask Mediavine to see or delete your information. The hearts and saved recipes built into this site are separate: they stay in your browser, as described above.

Advertising

The site carries advertising, which is what pays for it. The ads are served by Adsterra, not by me: they choose what you see, and they may set cookies or similar identifiers to do it, including for personalised advertising. I do not receive your data from them and I cannot see who was shown what.

Adsterra publishes its own privacy policy, which governs that part of your visit. If you would rather not be tracked for advertising, a content blocker may stop it, though the ads are served from addresses that change to get past blockers, so it is not a guarantee. You can also turn off ad personalisation in Google's ad settings for the Google side of the web.

What else the site loads

Fonts are served from this site itself, so no font provider sees your IP address.
Photographs are served from this site itself, not from anywhere else.
The search index is a file downloaded from this site when you first use the search box. Your search terms are handled entirely in your browser and are never sent anywhere.
Hosting. The site is served by Hostinger, whose servers log requests, including IP addresses, as any web server does.

Children

This is a recipe site with no account system and nothing aimed at children. I do not knowingly collect anything from anyone, of any age.

Your rights

Unless you have sent me a message, I hold nothing about you at all: everything the site stores is already in your hands, and clearing your browser data removes it. If you have used the contact form, what I hold is that message, and you can ask me to delete it — reply to my email, or send a new message saying so, and it goes.

For the data Google and Adsterra collect, their policies above set out how to make a request to them, since they are the ones holding it.

Changes

If what the site does changes — a real newsletter, a working contact form, a different ad network — this page changes with it, and the date at the top moves. There is no archive of previous versions; the site is small enough that the current one is the only one that matters.

Getting in touch

Use the contact form. If something on this page is wrong or unclear, that is exactly the sort of thing I would like to be told.

This page describes what the site does, honestly and in plain language. It is not legal advice, and it has not been reviewed by a lawyer. If you are reading it as a template for your own site, do not — write yours from your own code, as this one was.