Soft Desk
Security and privacy

Security and privacy,stated plainly.

This page describes how Soft Desk handles sessions, your Google data, AI requests and company isolation as the product is built today. Nothing here is a promise about the future, and nothing is left out because it sounds unimpressive.

How sessions work

Cookie sessions,short-lived tokens.

When you log in, the browser receives a refresh token in a cookie flagged HttpOnly, Secure and SameSite=Strict: scripts cannot read it and other sites cannot send it. The access token that actually authorises requests is short-lived and kept only in memory, never on disk.

Each refresh rotates the cookie and retires the old one. If a retired cookie is presented again, the whole session family is revoked, which is how a copied cookie is detected. "Log out everywhere" revokes every session at once.

  • Refresh token in an HttpOnly, Secure, SameSite=Strict cookie; the response body never carries it.
  • Short-lived access token held in memory only.
  • Rotation on every refresh with theft detection on reuse.
  • Log out everywhere from any device.
  • Passwords hashed with bcrypt; login rate limiting and a temporary lockout after repeated failures.
Session
Refresh cookie
Namesd_session
FlagsHttpOnly · Secure · SameSite=Strict
Readable by scriptsNo
On each refreshRotated; the old one is retired
Access token
Where it livesBrowser memory only
LifetimeShort-lived, renewed from the cookie
Stored on diskNo
A retired cookie presented again revokes the whole session family.
Your Google data

Fetched live,never copied.

Gmail, Google Calendar and Google Drive are connected through Google's own OAuth consent screen; you see exactly which permissions are requested before you agree. The tokens Google returns are encrypted at rest.

Your mail, events and files are requested from Google when you open them and shown to you. They are not copied into the Soft Desk database. Disconnecting an account removes its tokens in one click.

Soft Desk's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. The details are in the privacy policy.

  • OAuth through Google's consent screen; multiple accounts.
  • OAuth tokens and AI keys encrypted at rest.
  • Mail, events and files fetched live, not stored.
  • Disconnect in one click; revoke from Google at any time.
Connectors · Google

Gmail

Read, search, send, label

Token encryptedDisconnect

Google Calendar

Read and write events

Token encryptedDisconnect

Google Drive

Browse, upload, share, move

Token encryptedDisconnect
Mail, events and files are fetched live when you open them. They are not copied into the database.
AI without exposing people

The model gets tokens,not names.

Before any request goes to an AI provider, the names of people and clients you can see are replaced by stable tokens, and emails, phone numbers, addresses and similar identifiers are stripped. The provider's answer is translated back on your screen. Tool results are scrubbed the same way, so a task list or invoice summary reaches the model without contact details.

The assistant has no access to mailbox content or files: there are no email or Drive tools. Creating, updating or deleting anything requires your explicit approval; the model cannot execute those actions itself.

  • Names pseudonymised; emails, phones, addresses and other identifiers stripped.
  • No mailbox or file access for the assistant.
  • Bring your own key for Anthropic Claude, Google Gemini or OpenAI; no AI usage billed by us.
  • Approval gate on every modifying action; an audit trail of tool calls and approvals.
Before it reaches the AI provider
You typed

"Which tasks did Maya Ortiz finish for Northwind this week? Her email is maya@example.com."

The provider sees

"Which tasks did [[P12]] finish for [[C3]] this week? Her email is [email]."

The answer is translated back to real names on your screen only.
Company isolation

One tenantper company.

A company account gets its own tenant, and every record in it is scoped to the company. Access inside the tenant follows fixed company roles (Company Admin, HR, Manager, Team Lead, Employee) and project roles (Owner, Admin, Editor, Viewer).

Deactivating a user, or a whole company, revokes their sessions; existing tokens stop being accepted and refresh is refused.

  • Every record scoped to the company.
  • Role-based access with fixed company and project roles.
  • Session revocation on deactivation of a user or a company.
Company workspace
TenantOne company, one scope
Every recordCarries the company id
Company rolesCompany Admin · HR · Manager · Team Lead · Employee
Project rolesOwner · Admin · Editor · Viewer
Deactivate a userSessions revoked
Deactivate a companyAll sessions revoked

On the roadmap

Custom roles and a permission builder per company are not built today; roles are the fixed set above.
Operations

What runs underneath.

The controls in place on the servers and the site, without adjectives.

Request ids and logs

Every request gets an id that is returned to the client and stamped on every log line written while serving it, so an issue you report can be traced to exactly what happened.

Security headers

Responses carry standard security headers, and the site is served with a Content Security Policy.

Secrets encrypted

OAuth tokens and AI keys are encrypted at rest with a key held outside the database.

Managed Postgres

Data is stored in a managed PostgreSQL database on cloud infrastructure.

What we do not claim yet

  • No SOC 2 or ISO 27001 certification.
  • No published SLA or uptime figure.
  • No third-party penetration test report to share.

When any of these change, this page will say so.

Report a security issue

If you find a vulnerability, write to us through the contact page with steps to reproduce it. We read every report and reply by email.
Questions

Security FAQ

Soft Desk data lives in a managed PostgreSQL database on cloud infrastructure. Your Gmail messages, calendar events and Drive files stay with Google and are fetched live when you open them; they are not copied into the database.

More questions in the full FAQ.

Try it with a free account.Nothing to install.

Sign up, connect Google if you want mail and calendar inside, and read the privacy policy in full whenever you like.

No credit card required.