Security and data handling

LinqDesk holds mailbox credentials and client data, so this page sets out plainly how both are protected.

Credentials

Gmail refresh tokens and SMTP passwords are encrypted at rest using AES-256-GCM with a key held only in the server environment, never in the database. Disconnecting a mailbox deletes the stored credential immediately.

Mailbox access is narrow by design

LinqDesk requests permission to send mail and to read replies in threads it started. It never indexes your inbox, never stores message bodies beyond detecting a reply or bounce, and never exposes mailbox contents to other workspaces or to third-party providers.

Isolation between customers

Every record carries a workspace identifier, and every query is scoped to the authenticated workspace. Team member logins are scoped to their own workspace and cannot change workspace settings, billing or mailboxes.

Authentication

Passwords are hashed with bcrypt. Sessions use signed, HTTP-only cookies with a 30 day lifetime. Sign-in and sign-up endpoints are rate limited per IP address.

Sending safeguards

Per-mailbox daily caps, a fixed sending window, weekday-only defaults, automatic bounce handling and a permanent do-not-contact list all exist to keep sending volume low and reputable. Sequences stop the moment a human replies.

Payments

Subscriptions run through Dodo Payments. Card details never reach LinqDesk servers. Webhook events are verified with an HMAC signature and a timestamp window before any plan change is applied.

Reporting an issue

If you believe you have found a security problem, email security@linqdesk.com with the details. We will acknowledge within two business days.