Privacy Policy

Last updated 27 October 2026

This policy covers laverty.io, the FitCypher health tracker at laverty.io/fitcypher, the LavertIO phone app, and the Laverty.io sync tools that connect to the Google Health API. They are run by Alex Laverty as a personal project. Questions or requests: alaverty@gmail.com.

What is collected

• Account: your sign-in identity (name, email address and a user id) from Clerk, which handles sign-in.
• What you log in FitCypher or the phone app: metrics such as weight and blood pressure, meals and food photos, notes, habits, gym sets, workouts and office days.
• Wearable and health data you choose to connect: if you authorise a Fitbit or Google Health connection, the activity, heart rate, heart rate variability, sleep, blood oxygen, breathing rate, skin temperature, cardio fitness and exercise data in that account.
• The blog itself uses no analytics, advertising or tracking cookies. Fonts load from Google Fonts.

Google user data

When you sign in with Google and grant access, the Laverty.io sync tools request read-only access to the following Google Health API data, and nothing else:

• Activity and fitness (steps, distance, calories, active minutes, heart-rate zones, exercise sessions, VO₂ max)
• Health metrics and measurements (heart rate, resting heart rate, heart rate variability, blood oxygen, breathing rate, skin temperature)
• Sleep (sleep sessions, stages and timing)

This data is used only to show you your own health history and trends: it is copied into storage controlled by you (a private repository or your FitCypher account) and charted for you. It is never sold, never used for advertising, never used to build or train AI or machine-learning models, and never shared with anyone else. A person can read it only when you choose to show or publish it yourself.

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

How it is used

Only to provide the features you use: storing what you log, drawing charts and reports, and syncing your data between the website, the phone app and your own archive. Nothing is used for advertising or profiling, and nothing is sold.

Where it is stored

• FitCypher data is stored in a Cloudflare D1 database, and food photos in Cloudflare R2, both reachable only when signed in as you.
• Google Health and Fitbit sync tools write to a repository on GitHub that you own and control; access tokens are kept as encrypted secrets in that repository.
• Data is encrypted in transit (HTTPS) and at rest by those providers.

Who it is shared with

No one, beyond the services that run the site on its behalf: Cloudflare (hosting and storage), Clerk (sign-in) and GitHub (the sync tools' storage). They process data only to provide those services.

Keeping and deleting your data

• Your data is kept until you delete it or ask for it to be deleted.
• You can disconnect Fitbit from FitCypher's settings page at any time, and revoke the Laverty.io Google connection at myaccount.google.com/permissions. Once revoked, no more data is read.
• To have your account and everything stored for it deleted, email alaverty@gmail.com; it is removed within 30 days.

Children

These services are not intended for anyone under 16.

Changes

If this policy changes, the date at the top changes with it. A change in how Google user data is used would only happen after asking for your consent again.