Last updated: 1 July 2026

1. Introduction

Hub is a Chrome extension for Current RMS that enhances your workflow by injecting custom modules such as Shortages Hub, Supplier Hub, Message Hub and other workflow tools. Hub also offers paid Pro features via Lemon Squeezy.

This policy explains what information we collect, how we use it, when it is shared with third-party services, and your rights in relation to that data.

2. Data We Collect & Store

We collect and store the following information only where needed to operate Hub features.

Current RMS Subdomain & API Key

Purpose: Authenticate API requests to Current RMS for Hub features such as shortages, availability, suppliers, Message Hub and related tools.

Storage: Chrome Sync Storage (chrome.storage.sync).

Feature Toggles

Purpose: Remember which Hub modules and settings you have enabled or disabled across browser restarts.

Storage: Chrome Sync Storage (chrome.storage.sync).

Lemon Squeezy License Key & Pro Status

Purpose: Validate paid subscriptions and unlock Pro-only modules.

Storage: Chrome Local Storage (chrome.storage.local).

Device Identifier (Activation ID)

Purpose: Uniquely identify this Hub installation when creating or validating license activations and when recording extension upgrade/version telemetry.

Storage: Chrome Local Storage (chrome.storage.local).

Notes: This is a short random ID generated by Hub, for example 724A. It is not a name, email address, machine name, Chrome account ID, or Current RMS user ID.

Upgrade & Version Telemetry

What:

• Current RMS domain

• Hub extension version number

• Date and time the upgrade was detected

• Random Hub device identifier

• Whether the installation is Pro or non-Pro

Purpose: Record Hub extension upgrades, monitor version rollout, support customers, diagnose upgrade issues, and understand Pro/non-Pro upgrade coverage.

Storage and transmission: Sent to a Hub-operated Make.com webhook when Chrome reports that Hub has upgraded to a new version. This telemetry may be stored in Make.com scenario history or connected Hub records used for support and version monitoring.

Notes: Upgrade telemetry does not include your Current RMS API key, Lemon Squeezy license key, Google OAuth tokens, payment details, names, email addresses, Current RMS record contents, opportunity data, inventory data, or calendar data.

Google Account & Calendar Connection (Optional)

What:

• Google account email address used to connect Google Calendar

• Google OAuth access token and refresh token issued by Google

Purpose: Enable optional Google Calendar integration, allowing Hub to create, update, search and delete calendar events that mirror Current RMS opportunities and activities.

Storage:

• OAuth tokens: Chrome Local Storage (chrome.storage.local)

• Connected Google account email: Chrome Local Storage (chrome.storage.local)

Notes:

• Hub only accesses Google Calendar data when you explicitly connect Google Calendar and enable sync.

• Hub does not read unrelated calendar data or contacts.

• You can disconnect Google Calendar at any time, which removes stored tokens.

Product Volume Cache

What:

• productVolumeMap, a JSON mapping of product IDs to volume in cubic metres

• volumeLastRefresh, a timestamp of the last fetch

Purpose: Speed up Total Volume calculations by avoiding repeated full product catalogue fetches.

Storage: Local storage on the Current RMS domain.

Per-Session Volume Totals

What: volume_total_<opportunityId>, the last computed total volume.

Purpose: Immediately display the last total-volume calculation on popup reload.

Storage: Session storage on the Current RMS domain, cleared when the tab closes.

Message Hub Throttling

What:

• lastOpportunityId, the ID of the last opportunity shown

• lastPopupTime, the timestamp of the last popup

Purpose: Limit Message Hub auto-popups to once per hour per opportunity.

Storage: Local storage on the Current RMS domain.

3. How We Use Your Data

We use your data:

• To authenticate and fetch data from Current RMS.

• To validate your Lemon Squeezy license and unlock Pro features.

• To remember which modules and settings you have enabled.

• To improve performance with caching and session-specific calculations.

• To throttle in-app reminders so they are not disruptive.

• To provide optional Google Calendar, OpenAI, Google Maps, Google Places and Make.com automation features where enabled or used.

• To record Hub extension upgrades and support version rollout diagnostics using minimal upgrade telemetry.

Where UK GDPR applies, our likely lawful bases include performance of contract for core extension and licensing functionality, legitimate interests for support, security, diagnostics and version monitoring, and user action/permission for optional integrations such as Google Calendar.

4. Data Sharing & Third-Party Services

We do not sell your data.

We share data with third-party services only where needed to provide Hub features:

• Current RMS API: to retrieve and update Current RMS data required by enabled Hub features.

• Lemon Squeezy API: to validate paid subscriptions. We send the random device identifier with activation requests so Lemon Squeezy can track activations per device.

• Google Calendar API: used only when you explicitly enable Google Calendar Sync, to create, update, search and delete calendar events related to Current RMS opportunities and activities.

• OpenAI API: used only when you enable or use optional Hubi AI features.

• Google Maps / Google Places API: used only when postcode, address, venue or place lookup features are enabled or used.

• Make.com webhooks: used for Team Hub automation features where configured, and for Hub upgrade/version telemetry. For upgrade telemetry, Hub sends only Current RMS domain, upgrade date/time, random device identifier, Hub version and Pro status.

Lemon Squeezy handles payment processing and stores credit-card data on their servers. For details, see their Privacy Policy.

5. Data Retention

Most Hub data is stored locally in Chrome extension storage or in the Current RMS browser session.

Data sent to third-party services is retained according to the relevant service and the purpose for which it was sent. Hub upgrade/version telemetry sent to Make.com is retained only as long as needed for support, version monitoring, diagnostics and customer administration.

You can clear local Hub data at any time by:

• Using Chrome's Clear site data controls for Current RMS page local storage and session storage.

• Going to chrome://extensions -> Hub -> Details -> Storage -> Clear data.

• Uninstalling the extension, which removes stored extension data.

6. Security

• Your API keys, license keys and tokens are stored by Chrome and accessible only to this extension.

• We do not transmit your Current RMS API key or Lemon Squeezy license key to our own servers.

• Upgrade telemetry is limited to the minimum fields needed for version monitoring and support.

• Webhook URLs and third-party service credentials are treated as confidential operational data.

7. Your Rights

You have control over locally stored Hub extension data and can view, modify or delete it using Chrome's extension storage controls.

Where Hub or its processors hold data about your installation, such as licensing records or upgrade/version telemetry, you may contact us to request access, correction or deletion where applicable.

8. Changes to This Policy

We may update this policy to reflect new features, legal requirements or changes to how Hub processes data.

We will post the revised date above and link from the extension UI where appropriate.

9. Contact Us

If you have any questions or need assistance, please reach out:

Email: hub@clearsound.co.uk