Privacy Policy | Pushkar Deshmukh

This site (pushkardeshmukh.com) is run by Pushkar Deshmukh. This policy describes what data we collect, how we use it, and your rights. By using the blog's interactive features (comments, likes), you agree to this policy and to our Terms of Service.

Data we collect

Google account information (for sign-in). To like a post or leave a comment, you sign in with Google. We receive from Google: your email address, display name, and profile picture URL. We use these only to authenticate you and to display your name and avatar next to your comment. We do not use your email for marketing or share it with third parties for their marketing.
Comments. When you post a comment, we store the comment text and associate it with your account (user id, display name, avatar URL, and email). Your name and avatar are shown publicly with your comment; your email is stored for moderation and is not shown to other visitors. You can edit or delete your own comment from the blog post page.
Likes. When you like a blog post, we record that your account liked that post (one like per user per post). We use this to show like counts and to prevent duplicate likes. We do not currently display "who liked" publicly.
Technical and preferences. We may use local storage or cookies to remember your theme preference (light/dark) and to keep you signed in during your session. Analytics (if enabled) may collect anonymized usage data; see our analytics configuration for details.

How we use your data

We use the data above solely to: (1) provide and secure sign-in and engagement features (comments, likes), (2) display comments with author name and avatar, (3) show like counts and enforce one like per user per post, (4) moderate comments and respond to abuse, and (5) improve the site (e.g. theme preference). We do not sell your personal data. We do not use your data for advertising or profiling.

Third-party services and integrations

We use the following third-party services to operate and improve this site:

Supabase. Database and authentication provider. Stores user accounts, comments, likes, and blog data. See Supabase Privacy Policy.
Google OAuth. Used for sign-in authentication. See Google Privacy Policy.
Google Search Indexing API. When a blog post is published, we notify Google to index the page faster. Only the public blog URL is submitted; no personal data is shared. See Google Privacy Policy.
IndexNow (Bing/Yandex). When a blog post is published, we notify Bing and Yandex search engines via IndexNow protocol. Only the public blog URL is submitted; no personal data is shared.
LinkedIn. When a blog post is published, it may be automatically shared on the site owner's LinkedIn profile. Only public blog information (title, excerpt, URL) is shared. Your personal data is not shared with LinkedIn. See LinkedIn Privacy Policy.
Discord (Admin notifications). The site administrator receives notifications via Discord when users interact with the blog (likes, comments). These notifications include your public display name and the action taken. Your email may be included for moderation purposes but is only visible to the site administrator. Error logs for site maintenance may also be sent to Discord but contain no personal user data.
Vercel. Hosting and serverless functions provider. See Vercel Privacy Policy.

RSS Feed

We provide an RSS feed at /feed.xml for blog content syndication. The RSS feed contains only publicly available blog information (titles, excerpts, publication dates, and URLs). No personal user data is included in the RSS feed. Third-party RSS readers may collect their own usage data according to their privacy policies.

Where your data is stored

Authentication and stored data (comments, likes) are handled by Supabase (database and auth). Sign-in is provided by Google OAuth. Supabase and Google process data according to their own privacy policies and applicable law. The site is hosted on Vercel, which may process request data according to their privacy policy.

Retention and your rights

We keep comment and like data for as long as needed to operate the site. You can delete your own comment at any time from the blog post. If you want your account data (including comments and likes linked to your account) removed or exported, contact me at the email on the home page. We will respond within a reasonable time. You may also have rights under your local law (e.g. access, rectification, erasure, portability, or objection under GDPR, CCPA, or similar regulations). We do not discriminate against users who exercise their privacy rights.

Data security

We implement appropriate technical and organizational measures to protect your personal data, including secure authentication via OAuth, encrypted data transmission (HTTPS), and access controls. However, no method of transmission over the internet is 100% secure.

Changes

We may update this privacy policy from time to time. The "Last updated" date at the top of this page will be revised when we do. Continued use of the site after changes constitutes acceptance of the updated policy.

Contact

For privacy-related questions or requests, contact me at the email on the home page.