We don't build a profile of you.
Here's exactly what we store, and for how long. It reads in under two minutes.
What we store
| Data | Stored? | Detail |
|---|---|---|
| Your query text | Aggregated only | Counted into an hourly bucket per query string, with no identifier attached to it. Used to see which queries are common — never to build a history for a person. |
| Your IP address | No | Not written to any table we keep. |
| An account | No | There's no sign-in. Every page works anonymously. |
| Which result you clicked | No | Result links carry rel="noreferrer", so the site you open isn't told you came from a Sarath Search results page. |
| Your theme choice | In memory only | Light/dark lasts for the session and is gone when you close the tab. Nothing is written to localStorage or a cookie. |
| Third-party ad or analytics trackers | None | There are no ad scripts, no analytics scripts, and no tracking pixels on any page here. |
Who else sees your query
To return web results at all, your query text is passed to whichever upstream search provider serves it — currently Serper, Firecrawl, or as a last resort DuckDuckGo. They receive the words you searched for. They do not receive your IP address, a cookie, or any identifier from us, because the request is made by our server, not your browser.
What we honestly can't promise yet
The search endpoints are currently public and unthrottled. That's an abuse-protection gap, not a privacy leak — no personal data is exposed by it — but it's the one thing that has to be fixed before a real public launch, and it's more useful to say so than to leave it out.
Fonts and network requests
Webfonts are loaded from Google Fonts, which means your browser makes a request to fonts.gstatic.com. That's the only third-party request any page here makes, and self-hosting the fonts to remove it is a known follow-up.
In one sentence
You can search here, click through, and switch themes without anything you do being tied to an identity.