Privacy Policy

Overview

DayFrame is a personal productivity and cognitive workspace application that helps users organize and view information from services they choose to connect.

DayFrame is designed as a local-first application. Information displayed and managed within DayFrame remains on the user's device and within the external services the user chooses to connect.

This Privacy Policy explains how DayFrame handles information.

Local-First Design

DayFrame runs locally on the user's computer.

Information created, organized, viewed, or managed within DayFrame is stored on the user's device or remains within the services the user has chosen to connect.

DayFrame does not operate a centralized service that stores user notes, tasks, contacts, messages, emails, calendar events, workspace layouts, or other personal content.

Google Sign-In

DayFrame may allow users to authenticate using Google Sign-In.

Google may provide certain account information necessary to authenticate the user, such as:

• Name
• Email address
• Profile image
• Unique account identifier

This information is used solely for authentication and providing access to features that the user has authorized.

Google User Data

If a user connects a Google account, DayFrame requests only the permissions needed for the features that account powers. Each permission, and what DayFrame does with it:

• Read your Gmail messages (gmail.readonly) — to display your mail inside DayFrame's Email module.
• Change the state of your Gmail messages (gmail.modify) — to mark messages read or unread, archive them, and move them to Trash when you ask.
• Send mail on your behalf (gmail.send) — to send the messages you compose in DayFrame. DayFrame never sends mail you did not write and ask it to send.
• See and change your calendars (calendar) — to show your events and to create or edit the events you create or edit in DayFrame.
• See and change your contacts (contacts) — to show your contacts and to save the changes you make in DayFrame.
• See your primary email address (userinfo.email) — so DayFrame can show you which account is connected.

Google data reaches your computer directly from Google. It is not routed through, copied to, or stored on any server operated by DayFrame, because DayFrame operates no such server.

A local copy is kept on your device so the app works offline and does not re-download the same messages repeatedly. That copy is held in an encrypted database in your Windows local application data folder, and the key for it is stored in Windows' own secure credential storage, as are the access tokens for every account you connect.

DayFrame does not use Google user data for advertising, does not sell or transfer it, and no human at DayFrame reads it. There is nowhere for anyone at DayFrame to read it from.

Google API Services Limited Use Disclosure

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

Deleting Your Data and Revoking Access

You can end DayFrame's access to a connected account at any time:

• Disconnect it in DayFrame, from that service's settings page, which deletes the stored credentials for it from your device.
• Revoke DayFrame's access at the provider, which works whether or not DayFrame is still installed — for Google, at myaccount.google.com/permissions.
• Delete the local copy by removing the DayFrame folder from your Windows local application data folder. Notes are not kept there — they are the files in the folder you chose, and DayFrame does not copy them anywhere.

Revoking access at the provider stops DayFrame fetching anything new. Deleting the local folder removes what it already fetched.

Connected Services

Users may choose to connect third-party services, including services provided by Google and other providers.

Examples may include:

• Email
• Calendar
• Contacts
• Notes
• Files
• Source control systems
• Social platforms

DayFrame accesses information from connected services only after a user has explicitly authorized access.

Information accessed from connected services is displayed and organized within DayFrame on the user's device.

Users remain subject to the privacy policies and terms of the services they choose to connect.

Data Collection

DayFrame does not collect:

• User notes
• Tasks
• Email content
• Calendar content
• Contacts
• Messages
• Workspace layouts
• User-generated content
• Analytics
• Behavioral tracking data
• Usage telemetry

DayFrame does not maintain a centralized database containing user content.

Data Sharing

Because DayFrame does not collect or store user content on DayFrame-operated servers, DayFrame does not sell, rent, share, or disclose user content to third parties.

Information displayed within DayFrame originates from:

• The user's local device, or
• Services that the user has explicitly connected and authorized.

Data Security

DayFrame is designed to keep user information on the user's own device whenever possible.

Users are responsible for securing access to their devices and any third-party accounts connected to DayFrame.

Children's Privacy

DayFrame is not directed to children under the age of 13.

Changes to This Policy

DayFrame may update this Privacy Policy from time to time as the application evolves.

Any updates will be published on the DayFrame website.

Contact

Questions regarding this Privacy Policy may be directed to:

Jeff Fritz
support@getdayframe.app