Skip to content
Dee home

Privacy policy

Dee · Updated October 3, 2026

About Dee

Dee is a personal assistant operated by Derek Fidler. Access to the assistant is restricted to authorized users. This notice describes the connected-account features, including the local assistant.

Information used and why

Dee uses the messages, preferences, saved items and task details you provide to answer requests and organize your day. Google sign-in supplies account identity information. If you connect Google Calendar, the app reads calendars, events and availability to answer scheduling questions and prepare daily briefs. If you connect Gmail to the web app, it can read messages and manage message labels for inbox organization and summaries, within the permissions you grant.

Dee's calendar-reading connection requests read-only access. An optional, separately authorized booking connection can create events on the primary work calendar after a requested booking is confirmed. Google grants that connection permission to manage events on owned calendars, while Dee's booking tool restricts its use to creating events on the configured primary calendar, without guest invitations. Other connected services are used to fulfill your requests; bookings, outgoing messages and other calendar changes require your approval. Adding the confirmed booking to the primary calendar can be authorized in advance.

Processing and storage

The web app uses hosting and storage providers to process requests and keep account connections, chat history, task records and cached results. Cloud Google refresh tokens are encrypted in storage. Dee runs its language model locally on the operator's computer; its separate Calendar credentials and refresh tokens are stored there in a directory restricted to the Windows user. Responses sent through Dee chat pass through the web service and may be saved in chat history.

Features configured to use cloud AI, such as web-app summaries, send the relevant input to the configured AI provider. Google and other connected services receive the API requests needed to perform the requested function. Hosting providers also process technical information needed to operate the service, such as request and error logs.

Use and sharing limits

Dee does not sell Google user data or use it for advertising. Google data is used to provide the user-facing assistant features described here and is shared with service providers only as needed to deliver those features. Dee does not use Google user data to train generalized AI models.

Dee's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Retention and your controls

Account credentials are kept while a connection is in use. Disconnecting a Google account from the web app removes its stored connection tokens. Local Dee connections are removed on the computer running Dee. You can also revoke Google access through your Google Account connections. Revocation stops future authorized access but does not automatically erase previously saved chat history, task records or summaries.

Saved assistant records remain until removed by the operator; caches may expire sooner. To request deletion of retained information, or ask about data handling, contact df@derekfidler.com.