Privacy policy
Effective October 18, 2026
Tumble is a workspace for projects, conversations, documents, files, and personal work. This policy explains how the Tumble team handles information when you use our website, apps, and connected services. For privacy questions or requests, contact dev@futurepicnic.com.
Information we handle
- Account and workspace information. Your sign-in email, profile details you provide, workspace memberships, invitations, permissions, and preferences.
- Content you create or upload. Projects, tasks, messages, comments, documents, drawings, tables, files, and related history and metadata. Content you put in a shared workspace or conversation is available to people who have access to it.
- Connected-account information. When you connect a calendar or mailbox, we handle the account identifiers, authorization credentials, settings, and provider content needed for that connection. The Google-specific details are below.
- Device and service information. Local app settings and caches, session information, and technical information needed to deliver requests, operate hosting, diagnose failures, and protect the service, such as request times and network information.
We use this information to authenticate you, provide and synchronize the features you use, collaborate with your team, maintain security, resolve support requests, and operate Tumble. The public marketing website currently has no signup form, advertising trackers, or analytics integration. Our hosting provider may process ordinary web-server request logs.
Google Calendar and Gmail
Connecting Google is optional. Tumble requests permission through Google's authorization screen when you choose to connect a service. Calendar and Mail use separate permission flows.
Google Calendar. Tumble accesses your calendar list and event details, which can include titles, descriptions, dates, locations, attendees, and meeting links. We use this information to display your schedule and support calendar actions you request, including creating or updating events, inviting attendees, and adding meeting links. Calendar permissions allow reading calendars and reading and editing events; Tumble does not use them for advertising.
Gmail. If you connect Gmail to Tumble Mail, Tumble accesses the messages, threads, headers, labels, and attachments needed to display and search your mail. It uses Gmail permissions to perform the mail actions you request, such as sending messages, handling drafts, and updating message or label state. Email addresses and recipients are used to show conversations and deliver your messages.
Storage and account sync. Calendar events and mail content are fetched from the provider for use in the app, and mail content may be cached on your device. Device credentials are stored in the operating system's credential store. If you enable Calendar or Mail account sync, encrypted connection credentials and account settings are stored by Tumble's cloud service so your authorized devices can restore the connection and renew access. This encryption is managed by the service; the service can decrypt credentials to provide account sync. The credential vaults do not store calendar event bodies or email message bodies and attachments.
Personal calendar and mailbox connections are scoped to your Tumble account. Workspace membership does not give another member access to those connections. Content you choose to send, invite others to, copy into a shared workspace, or include in an assistant request is shared as needed for that action.
Tumble follows the Google API Services User Data Policy, including its Limited Use requirements. We do not sell Google user data, use it for targeted advertising, or use it to train or improve general-purpose AI models. Human access to Google user data is limited to your affirmative agreement, necessary security or abuse investigations, legal obligations, or other uses permitted by that policy.
AI features and providers you select
When you use an assistant or delegate work to an AI teammate, your instructions, selected page or document context, attachments, and relevant tool results are processed by the provider configured for that feature. Depending on the work you request, this can include workspace content, calendar details, or mail content. Use an assistant with private information only when you intend that provider to process it.
Provider applications and services, such as the Codex, Claude, OpenCode, or Choro setup you choose, have their own terms, retention settings, and privacy policies. Tumble uses these services to deliver the requested feature, not to train a general-purpose model on your Google data. Assistant conversation history and provider-side history may have separate storage and deletion controls.
Retention, disconnection, and deletion
We retain account information and workspace content as needed to provide the service and maintain the records you and your team use. Device caches, assistant histories, and provider-side records can have separate lifetimes. Deleted information may remain in backups, deletion records, or security logs until those records are rotated or no longer needed.
You can disconnect Calendar or Mail in Tumble and revoke Google's authorization at Google Account connections. Disconnection stops future use of that connection; it does not delete events or messages in Google, content already shared with others, or every local cache. Calendar disconnection does not automatically revoke a separate Mail connection.
Contact dev@futurepicnic.com to request access, correction, export, or deletion of your personal information or Tumble account. We may need to verify ownership before acting. Requests involving shared workspace records may require coordination with that workspace's owner, and legal or security obligations can require retaining some records. You can also use your device and chosen providers' controls for their locally or separately stored information.
Children and policy changes
Tumble is intended for workplace use and is not directed at children under 13.
We will update this page when our practices change and identify the effective date above. Material changes will be communicated through the app or another appropriate channel. If a new use of Google data requires additional consent, we will request it before that use.