Privacy at Basecamp

What Basecamp may collect

Basecamp will collect only information needed to operate the owner's Health & Performance module:

• Owner-provided data: account and device approvals; onboarding and settings; goals; measurements; workouts; text-first nutrition entries; accepted nutrition estimates; supplement schedules and confirmations; and notification preferences.
• WHOOP data, with authorization: cycles, recovery, sleep, workouts, and current body measurements available through the official WHOOP API. Basecamp does not request WHOOP profile access initially and does not receive the owner's WHOOP password.
• Technical data: authenticated session and approved-device records, synchronization and job status, redacted errors, push-subscription details, and limited security logs. Logs must not contain health payloads, OAuth credentials, nutrition text, notification endpoints, or direct identifiers.

Demographics, goals, measurements, nutrition targets, training loads, and supplements come only from first-run onboarding, later settings, or an explicitly authorized source. Basecamp does not populate personal values from planning documents or conversations.

How the data is used

Data is used to import and display authorized wellness history, preserve source provenance, support offline workout logging and synchronization, calculate owner-visible trends, prepare optional briefings and reminders, estimate editable nutrition entries, secure the application, and provide export, disconnect, and deletion controls. Basecamp does not sell personal data, show advertising, build advertising profiles, or share health data for another company's independent marketing.

Basecamp provides wellness and exercise information, not medical diagnosis or treatment. Cardio activity may be imported or logged, but Basecamp does not prescribe cardio.

WHOOP authorization and storage

When enabled, WHOOP connects through OAuth 2.0. Authorization codes and tokens are handled only by Basecamp's server. Rotating access and refresh tokens will be encrypted at the application layer and will not be stored in the browser or included in logs.

Basecamp will store the WHOOP records returned under the scopes the owner approves, together with normalized health facts and source, retrieval, device, algorithm, and revision provenance. This preserves history if the owner later replaces WHOOP and keeps imported facts distinguishable from manual entries. “All history” means all records made available by the authorized official API; WHOOP does not guarantee a particular earliest date, and current body measurements are not a historical collection.

Disconnecting WHOOP revokes or stops future access and synchronization. It does not silently delete previously imported history; retention or deletion of that history is a separate explicit choice.

AI processing

If the owner enables an AI-assisted feature, Basecamp plans to use the OpenAI API from the server. It will send only information necessary for the immediate task—for example, owner-entered meal text for an editable nutrition estimate, or a small derived facts summary for a briefing. Basecamp will not send raw bulk WHOOP exports, identity data, provider credentials, or unrelated health history by default.

API requests will use storage disabled where supported, and provider data sharing for model improvement will remain off. These settings are not a promise of zero retention: under the default OpenAI API policy, request content may be retained in abuse-monitoring logs for up to 30 days unless the actual project is approved and configured for a stricter control. Basecamp will not keep prompt or response content in its own application logs. Any recommendation that changes a target, supplement schedule, notification, or workout program requires the owner's separate explicit approval and an audit event.

Service providers and data locations

Subject to owner approval before deployment, the planned production service providers are:

• Vercel for managed application hosting and request delivery;
• Supabase for authentication, PostgreSQL storage, scheduled jobs, queues, and managed backups;
• WHOOP for the owner-authorized wearable connection;
• OpenAI for optional, minimized AI processing; and
• the owner's browser and Web Push service for local workout drafts and optional notifications.

Each provider processes information under its own terms and infrastructure. Basecamp will use encrypted transport, least-privilege access, and provider settings that minimize data use. No production provider account or data transfer is implied merely by this policy.

Retention

These periods are release requirements, not claims that a production database already exists. Basecamp will verify them before personal data is collected and update this policy if the deployed configuration differs.

Access, export, disconnection, and deletion

The owner may review and correct stored information and, before production use, will receive in-app controls to export data, disconnect WHOOP, delete imported source history, and delete the Basecamp account. During Phase 0, requests can be made through the contact below.

An account-deletion request will revoke provider access, stop jobs and notifications, and purge account, credential, health, raw-source, derived, export, and push-subscription records from the primary store. Residual encrypted copies expire within the disclosed backup windows. Remote revocation cannot guarantee erasure of an offline draft already stored on a lost or unreachable device; local erase and device-security guidance will be provided.

Security and owner choices

Basecamp is designed for one approved owner account and approved devices, with public signup disabled. Planned controls include TLS, secure sessions, multi-factor checks for sensitive actions, database row-level security, encrypted provider credentials, redacted logging, dependency review, and tested backup and deletion procedures. No internet service can guarantee absolute security.

WHOOP connection, AI features, push notifications, daily weight entry, supplements, and optional onboarding fields are voluntary. Core manual and deterministic features are intended to remain usable when optional AI is disabled or unavailable.

Children and policy changes

Basecamp is a private owner-operated application and is not directed to children under 13. Material changes to this policy will be dated here before the changed processing begins.