How Tooling Studio handles your data

Where your data is stored

The Tooling Studio application runs on Google Cloud. We use a PostgreSQL database on Google Cloud SQL for structured product data. Files that you upload are stored separately in Google Cloud Storage. These production services use the Warsaw region, europe-central2.

The public website is hosted by DigitalOcean in Frankfurt, Germany. Website content is part of the website itself. The website does not keep its own database of form submissions: newsletter sign-ups go to Zoho Campaigns, and other website forms, such as ebook and partner requests, are sent to our team in Google Chat. Other services support payments, communications, analytics, and security. Their processing locations depend on the service; the main product's EU storage location does not mean that every service processes data only in the EU.

Product database

Google Cloud SQL, Warsaw, Poland

Uploaded product files

Google Cloud Storage, Warsaw, Poland

Database backups

Google Cloud, EU backup location

Your browser

A local copy on the device you use

What reaches our servers

Your workspace content reaches Tooling Studio's servers when you create, import, or synchronize it. This lets team members work on the same records and lets you use more than one device.

• Account details, such as your name, email address, profile image, and Google account identifier.
• Team memberships, roles, invitations, preferences, and subscription information.
• Boards, tasks, checklists, comments, attachments, and links.
• CRM contacts, organizations, deals, notes, custom fields, and activity history.
• Time entries, timers, reports, goals, and related workspace records when you use those apps.
• Integration credentials, synchronization identifiers, and technical or security records needed to operate the service.

A local copy helps the app work quickly. The shared server copy lets your team work together. Clearing browser data does not delete your workspace from our servers.

How Google Workspace data is used

Google sign-in supplies your basic identity. Additional integrations use permissions for the feature you connect. Each integration has a different data flow.

Google Contacts

Contacts you import become CRM records on our servers. This can include names, email addresses, phone numbers, organizations, addresses, and notes present in the source contact.

Google Calendar

When meeting sync is enabled, matched events become CRM meeting records. These can include titles, descriptions, dates, attendees, organizers, locations, and meeting links.

Google Tasks

Task sync exchanges task data with Google and stores the identifiers needed to link the records.

Gmail task links

A task made from an email can store its title, email subject, Gmail link, and message or thread identifiers. These become part of the Tooling Studio task.

Email-to-task

When you send or forward an email to the task mailbox, our server processes the message. Its subject and message text can become the task title and description. The mailbox copy is deleted after successful processing; the created task remains.

Google Drive links

The Drive Picker stores the selected file's name, link, and available last-edited time as a reference. This feature leaves file contents in Google Drive and uses the existing Drive access permissions. A file you upload separately is stored in our file storage.

Disconnecting an integration stops its future access. Information already imported or copied into a task or CRM record can remain in Tooling Studio. Delete that record or contact support if you also want the stored copy removed.

What is kept on your device

The web app uses browser storage, including IndexedDB, to keep local copies of work data and synchronize changes with the server. Cookies and browser or extension storage also support your session and preferences. The Chrome extension keeps session information and settings in Chrome's local extension storage.

These local copies are on the device and browser profile you use. Use a trusted device and protect access to your browser profile. Browser controls let you clear site and extension data. Unsynchronized changes can be lost if you clear storage before they reach the server.

How access is protected

Tooling Studio uses Google sign-in and application sessions to identify users. Server checks use account, team, board, and role permissions to control access. Uploaded files use access checks and time-limited signed links.

Browser connections use HTTPS. The production application requires an encrypted database connection and verifies the database certificate. Stored Google access and refresh tokens are encrypted with AES-256-GCM. These tokens allow connected features to work without storing your Google password.

Tooling Studio's server processes workspace content to provide the service. The encryption described here protects connections and stored Google tokens; it does not make workspace content readable only by you.

What happens when you use AI

Built-in AI features use Google's Gemini API. The data sent depends on the action. Checklist generation sends the task title and description. CRM import assistance can send column names, file or sheet names, and a small sample of source rows. Assistant features can process your prompt and relevant workspace context.

When you authorize an external AI client through Tooling Studio MCP, that client can receive the workspace data returned by the tools you let it use. Its own processing and retention terms apply to that copy. You can revoke the connection in Tooling Studio.

Use your organization's rules when you select content for an AI feature or approve an external client. Ask us about a specific data requirement before including information that needs special handling.

Services that support Tooling Studio

The service involved depends on the feature you use. The main providers and their roles are listed below.

Google / Google Cloud

Product hosting, database, uploaded files, backups, operational logs, sign-in, Workspace integrations, Gemini, and team communications, including website form notifications in Google Chat.

DigitalOcean

Public website hosting and website content.

Stripe

Payments and subscriptions. Tooling Studio stores billing references and payment status; Stripe processes payment-card details.

Cloudflare

Website delivery and security.

Google Analytics / Tag Manager / PostHog

Website usage and product or marketing interaction measurement, where enabled.

Zoho Campaigns

Newsletter subscriptions and marketing email.

Backups, retention, and deletion

We keep workspace data to provide the service while the account or workspace is active. Account closure, removal from an active workspace, and permanent erasure are different operations. Some product records use soft deletion, which removes them from normal use but can leave a stored record.

The production database has automated daily backups configured to retain 15 backups, with seven days of transaction logs for point-in-time recovery. The three most recent automated backup jobs reported success on the review date. Uploaded files have a seven-day soft-delete recovery window. This file recovery window is separate from the database backup policy.

The application log bucket has a 90-day retention setting. Security, billing, legal, and other service records can have separate retention needs. Deleting an account does not mean that every copy in logs, backups, and other providers disappears at the same time.

For a permanent erasure request, contact [email protected]. We will review the scope, including shared-team records, connected services, and any required retention. Contact us before closing a team owner's account if other members still need its workspace.

Your controls and next steps

This explanation covers the general Tooling Studio service as reviewed on 29 October 2026. Read it with our Privacy Policy for the wider description of personal-data use and your choices.

• Choose which Google integrations and AI clients to connect.
• Manage team membership and permissions for shared workspaces.
• Disconnect integrations or revoke Tooling Studio access in your Google Account.
• Delete or correct stored product records, and contact support for an erasure request.
• Ask [email protected] for a review of your organization's storage, processing, or supplier requirements.