Privacy Notice
This notice explains data handling at handsoffdinners.com. Posted August 24, 2026.
No-registration browsing
The site has no current reader profiles, shopping cart, paid subscriptions, or comments. It does not ask for passwords, cards, delivery addresses, or public profiles for ordinary browsing.
Messages to hello (at) handsoffdinners.com provide an address, content, and attachments. They are used to reply, route rights requests, assess corrections and relevant proposals, and maintain necessary editorial records. Do not send confidential financial, identity, or health documents.
Logs and storage
Hosting and security providers may record IP address, time, browser, device, operating system, referrer, URL, status, and abuse signals for delivery, uptime, troubleshooting, capacity, and defense. Cookies and local storage can remember choices; none currently builds a behavioral-ad profile, though security or preference storage may be necessary.
Analytics and ads
Google Analytics is not enabled. If activated, this notice will describe Google’s role, the live configuration, retention, and regional controls. Ads are planned but no network is serving them. Before launch, the provider will be named with its cookies, identifiers, personalization, recipients, retention information, and opt-outs. Prospective networks are not current partners.
Purposes and sharing
Information supports operation, security, correspondence, corrections, terms, and law. Hosting, email, backup, maintenance, and protection vendors may process limited data. Disclosure may answer valid process, prevent harm, or accompany a protected website transfer. Hands-Off Dinners does not sell addresses or personal data for cash and does not currently share it for cross-context behavioral advertising.
Grounds and retention
For European and UK visitors, bases may include legitimate interests, requested steps, consent, and legal obligation. Logs remain only for proportionate operational periods; email remains through the matter and longer for correction, permission, complaint, or abuse records. Lawful safeguards should cover restricted international transfers. Absolute security cannot be promised.
Rights
Local law may allow access, correction, deletion, restriction, portability, objection, withdrawal, appeal, or regulatory complaint. Covered U.S. residents may know categories and recipients and opt out of sale, sharing, targeting, or profiling without discrimination. Recognized opt-out signals will apply to any active covered practice.
Requests and minors
Email “Privacy” to hello (at) handsoffdinners.com. Identity or agent authority may be proportionately verified. The site is not directed to children under 13 and does not knowingly collect their data. Outside pages have separate policies. Updates will carry a revised date.
Current collection categories
The categories that may pass through current systems include identifiers such as IP or email address, Internet activity such as requested and referring pages, device characteristics, approximate region derived by infrastructure, and communication content. Sources are visitors, their browsers or devices, and operating vendors. These data support delivery, protection, diagnosis, communication, and editorial records. They are not currently used for ad targeting or eligibility decisions.
Managing browser technologies
Browsers generally allow a person to inspect, remove, or block cookies and site storage. Settings may need to be repeated on each device and browser. Blocking all storage can affect security or preference features. If planned advertising goes live, a rejection of personalized ads may still permit ads based on page context. Hands-Off Dinners will not use a preselected consent choice where affirmative permission is legally required.
Sensitive data and automated processing
The publication does not seek government identification, exact geolocation, account credentials, medical records, biometric templates, or details revealing protected beliefs or identity. Please omit them from recipe email. The site does not perform automated decision-making that produces legal or comparably important effects, and it does not use cooking interests to assess a person for credit, insurance, housing, work, or education.
Appeals and accountability
A response that cannot fulfill a request will explain the applicable exception and any right to appeal. Residents of the EEA or UK can complain to their local data-protection authority. Hands-Off Dinners may retain a narrow record of the request, verification, outcome, and date to demonstrate compliance. That record is not used to restart marketing or reconstruct material that was properly deleted.
Future email features
A message about an air fryer or sheet pan will not place the sender on a mailing list. If a newsletter is later offered, signup will separately identify the email provider and the messages requested. Every marketing email will include a usable unsubscribe option. The publication may still keep a suppression record so an unsubscribed address is not accidentally added again, or preserve separate correspondence when needed for a correction, permission, privacy request, or legal obligation.
Third-party destinations
Recipe pages may link to appliance manuals, safety authorities, stores, brands, or other publishers. Once a visitor follows the link, the destination’s policy applies and Hands-Off Dinners does not control its collection. A link does not make the outside operator a service provider to this site. If an embedded feature is introduced, its direct collection will be explained and, where necessary, held back until the visitor makes a consent choice.
Aggregate use and browser signals
The publication may review counts or de-identified summaries that no longer reasonably point to a person, such as overall page demand or error frequency. It does not attempt to reverse that process. Conventional Do Not Track signals do not have one standardized legal meaning, but Global Privacy Control and other binding preference signals will be processed when they apply. If infrastructure cannot honor a required signal, the affected optional practice should not be enabled until an effective method exists.