Your HubSpot data stays yours

Sighub reads operational metadata from HubSpot: timestamps, dates, status fields, amounts, currencies, and owner assignments. It never reads email body content, note content, call recordings, meeting notes, or ticket content.

• Portal configuration (mapped properties, renewal window, owner routing)
• Encrypted HubSpot access and refresh tokens (AES-256-GCM)
• One risk snapshot per company (company name, signal type, severity, evidence strings, value at risk, owner name, task status, timestamps)
• Temporary OAuth state records (single-use, 15-minute expiry)

Sighub does not store email bodies, notes, call recordings, meeting content, ticket content, or full contact/deal records.

Only HubSpot tasks: subject, body, status, priority, due date, owner (when available), and company association. Sighub does not modify existing Company, Contact, Deal, or Ticket records.

Required scopes

• crm.objects.companies.read
• crm.objects.contacts.read
• crm.objects.deals.read
• crm.objects.owners.read
• sales-email-read (email metadata only: timestamps, direction, status)
• tickets (status only)

Optional read scopes

Sighub also requests optional read access to line items, quotes, subscriptions, custom objects, and your HubSpot currency settings (used to convert ARR into your home currency). These let Sighub find renewal timing in more places and report value consistently. If an optional scope is not granted or not available in your HubSpot tier, that source is skipped — nothing breaks.

Writes

• Tasks (create and update, for Sighub-created tasks only)

Sighub never requests write access to Companies, Contacts, Deals, or Tickets.

The Sighub card appears in the HubSpot Company sidebar and shows:

• Status: At-risk renewal or No active risk
• Explanation: why this renewal is at risk
• Evidence: the renewal timing source (deal, line item, quote, subscription, custom object) plus any supporting activity check
• Value at risk: the account value when available
• Owner and last evaluated timestamp

Opening or refreshing the card can trigger a fresh scan of that company when task automation is active.

Manual risk controls on the card

The card also exposes four manual controls that let you override the automated decision:

• Snooze 14 days: suppresses the risk for 14 days. After expiry, the automated check resumes.
• Mark healthy 90 days: marks the account as healthy and suppresses tasks for 90 days.
• Renewed: records a successful renewal, marks the account healthy for 90 days, and completes the open Sighub task.
• Lost: records a churn outcome and permanently excludes the account from future scans. The open task is completed.

Each control can be undone from the card. See Risk controls for full behavior.

The value at risk is sourced in this order:

1. Company value: a mapped numeric property with a value > 0, plus a valid 3-letter hs_currency_code.
2. Deal fallback: Sighub checks associated deals (active first, then closed-won, then any valid deal with a positive amount).

Sighub is not real-time. Scans are triggered three ways:

• Scheduled: a background scheduler checks every 60 minutes and runs a full portal scan when the last completed scan was at least 23 hours ago.
• On open / refresh: opening the Sighub card or settings panel can trigger a scan.
• Manual: from the settings panel.

A scan lease prevents concurrent scans. If a scan is already running when another trigger fires, the new request waits or is skipped rather than running in parallel.

The only HubSpot webhook used is for app lifecycle events (e.g., uninstall).