Privacy Policy

1. Who we are

This website (sankarayogi.com) is operated by Vamsi Krishna Sankarayogi as a personal and professional site. It publishes technology-related writing, a curated news digest backed by server-side RSS aggregation and summarization, links to public repositories and reading lists, and related informational content. This policy explains how information is handled when you use the site.

2. Scope

This policy applies to information processed in connection with use of this website and its integrated web application (including pages that call our backend API). It does not govern third-party sites (for example LinkedIn or Medium) when you leave this site; those services have their own policies.

3. Information we process

3.1 Server and technical data

Like most websites, hosting and application infrastructure may automatically process technical data when you visit, such as your IP address, approximate location derived from IP (at region/country level by infrastructure providers), browser type, request timestamps, and URLs requested. This supports security, reliability, abuse prevention, and troubleshooting.

3.2 News digest, RSS, and summarization

The home digest loads article metadata and summaries from our backend, which ingests public RSS feeds and may generate or store AI-assisted summaries to present a briefing-style experience. Processing is for display and operational purposes. We do not use this to build advertising profiles on this site.

3.3 Writing and blog content

Article listings and content shown under Writing are derived from public Medium (or similar) sources exposed through our API cache. That content is governed by the respective publishers’ terms.

3.4 Data stored in your browser (local storage)

Certain features store data only on your device:

• Bookmarked stories — story identifiers you save are kept in localStorage so “saved” views work on that browser. This is not transmitted to us as account data.
• Location lens fields — city, state/province, and country you enter (or that are filled when you choose device location) may be stored in localStorage to remember your reading filter. The site’s copy states that coarse location used for matching is not sent to our servers for that flow; optional browser geolocation and reverse geocoding may call your browser APIs and a public geocoding service from the client.
• Admin session — if an administrative area is used, a token may be held in sessionStorage for the browser session only.

3.5 Optional location

If you enable browser location, the operating system prompts you; coordinates may be converted to place labels using a third-party reverse-geocoding endpoint called directly from your browser. You can instead enter location manually or use a global lens.

4. Cookies and similar technologies

We do not rely on invasive third-party advertising cookies for core functionality. The site may use essential or functional mechanisms provided by the hosting stack, and third-party assets (for example stylesheet or icon CDNs loaded by the app) may set or read cookies according to those providers’ policies. You can control cookies through your browser settings.

5. Legal bases (where applicable)

If the EU/UK GDPR or similar laws apply, we rely on appropriate bases such as: (a) legitimate interests in operating, securing, and improving the site and digest; (b) consent where required (for example optional location); and (c) performance of any requested service.

6. Retention

Server logs and backend caches are kept only as long as needed for security, operations, and content freshness. Browser-stored data persists until you clear site data or use in-app controls where available.

7. Sharing

We use infrastructure and service providers (hosting, DNS, TLS, and similar) who process data on our behalf under appropriate terms. We do not sell your personal information. We may disclose information if required by law or to protect rights, safety, and integrity of the service.

8. International transfers

Visitors may access the site from many countries. Providers may process data in multiple jurisdictions. Where transfers require safeguards, we rely on contractual or statutory mechanisms as applicable.

9. Security

We implement reasonable technical and organizational measures appropriate to the nature of the service. No internet transmission is completely secure; use the site with that understanding.

10. Your rights

Depending on where you live, you may have rights to access, rectify, delete, restrict, or object to certain processing, and to lodge a complaint with a supervisory authority. To exercise rights related to data we control, contact us at vamsi@sankarayogi.com. We will respond within a reasonable time.

11. Children

The site is not directed at children under 16 (or the minimum age in your jurisdiction). We do not knowingly collect personal information from children for targeted purposes.

12. Changes

We may update this policy from time to time. The “Last updated” date will change; continued use after changes constitutes notice where permitted by law.

13. Contact

Questions about this policy: vamsi@sankarayogi.com

14. Editorial policy

Sankarayogi aggregates publicly available RSS feeds from publishers, preprint servers, and technology newsrooms. We do not claim independent reporting on third-party stories; the canonical version is always the outbound link to the original publisher.

Topic labels, tags, and summaries are generated automatically to organize large volumes of items. They may omit nuance or occasionally mis-rank importance; readers should rely on primary sources for decisions that matter.

We prioritize breadth of reputable sources and freshness. Inclusion of a feed or story is not an endorsement of its claims. See also our sources policy.

15. Methodology

News items are retrieved on a schedule from registered RSS feeds, deduplicated by URL, and stored in a cache with fetch and “last seen” timestamps. Archived items are retained according to backend retention rules.

Plain-text fields from each item (title, description, and extracted body where available) are passed through NLP for topics, lightweight tags, entities, and keywords used in the briefing UI and word cloud.

AI summaries are generated for many items using a local-first pipeline with an optional cloud model fallback, depending on server configuration. A summary is an aid to scanning — not a substitute for reading the publisher’s full article or paper.

Trend and programmatic pages apply transparent keyword filters over the same cached corpus so the reader can see which stories triggered inclusion.