Privacy policy: no cookies, no tracking, no stored form data

Privacy at a glance

dilbdrbk.com.np is a static website: it has no database, no user accounts and no tracking scripts. Personal data reaches me only when you choose to send it, such as an email, a phone call or a LinkedIn message.

Who is responsible for your personal data?

Dil Bahadur B.K., a semantic SEO consultant based in Nepal, owns dilbdrbk.com.np and is the data controller for this site. I decide what personal data the site handles and why, and I answer every privacy request myself.

You can reach me at [email protected] or on +977 9810234765. Messages sent through this site come to me directly, with no agency or sales team in between.

What personal data does this site collect?

The site collects no personal data on its own. Every piece of personal data I hold comes from a message you decide to send.

The contact form sends nothing to this site

The "Hire Me" form asks for your name, email address, website and message. When you press send, the form opens your own email app with the message filled in, and nothing leaves your device until you send that email yourself.

Emails, calls and LinkedIn messages

An email you send reaches my Gmail inbox with your name, email address and anything you write, such as your website, goals or project details. A phone call or a LinkedIn message shares the details that your phone carrier or LinkedIn passes on, such as your number or profile name.

Does this site use cookies or analytics?

No. dilbdrbk.com.np sets no cookies, stores nothing in your browser's local storage and loads no analytics, advertising or social media tracking scripts, such as Google Analytics or a Meta pixel.

The share buttons under each blog post are plain links and a copy button, so a social network learns nothing about you unless you click one. The interactive tools on the blog, such as the topical coverage checker, run entirely in your browser and send your answers nowhere.

I use Google Search Console to see how the site performs in Google Search. Search Console reports totals from Google's own search results, such as clicks and queries, and identifies no individual visitor.

Which third-party services process data when you visit?

Three infrastructure services handle your connection when you load a page. Each one receives your IP address and basic request data, such as the page you asked for and your browser type, because no web page can be delivered without them.

Cloudflare: delivery and security

Cloudflare sits in front of the site, encrypts the connection and blocks abusive traffic. Cloudflare's privacy policy describes it as a data processor for visitor data, which may include IP addresses and traffic routing data. Its Network Error Logging feature reports failed connections, and Cloudflare states that it does not log the client IP address in that pipeline. See the Cloudflare privacy policy.

GitHub Pages: hosting

GitHub Pages stores and serves the site's files. GitHub's documentation states that the IP address of every GitHub Pages visitor is logged and stored for security purposes, whether or not the visitor has a GitHub account. See the GitHub privacy statement.

Google Fonts: the site's typeface

Google Fonts delivers Archivo, the typeface used across the site. Google receives your IP address, the requested font URL and HTTP headers, such as the user agent and referrer, and states that the Google Fonts API sets no cookies. See the Google Fonts privacy FAQ.

How is your personal data used?

I use your details for two purposes only: replying to your message and delivering work you agree to, such as an SEO audit or a topical map. The legal basis is your consent, given when you contact me, and the steps needed to prepare or perform an agreement with you.

• I never sell, rent or trade personal data.
• I never add you to a mailing list or newsletter.
• I never share your details with other businesses for their marketing.
• I make no automated decisions or profiles about you.

Project data you share during an engagement, such as Search Console access or site analytics, stays inside that project and is used only for the agreed work.

How long is your data kept?

Emails and messages stay in my inbox while a conversation or project is active and while I need them as a record of agreed work. I delete them sooner whenever you ask, unless a legal obligation, such as a tax record, requires me to keep part of them.

Cloudflare, GitHub and Google keep their own request logs under their own retention rules, which their privacy policies describe.

What are your rights over your personal data?

You can ask me at any time to see, correct or delete the personal data I hold about you, or to stop using it. These rights apply to every visitor and client, wherever you live.

1. Access: receive a copy of the messages and details I hold about you.
2. Correction: fix details that are wrong or out of date.
3. Deletion: have your messages and details erased.
4. Objection: withdraw your consent and stop further use.

Send your request to [email protected] and I will reply within 30 days. I am based in Nepal, where the Individual Privacy Act, 2075 (2018) protects personal information, and visitors in other countries can also contact their local data protection authority.

How is your data protected?

Every page loads over HTTPS, so the connection between your browser and the site is encrypted. The site stores no visitor data on a server, so a breach of the site itself would expose no form submissions or accounts.

Messages you send are stored in Gmail, which Google protects under its own security program, and the account that receives them belongs to me alone.

Children and external links

This site serves businesses and is not directed at children under 16. I do not knowingly collect personal data from children, and I delete any I learn about.

Pages link to other websites, such as LinkedIn, GitHub, Google's documentation and cited research. Those sites follow their own privacy policies, which this policy does not cover.

Changes to this policy and how to contact me

I update this policy whenever the site starts or stops using a service that handles personal data, and the effective date at the top changes with each update. A new service, such as an analytics tool or a form provider, will be named here before it goes live.

Questions about privacy go to [email protected]. The editorial policy explains how the content on this site is researched and checked.