This policy describes the Shivaay Waves website as it actually works. It does not describe a company registration, a postal address, or a data-protection officer, because those details have not been provided. If they are added, this page will be updated and the date at the top will change.
Who publishes the site
The site is published under the name Shivaay Waves, as the home of the Shivaay Waves YouTube channel. To ask a privacy question, use Contact Us. If a contact email is shown on that page, you may use it as well.
Information the site collects
If you send the contact form, we store your name, email address, the enquiry type you chose, the message, and the fact that you consented to storage. The record is a private message in the WordPress dashboard. Editors can read it. It is not published. It stays until an editor deletes it, or until it is removed with WordPress’s personal-data eraser.
The form also keeps a short-lived rate limit so one network cannot submit endlessly. That limit is stored as a hash, not as a profile, and it expires within an hour. A form token is kept for up to two hours so a submission can be checked, then it is deleted.
The host that serves the website may keep ordinary server logs, which can include an IP address, browser type, and the address of the page requested. This theme does not copy those logs into a marketing list. We do not run a separate analytics product.
If you are an editor and you log in, WordPress sets its own login cookies. If comments are opened later and you choose to leave one, WordPress can store the name and email you type, and it can set the usual comment cookies. Comments on the journal are closed at the moment.
Cookies in use now
The cookie notice can set one preference cookie, sw_cookie_notice, so the notice stays dismissed. That is an essential preference, not an advertising cookie. Details and the inactive categories are in the Cookie Policy.
Analytics
No analytics service is installed. We do not currently send visit statistics to a third party. If that changes, this policy will name the service before it runs.
Advertising and Google AdSense
Advertising is not active. The theme does not load AdSense, does not request an advertising cookie, and does not personalise ads, because there are no ads.
If advertising is enabled later, third-party vendors, including Google, may use cookies to serve advertisements based on a user’s previous visits to this website and other websites. Google’s use of advertising cookies enables it and its partners to serve ads to users based on their visit to this site and other sites on the Internet.
Users may opt out of personalised advertising by visiting Google Ads Settings. Users can also visit aboutads.info to learn about interest-based advertising and the opt-out choices offered by participating companies.
Those two paragraphs describe a future state. They are not a statement that the cookies are already present.
YouTube and other third parties
A film is shown only after an editor pastes its YouTube URL and YouTube confirms the title. Latest uploads are links an editor adds by hand. Opening the page does not load a player. A saved film may show its YouTube thumbnail, which is requested from YouTube’s image servers and does not start playback. Pressing play requests the player from youtube-nocookie.com. The film does not start until you use YouTube’s own play control. From that moment YouTube may set cookies under its own policy. Watch and Subscribe links leave this site and do not embed a player. This site does not use the YouTube Data API. We do not control YouTube. Links to YouTube, Google’s Ads Settings, and aboutads.info also leave this website.
Why we keep contact messages
We keep a message so an editor can answer it, refuse a request, or act on a copyright notice. We do not use contact messages to build an advertising audience. We do not sell them.
How long information stays
Contact messages remain until deleted. Rate-limit records and form tokens expire on their own, as described above. Server logs follow the host’s schedule, which this page does not invent. The preference cookie is set for about six months.
Security
Messages are stored in the site database and are not meant for the public web. Access to the dashboard is limited to editor accounts. The public site should be served over HTTPS once it is on its production address. A local preview may still be HTTP. No method of storage is perfectly safe, and this page does not claim otherwise.
Your choices
You may ask to see the messages stored under your email, to correct them, or to delete them. Use the contact form and say that the message is a privacy request. Editors can also use WordPress’s export and erase tools, which are connected to these messages. What a local law requires depends on where you and the site operator are. This page does not name a statute or a court, because a jurisdiction has not been designated here. We will handle a request we can match to an email address, and we will not invent a response-time badge we cannot keep.
Children
The site is written for adults who want a quieter hour. It is not directed at children, and the contact form should not be used to send a child’s personal information.
Changes
When this policy changes, the updated page is the notice. The “last updated” line uses the page’s modified date in WordPress.