Privacy Policy
Relic analyzes SEC/EDGAR filings and comparable investor documents entirely on your device. It does not collect, store on our servers, transmit, sell, or share any personal data — because there are no servers and no data collection to begin with. This policy discloses that in full.
Relic collects nothing. All analysis runs locally in your browser. There is no account, no sign-in, no telemetry, and no analytics. The only network request the extension itself makes is an optional, user-initiated fetch of a public filing from SEC.gov.
01Data the extension accesses
Described using Google's own user-data categories, stated truthfully against what the extension's manifest actually permits:
Website content
Relic reads the text of the filing you are viewing. Its content script runs automatically on SEC EDGAR pages (https://*.sec.gov/*); on any other page, it reads the document text only after you explicitly click the toolbar icon or Analyze this page, using a temporary activeTab grant for that one tab. This text is read solely to analyze it on your device — to produce summaries, sentiment, language flags, fundamentals, and redlines.
Local settings and cached results
Relic stores your preferences and caches of its own analysis output (summaries, sentiment scores, fundamentals, redlines) locally via chrome.storage, so re-opening a filing is instant. This data lives on your device and is never transmitted to us.
What Relic does not access or collect
Consistent with its manifest — which requests no permissions for any of the following — Relic does not access or collect:
- Personally identifiable information (name, address, email, phone, government IDs)
- Authentication data (passwords, credentials, tokens, cookies)
- Financial or payment account data
- Form-field entries or anything you type into web pages
- Browsing or search history, or a record of the sites you visit
- Personal communications (email, messages, chats)
- Location, health, or any special-category data
02How data is used
Relic has a single disclosed purpose: the on-device analysis of financial disclosure documents. The filing text it reads is used only to compute the summaries, sentiment, language flags, fundamentals, and year-over-year redlines shown in the side panel. It is not used for any other purpose.
03How data is processed
All processing happens entirely within your browser. Relic's machine-learning models are bundled inside the extension package and run locally — they are never downloaded from or contacted at a remote server at runtime. Where your device provides Chrome's built-in AI (Gemini Nano), Relic uses it for natural-language notes; that model is downloaded and managed by Chrome itself, on-device, not by Relic. There is no server-side processing of any kind — see the security page for how this is enforced.
04Data transmission and network egress
Relic performs no telemetry, no analytics, no error reporting to us, no account sync, and contacts no servers of ours — we operate none.
The only network request the extension itself initiates is an HTTPS GET to SEC.gov (*.sec.gov) to retrieve a prior-year public filing for the Redline tab's year-over-year comparison, and only when you request one. That request carries no personal data — it is an ordinary public request for a public SEC document. You can disable it entirely in Settings → "Fetch prior-year filings from SEC.gov"; with it off, Relic makes no network requests at all.
Your filing text and everything Relic derives from it never leave your device. This is enforced at the browser level by a Content Security Policy with default-src 'none', form-action 'none', and connect-src 'self' https://*.sec.gov — so the browser refuses any network path outside that allowlist, regardless of what the code attempts. See the security page for how this is verified.
05Data sharing
Relic shares no data with anyone. Because no personal data is collected or transmitted, there is nothing to share. Specifically, Relic does not sell, rent, or share user data with any third party, and specifically not with advertisers, data brokers, or information resellers. User data is not used for personalized or targeted advertising, and not used to determine creditworthiness or for lending purposes.
06Data retention
Your local settings and cached analyses persist on your device until you clear them (Settings → Cached analyses → Clear) or uninstall the extension, which removes them. There is no remote retention, because no data is ever transmitted to or stored on any server we control.
07Data security
On-device processing is itself the primary security control: data that never leaves your machine cannot be intercepted or breached in transit or at rest on a server. The single category of network traffic Relic can produce — public document fetches from SEC.gov — is made over HTTPS using modern transport encryption. The extension loads no remote code, which further limits its attack surface (see the security page).
08Local storage and cookies
Relic uses chrome.storage.local to store settings and analysis caches on your device, as described in §1 and §6. Relic sets no tracking cookies, uses no cross-site identifiers, and does not fingerprint your device or browser. This website (the one you are reading) likewise sets no cookies and loads no third-party trackers or analytics.
09Children's privacy
Relic is a professional research tool and is not directed to children under 13 (nor under 16 where a higher age applies). It knowingly collects no personal data from anyone, and therefore none from children. If you believe a child has somehow provided personal data through the product, contact us and we will address it — though by design there is no such data for us to hold.
10Your rights under the GDPR (EU / UK)
Where the EU or UK GDPR applies, the data controller is the developer, Raaghav Ramji. Relic processes filing text only transiently and locally on your device to provide the functionality you request and transmits no personal data to us, so we hold no personal data as a controller (the legal basis for that on-device processing being Art. 6(1)(b)/(f) — performance of the service you initiate and our legitimate interest in providing it). You keep the usual data-subject rights — access, rectification, erasure, restriction, portability, objection, and complaint to a supervisory authority — but in practice most are moot, because there is nothing on our side to access, export, or erase, and you can clear all locally stored data yourself at any time (§6). To raise any request, contact raaghav.ramji@gmail.com.
11International data transfers
There are no international transfers of your data, because processing is on-device and no personal data is transmitted to us or to any third party. The only outbound traffic Relic can generate is a user-initiated retrieval of a public document from SEC.gov; that is a request for public information, not a transfer of your personal data.
12Google Limited Use disclosure
The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
13Changes to this policy
If this policy changes, we will update the "Last updated" date above, and the revised policy will ship with the corresponding extension version and be published at this URL. We commit to proactively disclosing any change to our data-handling practices — in-product and on this page — before or when the change takes effect, consistent with the Chrome Web Store policy updates taking effect in July 2026. If a future change were ever to introduce any new collection, transmission, or sharing of data (none is planned), we would disclose it prominently rather than by a silent edit.
Not investment advice. Relic summarizes and analyzes filings for informational and research purposes only. It does not provide investment advice and does not recommend that you buy, sell, or hold any security.