Privacy policy
Effective September 29, 2026
ArgoRise develops Quest. Quest is currently a private, owner-only prototype. Workout connections are optional, imported activities start private, and we do not sell workout information or use it for advertising. Garmin access is not yet available.
1. Scope and operator
This policy covers the public ArgoRise website and the Quest prototype, including its optional AI companion, Aco. ArgoRise is the project brand responsible for these services. The prototype is used by its adult founder and is not open for public registration or directed to children.
2. The public website and correspondence
This information website has no signup form, advertising pixels or site-authored analytics. Our hosting providers, OpenAI Sites and Cloudflare, may process IP addresses, browser information, requested pages, timestamps and security-related information to deliver and protect the site. Any cookies used by the hosting platform are governed by that platform’s operation. When you email us, Google Workspace processes your address, message, attachments and related email metadata so we can respond and maintain correspondence. Please do not send health records or passwords by email.
3. Information stored by Quest
Quest stores your account identifier, profile information you enter, quests, goals, activities, workout logs, audience choices, notes and uploaded photographs. This information provides your journal, profile and progress views. Sign-in is provided through OpenAI. Uploaded photographs have embedded EXIF and XMP metadata removed. External stock-cover providers may receive ordinary request information when an image is loaded in the app.
Quest also stores follows, likes and comments. Visibility follows the associated profile and activity audience. A comment exposes its author’s display name to people allowed to see that activity, even if the author’s profile is private. Following someone does not grant access to their private records. These features do not make the owner-only hosted prototype publicly accessible.
4. Optional workout connections
Connections require your authorization and a selected history range. The prototype contains integrations for WHOOP, Apple Health through the iPhone app, and optional Oura, Polar Flow, Wahoo, Withings and Google Health connections where provider and server configuration is complete. Google Health supplies supported Fitbit and Pixel Watch exercise sessions.
Quest keeps normalized workout information: provider account and workout identifiers, activity type, start and end time, timezone, duration, update information, and available distance and elevation. Apple Health imports may also include the name and identifier of the app that recorded a workout. Quest does not read Apple Health routes, heart rate, sleep, recovery or calorie records, and does not write to Apple Health. WHOOP imports do not retain heart-rate measurements, strain, sleep, recovery or calorie scores.
Some providers bundle broader permission scopes. Quest uses the workout summaries and account identifiers needed for the connection and discards unrelated response fields. Provider notifications and background checks may update imports while the browser is closed. The iPhone app checks when opened and when iOS permits background work. Connectivity, quotas, locked devices or expired permissions may delay syncing.
5. Planned Garmin connection
Garmin integration is not active and Quest does not currently collect information through the Garmin Connect API. The proposed integration is for user-authorized workout summaries: activity type, date and time, duration, distance and elevation, plus identifiers needed to synchronize records. Access depends on Garmin’s approval and a future consent flow. Before any Garmin collection begins, this policy and the connection screen will describe the actual permissions, uses, sharing and deletion behavior. No Garmin approval or partnership is implied.
6. Aco, the optional AI companion
The founder’s Aco messages, relevant eligible Quest records and conversation history are processed through a Railway-hosted service and OpenAI to provide replies and requested app actions. Text extracted from attached documents and spreadsheets is reviewed on the device before sending; the original files are not sent by that extraction flow. Sent text, conversations, imported program text and action receipts are stored in Quest. Longer material can be read in bounded pages and searches.
Aco can carry out owner-requested actions such as saving goals, adding or editing manual activities and recording workout sets. It cannot delete the account, change sharing, manage integration credentials or send external messages. Apple Health and additional cloud-provider imports, including their derived totals, are excluded from AI context. Eligible manually entered records and WHOOP-derived workout summaries may be included. Uploaded photos, integration credentials and login details are not supplied to the model.
The founder’s separate ChatGPT authorization is encrypted on Railway. Disconnecting removes those stored credentials without deleting conversations. OpenAI processes AI inputs under the terms and data settings of that connected account; this policy does not promise a separate zero-retention or no-training arrangement for all AI content. Google Health data is excluded from AI context and is not used to train general-purpose AI models.
7. Purposes, visibility and service providers
We use information to operate the journal, synchronize authorized workouts, display progress, provide requested AI assistance, manage account access, respond to questions and protect the service. We do not sell workout information or use it for advertising. Google Health information is used only for the requested journal and connection features, in accordance with the Google Health API Developer and User Data Policy and Google API Services User Data Policy, including Limited Use requirements.
Imported workouts start private. Changing an activity’s audience can expose its displayed details to people who can access that profile, subject to hosting access. OpenAI Sites and Cloudflare provide hosting, identity-related services, storage and background delivery; Railway hosts the AI companion; OpenAI processes AI requests; Google Workspace handles correspondence. Connected workout providers operate under their own privacy policies and your granted permissions. Providers may process information in countries outside your own.
8. Security
HTTPS protects information in transit. Connected-provider app secrets and access/refresh tokens are encrypted before database storage, with encryption keys held separately as server secrets. Credentials are excluded from profile views and record exports. Access controls apply to records and media. These measures reduce risk but cannot guarantee absolute security.
9. Retention, disconnection and deletion
Quest records and conversations remain until you remove them or delete the account. Disconnecting a workout provider stops imports and removes connection data and entries supplied only by that connection. Entries also supplied by another connection and separately logged activities may remain. Attached notes on removed imports are deleted; photographs may be detached into private storage and can require a separate removal request. Revoking provider access does not itself delete records already copied into Quest.
Customized entries may remain without their removed source details. Deleted-import identifiers and matching information can be retained to prevent retries from recreating removed workouts. Provider limitations mean some missing records cannot be treated as proof of deletion. WHOOP app-registration credentials may remain encrypted after disconnect to allow reconnection; deleting the Quest account removes them.
Account deletion removes the profile, quests, activities, conversations, uploaded photos and related social records from active storage. Encrypted credentials needed only to retry provider revocation may remain for up to 24 hours. Completed notification records are removed after seven days. Provider database backups may retain deleted records for up to 30 days; deletion requests must be reapplied if a backup is restored. Correspondence is kept while needed to address the inquiry or associated service issue, subject to applicable legal obligations. Contact us to request deletion of correspondence or detached photographs.
10. Your controls and requests
You can edit your records and audience choices, disconnect providers, export your activity record, or delete your Quest account from the profile. You can also revoke permissions in the original provider’s settings. For access, correction or deletion, use the account controls described above. We may need to verify account ownership before acting. Rights and applicable exceptions depend on your jurisdiction; you may also contact your local data-protection authority.
11. Policy changes
We will update this page and its effective date when practices change. New integrations, wider access or materially different uses of information will require an updated notice and, where appropriate, a new permission step before collection or use begins.