Flow Architect Privacy Policy

Flow Architect is a mobile productivity app focused on rhythm planning, daily blocks, weekly reflection, and optional calendar-aware availability on supported iOS builds. This Privacy Policy explains the limited data Flow Architect collects and stores off-device, what stays on your device, how optional calendar access works, how long data is retained, when it is shared, and how you can delete it.

Summary

• You can use core parts of Flow Architect without creating an account.
• Core planning data is stored on your device first, and guest usage is designed to stay local to the device except for technical requests needed to deliver the app and app updates.
• If you sign in, Flow Architect collects your email address, a Firebase account identifier, and a backup of your saved app state in Firebase Firestore so you can restore it on another device.
• On supported iOS builds, calendar connection is optional. Flow Architect uses calendar timing data only on-device to estimate availability and is designed to discard event titles, notes, locations, attendees, organizer details, URLs, and similar event-content fields before they reach the planning layer. Raw calendar event content is not stored in Firebase.
• Expo application services may receive technical metadata needed to deliver app updates and operate the update service.
• Flow Architect does not sell personal data and does not currently use third-party advertising SDKs, cross-app tracking, or third-party analytics SDKs in the mobile app.

Data We Collect and Store Off-Device

1. Account information

If you create an account or sign in, Flow Architect collects:

• your email address
• an authentication record managed through Firebase Authentication
• a Firebase account identifier associated with your sign-in

This data is used to authenticate you, keep you signed in, and connect your backup data to your account.

2. Signed-in cloud backup content

If you sign in, Flow Architect stores a serialized backup of your saved app state in Firebase Firestore. That backup can include content you enter or generate in the app, such as:

• onboarding choices and rhythm preferences
• peak-time and slump preferences
• reduced-motion preference
• daily blocks, tasks, shifts, and related planning state
• weekly intentions, focus areas, and reflection notes
• daily energy and meaning scores
• onboarding completion and other saved app-state values needed to restore your experience

If you do not sign in, this saved app state is designed to remain on your device only.

3. Technical service and delivery data

Flow Architect uses Expo application services to deliver app updates. This can require technical metadata related to update delivery, app versioning, device or app compatibility, and service operation. Flow Architect does not currently use this update infrastructure for third-party advertising, cross-app tracking, or third-party analytics.

Data Processed Locally on Your Device

4. Local app state

Flow Architect saves core planning data locally on your device so the app can work without an account. This can include the same categories of app content and preferences listed above, such as tasks, planning state, reflections, scores, and rhythm settings.

When you later sign in, the app may sync a backup copy of that saved state to your account so you can restore it on another device.

5. Calendar integration data

If you choose to connect iOS Calendar on a supported build, Flow Architect may process the following data locally on your device:

• calendar permission status
• device-local calendar integration settings such as whether the integration is enabled, selected calendar IDs, a first-app-open date marker, and last refresh timestamp
• privacy-minimized busy-time windows for the current day, including start time, end time, duration, calendar ID, source, and all-day status

Flow Architect is designed to discard event titles, notes, locations, attendees, organizer details, URLs, and other event-content fields before they reach the planning layer. Calendar integration settings are stored locally on the device and are not included in the Firebase backup payload. Raw calendar event content is not stored in Firebase under this policy.

How We Collect Data

Flow Architect collects data in the following ways:

• directly from you when you enter account credentials, preferences, tasks, reflections, and other planning information
• automatically when the app saves your current state on-device
• when you are signed in, by syncing your saved app state to your Firebase-backed cloud document
• if you opt into iOS Calendar access on a supported build, by reading calendar timing data locally from the device through the operating system permission flow
• through update infrastructure used to deliver the app and over-the-air updates

How We Use Data

Flow Architect uses collected data to:

• create and maintain your account
• sign you in and keep your session active
• save and restore your rhythm setup and planning state
• back up your saved app state across devices when you choose to sign in
• if calendar access is connected, analyze busy windows locally to estimate availability, detect meeting-heavy days, and protect or adapt focus blocks
• export your data when you request a JSON export
• delete or reset data when you request it in the app
• deliver app updates and maintain the app's technical operation

Flow Architect does not use your data for targeted advertising or cross-app tracking.

Third Parties and Service Providers

Flow Architect shares data only with service providers needed to run the app:

• Firebase Authentication: used to create and manage your sign-in account.
• Firebase Firestore: used to store the signed-in backup copy of your saved app state.
• Expo application services: used for app delivery and update infrastructure.
• iOS calendar APIs via Expo Calendar: used locally on supported iOS devices, after permission, to read time ranges needed for availability analysis.

These providers may process data on our behalf to provide their services. Calendar-derived busy windows are designed to stay local to the app experience and are not uploaded as raw event content under this policy. Flow Architect does not share your data with third-party advertisers or data brokers.

Retention

Flow Architect keeps data for different lengths of time depending on the type of data:

• Local app data stays on your device until you reset saved profile data, uninstall the app, or delete your account.
• Signed-in cloud backup data stays in Firebase Firestore until you reset saved profile data while signed in or delete your account.
• Account records stay in Firebase Authentication until you delete your account.
• Calendar integration settings stay on your device until you disconnect calendar access in the app, remove the app, or clear app storage. They are not included in the Firebase backup payload.
• Calendar-derived availability context is used for current-day planning behavior and is recomputed as needed rather than stored as a raw calendar archive in Firebase.

If you sign out without deleting your account, your saved backup can remain associated with your account so you can sign back in later.

Your Choices, Deletion, and Revoking Consent

You can manage your data inside the app:

• Export JSON from the Profile screen to create a portable copy of your saved data.
• Reset saved profile data from the Profile screen to clear saved app data. If you are signed in, this also clears the Firebase-backed backup tied to your account.
• Delete account from the Profile screen to permanently remove your Flow Architect account and its backed-up profile data.
• Disconnect iOS Calendar from the Profile screen, or revoke permission in iOS Settings, to stop calendar-based availability processing on supported iOS builds.

If Firebase requires a recent sign-in before account deletion, sign in again and retry the delete-account action inside the app.

You can also revoke consent for ongoing storage by deleting your account, resetting saved profile data, disconnecting calendar access, revoking iOS calendar permission, or uninstalling the app.

Children

Flow Architect is not intended for children under 13, and we do not knowingly collect personal information from children under 13.

Security

Flow Architect relies on platform and service-provider security controls, including Firebase authentication and Firestore access rules that restrict backup documents to the signed-in user associated with the document.

For calendar integration, the app is designed to minimize event data by reducing calendar input to busy-time windows and discarding event titles, notes, locations, attendees, organizer details, and similar fields before they are used by the planning layer.

No method of transmission or storage is completely secure, but we work to limit data collection to the data needed for the app to function.

Changes to This Policy

If this policy changes, the updated version will be posted at this URL with a new effective date.

Contact and Support

Use the in-app Profile screen for export, reset, calendar connection, and delete-account actions. If you need help with a privacy or deletion issue that you cannot complete in the app, contact Flow Architect support via GitHub Issues.