1. Scope
This Privacy Policy applies to Snoze websites, applications, APIs, desktop and mobile clients, and related services that link to this policy (together, the Service). Snoze is currently offered as a public beta. The Service is available for real use, but features and data practices may develop as the product matures. We will update this policy before using personal information in a materially different way.
If you use Snoze through an organization, that organization may control the workspace content and account settings it manages. Its own privacy notices may also apply.
2. Information we collect
Information you provide
- Account information: your name, email address, profile details, sign-in method, and authentication identifiers.
- Workspace content: pages, databases, records, files, comments, messages, forms, automations, prompts, and other content you create or upload.
- Communications: information you send when you request support, submit feedback, or otherwise contact us.
- Billing information: subscription, plan, invoice, and transaction details. Payment card details are handled by our payment provider and are not stored directly by Snoze.
Information collected when you use the Service
- Usage information: features used, actions taken, timestamps, workspace events, and interactions needed to operate and improve the Service.
- Device and log information: IP address, browser or app version, device type, operating system, referral URL, and diagnostic or crash data.
- Cookies and local storage: information needed to maintain sessions, remember preferences such as theme, protect the Service, and understand basic site performance.
Information from connected services
When you connect a third-party service, Snoze receives the account information, authorization tokens, files, records, events, or other data permitted by the scopes you approve. The exact information depends on the provider and the connection you configure. You can disconnect an integration in Snoze or through the provider.
Snoze does not copy or store your mailbox. When you connect Gmail or Outlook, Snoze reads or changes email live through your provider when you, an AI feature acting for you, or an automation you set up asks it to, for example to send, reply to, draft or label a message, or to read an attachment an automation needs. Email content is kept only where it is saved as part of that work, such as the related AI conversation, automation run history, or content you save it into.
The exception is a workspace Google connection with Gmail events enabled: it reads new and changed messages so they can start automations, and shares that trigger content with the workspace's readers, including through its event feed even without an automation rule; see Google user data for the fields and sharing boundaries. Automation outputs follow their destination's permissions.
Snoze previously offered a personal Mail inbox that stored a copy of your email. That feature has been removed and its stored copies have been deleted from the active Service; backup copies may remain until their applicable retention ends.
Disconnecting an email account in Snoze, or revoking Snoze's grant at your provider, stops further access. It does not erase email content already saved in Snoze, such as workspace events, automation runs or AI conversations. Remove those through their workspace controls or request deletion atsupport@snoze.dev.
3. How we use information
We use information to:
- provide, synchronize, secure, and maintain the Service;
- authenticate users and manage accounts, workspaces, permissions, and subscriptions;
- run the actions, automations, integrations, and AI features you request;
- respond to support requests and communicate service, security, billing, and policy updates;
- monitor reliability, prevent abuse, investigate incidents, and enforce our Terms of Service;
- analyze and improve product performance, accessibility, and user experience; and
- comply with legal obligations and protect users, Snoze, and the public.
We do not sell personal information. We do not use workspace content to advertise to you or others.
5. AI features
If you use an AI feature, Snoze may send your prompt and the workspace context needed to complete your request to the model provider selected or configured for that feature. Responses and tool actions may be stored with the related workspace activity so that the feature can function, be audited, and recover from errors.
Do not submit sensitive information to an AI feature unless you are authorized to do so and the feature is appropriate for that information. Model outputs can be inaccurate. Review important output and proposed actions before relying on them.
6. Google user data
When you connect a Google account, Snoze accesses only the Google data needed for the features you use, and only with the permissions you grant on Google's consent screen:
- Workspace Gmail automations: When Gmail events are enabled for a workspace Google connection, Snoze reads new and changed messages and stores sender and recipient addresses, subjects, snippets, labels, attachment names and handles, and up to the first 5,000 characters of message text in workspace event and automation records. These records can start and filter automations when mail arrives, is sent, starred, labelled, archived, or moved to trash. Members permitted to read that workspace can receive these email payloads through its event feed; access is not limited to the permissions of an automation's destination page or database. Connect only a mailbox whose data you are authorized to share with those members. Actions that send, draft, reply to, or label email run on your behalf; attachments are fetched when an action needs them.
- Your own Gmail account: If you connect your personal Google account in Settings, Snoze stores the account and its authorization, not your mailbox. Email is read or changed only when you or an AI feature acting for you asks, as described under Email.
- Google Calendar: events from the calendars you choose are shown in Snoze Calendar and kept up to date, including their times, attendees, and responses, and changes you make in Snoze are sent back to Google.
- Google Drive, Docs, Sheets, Slides, and Forms: Snoze lists and opens the files you browse, link, or import, reports file activity (created, edited, renamed, moved, shared, trashed) to your automations, and makes the changes your automations or actions request.
Snoze's use and transfer of information received from Google APIs adheres to theGoogle API Services User Data Policy, including the Limited Use requirements. In particular, Snoze:
- uses Google user data only to provide and improve the user-facing features described above;
- does not sell Google user data or use it for advertising, including personalized or retargeted ads;
- does not use Google user data to develop, improve, or train generalized AI or machine learning models. When you ask an AI feature to work with Google data, that data is sent to the model provider only to complete your request;
- transfers Google user data only as needed to provide or improve the user-facing features you request, including disclosed workspace sharing and necessary service-provider processing; to comply with applicable law; or as part of a merger, acquisition, or sale of assets after obtaining your explicit prior consent. A financing or other business transaction alone is not permission to transfer Google user data;
- allows human access to Google user data only with your affirmative permission for specific content, including content you explicitly share with disclosed workspace recipients; when necessary for security, such as investigating abuse; when required by law; or for internal operations using data aggregated and anonymized as required by Google's Limited Use rules.
You can disconnect a connected Google account in Snoze Settings, and separately revoke Snoze's grant in yourGoogle Account permissions. Snoze keeps no copy of your Gmail mailbox, so there is no mailbox copy to delete. Disconnecting a personal Google account or a workspace Google connection stops new access through that connection but does not erase previously saved workspace events, imported content or automation outputs. Revoking access in Google also does not erase data already stored in Snoze. Remove that workspace content through the appropriate workspace controls or request deletion atsupport@snoze.dev. Backup and legally retained copies may remain until their applicable retention ends; we do not promise that every copy disappears immediately.
7. Retention and security
We keep information for as long as needed to provide the Service, maintain legitimate business records, resolve disputes, enforce agreements, and meet legal obligations. Retention periods vary by data type, account status, workspace settings, and backup cycle. Deleting content or an account may not immediately remove copies from backups or records we must retain by law.
We use administrative, technical, and organizational safeguards designed to protect information. No method of storage or transmission is completely secure, so we cannot guarantee absolute security. Please protect your credentials and notify us if you believe your account or workspace has been compromised.
8. Your choices and rights
You can update certain profile and workspace information in the Service, change sharing permissions, disconnect integrations, and control cookies through your browser. You can request access to or a portable copy of your information through the contact below. Workspace owners and administrators may be able to access, export, correct, or delete content managed by their organization.
Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or receive a portable copy of personal information. You may also have the right to withdraw consent or appeal a decision about a request. To submit a request, email support@snoze.dev. We may need to verify your identity and authority. If an organization controls the relevant workspace, we may direct the request to that organization.
9. International use
Snoze and its service providers may process information in countries other than the one where you live. Those countries may have different data protection laws. Where required, we use recognized safeguards for international transfers.
10. Children
The Service is not directed to children under 13, and we do not knowingly collect personal information from them. A higher minimum age may apply in your country. If you believe a child has provided personal information in violation of this policy, contact us so we can investigate and take appropriate action.
11. Changes and contact
We may update this policy as the Service, our practices, or applicable laws change. We will post the revised policy and update its effective date. If a change materially affects how we use personal information, we will provide additional notice when required.
Questions or privacy requests can be sent to support@snoze.dev.