Skip to main content
Back to home

Privacy Policy

Sylva Capture Chrome Extension

Last Updated: October 25, 2026

This privacy policy describes how the Sylva Capture Chrome extension (“the Extension”) collects, uses, and protects your information. Sylva Capture is developed and operated by Sylva (“we,” “us,” or “our”).

What Sylva Capture Does

Sylva Capture is a browser extension that helps you capture content from web-based communication tools — specifically Slack, Microsoft Outlook, and general web pages — and sends that content to your personal Sylva account for search, summarization, and task management.

The Extension operates entirely at your direction. It captures content only from pages you navigate to and sources you explicitly enable.

What Data We Collect

Authentication Data

When you log in to the Extension, we collect your email address and password to authenticate with your Sylva account. Your password is sent directly to the Sylva authentication server over HTTPS and is not stored by the Extension. An authentication token is stored locally in your browser to maintain your session.

Slack Message Data

When Slack capture is enabled, the Extension reads the following from the Slack web client as you view messages:

  • Message text content
  • Sender name
  • Channel or DM name
  • Message timestamps
  • Thread context (whether a message is a thread reply)
  • Whether you were @mentioned
  • Reactions on messages

The Extension reads this information from the web page DOM — the same content already visible on your screen. It does not access Slack's APIs, your Slack credentials, or any messages you have not navigated to.

Outlook Email and Calendar Data

When Outlook capture is enabled, the Extension reads the following from the Outlook web client:

  • Email subject lines, sender, recipients, and body text
  • Email timestamps and read/unread status
  • Calendar event titles, times, and attendee lists

Like Slack capture, this information is read from the web page DOM — only content you are actively viewing. The Extension does not access Microsoft's APIs or your Outlook credentials.

Web Page Data

When you use the right-click “Send to Sylva” feature, the Extension captures:

  • Selected text or full page content (depending on your choice)
  • Page title and URL
  • Timestamp of capture

Web page capture only occurs when you explicitly trigger it via the context menu. The Extension does not automatically capture content from arbitrary web pages.

Quick Notes

When you use the Quick Note feature in the Extension popup, the text you enter is sent to your Sylva scratchpad.

What Data We Do NOT Collect

  • We do not collect your browsing history
  • We do not track which websites you visit
  • We do not capture file attachments or download files
  • We do not access your Slack or Microsoft account credentials
  • We do not read messages or emails in pages you have not navigated to
  • We do not collect analytics, telemetry, or usage statistics from the Extension
  • We do not use cookies or tracking pixels

How Your Data Is Used

All captured data is sent to your personal Sylva account and used solely for the following purposes:

  1. Search — Making your captured content searchable through Sylva's Ask Sylva feature
  2. Summarization — Generating AI-powered summaries and digests of your communications
  3. Task Extraction — Identifying action items and deadlines from your messages and emails
  4. Daily Briefings — Including relevant captures in your personalized daily briefing

Your captured data is not used for advertising, profiling, analytics, or any purpose other than powering your personal Sylva workspace.

Where Your Data Is Stored

Captured content is:

  1. Queued locally in your browser's IndexedDB storage temporarily (up to 1,000 items) before syncing
  2. Transmitted over HTTPS to your Sylva account
  3. Stored in Sylva's database, subject to Sylva's own data protection and encryption policies

The Extension does not send your data to any server other than your configured Sylva instance. Data you capture with the Extension is sent to your own Sylva account. Sylva shares it with the outside service providers listed below, only to run the Sylva feature described next to each one.

Data Sharing

We do not sell, rent or trade your captured data. Your data is sent to your own Sylva account. We share it with the outside service providers listed below, and only to run the Sylva feature described next to each one.

Sylva uses these outside service providers:

  • Anthropic (Claude) — Sylva uses Claude to generate summaries, extract tasks, and power the conversational AI features. Your content is sent to Anthropic's API.
  • OpenAI — Sylva uses OpenAI to turn your content into search vectors (this powers natural language search across your captures), to read text aloud when you use the read-aloud voice, and to sort the bug reports you send us.
  • AssemblyAI — turns your speech into text live while you record.
  • Deepgram — turns recorded meetings and voice notes into text.
  • Tavily — runs web searches when you ask Sylva to look something up online. The search words, which can include parts of your question, are sent to Tavily.
  • Jina — reads web pages Sylva cannot open directly. The page address is sent to Jina.
  • Supabase — stores your Sylva account data in its database.
  • Vercel — hosts the Sylva app and website.
  • Resend — sends email from Sylva, such as your welcome email.
  • Zoho — runs our support desk. Bug reports and support messages you send us, with your email, are stored there.
  • GitHub — holds bug-report details. Bug reports you send us, and your replies when you tell us a bug is still broken, can be posted there so our team can follow up on them.
  • Twilio — carries text messages you send to Sylva's text-message intake number. The messages pass through Twilio.
  • Stripe — handles payments and billing for paid plans.
  • Google — if you connect your Google account, Sylva exchanges data with Google for the connected feature (for example, your calendar).
  • Google Analytics — if you accept analytics cookies, it measures visits to our public pages.

If we add another provider that receives your content, we will update this page first.

Under their standard API terms, Anthropic and OpenAI do not use data sent through their APIs to train their models. Both keep API data for up to 30 days to check for misuse, and longer where the law requires or where content is flagged.

AssemblyAI's terms allow it to use some submitted audio, after removing personal information, to improve its models unless the customer opts out. Deepgram has a model improvement program under which submitted audio can be used to train its models, and a request can be excluded from it. Tavily's privacy policy says it may use parts of search queries to improve its service.

Your Controls

You have full control over what the Extension captures:

  • Source Toggles — Enable or disable Slack and Outlook capture independently
  • Channel Filtering — Whitelist or blacklist Slack channels using exact names or wildcard patterns
  • Capture Mode — Choose between automatic capture or manual “Capture Selected” mode for Outlook emails
  • Folder Filtering — Exclude specific Outlook folders from capture
  • Message Filtering — Choose whether to capture your own messages and bot messages
  • Global Pause — Pause all capture activity with one click
  • Quick Note Control — Quick notes are only sent when you explicitly click “Send”

Data Retention and Deletion

  • Local queue — Captured items are temporarily stored in your browser's IndexedDB and are cleared after successful sync to Sylva. You can clear this at any time by removing the Extension.
  • Sylva account data — Captures stored in your Sylva account are subject to Sylva's data retention policies. You can delete individual captures or export and delete all your data through Sylva's settings.
  • Authentication token — Stored in your browser's local storage and cleared when you log out of the Extension or remove it.
  • Uninstalling the Extension — Removing the Extension from Chrome deletes all locally stored data including your authentication token, settings, and any queued captures that have not yet been synced.

Security

  • All data transmission between the Extension and your Sylva account occurs over HTTPS (TLS encryption in transit)
  • Authentication tokens are stored in Chrome's extension storage, which is sandboxed and inaccessible to web pages and other extensions
  • The Extension does not inject any content into web pages — it only reads the DOM
  • Content script execution is limited to the specific domains you enable (Slack, Outlook)
  • The Extension requests only the minimum permissions necessary for its functionality

Children's Privacy

Sylva Capture is not intended for use by children under the age of 13. We do not knowingly collect personal information from children under 13.

Changes to This Policy

We may update this privacy policy from time to time. When we do, we will update the “Last Updated” date at the top of this document. Continued use of the Extension after changes constitutes acceptance of the updated policy.

Contact

If you have questions about this privacy policy or how Sylva Capture handles your data, please contact us:

Email: privacy@mysylva.app

Website: mysylva.app