Privacy Policy

Last updated: March 2026

Our Commitment

ORIC Labs ("we", "us", "our") is committed to protecting your privacy. This policy describes what data our extensions and services collect, how it is used, and your rights regarding that data.

Open Source

All extensions are open source. You can inspect exactly what data is accessed in the source code.

No Data Sales

We do not sell, share, or monetize any user data. Your data is never provided to third-party advertisers.

No Tracking

No analytics, telemetry, or tracking scripts are included unless explicitly noted per extension.

Local First

Data stays on your device unless a feature explicitly requires network access, which is always documented.

1 Information We Collect

Our extensions are designed with a privacy-first approach. The specific data accessed varies by extension and is detailed in the per-extension sections below. In general:

  • We do not collect personal information (name, email, address) through our extensions.
  • We do not access browsing history beyond what is required for the extension's stated functionality.
  • Any data processed is stored locally in your browser using standard browser storage APIs (localStorage, IndexedDB).
  • If an extension requires network requests, only the minimum necessary data is transmitted, and this is documented below.

2 How We Use Information

Any data accessed by our extensions is used solely to provide the extension's core functionality. We do not use your data for:

  • Advertising or ad targeting
  • User profiling or behavioral analysis
  • Sale or transfer to third parties
  • Any purpose unrelated to the extension's functionality

3 Data Storage & Security

All data is stored locally on your device using your browser's built-in storage mechanisms. We do not operate external servers that store user data. Your data is protected by your browser's security model and your device's own security.

When you uninstall an extension, all locally stored data associated with it is removed by the browser.

4 Your Rights

You have full control over your data:

  • Access: All data is stored locally and accessible through your browser's developer tools.
  • Delete: Clear extension data at any time through your browser settings, or uninstall the extension entirely.
  • Portability: Since data is stored locally, it is inherently under your control.
  • Inspect: All extensions are open source. Review the code on GitHub to verify our claims.

5 Third-Party Services

Some extensions may interact with third-party APIs to provide functionality (e.g., querying biological databases). In these cases:

  • Only the minimum data required for the query is sent (e.g., search terms).
  • No personal identifiers are included in API requests.
  • Third-party services are governed by their own privacy policies.
  • Which extensions use third-party services is documented in the extension-specific sections below.

6 Children's Privacy

Our extensions do not knowingly collect any personal information from children under 13. Since our extensions do not collect personal information from any users, they are safe for use by all ages.

7 Changes to This Policy

We may update this privacy policy from time to time. Changes will be reflected on this page with an updated "Last updated" date. Significant changes will be communicated through our GitHub repositories.

Extension-Specific Details

ibid

Browser extension (Chrome, Edge, Firefox) & Web App

What data is accessed

  • Page content on the active tab (to extract citations and references)
  • Page URL and title (to associate citations with their source)

How data is stored

  • All extracted data is stored locally in your browser's storage (localStorage / IndexedDB)
  • No data is transmitted to external servers

Permissions required

  • activeTab — to read the current page's content when you activate the extension
  • storage — to save your citations and preferences locally
No remote data collection No tracking Local storage only

biopeek

biolang extension (Chrome, Edge, Firefox)

What data is accessed

  • Biological data structures on the current page for inspection and preview

How data is stored

  • Data is processed in-memory only; nothing is persisted or stored
  • No data is transmitted to external servers

Permissions required

  • activeTab — to read biological data on the current page
No data collection No storage No network requests

biogist

biolang extension (Chrome, Edge, Firefox)

What data is accessed

  • Page content and selected text for summarization and gist extraction
  • Document metadata (title, author) when available

How data is stored

  • Summaries are processed locally and may be saved to browser local storage
  • No document content is sent to external servers

Permissions required

  • activeTab — to read page content for summarization
  • storage — to save generated summaries locally
No remote data collection No tracking Local storage only

biokhoj

biolang extension (Chrome, Edge, Firefox)

What data is accessed

  • Search queries you enter into the biokhoj search interface
  • Selected text on pages when using the "search this" feature

How data is stored

  • Search history is stored locally in browser storage
  • Search results are cached locally for performance

Network requests

  • Search queries are sent to external biological databases (e.g., NCBI, UniProt) to fetch results
  • Only the search term is transmitted — no personal identifiers, cookies, or browser fingerprints
  • These third-party databases have their own privacy policies

Permissions required

  • activeTab — to read selected text for search
  • storage — to save search history and cache results
  • host permissions — to query biological database APIs
Search queries sent externally No personal data transmitted No tracking

Contact Us

If you have questions about this privacy policy or our data practices, you can reach us through:

GitHub Issues