Privacy Policy

Searcy System · Last updated 5 September 2026

Who this covers

Searcy System is a private household application. Its only users are two named adults in a single household, both known personally to the developer. It is not offered to the public, there is no sign-up, and no other person's data is processed by it.

What data is accessed

With the user's explicit consent, the application reads the following from the Google Health API, and nothing else:

DataWhy
StepsDaily activity reporting
Active energy burnedEstimating energy expenditure
Exercise sessions (type, start, duration, calories)Prompting the user to record what they lifted, and modelling training load
Body weightComputing a smoothed weight trend, the system's primary feedback signal
Body fat percentageBody-composition reporting

Scopes requested

Both are read-only. No write scopes are requested and no data is ever sent back to Google Health. Scopes for sleep, nutrition, location and other data types are deliberately not requested, because the application does not use them.

How it is stored

Data is stored in a private PostgreSQL database (Supabase) accessible only to the developer, over encrypted connections. It is not published, not indexed, and not exposed on any public endpoint. A read-only personal dashboard, if enabled, is served from an unguessable URL and carries noindex headers.

How it is used

Solely to produce reports and recommendations for the two household members — meal plans, grocery lists, training progress, and bodyweight trends.

Some text the users write is sent to Anthropic's Claude API to be interpreted — for example, turning "squat 285 5x3" into structured training records. Health measurements from Google Health are used in these requests only where needed to answer the user's own question. Anthropic does not train models on this data.

What is never done

Retention and deletion

Records are kept for as long as the household finds them useful. Either user may ask for their data to be deleted at any time, and it will be removed from the database in full.

Revoking access

Access can be withdrawn at any time from myaccount.google.com/permissions, independently of the developer. Revoking access stops all further reading of Google Health data immediately.

Limited Use

Use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.