Sanskar

Legal

Privacy Policy

What information this website handles — and what it does not.

Last updated

In short: this website has no analytics, advertising, or tracking, and it sets no cookies. It is hosted on GitHub Pages, which logs visitors’ IP addresses for security purposes. If you email me or use the contact form, I receive what you send and use it only to reply. If you write a blog post, it is published on GitHub and on this website under your GitHub username or, if you write it with an account on this website, your display name. Accounts need only an email address, which is used to sign you in and is never shown.

Who is responsible

This Privacy Policy explains how information is handled when you visit sanskarIN.github.io (the “website”), the personal website of Sanskar (“I”, “me”, “my”). For privacy questions, email sanskarin@outlook.in.

Information I collect

The website collects personal information only when you choose to give it: when you create an account to write for the blog, and when you publish a blog post. It has no comment sections, newsletter sign-ups, analytics, or advertising. Accounts are stored by Supabase, the optional contact form sends your message to me through a form-delivery service, and blog posts are stored on GitHub, as described below.

Information you provide

If you email one of the addresses listed on the website, I receive your email address, your name if you include it, the content of your message, and any attachments. I use this information only to read and reply to your message and to handle your request, such as a business inquiry or a support question. I do not sell it or use it for marketing.

If you use the contact form, it sends your name, email address, chosen topic, and message to Web3Forms, a form-delivery service, which forwards them to my email inbox. Web3Forms states that it does not store form submissions and only passes them on. I handle messages sent through the form the same way as emails.

Accounts

You can create an account to write for the blog. Accounts are provided by Supabase, which stores them for me.

  • Signing in: you enter your email address, and a 6-digit code is sent to it by Gmail. Entering the code signs you in, and creates your account the first time. There is no password.
  • What is stored: your email address; when your account was created and last used; your author profile (username, display name, and, if you add them, a short bio and a website); the posts you send, with where they are in the review; and the images you upload. To keep accounts secure, Supabase also records technical details of each sign-in, such as its time and the IP address used.
  • Your email address is used only to sign you in, and to contact you about your account or your posts if needed. It is never shown on the website or on GitHub, and it is not used for newsletters or marketing.
  • What is public: your username, display name, bio, and website appear on your author page and with your posts. The images you upload can be seen by anyone with their link, and they appear in your post’s public issue on GitHub. Location and camera details are removed from them in your browser before they are uploaded.
  • Staying signed in: your browser keeps your session in its local storage, and the post you are writing is kept there too until you send it. The Cookie Policy lists both.
  • Deleting your account: you can delete your account on your account page. This deletes your account, profile, and uploaded images from Supabase, and withdraws your posts that are still waiting for review. Your published posts stay on the blog under your display name, unless you choose to remove them as well. The GitHub issues for your posts are closed but stay public, as do earlier versions in the repository’s history; email sanskarin@outlook.in if you would like the issues deleted.

Blog posts

The blog accepts posts written with an account on this website or with a form on GitHub. When you send a post:

  • it becomes a public issue in this website’s GitHub repository: posted from your GitHub account if you use the form on GitHub, or by my GitHub account for you if you use an account on this website, together with your username and display name and a number that links it to your account;
  • if it is published, the website shows your post, its images, and your name as the author — your GitHub username, linked to your GitHub profile, or your display name, linked to your author page — and the post’s text and images are stored in the website’s public repository on GitHub;
  • its images are copied to the website and saved without their metadata, such as location and camera details, and very large images are scaled down; and
  • anything you include in the post, including any personal information, becomes public, so please include only what you are happy to share.

To remove a post you wrote with an account, use your account page. To have any other post removed, comment on its issue or email sanskarin@outlook.in. I will remove it from the website and can delete its issue too. Earlier versions of a published post remain in the repository’s public history on GitHub. Your GitHub account itself is handled by GitHub under its own privacy statement.

Automatically collected information

The website is hosted on GitHub Pages. When you visit, your browser connects to GitHub’s servers, which receive the technical information needed to deliver the pages, such as your IP address and browser details. According to GitHub’s documentation, when a GitHub Pages site is visited, the visitor’s IP address is logged and stored for security purposes. I do not have access to these logs, and the website adds no logging or analytics of its own. The account pages and author pages also connect to Supabase, which receives the same kind of technical information when they do.

Cookies

The website does not set cookies. If you use the theme switch, your choice of light or dark theme is saved in your browser’s local storage so the site remembers it on your next visit. That preference stays on your device and is never sent to me. If you sign in, your session and any unsent post are kept in local storage too. The Cookie Policy explains this in detail.

Analytics

The website does not use analytics, tracking pixels, or similar measurement tools. If that ever changes, this policy and the Cookie Policy will be updated to describe the tools used.

Searching the website happens entirely in your browser. When you open the search, your browser downloads a list of the website’s pages, blog posts, and projects from the website itself and looks for matches in it. What you type is never sent anywhere, and it is not saved. The terminal on the Home page works the same way: its commands are handled in your browser, and nothing you type in it is sent or saved. The filters on the Projects page also work in your browser; they are added to the page’s address so that you can bookmark or share the filtered list.

Third-party services

The website relies on, or links to, the following services. Each has its own privacy policy:

The website does not embed content, scripts, fonts, or images from any of these services; only its account and author pages connect to Supabase. They receive information about you only if you follow a link to them, send an email, submit the contact form, use an account or author page, or write a blog post.

The Projects page shows public information about my GitHub repositories, such as their descriptions, languages, and stars, and the contribution activity shown on my GitHub profile. A scheduled GitHub Actions workflow copies this information from GitHub’s API and saves it with the website, so your browser does not contact GitHub to show it.

Links to other websites are provided for convenience. Once you leave this website, the other website’s privacy policy applies, and I am not responsible for its practices.

Data retention

I keep emails for as long as they are needed to reply and to handle any ongoing conversation, collaboration, or support request, and for reasonable record-keeping afterwards. Messages sent with the contact form arrive as emails and are kept the same way. You can ask me to delete your correspondence at any time. Accounts are kept until you delete them, or until I delete them, for example because they break the Terms. Published blog posts stay on the website until they are removed; their issues, and the repository’s history, stay on GitHub unless they are deleted. Information logged by GitHub is kept according to GitHub’s own policies.

Data security

The website is served over HTTPS. Accounts are stored by Supabase, whose database rules let each person read and change only their own account details. Sign-in codes work once and expire after a short time, and there are no passwords to steal. Apart from accounts, the website stores no personal information other than the blog posts people choose to publish. Emails are protected by the security measures of the email providers. Contact form messages are sent to Web3Forms over an encrypted (HTTPS) connection. No method of transmission or storage is completely secure, so please do not send sensitive information such as passwords by email or through the contact form.

Children’s privacy

The website is intended for a general audience and is not directed at children. It does not knowingly collect personal information from children. If you believe a child has sent me personal information or published it in a blog post, please contact me and I will delete it.

International users

The website can be visited from anywhere. GitHub, the email providers, Web3Forms, Supabase, and the other services mentioned above may process information in countries other than your own, including the United States.

Your rights

Depending on where you live, you may have rights over your personal information, such as the right to access, correct, or delete it, or to object to how it is used. Because the only personal information I hold is what you send me, your account, and any blog posts you publish, you can exercise these rights by emailing sanskarin@outlook.in; for a blog post, you can also comment on its GitHub issue. If you have an account, you can see and change your profile, and delete your account, on your account page. For information processed by GitHub or another service, please contact that service directly.

Changes to this policy

I may update this Privacy Policy from time to time. The “Last updated” date at the top of this page shows when it last changed.

Contact

Questions about privacy? Email sanskarin@outlook.in.