Privacy policy

1. Overview

This policy covers the Helios website, iPhone app, web app, and agent connection service. Your training and nutrition records can contain sensitive personal information. This page explains how those records are used and the controls you have.

2. Information we collect

Account and sign-in

We store your account identity, email address, verification status, and sign-in records. Sign in with Apple supplies identity information and can provide a private relay email address.

Training and nutrition

We store the records you save: workout plans, exercises, completed workouts, nutrition targets, food entries, saved meals, notes, and attached photos. The iPhone app also keeps local records and changes that wait for a network connection.

Agent permissions and changes

We store approved connections, permissions, and access credentials. Saved changes can include a request reference, the reason for a change, and the previous record version. These records support review, duplicate prevention, and undo where available.

Subscriptions

For an Apple subscription, we store purchase and subscription identifiers, product, status, and access dates. Apple handles payment details. Helios uses verified purchase information to determine account access.

Support and service operation

Support receives your name, email, message, and any optional phone number, images, or videos you submit. Diagnostic records include request references, result codes, app versions, and timing information. Hosting and sign-in services can also process network addresses and session information.

3. How we use information

• Open and protect your account, and check permissions for each request.
• Save and sync your training records across your apps.
• Respond to agent requests you authorise.
• Check subscription access and send account emails.
• Answer support requests, investigate faults, and prevent abuse.
• Measure product use according to your usage-data choice.

A food search sends your search text to Open Food Facts. If you request an AI nutrition estimate, Helios sends the meal description, portion, and public nutrition evidence to OpenAI. Review an estimate before you save it.

4. Connected agents

The Helios permission screen shows the access requested by ChatGPT, Claude, or another supported agent. An approved agent can read records or make permitted changes for your account. Review a proposed change before you approve it.

Records returned to an agent are handled by its provider under its own privacy policy. See the OpenAI privacy policy and Anthropic privacy policy.

Revoke a connection under Connected agents in iPhone Settings or web Profile to stop future access. Revocation does not remove records already returned to the provider or erase previous chat messages. Use that provider's controls for those copies.

5. Storage and security

Server records are stored in a Neon PostgreSQL database. Uploaded photos and support attachments use private Vercel Blob storage. Support tickets use a separate permission-restricted database table. The iPhone app keeps local data on your device.

Server requests use secure connections, sign-in checks, account isolation, and agent permission checks. Normal diagnostic events use fixed names, request references, status codes, and durations. They exclude passwords, access tokens, and training content.

Remove private details from support screenshots and recordings before upload. The service checks supported image and video formats. Images are re-encoded to remove metadata. Accepted videos are checked but are not re-encoded, so they can still contain metadata.

Providers can process information outside your country.

6. Service providers

• Vercel: website and API hosting, and private file storage.
• Neon: account, training, permission, subscription, and support database records.
• Resend: sign-in, account, deletion notification, and support email delivery.
• PostHog: website measurement and product usage data, as described below.
• Google Ads: advertising measurement on the public website after you allow optional analytics.
• Apple: Apple sign-in, App Store distribution, and Apple subscription payments.
• Open Food Facts: public food search and nutrition evidence.
• OpenAI: requested nutrition estimates and records returned through your ChatGPT connection.
• Anthropic: records returned through your Claude connection.

Each provider has its own terms and privacy policy. Agent providers receive records through the connections you approve.

7. Usage data and cookies

Share usage data controls optional account usage collection. Events can include the account identifier, feature used, app version, result, and timing. Helios product events exclude food and exercise names, notes, photos, prompts, passwords, and search text. Optional web measurement can include masked interactions, performance, and error events.

Turning the setting off stops future optional collection. It does not erase data already sent or queued. Essential security, access, and support records are separate from this setting.

The public website has its own usage-data choice. Before a choice, it sends a basic visible-page presence event with a reduced page URL and approved campaign fields. Basic measurement uses memory and does not record sessions or clicks. Full measurement uses local storage and masked interactions. The app setting does not change the website setting.

If you allow optional website analytics, the production website loads the Google Ads tag for advertising measurement. Google can use cookies for this measurement. Ad personalization stays off. Choose Basic only under Usage data in the footer to stop future optional measurement. This does not erase data already sent. See Google’s privacy policy.

The web app also uses cookies for sign-in and session protection. Blocking essential cookies can prevent sign-in.

8. Retention and deletion

Saved records are kept while your account exists, subject to your changes and deletion requests. Retention periods differ for backups, logs, support records, analytics, and deletion records. Live cleanup and backup expiry are separate processes.

Account deletion requires recent sign-in and a confirmation dialog. Account access stops when the server accepts the request. Cleanup removes live account records and uploaded photos; failed steps remain pending for retry. The requesting iPhone also removes its local account data, including unsynced changes.

For a verified email address, Helios queues an acceptance email and a separate email when live cleanup finishes. Acceptance is not completion. Email delivery depends on the email service.

A separate deletion record retains account identifiers, a protected request reference, dates, and cleanup status to prevent deleted accounts returning after a database restore. Backups expire under provider retention periods. A completion email does not confirm that every backup has expired.

Deletion does not erase agent providers' copies, your saved exports, or support messages already delivered to a staff inbox. It does not cancel an Apple subscription.

9. Your data controls

• View and correct: review and update saved records in the app.
• Export: use Account data in iPhone Settings or web Profile to export saved server records and photos. Export pending iPhone changes separately if they have not synced.
• Disconnect: remove a connection under Connected agents to stop future access.
• Usage data: change Share usage data for optional account measurement.
• Delete: request deletion under Account data. Export first; deletion cannot be undone.

Keep exports private. Contact support if you cannot use a control or need other personal information we hold. Export and deletion controls remain available when paid access ends, with their normal sign-in checks.

10. Policy changes

We may update this policy as the service changes. The date above identifies the current revision. The latest policy is available at this address.

11. Privacy enquiries

Use Helios support to request access or correction, report a privacy concern, or ask about deletion. State that your message is a privacy enquiry. Do not include passwords, sign-in links, or access tokens.