Extension Privacy Policy

Effective date: November 3, 2026

Scope and contact

This policy describes how the GoBessa Chrome extension handles information. GoBessa is the product and public publisher name. Contact hello@gobessa.com with privacy questions or requests. This policy does not govern retailers’ websites or your email provider.

Information kept on your device

The extension reads product links, titles and image references on supported retail pages to provide the selections you request. Selected product identifiers, URLs, titles, image references, selection order, the source-page URL and selection-mode settings are stored in Chrome session storage. The supported page URL is used to highlight the current item. GoBessa does not build a general browsing-history log or upload these product details to its analytics server.

Local storage and deletion

Session data remains available during navigation and page refreshes. Chrome clears extension session storage when the browser restarts or the extension is reloaded, updated or disabled. Remove deletes an individual selection; Clear Queue removes saved selections and the source page. GoBessa does not provide account-based storage or cloud synchronization. The extension stores the optional usage-sharing preference and its latest random daily identifier in Chrome local storage.

Optional usage reporting

Usage sharing is off by default. If you explicitly enable it and grant the optional gobessa.com permission, the extension sends limited usage events to https://gobessa.com/api/telemetry to measure and improve its operation. Each event contains an event ID, UTC date, random daily identifier, random session identifier, retailer code, action type and extension version. Action types represent selection additions, navigation and selection-mode interactions. These events do not include product URLs, product identifiers, titles, images, search terms, shopping-bag contents, credentials, payment details or general browsing histories.

Identifiers, retention and controls

Daily identifiers change on activity in a new UTC day. Session identifiers change after 30 minutes without a measured action, at UTC day rollover or when the browser session ends. The server hashes the event, daily and session identifiers before storing them. Event records are retained for approximately 90 days, using UTC-day boundaries, and removed during server maintenance. They contain the UTC day rather than precise event timestamps. These identifiers are pseudonymous; they are not a guarantee of anonymity or a count of identifiable people. Turn usage sharing off in the side panel to stop future reports, discard pending reports and remove local telemetry identifiers. Requests already received may remain until their retention period expires. Disabling reporting does not disable the extension’s shopping functionality.

Network information and service providers

The extension does not include raw IP addresses or user-agent strings in its analytics payload, and the analytics database does not store those fields. Network services necessarily process an IP address and ordinary connection information when receiving requests. GoBessa uses Amazon Web Services to host its first-party endpoint. The application does not log telemetry request bodies, and the GoBessa Apache virtual host is configured without access logging. This does not mean all infrastructure security or operational records are eliminated.

Retailer connections

Displaying product thumbnails sends ordinary image requests directly to retailer image hosts. Opening a saved product or source page navigates directly to that retailer. Retailers and their service providers receive normal network information and any cookies permitted by your browser. Side-panel images are requested without a referrer. Retailers’ own policies apply to their services.

Website analytics and store reports

The extension does not embed Google Analytics. Website analytics is a separate choice: on website pages that offer it, Google Analytics loads only after website consent, and that choice does not enable extension usage sharing. The pre-launch holding page does not load analytics scripts. GoBessa may read aggregate website reports from Google Analytics and import aggregate installation and uninstallation reports supplied by Chrome Web Store. Those reports do not provide GoBessa with your product selections or identify an installation from a website click.

Permitted uses and sharing

GoBessa uses locally handled information to deliver requested extension features and optional usage reports to measure and improve those features. Data is not sold, used for personalized advertising, shared with data brokers, used for credit or lending decisions, or linked to a named shopping account. Hosting providers process information as needed to operate the service. Support messages are processed by GoBessa and its email provider to respond to inquiries. Information may also be disclosed where legally required or necessary to address security incidents. GoBessa’s use and transfer of user data complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.

Support and privacy requests

If you email us, we receive the contact details and information you choose to send. Do not send passwords, payment details or unnecessary personal information. We keep correspondence only as needed to handle the inquiry and meet applicable obligations. Contact hello@gobessa.com to ask about access, correction or deletion of information we can identify, or to raise a privacy concern. Rotating identifiers mean we may be unable to match historical usage events to a particular person. We do not ask you to provide additional sensitive information merely to identify usage counts.

Changes

We will update this page when these practices change. Material changes to collection or use will also be disclosed in the extension as appropriate, with renewed consent where required.