Privacy Policy

The short version

Spring collects only the information needed to run the flow builder and sync flows to your watch. It has no advertising or third-party analytics, and personal information is never sold. The watch app does not request Apple Health access or collect health and fitness data.

Information Spring processes

• Account information: your email address, password hash, and essential sign-in session data when you create a springflows.dev account.
• Content you create: flows, custom moves, cues, and spring settings that you save to your account.
• Watch connection data: a short-lived pairing code, a one-way digest of the watch token, the watch-reported model name or identifier, and the time it last synced.
• Operational data: routine server logs such as IP address, request time, requested URL, browser or device information, and errors. These logs are used to secure and operate the service.
• Campaign information: if you arrive through a tagged campaign link, Spring may save its source, medium, campaign, creative, keyword, landing page, and referring website host with your account. This helps measure which Spring outreach is useful without an ad pixel or third-party analytics service.

Apple Health and workout data

Spring does not use HealthKit, request Apple Health permission, read heart rate or active energy, or write workouts to Apple Health. The end-of-flow summary contains elapsed time and move count only. No health or fitness data is sent to springflows.dev.

Information stored on your watch

A paired watch stores its sync token in the device keychain and caches your synced flows in its app container so they remain available offline. The latest completed-session summary is stored in Spring's private app group so its complication can update. Unlinking the watch removes its token and synced-flow cache.

How information is used and shared

Information is used to authenticate your account, save and sync your flows, secure the pairing process, provide support, prevent abuse, and keep Spring reliable.

Spring may use infrastructure providers to host the service and deliver account email. Those providers process information only to provide their services. Information may also be disclosed when required by law or to protect the security and rights of Spring and its users. Spring does not sell personal information or share it for cross-app tracking.

Cookies and tracking

springflows.dev uses essential cookies for sign-in, security, and session continuity. Its first-party session can also hold basic campaign labels until you register, at which point those labels are saved with your Spring account. It does not use advertising cookies, tracking pixels, or third-party behavioral analytics. The Apple Watch app does not track you across apps or websites.

Retention, deletion, and your choices

Account information and saved content are retained while your account is active. Routine operational logs are retained only as needed for security, troubleshooting, and reliable operation. Legal obligations may require limited information to be kept longer.

You can unpair a watch from the Pair Watch page, unlink it in the watch app, or delete your account from the springflows.dev Account page. Account deletion removes your flows, custom moves, and paired-watch records. For access, correction, or deletion questions, contact support@springflows.dev.

Children

Spring is not directed to children under 13, and Spring does not knowingly collect personal information from children under 13.

Changes and contact

This policy may be updated as Spring changes. The effective date above will be revised when that happens. Questions can be sent through the Spring support page.