Introduction and scope
This policy describes information that Saarthi, a Chrome browser assistant offered under the TOMIVA brand, may process when you use its account features, browser tools or optional integrations. Features and data flows can vary by release, account and configuration.
Information processed
Depending on the features you use, this may include account identifiers, name and email address; sign-in and session credentials; typed or spoken commands; browser tab addresses, domains and page information used for a requested action; selected images, screenshots or media details; timer and focus-session totals; and smart-home device identifiers, names, reported states or commands. Commands and captures can include personal information you choose to provide or that appears on a page.
Accounts and authentication
Version 2.1.1 includes Google sign-in through Supabase using a PKCE flow and a separate access-code sign-in. Google account information used by the extension can include an account identifier, email address and name. Google/Supabase session data, including access and refresh tokens, is kept in Chrome session storage. The access-code flow sends the code to Saarthi’s backend to validate the session and keeps it in Chrome session storage while signed in. Signing out clears these local sessions; Google sign-out also asks Supabase to end the local session. Neither action deletes your account, removes unrelated local settings, nor guarantees revocation of provider credentials.
Assistant commands and backend processing
Commands recognized as local tools, such as focus, timer, screenshot and blocker actions, are handled in the extension. Other typed or speech-recognized commands are sent over HTTPS to Saarthi’s Railway API with an authentication token; the request contains the command text and may include structured intent. The reviewed 2.1.1 request does not automatically include the active tab URL or full page text. Separate browser features can use tab or page information as described below. Depending on backend configuration, command text may be forwarded to an AI service. Project records dated 25 October 2026 report command-derived diagnostic information and HTTP request metadata in Railway application logs. Current logged fields, access controls, forwarding and retention are not established by the available production records. Do not include passwords, access codes or other secrets in a command.
Browser access and permissions
Version 2.1.1 requests Chrome permissions for storage, the side panel, downloads, alarms, tabs, notifications, identity, offscreen audio, scripting, declarative network rules and temporary active-tab access. It also declares access to Saarthi’s Railway API, Cloudflare’s speed-test service, SmartThings and Atomberg APIs, with optional access to Supabase and websites. Tab addresses are used for user-requested actions, media discovery, site controls and blocking. The blocker checks tab and navigation addresses locally; it does not maintain a general browsing history. Optional access to websites is requested for features such as Screenshot Studio. The Chrome permission prompt and extension settings control that access.
Screenshot Studio
When you request a capture, Screenshot Studio can capture the visible area, a full page, a selected area or a supported scrollable region, then let you edit or annotate it and export PNG, JPEG or PDF or copy it to the clipboard. In the reviewed 2.1.1 package, capture, editing and storage are local; the screenshot flow does not send the screenshot to Saarthi’s backend, an AI service or another provider. The local record can contain the image, preview, page title, hostname, capture mode, image dimensions, scale, whether the capture was cut short and capture time. Screenshot history is off by default: the latest capture is kept so it can be opened in the editor. If you enable history, you can choose to keep 5, 10 or 20 recent captures and delete an individual capture or all screenshots. Downloading, copying or sharing a screenshot moves it outside the extension, where the receiving app or service handles it.
Website blocking
The blocker can apply presets, custom domains, allow-only mode, focus-linked or scheduled blocking, manual blocking and temporary bypass. It stores rules and settings in Chrome storage and applies them with Chrome’s declarative network rules. To apply rules to open tabs and navigations, it checks tab addresses and domains on your device. The 2.1.1 package does not send the block list or that address-checking activity to Saarthi’s backend and does not store a general browsing history. Temporary bypasses are kept in browser session storage until they expire.
Timers and productivity statistics
Pomodoro sessions, countdowns, alarms and the stopwatch store their state and settings locally; alarms and notifications support the timers and focus tools. Completion sounds are generated and played by the extension. Focus statistics contain daily completed focus time, session counts and your daily goal; they do not include website addresses. Statistics are stored locally, days older than 90 days are removed when statistics are written, and the Focus tool lets you clear them. This 90-day cleanup applies to those statistics only, not every setting or other local information.
Voice and speech recognition
If you start voice input and allow microphone access, Saarthi uses the browser-provided SpeechRecognition interface. The recognized transcript is handled as a command. Audio processing may involve the browser or its speech-recognition provider; the provider, transmission, retention and deletion practices are not verified here. You can use typed commands instead.
Documents and media
The reviewed image-to-PDF tool processes images you select in the browser and creates a file for download; its inspected path did not upload those images to Saarthi’s backend. Saarthi’s media feature may inspect a user-requested page, send requests to the relevant website or media provider, and ask Chrome to save supported media. The website or provider receives its ordinary request information. These behaviors and any other document tools must be checked against the exact release.
Smart-home integrations
On the owner access-code flow, connecting SmartThings or Atomberg lets Saarthi send the configured provider credential directly to that provider’s API for device discovery, state checks and supported commands. The extension stores the configured credentials in Chrome local storage encrypted with AES-GCM using a key derived from the Saarthi access code. Device identifiers, names, reported states and commands are also processed to provide the feature. In this 2.1.1 package, the smart-home client sends these requests directly to SmartThings or Atomberg, not through the Saarthi backend. Disconnecting removes the saved connection from Saarthi’s local vault; it does not revoke the credential with the provider. Logging out does not itself clear that local vault.
How information is used
Information is used to provide the feature you request, authenticate access, process commands, apply your browser settings, operate connected devices, save your requested output, maintain service reliability and protect against misuse. Project records dated 25 October 2026 report command-derived diagnostic information and HTTP request metadata in Railway application logs. The current production uses and operational logging settings are not established by the available records.
Third-party services and sharing
Version 2.1.1 connects to Google and Supabase for Google sign-in; Saarthi’s Railway API for access-code validation, account/usage checks and non-local commands; and Cloudflare when you run a speed test. Project records identify Railway as the API host and report Google sign-in enabled in the production Supabase project at the time reviewed. The current deployment pairing and provider settings have not been confirmed. Depending on backend configuration, command text may be sent to the configured AI service; project records identify TypeSafe as a prior processor, but the current processor and any subprocessors are not established. When you connect a home service, your requests go directly to SmartThings or Atomberg. The browser’s speech-recognition provider may process audio. User-requested websites and media services receive the requests Saarthi makes to them. Provider-specific retention and deletion practices are not established here.
Storage, retention and deletion
Session credentials, preferences, timer state, blocker rules, focus statistics and the encrypted smart-home vault are kept in Chrome storage; screenshots and previews are kept in the extension’s local IndexedDB. Screenshot and focus controls let you delete those records as described above. The extension provides sign-out, but no in-product account-deletion control. To request account deletion, email the privacy contact below; requests are handled manually. The identity-check steps and which account records can be deleted have not been established. Handling of service logs, backups and provider-held copies is also not established. No general server retention period, complete-erasure guarantee or completion timeframe is stated.
Security
The reviewed candidates use HTTPS for service requests and include local or server-side credential protections in some flows. These source findings do not establish the safeguards configured in production or guarantee absolute security. Current operational controls and provider security practices require verification.
Your choices and privacy requests
You choose whether to use voice input, connect SmartThings or Atomberg, grant optional website access, enable screenshot history, download or copy captures, run local tools, or use the blocker. You can delete screenshots, clear focus statistics, restore blocker defaults, disconnect a home integration and sign out. Signing out clears the authentication session and requests a local Supabase sign-out, but does not delete your account or clear all other local feature data. Uninstalling Saarthi or disconnecting a provider does not itself request deletion or revocation from Saarthi’s services or that provider. To request account deletion or exercise a privacy right, email the privacy contact below; requests are handled manually. The identity-check steps, records covered (including logs, backups and provider-held copies) and time required to complete a request have not been established.
Children’s privacy
Saarthi is a general-purpose browser assistant and is not specifically directed to children. This policy does not set a minimum-age or other age-eligibility rule.
International processing
Service providers may process information in countries other than where you live. The locations used by current production services and any applicable transfer arrangements have not been verified.
Changes to this policy
This policy may be updated when Saarthi’s features, providers or data practices materially change. The effective date above identifies when this version takes effect.
Contact
For privacy questions or requests, contact saarthi.explore@gmail.com. Account deletion requests are handled manually by email; which systems and records can be deleted, identity-check steps and completion timing have not been established. TOMIVA is the product brand; this policy does not assert a registered legal entity or postal address.
Chrome Web Store Limited Use
Saarthi’s use and transfer of information received from Chrome APIs will comply with the Chrome Web Store User Data Policy, including the Limited Use requirements. This commitment covers use, transfers and human access to such information under the policy.