Privacy policy

Effective date: 27 October 2026

Fromensics is operated by Zima Media OÜ, an Estonian private limited company (registry code 17241943, VAT EE102861338), doing business as Fromensics (“Fromensics,” “we,” “us,” or “our”), located at Sepapaja tn 6, Lasnamäe linnaosa, Tallinn, 15551, Harju maakond, Estonia. This Privacy Policy explains how Fromensics handles information when you use the Fromensics Chrome extension, visit fromensics.com, use api.fromensics.com (the lookup service the extension uses), or contact us. Fromensics is free. There are no accounts and nothing to buy.

Fromensics’ single purpose is local sender investigation for the Gmail or Outlook on the web message you select.

1. The short version

Fromensics investigates a Gmail or Outlook on the web message only after you choose it and click Investigate Sender. The extension reads and analyzes that message primarily on your device. Fromensics does not operate a central database of analyzed emails and does not receive the full message through the ordinary investigation flow.

Strict Local mode prevents investigation-related DNS and RDAP lookups. The extension still makes operational requests that do not contain message content, such as checking fromensics.com for signed threat-feed updates. If you enable Private Live-Check or choose Check once, the extension may send a single domain or hostname needed for a lookup. If you allow Fromensics to check a sender’s website, it sends that domain and an anonymous install id to api.fromensics.com. The extension never sends a company or person name, and never sends the email.

We do not sell personal information, use analyzed-message data for advertising, or train general-purpose AI models on your messages.

2. Scope and roles

This policy applies to Fromensics-controlled services. Gmail, Outlook on the web, Google Chrome, the Chrome Web Store, Cloudflare, Whop, DNS and RDAP providers, and other third-party services have their own privacy notices and act under their own terms.

Where applicable under data-protection law, Zima Media OÜ is the controller of personal information received by Fromensics-operated services. Information that remains solely in your browser is stored and processed locally by the extension and is not collected into a Fromensics server database.

3. Information the extension handles

A. The Gmail or Outlook message you select

After you click Investigate Sender, the extension may read the following from the open Gmail or Outlook on the web page:

If you use the optional Show original (Gmail) or View message source / View message details (Outlook) workflow, the extension may also process headers or original-message content that you explicitly paste or ask the mail provider to display. Pasted headers are kept in extension session storage for the current browser session.

Fromensics does not use the Gmail API or Microsoft Graph and does not request Google or Microsoft account OAuth in the current version.

B. On-device results and settings

The extension creates findings, scores, model outputs, and investigation summaries on your device. Local storage may include:

Fromensics keeps up to 500 investigation summaries and AI scan records. The most recently selected full message remains until another message replaces it or the extension’s data is cleared. Removing the extension or clearing its site/extension data through Chrome deletes extension-controlled local storage. Chrome-managed model files may need to be managed through Chrome.

C. On-device AI

If available and you choose to run it, Chrome’s on-device Prompt API (Gemini Nano) analyzes selected message text locally. Chrome may download and manage the model. Fromensics servers do not receive the prompt or message through this analysis path. Google or Chrome may process operational information about browser and model functionality under Google’s own policies.

The current version does not download third-party WebGPU model weights. If that changes, we will disclose the model provider, download source, size, and data flow before enabling the feature.

D. Device signing key

When you use Verified Contacts, the extension creates an Ed25519 key pair in this browser’s IndexedDB. The private key is non-extractable, never written to chrome.storage, never synced, and never sent to Fromensics. Only the public key is used in signature footers and contact cards; the 8-character key id shown in the panel is derived from it.

E. Verified contacts

Contacts you pin (email, public key, policy, last-signed date) stay on this device. Nothing is pinned automatically: a card link or a first signed email is held as pending until you confirm its fingerprint. You may optionally mirror public keys through Chrome sync. Fromensics does not operate a contact directory. Signature pages on fromensics.com/s and /c keep the payload in the URL fragment and send a Referrer-Policy: no-referrer header so the fragment is not posted to our servers.

F. Optional inbox badges

Contact badges are off by default. If you turn them on, the extension may read the visible sender address and the trailing signature footer of messages already on screen so it can draw a shield next to Investigate Sender. It does not upload those strings, does not scan your mailbox via API, and does not run on-device AI on this path.

4. Information sent off the device

A. Signed threat-feed updates

The extension includes a local threat feed and ordinarily checks https://fromensics.com/feed/ for a signed update about every 12 hours. These requests do not include message content or message-derived indicators. As with ordinary web requests, the hosting provider may receive network and HTTP information such as IP address, request time, requested file, user agent, and security logs.

B. Private Live-Check

If you explicitly enable Private Live-Check, or choose Check once for one message, the extension derives a single indicator from the selected message — a registrable domain or URL hostname — and may send that indicator for:

The ordinary lookup flow does not send the message body, subject, recipient list, email-address local part, full headers, or full private URL. The report identifies the lookups attempted. DNS and RDAP providers receive the indicator and ordinary request metadata and apply their own privacy policies. Company and person names are never sent: the report offers web-search buttons that you open yourself in a new tab.

C. Website check

When an email needs a second look, the report can offer to check the sender’s website. It runs only after you choose Check website for that site. Fromensics then remembers the site in the extension, on your device, and checks it again for later emails from the same site. You can remove a site, or all of them, in Settings.

For the check, the extension sends three things to https://api.fromensics.com, a service we run on Cloudflare Workers: the kind of lookup, the sender’s domain, and an anonymous install id. It does not send the email, its subject, or its recipients. The service fetches up to five public pages of that site (the home page, /about, /contact, /impressum, and /legal) without cookies, and returns them to the extension. The extension reads them on your device and keeps only facts such as the company name, VAT number, LEI, company number, contact domains, and redirects. The service does not store or log the pages. The sender’s site sees a request from Fromensics, not from your IP address.

The install id is random. The service creates it the first time you check a website, after a one-time Cloudflare Turnstile check on fromensics.com/install that shows a person is using Fromensics. The extension keeps the id; it is not made from your signing key and is not tied to you, your account, or your email. Turnstile processes browser and device signals under Cloudflare’s privacy policy.

To keep the service free without accounts, it counts lookups per day for each install id, for each network, and overall. Install and network counters are stored as keyed hashes. The network hash is made from your IP address and changes every day, and the IP address itself is not stored. Counter rows are deleted after about two days. Public DNS and RDAP answers may be cached for up to 14 days under hashed keys. The service’s logs hold no domains, IP addresses, or page content.

You can choose Use this browser instead. Your browser then fetches the same pages directly, after a warning that the sender’s site can see your IP address and that you opened the email. Chrome asks for permission to read that one site, and the extension gives the permission back right after the check. Nothing is remembered.

D. Pro and earlier versions

Fromensics Pro was a paid membership sold through Whop. It has ended, and Fromensics is now free. Extension versions before 0.2.0 may still send a stored license key and the extension version to https://proxy.fromensics.com to check it, and that service may pass the key to Whop, until we shut the service down. We keep records of past purchases as Estonian accounting law requires.

E. Website and support

The fromensics.com site uses Google Analytics 4 to measure visits, page views, and similar usage statistics. Google may process a client identifier stored in cookies or local storage, approximate location derived from IP address, device and browser information, referring pages, and the pages you view. This analytics runs only on the website; it is not loaded in the Chrome extension and is not applied to Gmail or Outlook message content. Google’s privacy policy describes how Google processes this information. The site also loads a Whop page pixel from t.whop.tw so we can attribute visits from Whop storefronts. That pixel is not in the Chrome extension and is not applied to Gmail or Outlook message content. You can limit analytics cookies through your browser controls. The site does not contain advertising networks. Our hosting and security providers may also process IP address, request headers, timestamps, requested pages, and security events in standard logs.

If you contact us, we receive the information you provide, such as your name, email address, message, and attachments. Do not send an unredacted email under investigation unless we specifically ask for it and you consent to our reviewing that specific content.

5. Why we use information

We use information to:

For users in the EEA, UK, or similar jurisdictions, the legal bases may include performance of a contract, your consent for optional live checks or specific support access, our legitimate interests in operating and securing the service, and compliance with legal obligations. You may withdraw consent for future live checks at any time by returning to Strict Local mode, and for future website checks by removing a site in Settings.

6. When we disclose information

We disclose information only as described in this policy:

We do not sell or rent personal information, provide it to data brokers, use it for personalized advertising, or use it to determine creditworthiness or lending eligibility.

7. Human access and AI training

Fromensics personnel do not read the content of messages analyzed by the extension because those messages are not ordinarily sent to us. If we do receive user data, humans may access it only with your explicit consent for specific data, where necessary for security or abuse investigation, to comply with law, or in aggregated and anonymized form for lawful internal operations.

We do not use Gmail or Outlook message content to train general-purpose or shared AI models. On-device output is used only for the report and local history unless you deliberately send specific content to support.

8. Retention and deletion

Local extension data remains in your Chrome profile until it reaches a record cap and older records are replaced, you overwrite it through later use, or you clear the extension data/remove the extension. DNS cache entries are used for up to 24 hours, and RDAP cache entries for up to 30 days, but expired browser records may remain physically stored until replaced or extension data is cleared.

On api.fromensics.com, daily counters are deleted after about two days and cached DNS and RDAP answers expire within 14 days. Pages read for a website check are not stored. Until the older privacy proxy is shut down, its entitlement cache records expire after approximately 30 days and its rate-limit counters after approximately two hours. Support correspondence is retained for up to 24 months after the last contact unless a longer period is required for an ongoing dispute. Transaction, tax, and accounting records are retained for seven years as required by Estonian accounting and tax law. Cloudflare and Vercel security and access logs follow those providers’ schedules, typically up to 90 days unless a security investigation requires longer. Google Analytics retains website measurement data according to the retention period configured in our Google Analytics property.

To request deletion of information held by Fromensics, contact privacy@fromensics.com. We cannot directly delete local browser data on a device we do not control; use Chrome’s extension controls for that data. Purchases and Whop account data may also require a request to Whop.

9. Security

Fromensics uses HTTPS for network transfers, validates signed feed updates, omits credentials from ordinary lookup requests, minimizes lookup payloads, accepts only the three fields a lookup needs on api.fromensics.com, refuses to fetch private network addresses, and stores counters only as keyed hashes. No system is perfectly secure, and we cannot guarantee absolute security.

10. International transfers

Our providers may process information in the European Union, the United States, and other countries. Cloudflare hosts fromensics.com, the threat feed, the api.fromensics.com lookup service, and Turnstile. Google Analytics processes website measurement data. Vercel hosts the older privacy proxy, and Upstash its hashed cache, until that proxy is shut down. Whop holds past purchase records and processes website visit attribution. Optional lookups may go to Google Public DNS, Cloudflare DNS, IANA, or RDAP.org.

Where GDPR or UK GDPR requires a transfer mechanism, we rely on the European Commission’s Standard Contractual Clauses or another approved mechanism offered by the provider, or on a transfer that is otherwise lawful.

11. Your privacy rights

Depending on where you live, you may have rights to request access, correction, deletion, portability, restriction, or objection; withdraw consent; and complain to a data-protection authority. You may also have rights to know the categories and sources of personal information, the purposes for use, and the recipients, and to opt out of sale or sharing. Fromensics does not sell or share personal information for cross-context behavioral advertising.

Send requests to privacy@fromensics.com. We may need to verify your identity. Authorized agents may submit requests where local law permits. You will not receive discriminatory treatment for exercising a privacy right.

The Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon) is Zima Media OÜ’s lead supervisory authority.

12. Children

Fromensics is not directed to children under 13, or the higher minimum age required where they live. We do not knowingly collect children’s personal information through Fromensics-operated services. Contact privacy@fromensics.com if you believe a child provided information to us.

13. Chrome Web Store Limited Use

Fromensics complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. Our detailed statement is available at fromensics.com/limited-use.

14. Changes

We may update this policy. We will change the effective date and provide additional notice in the extension when a change materially expands collection, use, or disclosure. Where law or Chrome Web Store policy requires consent, the new practice will not begin until consent is obtained.

15. Contact

Zima Media OÜ
Sepapaja tn 6, Lasnamäe linnaosa
Tallinn, 15551, Harju maakond
Estonia

Registry code 17241943 · VAT EE102861338
privacy@fromensics.com · support@fromensics.com