Daysie

A little less to think about.

Your data in the Daysie pilot.

You choose which accounts to connect and whether the assistant can use them.

Connected mailboxes

Daysie connects the Google identities you choose to show saved mail and calendars and prepare work for your review. Basic syncing covers that identity’s recent mail and accessible calendars; sender filters limit assistant processing rather than basic syncing. Your Daysie account and password are separate from Google.

For an Outlook.com or Microsoft 365 account, Daysie reads the Inbox and calendar list. You choose which calendars appear in Day and separately choose which may be checked for availability. Optional mail management lets you change read status and move messages to Archive, Deleted Items or Junk. Enabling Outlook replies also grants permission to send. Daysie shows the sender, recipient and exact text for approval. If confirmation is interrupted, Daysie checks the same message in Sent Items.

Access and processing

Google authorization controls access to each identity. Optional mail management permits sending and other mailbox changes; optional calendar access permits event changes. Daysie requires your separate exact approval for external actions. Unknown outcomes stay held for checking.

Assistant processing starts off. You choose an identity, permitted senders and availability calendars, review the named processing service and model, and explicitly enable it. New eligible messages trigger processing; up to ten saved messages in that conversation can provide context. Conversations with unsupported content or participants outside the selected sender filters are held. Matching a sender address does not authenticate that person.

Eligible email text, sender details and conversation context are sent to the selected model service to prepare summaries, replies and event proposals. Saved Daysie event titles and times may provide context for the same conversation; their notes and locations are excluded. Event content from calendars checked for availability is not sent to the model; permitted busy intervals constrain times in Daysie’s backend. Provider credentials are not sent to the model.

Current configured service: DigitalOcean Inference. Model: Not configured. DigitalOcean can route commercial models to their providers. Processing and retention depend on the selected service, model and account arrangement. Daysie does not use your mail or calendar content to train general-purpose models.

DigitalOcean data handling · OpenAI data controls

Daysie uses and transfers Google Workspace data under Google’s User Data Policy, including its Limited Use restrictions. It does not sell Google user data or use it for advertising or general model training.

Pilot access requests

If you request pilot access on the homepage, Daysie stores your contact email encrypted, plus a keyed lookup value to avoid duplicate requests, the notice version and request timestamps. This is separate from a Daysie app account and does not connect Google or enable AI processing. We use the address to contact you about the pilot, not add you to a general marketing list. Requests are removed from the active service after 90 days without another request. Contact support to request earlier removal; backup retention follows the policy below.

Saved data and notifications

Daysie stores connected credentials and saved content encrypted in its database. Normal mail syncing retains a recent 30-day window; calendar syncing generally covers the previous 30 days and next year. Saved drafts, preparation snapshots, assistant work and action history can persist independently of that window until you disconnect or delete your account. This preserves review and uncertain-action recovery.

Operational records include processing status, model name, token counts, timing and bounded usage counts. The model-run records contain no additional copy of email text. Aggregate daily counts and an unlinked hash used to honor deletion during recovery can remain after deletion. The recovery record contains no name, email address, message content or provider credentials.

If you separately enable email notices, Daysie sends a generic review count to your verified Daysie email address. The notice omits message content. Verification and password-recovery emails are also sent through the configured mail service.

Pause, disconnect and delete

Pause assistant processing in its identity settings. Reconnecting Google also pauses assistant processing until you enable it again. A request already in flight cannot be recalled, and pausing does not undo an action you already approved.

Disconnecting removes that identity’s saved data and credentials from Daysie. Deleting your Daysie account removes active saved data, connected identities, assistant work and device tokens. Mail, sent messages and events in Google remain there. Check uncertain actions in Google before acting again. You can separately revoke Daysie’s Google grant in Google account permissions.

Backup copies are governed by the configured retention and restoration procedure. Ask Daysie support for the applicable retention period before connecting content that requires a specific deletion deadline.

Mail you send to Daysie Support, Privacy or Security goes to our support email service. It may be forwarded to our designated support mailbox so a person can respond. Please do not include passwords or private message content. Support correspondence is separate from the Google mail you connect.

Delete your Daysie account · Daysie support