Rudra Recall · Chrome extension
Privacy Policy
Summary: Rudra Recall is local-first. Saved memories, notes, screenshots, media, and related local data stay in your browser's IndexedDB storage. Core use needs no AI, account, cloud sync, or server. The optional sponsor footer is separate and may use anonymous metadata.
1. Who we are
Rudra Recall (“the extension”, “we”, “us”) is a Chrome browser extension operated by Rakesh Raja. This policy explains what the extension accesses, what it stores locally, and what may leave the browser when the optional sponsor footer is enabled.
Contact: me@rakesh.in · rakesh.in · Product page: Rudra Recall overview
2. What Rudra Recall does
Rudra Recall is a local-first browser second brain. You can save webpages, selected text, images, videos, links, screenshots, notes, and files or text dropped into the extension. The library includes Inbox, All items, Collections, Trash, tags, bulk moves, and deterministic domain/URL auto-file rules. Search can cover titles, URLs, domains, notes, descriptions, and tags. A contextual badge and “On this page” view can show related memories for a page when you invoke that page-context action.
Rudra Recall does not use AI for its core workflow. An account, cloud sync, and server are not required to capture, organize, search, or recall your local memories.
3. What is stored locally
Saved memories and their local metadata are stored in IndexedDB inside your browser's extension profile. This can include the content you choose to save, such as selected text, notes, screenshots, image or video references, dropped files or text, titles, descriptions, tags, collection placement, URLs, and domains.
Local extension preferences and optional sponsor-footer state may also use Chrome's extension storage. These local stores are not a cloud backup and are not readable by this website as part of the core product.
4. When the extension accesses a page
Page access is on demand. Rudra Recall reads the active page or selected page data only when you invoke a save, screenshot, context-menu capture, or “On this page” related-memory action. It is not intended to continuously collect the pages you browse.
The extension does not send saved page content, saved notes, screenshots, media, or page URLs to a Rudra Recall server for core use. If a page cannot be accessed because Chrome restricts it, the corresponding action will not run.
5. Optional sponsor footer
Rudra Recall may include an optional sponsor footer inside the extension panel. If that feature is enabled, it may request an ad or sponsor feed and send anonymous metadata needed to serve and measure that footer: an anonymous install identifier, slot identifier, ad identifier, event type, and country metadata.
The sponsor-footer request is separate from the local memory library. It does not include saved page content, selected text, note text, screenshots, images, videos, dropped files, or page URLs. Sponsor-feed providers may process that anonymous metadata under their own terms and retention practices. You can ask about the currently used sponsor service at me@rakesh.in.
6. Permissions we request
- activeTab — access the current tab after you invoke a capture or page-context action.
- tabs — identify the relevant tab and read tab metadata needed to label and relate saved items.
- storage — store extension preferences and optional sponsor-footer state locally.
- contextMenus — provide save actions for selected text, links, images, and other supported page targets.
- sidePanel — show the Rudra Recall library and capture workflow beside the current page.
- unlimitedStorage — allow the local IndexedDB library to grow beyond the browser's default extension quota.
These permissions support explicit user actions. They do not turn the extension into a background archive of every page you visit.
7. Restricted pages
Chrome does not permit extensions to use normal page access on some restricted locations, including chrome://
pages, the Chrome Web Store, extension pages, and other privileged browser surfaces. Rudra Recall may also be unable to
capture content from a page when the browser or the page prevents access. This is a Chrome security limitation, not a
transfer of that content to us.
8. What we do not do
- We do not require an account for core use.
- We do not require a server, cloud sync service, or AI provider for core use.
- We do not sell the contents of your local memory library.
- We do not use saved page content or URLs for the optional sponsor footer metadata.
- We do not inject sponsor content into the websites you visit; it appears only in the extension panel.
9. Retention and deletion
Local memories remain in IndexedDB until you move them to Trash, permanently delete them, empty Trash, clear the extension's local data, or uninstall the extension. Rudra Recall does not keep a remote copy for core use, so deleting local data cannot be recovered from a Rudra Recall server.
Optional sponsor-footer metadata is separate from the local library and may be retained by the relevant sponsor-feed provider under its own policy. Contact me@rakesh.in if you need help identifying the current provider or understanding a sponsor event.
10. Children’s privacy
Rudra Recall is not directed at children under 13 (or the minimum age required in your country). Do not use the extension to save another person's information without a lawful reason to do so.
11. International users
Rudra Recall is operated from India. Core memory data stays in the browser profile where you use the extension. If you enable the optional sponsor footer, its anonymous metadata may be processed by the relevant sponsor-feed service in other regions under that service's terms.
12. Changes to this policy
We may update this page when Rudra Recall's storage, permissions, or optional sponsor footer changes. The “Last updated” date at the top will change when we do.
13. Contact
Questions about this policy or Rudra Recall's data practices: me@rakesh.in · Rudra Recall product page