Privacy Policy

Effective date: 10 November 2026 (Asia/Singapore) · Last updated: 10 November 2026

This Privacy Policy describes how Tabswell (“we”, “us”) handles information in the macOS application Desk (also called Client Onboarding), available at desk.tabswell.com. Contact: cristian@tabswell.com.

For Cristian to review (legal): This draft is written for Google OAuth verification and general transparency. It is not legal advice. Have counsel review Limited Use wording, retention periods, and any Malaysia / PDPA obligations before you publish or submit to Google.

1. What Desk is

Desk is a local-first desktop app that runs on your Mac. Client records, notes, work items, invoices, synced mail metadata and bodies needed for the desk, and integration settings are stored in a database on your computer. We do not operate a Tabswell cloud that stores your desk data for everyday use.

2. Information we process

Account and profile data from sign-in providers (for example Google or Microsoft): name, email address, and profile identifiers when you connect an account.
Mail data when you connect Gmail or Outlook: messages and threads the app syncs so you can match mail to clients, draft replies, and send after approval.
Client and business data you enter: people, companies, notes, work items, invoices, and related activity.
Integration credentials you choose to connect (for example Stripe test keys, CRM keys, or AI helper keys), stored locally using the Mac keychain / OS secure storage where applicable.
Website contact: if you email cristian@tabswell.com, we receive whatever you send in that message.

3. Google user data

When you connect Gmail, Desk requests Google OAuth access with these scopes:

openid, email, profile — to identify the Google account you connect.
https://www.googleapis.com/auth/gmail.readonly — to read Gmail messages so the desk can show inbox mail, match it to clients, and help draft replies.
https://www.googleapis.com/auth/gmail.send — to send mail only after you approve a draft in the Approvals queue.

How we use Google user data

Display and organise your mail inside Desk.
Associate messages with the clients you manage.
Prepare draft replies (including with optional AI helpers you enable).
Send a message only when you explicitly approve it.

How we store Google user data

OAuth tokens are stored on your Mac using OS secure storage (keychain / Electron safeStorage). Synced mail content needed for the desk is stored in the local database on your Mac. We do not upload your Gmail content to Tabswell servers for storage.

How we share Google user data

We do not sell Google user data. We do not share Google user data with third parties for advertising or data brokerage. Optional AI helpers you enable on your Mac may process mail content you choose to involve, under the permissions you grant, to draft or summarise — they do not send mail without your approval. Outside helpers you connect with a revocable key only receive what that key is allowed to access.

Google API Services User Data Policy — Limited Use

Desk’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Confirm with counsel that product behaviour matches Limited Use (no ads, no selling, human access only for security/compliance/support with user consent or as required, etc.) before submitting verification.

4. Microsoft / Outlook data

When Microsoft sign-in is available, Desk may request mail read and send permissions comparable to Gmail, plus offline access for refresh tokens. Storage and approval rules are the same: local on your Mac, send only after Approvals.

Update this section with the final Microsoft Graph scopes once the Microsoft app registration is complete.

5. AI helpers

Desk can connect to AI tools you set up (for example Codex / ChatGPT or Grok) and ship ready-made helpers (email drafter, general assistant, analytics, notifications, reminders). Those helpers start off. When enabled, they may read desk data you permit in order to draft or summarise. Outgoing actions such as sending mail wait in Approvals. You can revoke helper keys at any time.

6. What we do not do

We do not sell your personal data or Google user data.
We do not use Google user data for advertising.
We do not train Tabswell models on your desk contents.

If a connected third-party AI provider has its own training policies, disclose that here after you confirm which providers ship in production.

7. Retention, deletion, and revocation

Disconnect an account in Connections to stop sync and remove that provider’s tokens from local secure storage.
Revoke Google access at Google Account permissions.
Delete local data by removing the Desk application data on your Mac (and uninstalling the app). Because data is local-first, deleting the app data on your machine removes the desk database we store there.
To request help with deletion or privacy questions, email cristian@tabswell.com.

Specify exact local paths / menu actions for “Delete my data” once the product exposes a one-click wipe, and any backup copies users may have made.

8. Security

Tokens and secrets are kept out of source control and are stored with OS-backed encryption where available. The Approvals queue is designed so mail send and live payment links do not run without your confirmation. No security measure is perfect; protect your Mac login and disk encryption.

9. Children

Desk is intended for business use by adults. We do not knowingly collect data from children under 16.

10. Changes

We may update this policy. The effective date above will change when we do. Material changes for Google OAuth verification will remain published at desk.tabswell.com/privacy.

11. Contact

Tabswell · cristian@tabswell.com · tabswell.com