Privacy

Your work. Your privacy.

Understand how information moves through Blank, from storing a document to sharing it or working with an agent.

Updated 9 September 2026

What we use and why

Account details, such as your name, email address and workspace membership, help us identify you and provide access to your account.

Your content includes the files you upload and the work you create in Blank: documents, tasks, calendar entries, conversations and agent results. Blank stores and processes this content to provide the features you use.

Billing information supports subscriptions and payments. When you contact us, we use your contact details and message to respond.

Technical records, such as request logs, errors and security events, help operate the service, investigate problems and protect accounts.

Zero data retention for AI

Zero data retention is a requirement for the AI model services we choose. Prompts and content submitted for model processing must not be retained by the provider after processing.

This requirement concerns the model provider. Conversations and files saved in your Blank workspace remain available for you to return to.

What happens when you use AI

An agent processes your instructions alongside relevant conversation history, file content and information returned by tools. External AI services may receive this information to produce a response or complete a task.

Search can use AI to make document content searchable by meaning. This can involve processing extracted text during indexing, as well as processing a search query.

Some tasks send files to an external code-execution service or queries to a web-search provider. The services involved depend on the feature and configured model.

Sharing and connected tools

File permissions let you choose who can view or edit your work. In a shared workspace, your organisation also manages membership and access.

When you connect another tool, its integration exchanges information needed for the enabled features. This can include account details, messages, events, files and access credentials, depending on the connection.

Connecting your Google account

Connecting Gmail or Google Calendar is optional. You sign in with Google and choose whether to grant the permissions shown on its consent screen. Blank receives your account identity and access tokens to maintain the connection; it does not receive your Google password.

Gmail permissions allow Blank to find and read messages, work with drafts and send email for the features you use. This can involve email addresses, subjects, message content, labels and attachment information. Google Calendar permissions allow Blank to read, create, update and delete events, including their titles, descriptions, times, locations and attendees.

These permissions apply to the Google account you connect. Your Google permissions and any restrictions set by your organisation continue to apply.

How Blank uses Google information

Blank uses connected information to provide email and calendar features, search, summaries and work you delegate to an agent. Enabled synchronisation can refresh information in the background, as well as when you request it.

For Gmail search, Blank stores an index containing message details such as senders, recipients, subjects, short snippets, labels and dates. This background index does not store complete message bodies or attachment contents. Agent tasks can retrieve additional message content when needed. Calendar synchronisation stores event information so it can appear in Blank and support scheduling.

When you ask an agent to use connected information, relevant content can be included in the conversation and sent to an AI model service to perform the task. Other processing services may receive content where needed for the feature you use. The AI provider requirements described above apply to this processing.

Limits on using Google data

Blank’s use of information received from Google APIs must comply with the Google API Services User Data Policy and the Google Workspace API user data and developer policy, including their Limited Use requirements.

We do not sell Google user data, use it for advertising or credit decisions, or use it to train general-purpose AI models. These restrictions also apply to information derived from that data and to providers processing it for Blank.

Access and transfers are limited to permitted purposes: providing the features you authorise, protecting the service and meeting legal obligations. Human access requires your specific consent unless needed for security or legal compliance.

Stored information and disconnection

Blank encrypts the access credentials it stores for your Google connection. Synced email details and calendar events are stored separately from files in Drive.

During successful synchronisation, Blank removes Gmail index entries older than 180 days and Google Calendar events that ended more than 365 days ago. These are clean-up windows for the synced indexes, not deletion deadlines for conversations, files, backups or disconnected accounts.

To stop using a connection in Blank, open Extensions, select Gmail or Google Calendar and choose Disconnect. Disconnecting marks the connection inactive. It does not delete previously synced information, saved conversations or files, and encrypted connection credentials remain stored.

You can also revoke Blank’s Google permissions from your Google Account connections page. Revoking access prevents further authorised access through that grant; it does not delete copies already held in Blank.

To request deletion of stored Google information, contact hello@blanksuite.com and identify the connected account. Blank’s account-deletion process removes locally stored connector credentials and synced email and calendar records, and requests revocation of the Google tokens. Information saved in conversations or shared files must also be considered when handling your request.

Services that help run Blank

Service providers support account access, payments, email delivery, hosting and AI features. They receive information needed for those functions.

For example, a payment service processes billing information, while an AI provider can process the instructions and relevant content used in an agent task. This processing can take place separately from file storage.

How stored files are protected

Drive encrypts stored files and uses a separate key for each drive. Sharing permissions control who can view or edit them. Explore our Security page for more detail.

Privacy questions and requests

Contact hello@blanksuite.com with questions about how information is processed, or to ask about access, correction or deletion of your personal information.

For information managed in an organisation’s workspace, your workspace administrator may also need to help with the request.