Privacy Policy
How this cooking journal handles your information
This policy describes how vitaltidebodycaresit.site handles personal data. It covers what is collected, why it is collected, how long it is kept, and how you can contact the site about your data. The site is an informational cooking journal and does not sell products or process payments.
What this page answers
- Which details the contact form asks for
- Why recipe notes and messages are read
- How long messages and logs are kept
- How to ask for access or deletion
Last reviewed October 2026. This policy sits alongside the cookie policy and the terms of service for the journal.
What data is collected
Three kinds of information can reach the journal, and each behaves differently.
Contact form details
Data is collected only when you submit the contact form. That includes your name, your email address, and the message you write. Nothing else is asked for.
No account data
No account registration is offered and no order or payment data exists on this site. There is nothing to log in to, and no checkout runs behind any page.
Server logs
Standard server logs may record technical information such as IP address, browser type, and the pages requested. Logs stand apart from anything you type into a form.
Because this is a home cooking blog of traditional Japan recipes and everyday home meals, the only free-text material the journal ever holds is what a reader chooses to send in a note about a dish.
Why data is collected
A reply, a correction, and nothing more
Contact form data is used to reply to your message and to correct or expand recipes when the information is useful. Server logs are used to keep the site working and secure. Data is not used for advertising profiles and is not sold.
Answering a reader
If a note questions a step in a recipe or asks how a seasonal substitution behaves, the reply goes back to the address you used. That is the whole purpose of holding it.
Improving the notes
Reader questions often point at unclear steps in a comfort food idea or a baking note. When a message shows a gap, the corresponding recipe text can be rewritten.
Keeping the site running
Server logs help spot broken pages, heavy traffic, and attempts to interfere with the site. They are technical records, not reader profiles.
What never happens
Information is not sold, rented, or turned into advertising audiences. Nothing sent to the journal is published without being discussed first.
Cookies
Cookies and similar technologies are described in the cookie policy, which is a separate document. In short, only the cookies needed to run the site and, where applicable, basic analytics are used. You can control cookies through your browser settings.
Nothing on the journal depends on a cookie to show you a recipe. If you clear them, the pages still read the same. The cookie policy explains which names appear on your device and what each one does, in the same plain wording used here.
Retention
Two kinds of records, two different clocks. Neither one is kept longer than its job requires.
If a question leads to a longer exchange, the message stays only while that exchange is active.
- Contact messages
- Kept for as long as needed to handle the request and any follow-up, and then removed.
- Server logs
- Kept for a limited period for security and diagnostic purposes.
- When it is no longer needed
- The record is deleted. Nothing is archived indefinitely for later reuse.
Your rights
You can request access to the personal data held about you, ask for a correction, or ask for deletion. You can also object to certain processing. Requests can be sent to the contact address on the contact page. A response will be provided within the period required by applicable law.
Send the request from the same email address you used before, if you have one, so the record is easy to find.
Ask what is held
You receive a plain description of the records tied to your address, and where they came from.
Ask for a correction
A misspelled name or a wrong address on a message can be fixed, or the message can be removed outright.
Ask for deletion
Old messages are removed on request, unless a legal obligation requires them to be kept for a set time.
Object to processing
If you would rather a message were not used to revise a recipe, say so and it stays as an unanswered note.
Third parties and transfers
The site does not sell or rent personal data. Limited service providers, such as hosting, may process technical data on the site's behalf and only as necessary to operate it. Where data is transferred outside your country, appropriate safeguards are used.
In practice that means a small number of providers touch the technical layer, and none of them receive the text of your message for their own purposes. Providers are bound to process data only on the journal's instructions.
Changes to this policy
This policy may be updated to reflect changes in the site or in applicable law. The current version is always the one published on this page. Continued use of the site after an update means you accept the revised policy.
Substantive rewrites — a new category of data, or a change to how long messages are kept — will show a new review date at the top of the document so readers can tell the text apart from the earlier version.
Related documents
Questions readers send most
Four short answers that cover almost everything asked about data on a seasonal cooking guide with no accounts and no checkout.
What happens to a message after it is sent?
It is read, answered if a reply is needed, and kept only while the exchange is active. If a question points at an unclear step in a recipe, the recipe text may be revised — without naming the reader.
Do I need an account to read the recipes?
No. Every page of this home cooking blog reads the same whether you are signed in or not, because there is no sign-in to begin with. Only the contact form collects anything.
Can I ask for a recipe correction?
Yes, and it is welcome. Notes on quantities, simmering times, or a seasonal substitution that behaves oddly are exactly the kind of message that improves the journal.
How long does a data request take?
Requests are answered within the period required by applicable law. Send yours to the contact address and include the email you wrote from, so the record can be located quickly.
Where to continue reading
Policy pages are short stops. These four routes lead back into the actual cooking writing, or to the address that handles data questions.
Written enquiries are read Monday to Friday, 9:00 AM – 6:00 PM.