Security

• Sign-in through HubSpot OAuth; your HubSpot two-factor settings apply. We have no passwords.
• Read-only by design: the app has no code path that writes to HubSpot, and every HubSpot permission it requests is read-only: crm.objects.tickets.read (tickets, pipelines and statuses), conversations.read (help desk conversations), crm.objects.owners.read (owner names), files.ui_hidden.read (attachment download links), crm.objects.contacts.read (notes, calls and contacts of a ticket) and, optionally, sales-email-read (logged e-mails). The only other one is HubSpot's standard oauth scope, which every connected app needs.
• Tokens encrypted at rest with AES-256-GCM; secrets live in Cloudflare's secret store, never in code.
• Archive files are stored in Cloudflare R2 only until the retention date, then deleted; download links are signed and expire after minutes.
• Message HTML is never rendered: it is converted to plain text before it goes into a PDF.
• HTTPS only, strict Content Security Policy, CSRF protection, HttpOnly/Secure/SameSite cookies, spreadsheet formula neutralisation in every CSV, SHA-256 checksums for every file in manifest.csv.
• An operator kill switch pauses all archiving. Logs contain ids and counts only. Report a vulnerability to support@atesensoftware.com (subject “SECURITY”).