Security Overview

Authentication

Passwords are strongly hashed and sessions use opaque secrets stored only as hashes. Supported provider authorization happens on the provider’s domain; Privly does not store provider passwords.

Account and workspace isolation

Protected records are checked against the active workspace and role. Least-privilege access limits who can read or change workspace data.

Provider connections

• Credentials and tokens stay out of browser responses.
• Provider webhooks are authenticated and validated.
• Connecting an account does not itself send a message.
• Delivery is limited to an explicit reviewed action and protected by idempotency controls.
• Work-email lookups require an authorized user request; Findymail receives the selected lead’s profile URL for that lookup.
• HubSpot uses provider-hosted authorization. Stored CRM access and refresh tokens are encrypted, and each connection is scoped to a workspace. Connecting alone does not export contacts.
• Background CRM exports recheck workspace permissions and the connected destination. Saved export records support duplicate prevention and recovery without ongoing two-way synchronization.

Secrets and data protection

Application keys and provider secrets live in server-side environment variables. Privly uses encrypted transport, constrained permissions, bounded provider requests, safe public errors, and audit records for important actions.

Logging and monitoring

Operational logs and metrics support reliability, diagnosis, and abuse detection. Access is restricted and retention is limited to operational and legal needs.

Report a concern

Email [email protected] with enough detail to reproduce the issue. Do not include passwords, raw tokens, or unrelated personal data.