Privacy Policy – Layr HubSpot Sender Guardrail (Chrome Extension)

Summary
The Layr HubSpot Sender Guardrail Chrome extension (“Extension”) helps ensure the correct sender address is selected in HubSpot email compose dialogs by reading the page’s DOM to identify the active pipeline and disabling Send until the appropriate From address is chosen. It is intended for use by our internal Service Team.

What data we access and why

• Page content on HubSpot pages only (e.g., *.hubspot.com): The Extension reads specific elements of the HubSpot email compose UI (e.g., pipeline indicator, From dropdown state) solely to determine whether the selected sender address matches internal rules. This processing happens locally in the browser to enforce the “correct sender” requirement. We do not use this data for any other purpose.
• No email bodies or recipients are transmitted off the device by the Extension.
• No personal data is collected for analytics or ads.

If your build actually sends anything to a server (logs, telemetry, error reports, etc.), tell me and I’ll add that precisely. For now, this text assumes local‑only processing.

Permissions used

• scripting / activeTab (or tabs): To run content scripts that inspect the HubSpot compose dialog and enforce the correct sender selection.
• storage (if used): To save local‑only settings (e.g., which pipeline maps to which sender address).
• Host permissions for HubSpot domains (e.g., https://app.hubspot.com/*): To run on relevant pages only.

Replace the list above with the exact entries from your manifest.json. Google expects your policy to match the permissions you request.

Data collection, sharing, and retention

• Collection: The Extension does not collect or store personal data beyond ephemeral, in‑memory evaluation of the HubSpot DOM necessary to enforce the sender rule.
• Transmission: No data is transmitted to Layr or third parties by the Extension.
• Sharing: No data is shared with third parties.
• Retention: No server‑side retention because no data leaves the browser. If the Extension uses chrome.storage, values are limited to configuration (not user content) and remain on the user’s device until the extension is removed or settings are cleared.

Security

• The Extension runs client‑side in the user’s browser. Any administrative endpoints (if introduced later) will enforce HTTPS and access controls. (If you start sending data, we will update this section accordingly.) Google requires secure handling of any personal/sensitive data.

User controls

• Users can disable or remove the Extension from Chrome unless the organization enforces it via enterprise policy (see below).
• The Extension displays an on‑page warning/disable‑send behavior only inside HubSpot compose dialogs; it does not modify pages outside HubSpot.

Contact

Questions about this Extension’s privacy practices: itsupport@layrins.com