Weekflow privacy policy

Last updated: May 5, 2026

Weekflow is a personal time-audit app. It reads your Google Calendar so you can reflect on how you spend your time each week. This page explains exactly what data the app touches and what it doesn't.

What Weekflow accesses

With your permission via Google Sign-In, Weekflow reads your Google Calendar entries — events, calendar names, and colors — through the Google Calendar API. If you choose to log time entries directly from Weekflow, the app also writes new events back to a calendar you choose. Weekflow additionally reads your "Start of the week" preference from Google Calendar settings so the weekly view begins on the same day as in Google Calendar.

What Weekflow stores

• A Google authentication token, kept in your device's secure storage (Keychain on iOS, EncryptedSharedPreferences on Android).
• A local cache of your calendar events, kept in your device's app storage.
• The reflection notes and weekly commitments you write inside the app, kept in your device's app storage.
• Your in-app preferences (tracked calendars, weekly targets, session presets), kept in your device's app storage.

What Weekflow does not do

• Weekflow has no backend server. No data is sent to any server operated by the developer.
• Weekflow does not share, sell, or transmit your data to any third party.
• Weekflow does not run analytics, tracking, telemetry, or advertising.

How your data is protected

Weekflow uses the following mechanisms to protect data obtained from Google APIs and any related personal data stored on your device:

• Encryption in transit. All requests to Google APIs are sent over HTTPS using TLS provided by the operating system's networking stack. Weekflow does not disable, downgrade, or bypass certificate validation.
• Encryption at rest. The Google authentication token is stored in the platform's secure credential store — iOS Keychain (hardware-backed via the Secure Enclave on supported devices) on iPhone and iPad, and EncryptedSharedPreferences on Android. Other locally- cached data (calendar events, reflection notes, preferences) is written to the app's sandboxed storage, which is protected by iOS Data Protection and Android file-based encryption — both unlocked only after the user authenticates to the device.
• Access control. Because Weekflow has no backend server, no employee, contractor, or third-party processor of the developer can access your data. The data is readable only by the signed-in user on the device where it was stored, and is isolated from other apps by the platform's app sandbox.
• Data retention and deletion. Data is kept on the device only as long as it is useful to the app. Signing out of Google inside Weekflow deletes the authentication tokens immediately. The "Wipe local data & sign out" action additionally deletes the entire local cache and all in-app preferences. Uninstalling the app removes everything Weekflow has stored. There is no server-side data to retain because there is no server.
• Security incident response. Because Weekflow stores no data on developer-controlled infrastructure, there is no developer-side breach surface for Google user data. Vulnerabilities in the app itself are addressed through updates distributed via the App Store and Google Play. Users may report suspected vulnerabilities to the contact address below; reports are reviewed and patched as soon as practical.

Signing out

When you sign out of Google inside Weekflow, your authentication tokens are deleted from the device. The "Wipe local data & sign out" action additionally clears every locally-stored entry — event cache, reflection notes, commitments, calendar tracking preferences, weekly targets, and session presets. Data on Google Calendar itself is never modified by either action.

How Google user data is used

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

Specifically: Google Calendar data accessed by Weekflow is used only to provide the user-facing time-audit features described on the homepage. It is not transferred to any third party, not used to serve advertisements, and not read by humans except as necessary for app operation or with the user's explicit consent.

Contact

Questions about this policy? Email klaritylab.app@gmail.com.