HubSpot data access
- Each app requests HubSpot OAuth scopes required for its documented behavior.
- Scope requests are app-specific and limited to the objects required for installed app behavior (for example, DupliCat clone paths, PressKit Company profile workflows, and TabCalendar Company/Deal calendar workflows).
- Scope details are documented in DupliCat scopes, PressKit scopes, and TabCalendar scopes.
- If a requested scope does not match your policy, contact support before installing.
Storage (minimal)
- HubSpot OAuth token records (
access_token,refresh_token,expires_at) per portal, used for authenticated HubSpot API access. In OAuth mode, token records are encrypted at rest. - Stored app data varies by installed app and is limited to documented behavior:
- DupliCat: per-portal settings for clone behavior and defaults.
- PressKit: Company profile/publish metadata stored in HubSpot Company properties; uploaded files remain in HubSpot storage.
- TabCalendar: calendar config, holds, and import-related metadata for documented workflows.
- App boundaries are published in DupliCat limitations, PressKit limitations, and TabCalendar limitations.
- We do not persist full DupliCat clone payloads or copied CRM property values in our application database.
DupliCat clone data lifecycle
- When a clone is triggered, CRM record data is read from HubSpot, processed in server memory for the duration of the clone request, and written back to HubSpot as a new record.
- Property values are never written to disk, queued, cached, or included in application logs.
- After the clone response completes, all in-memory CRM data is discarded. There is no intermediate storage or retention of record property values.
- DupliCat does not provide a separate per-run customer-facing audit trail. CleverCat retains minimal operation records for support and operational review. These records contain only portal ID, object type, source record ID, cloned record ID, operation status, warning count, and configuration flags (such as deep-clone and empty-value settings). Those records exclude property names and property values.
Retention
- Active prune windows currently documented in repo: OAuth state records after 10 minutes, and ops-event records after 30 days.
- Portal-scoped app records are otherwise retained until settings change, data is offboarded, or manual cleanup runs.
- OAuth access tokens can become invalid after uninstall/revocation, and we remove stored token records as part of our support deletion workflow.
- Current DupliCat runbooks describe daily backups with 30-day retention, so deleted portal rows can remain recoverable from backups until that window expires.
- App-specific support and deletion handling is documented on Support.
Subprocessors
- Current subprocessor disclosures are published at Subprocessors.
- We update that page when introducing a new production subprocessor.
DPA and legal review
- The current standard-form DPA review draft is published at /dpa.
- Signatures, customer legal entity details, and redlines are handled manually through support.
- Privacy and subprocessor pages remain the canonical operational inputs during DPA review.
Deletion requests
- Send deletion requests to
support@clevercat.appfrom an authorized account email. - Include your HubSpot portal ID and use subject line:
Data Deletion Request. - We may ask for ownership verification before completing the request.
- After verification, we purge stored tokens, app settings, and related CleverCat app records for the portal.
- This does not delete CRM records or files stored in your HubSpot account.
- Deleted portal rows can remain recoverable from backups until the documented backup-retention window expires.
Contact
For privacy or data-handling questions, email support@clevercat.app.