Tab-audio path
Page media detection, tab capture, equalization, dynamics processing, limiting, metering, and playback run inside Chrome or Edge. Captured tab audio is not uploaded to Hearably.
SECURITY & DEPLOYMENT
Inspect the boundary before you deploy
This page documents the repository candidate manifest (version 1.3.4, reviewed August 28, 2026). Chrome Web Store submission, review, approval, and public availability are separate release states; procurement must verify the exact store package and version it deploys.
CURRENT PRODUCT BOUNDARY
What is local, and what uses the network
Account and billing path
Authentication, cloud presets, referral links, subscription status, checkout creation, and support use api.hearably.app. PayPal hosts approval and payment processing.
Live captions
The repository contains work in progress, but the current release flag keeps live captions unavailable. This page does not promise model downloads, transcription, translation, SSO, an SLA, or an on-premise deployment.
Web pageaudio/video elements
→ User actionselect tab + enable
→ Local DSPoffscreen Web Audio
→ Outputbrowser audio element
Separate network flow: extension or website → HTTPS API → account/preset/entitlement records; checkout → PayPal approval → signed webhook → idempotent reconciliation → entitlement.
MANIFEST REVIEW
Permission matrix
Chrome gives tabCapture a broad user-facing warning. Administrators should judge the effective behavior from both the warning and the package code. The content script is declared on <all_urls> and all frames so it can detect media wherever it appears; its current logic queries audio/video elements rather than page text or form fields.
| Capability | Current use | Data boundary |
|---|---|---|
tabCapture | Starts capture only after a user action and routes the selected tab audio into the local Web Audio DSP. | Captured audio stays in the extension audio graph. |
offscreen | Keeps the Manifest V3 DSP graph alive outside the popup. | No separate data category; it hosts local processing. |
storage | Stores settings, presets, authentication state, subscription state, transient capture state, and reads administrator-owned managed policy. | Cloud sync happens only through authenticated API features; managed policy is not sent to Hearably. |
tabs | Reads tab ID, URL, title, favicon, and audible state for capture eligibility and the local mixer. | Current extension code does not send these tab fields to Hearably. |
activeTab | Provides temporary access to the focused tab after user interaction. | Scoped by the browser to the user-invoked tab. |
alarms | Runs health and state-reconciliation tasks. | No data transmission is required by the permission itself. |
contextMenus | Adds a user-invoked Enhance with Hearably action. | Uses the clicked tab locally to start enhancement. |
sidePanel | Shows Hearably controls in the browser side panel. | No additional data access is granted by the panel itself. |
Output-device labels: when a user asks to list audio outputs, the browser may request microphone permission to reveal device labels. Hearably immediately stops that temporary stream; it is not connected to the DSP, recorded, or uploaded.
EVIDENCE STATUS
Controls we can substantiate today
Implemented
- Manifest V3 and a self-only extension script policy
- Administrator-enforced managed configuration in candidate 1.3.4
- HTTPS API and provider-managed secrets
- Schema-validated inputs and trusted-origin checkout gate
- Signed, idempotent billing-webhook ledger
- Checkout-to-entitlement reconciliation report
- Reproducible look-ahead limiter regression benchmark
Requires customer review
- Exact Chrome/Edge package and permission warning
- Compatibility with protected media and conferencing policy
- Identity, endpoint, logging, and data-retention requirements
- Accessibility and hearing-safety fit for the intended population
- Legal basis and procurement terms
Not claimed
- SOC 2 or ISO 27001 certification
- Independent penetration-test report
- SSO/SCIM or on-premise deployment
- Guaranteed data residency
- Medical-device or WCAG/ADA compliance certification
- Commercial SLA without a signed agreement
MANAGED CONFIGURATION
Policy that changes product behavior
Candidate 1.3.4 declares a Chrome managed-storage schema. The service worker enforces capture, domain, boost, output-device, checkout and uninstall-feedback controls at their action boundaries; the popup suppresses cloud flows before loading them. An absent policy preserves normal consumer behavior.
| Policy | Enforced result |
|---|---|
CaptureEnabled | Blocks new capture and stops active capture when false. |
AllowedDomains | Allows only listed hosts and their subdomains when the list is non-empty. |
MaxBoostPercent | Caps the service-worker DSP value from 100–800%; plan limits may be lower. |
CloudFeaturesEnabled | Suppresses sign-in, cloud presets, community and referral network flows when false. |
CheckoutEnabled | Hides and blocks subscription checkout from the extension when false. |
OutputDeviceSelectionEnabled | Blocks device enumeration and output-routing changes when false. |
FeedbackLinksEnabled | Clears the uninstall URL and hides review/referral prompts when false. |
A schema and passing unit tests are candidate evidence, not proof of customer-fleet deployment. Verify policy readback and behavior on the exact managed browser, package and device image.
CONTROLLED ROLLOUT
Two-week pilot with a real rollback
- Review: record the store version, package source, requested permissions, target URLs, user group, and owner.
- Canary: deploy to 5–25 consenting users or a test organizational unit. Do not force-install fleet-wide first.
- Validate: test enable/disable, native-audio restoration, fullscreen/navigation recovery, meetings, protected media, CPU, memory, support and billing entitlement.
- Accept: expand only if the written compatibility, privacy, performance, and support thresholds pass.
- Rollback: remove the extension from the force-install policy or set its installation mode to blocked, reload policy, verify removal, and confirm native audio on representative devices.
Google recommends first applying extension policy to a small test organizational unit and checking chrome://policy. Microsoft Edge supports force-install and removal through its extension policies. Follow your browser vendor's current documentation and change-management process.
PROCUREMENT
Request the review pack
Ask for the versioned permissions matrix, data-flow document, deployment runbook, security questionnaire, and pilot acceptance sheet. Answers reflect the current candidate and are not certifications.
[email protected]