Privacy Policy

1. Your local library

When you save a highlight, Strata stores the selected text, your optional note, the source page’s title and URL, and creation and update dates. It also stores text positions and small amounts of surrounding text to restore the highlight. If you enable access to local files, their URLs may contain local file paths.

Strata processes webpage text and URLs to show its selection tools, restore highlights, and open saved passages. It does not maintain a general browsing-history log or track keystrokes, mouse movements, or browsing activity for advertising or analytics.

Your library and its pending sync changes, notebook setup state, browser identifier, progress cursors, and retry information are encrypted in extension-owned localStorage in your Chrome profile. Without a Notion connection, highlights and changes remain local to that profile; signing into Chrome alone does not sync them.

2. Optional Notion connection and sync between browsers

Connecting Notion is optional. Review the access explanation in Strata’s library before authorization, then explicitly choose an existing Strata notebook or create one. Choosing an existing supported notebook restores its readable passages into this profile. Connect another Chrome installation to the same notebook to share subsequent changes. A connection to a different notebook does not share that collection.

While connected and Chrome is running, Strata periodically reads changes from the notebook, sends pending local changes, and records completed changes in a child page named “Strata sync log.” Offline changes wait for connectivity. Newer update timestamps decide competing note edits. Reconnecting an initialized profile resumes sync without repeating its initial notebook restore. Direct edits made inside Notion are not an ongoing editing channel back into Strata; edit notes in Strata for them to sync between browsers.

• Content sent to Notion: saved web passages, notes, source URLs, page titles, creation/update dates, record identifiers, and highlight placement information, including text positions and surrounding text in saved links. Local-file highlights and their file paths are excluded from Notion sync.
• Content read from Notion: notebook search results, workspace and page details, supported saved passages and notes, source URLs, titles, dates, placement information, page/block identifiers, and sync-log entries. These support initial restore, ongoing sync, and targeted recovery. Unreadable passages are reported.
• Sync metadata: the notebook’s sync log contains a randomly generated browser/profile identifier, sequence numbers, dates, change types (add, note, or delete), record identifiers, and article-page identifiers. It does not contain note or passage text. Strata retains local cursors and pending changes to track delivery.
• Authorization data: OAuth client registration, access and refresh tokens, expiry information, and account/workspace identifiers returned by Notion are stored encrypted in extension-owned Chrome storage restricted to trusted extension contexts. Strata does not receive your Notion password.
• Connection verification: Notion may return basic account details such as a name or email address, workspace details, and tool capabilities. Strata uses these to verify and label the connection.

Strata connects directly to Notion’s hosted MCP service over HTTPS; requests do not pass through a Strata server. Notion also receives network information such as your IP address.

Notion authorization may provide access to content beyond the Strata notebook within your account’s permissions. Review Notion’s consent screen. People with access to your notebook may see its passages, notes, saved links, and sync metadata. Their visibility and Notion’s retention are governed by your workspace/sharing settings and Notion’s privacy policy.

3. How data is used and shared

Strata uses this data to save and restore highlights, display and search your library, edit notes, open source passages, and provide optional notebook restore and sync between your browsers.

Saved-highlight links contain the source URL and a fragment with a record identifier, text position, creation/update timestamps, and nearby prefix/suffix text. They do not contain your note or credentials. Copying or sharing a link shares all information encoded in it, including surrounding text and any information in the original source URL. Opening the source contacts that website normally. Resolving a saved highlight requires Strata and the corresponding local record, which can arrive through the shared notebook; otherwise the page opens without Strata’s saved highlight.

Strata does not sell or rent user data, serve advertisements, run analytics or behavioral telemetry, or transfer your reading collection to a developer-operated server. Its sync code makes predetermined tool calls and does not itself run an AI model.

Limited Use: Strata’s use and transfer of information received through Chrome APIs adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements. Data is used only for the described reading and annotation features, not advertising, unrelated purposes, creditworthiness, or lending. Transfers to Notion provide the optional connection you enable.

4. Retention and your controls

• Review, edit, or delete: use Strata’s library to view passages, edit notes, or remove highlights. For a synced highlight, deletion is queued to remove its managed passage in Notion and notify other connected browsers. Delivery requires a working connection and Chrome running; offline copies can remain until they sync.
• Disconnect Notion: disconnect in Strata to stop sync and clear its stored access and refresh tokens. Your local library stays on the device. Client registration and connection/sync metadata may remain for reconnection. Disconnecting does not delete the notebook or stop other connected browsers. Revoke the connection in Notion to remove the authorization grant there.
• Remove local data: uninstalling Strata removes its extension-owned data from that profile. It does not delete your Notion notebook or other browsers’ local copies. The developer holds no server copy. A new profile can restore supported passages still present in an accessible notebook.
• Manage Notion copies: manage notebook sharing, trash, and retained content in Notion. Direct deletion inside Notion does not guarantee deletion from Strata libraries. To propagate a supported deletion, delete the highlight in Strata while connected. Content outside Strata’s managed passages is preserved.

Local records and pending changes normally remain until you delete them or remove extension data. Sync-log entries older than 30 days are eligible for pruning during sync, but the latest entry from each browser is retained to detect missed changes. A browser that misses pruned entries re-reads the notebook without deleting local records, so a long-offline browser may retain a deleted highlight. Notion backups, history, trash, and independently copied/shared content follow Notion’s rules and recipients’ actions.

Version 2 upgrade: version 2 uses a new library and notebook format. It removes the earlier version 1 local library when first read and does not migrate it. Earlier notebook formats are not supported for restoration. Preserve any older collection you need before upgrading; remote copies are subject to Notion’s retention and your actions there.

5. Storage and security

Strata isolates stored records from webpages and restricts connection administration to extension contexts. It encrypts its local library, pending sync state, and Notion credential store with AES-256-GCM. Each profile has a locally generated key in extension-owned IndexedDB, non-extractable through the Web Crypto API. This allows restoration after restart without a password prompt.

This local encryption is not end-to-end encryption of the notebook: Notion receives readable passages, notes, links, and sync metadata. Each browser encrypts its own local copy with its own key; local keys are not synced through Notion.

If supported stored data cannot be decrypted or a supported plaintext-to-encrypted write fails, Strata preserves it and reports an error. This does not provide migration for the retired version 1 library described above. Encryption does not erase previous disk blocks or backups.

Someone controlling your full Chrome profile, extension runtime, or device may still access data. If the local key is lost, the developer cannot recover encrypted local records. A failed or interrupted Notion verification keeps sync paused until successful verification. No storage or transmission method guarantees absolute security.

6. Questions and policy changes

For privacy questions, contact daqo@hey.com. Manage local data in Strata and notebook content in Notion.

When data practices change, this policy will receive a new effective date. Material changes will be disclosed through the extension or Store listing, with additional consent where required.