Privacy Policy for the Spirah Chrome Extension

Local Storage and Default Sync

The Spirah Chrome extension stores extension settings, offline drafts, sync state, and other runtime data on the user's own device. The default save and sync endpoint is the local service http://127.0.0.1:14159/v1/captures/upsert, so under the default configuration saved session data is written to the user's own local environment first.

Analytics Are Off by Default

Spirah only sends usage analytics to PostHog if the user explicitly enables Share anonymous usage analytics. When enabled, analytics events may include a random installation identifier, a random session identifier, the extension version, event time, event name, distribution channel, and feature usage fields such as query length, result count, annotation count, failure code, and entry point.

Current analytics do not include note bodies, chat bodies, tag text, page URLs, or search keywords themselves.

Location Data Clarification

The extension does not actively call the browser geolocation API. However, the current implementation does not disable analytics-service GeoIP inference based on request IP addresses.

This means that if analytics is enabled, PostHog may derive approximate location data such as country, region, or city. Because of that, Spirah cannot claim that it collects no location-related data under the current implementation.

What Is Sent When You Save or Sync

When the user uses save or sync features, the extension processes the data directly related to that save, including the source page URL, conversation title, conversation content, annotation excerpts, notes, and tags. That data is sent to the backend endpoint configured by the user. By default, that endpoint is a local service running on the user's own device. If the user changes the setting to a custom HTTPS endpoint, the data is sent to the service specified by that user.

Support Feedback

If the user intentionally submits support feedback, Spirah sends the information entered in the form to Formspree. This may include the issue description, reproduction steps, optional contact details, links provided by the user, device/system information fields, and the current page URL. This data is sent only when the user actively submits the feedback form and is not submitted in the background automatically.

What We Do Not Use for Analytics

Spirah does not actively read precise browser geolocation, and it does not use note bodies, chat bodies, tag text, or search keywords for usage analytics.

Users can turn analytics off at any time and clear analytics-related local identifiers and any queued analytics events.