Your privacy
Privacy Policy
Last updated: July 26, 2026
This policy explains what Sim Village Cooking processes when you browse the website, use an account, post a comment, like an episode or allow optional services.
Who operates this website
Sim Village Cooking operates this website from Azerbaijan. Privacy, access and deletion questions may be sent to contact@simvillagecooking.com. The confirmed legal operator name, postal contact and monitored support address must be inserted before public launch.
Information we process
Hosting and security systems may process IP address, request time, browser and device information, referring page, requested URL and approximate region. WordPress processes account username, email address, authentication records and password-reset requests. A submitted comment may also include the account ID, public display name, email address, IP address, browser user-agent, date, text and moderation status. We process episode likes, device-local privacy choices and messages you send. Passwords are one-way hashed by WordPress and are not visible to administrators.
Purposes and legal grounds
Information is used to provide requested features, secure the service, prevent abuse, moderate public comments, maintain essential records, improve performance and meet legal duties. Processing may rely on providing a requested service, legitimate interests in a safe website, consent for optional media or analytics, or legal obligations. We do not sell personal information.
Accounts, likes and comments
Public registrations receive subscriber-only access. Each account can record one like per episode. Approved comments display the chosen public name, a locally generated initial, date and text; email address, IP address and browser information are not displayed. Authentication, registration, reset and comment attempts are verified and temporarily limited.
Approved comment text may be used by a local keyword-matching rule to select three related episodes. That matching runs on this website and is not sent to an external artificial-intelligence service.
YouTube and automated presentation
YouTube players use youtube-nocookie.com and remain unloaded until YouTube Media is allowed in Cookie settings. Ordinary preview images are requested from YouTube's image server before playback, so Google may receive the visitor's IP address, browser request and referring information when an image loads. Media consent controls embedded players; it does not currently stop these preview-image requests.
The site can use a model supplied with the theme to locate the combined area occupied by people in a YouTube preview image and centre the crop. Analysis runs in the visitor's browser, does not identify a person, and stores only a video-specific crop coordinate on that device. Daily Story introductions and related-video suggestions are produced by local title, description and keyword rules; they are not sent to an external AI service.
Analytics and advertising
Optional Google Analytics 4 remains unloaded until a valid Measurement ID is configured and Analytics is allowed. Advertising is currently unavailable in Cookie settings, so Google AdSense code remains blocked even if placement IDs have been prepared. Before activation, final provider and cookie details must be added and a compliant advertising-consent system must be installed. Where Google requires it for AdSense traffic in the EEA, the United Kingdom or Switzerland, this must include a Google-certified consent management platform integrated with the applicable IAB Transparency and Consent Framework. After an allowed Google service loads, Google and its partners process information under their own policies and configured controls.
Recipients, transfers and retention
Hosting, email and security providers may handle information. Google may receive preview-image requests and may process additional data after an optional Google service is allowed. Providers may process information in other countries using their contractual and legal safeguards. Account data remains while the account is active; comments and likes remain until removed or the related account is deleted; short security counters expire after minutes or hours. Private daily theme snapshots rotate to the newest seven copies, so a recently deleted comment or like may remain in those recovery copies until rotation removes it. Hosting logs and full backups follow the hosting provider settings.
Your rights and choices
Depending on your location, you may have rights to access, correct, delete, restrict or object, withdraw consent and complain to an authority. Withdrawal does not invalidate earlier lawful processing. Use Cookie settings in the footer or contact contact@simvillagecooking.com. We may need to verify a request. WordPress privacy tools cover account and comment data, and this theme adds export and erasure support for episode likes.
Children, security and changes
This is a general-audience site and is not designed to knowingly collect children's data without required consent. WordPress hashing, request verification, access limits, moderation, HTTPS-ready headers and private snapshots reduce risk, but no internet service can promise absolute security. The updated date changes when material practices or providers change.