Holos privacy notice

Account and application information

Registration receives your email, first and last names, and password. The registration code hashes passwords with bcrypt. Sign-in uses a server-side session and a cookie; these implementation facts are not a general security or encryption guarantee.

If provided, profile information can include a phone number and profile image. Account records also include identifiers, referral codes and timestamps.

When used, the application stores self-reported sleep, sleep quality, energy, stress, steps, focus time, mood, tasks and descriptions, local schedule entries, preferences, streaks, recommendations and shared snapshots. The data model also contains a heart-rate field; it does not establish that a connected device measures or supplies it.

Wellness scores are software-derived estimates. They are not clinical measurements, and their accuracy or health efficacy is not established by the code.

Services and recipients

The project is configured to run on Replit and uses PostgreSQL for application records and sessions. The current database provider, deployment locations and contractual arrangements require owner confirmation; no residency or provider-security claim is made here.

If you explicitly enable AI for a signed-in session, AI routes can send wellness metrics, preferences and relevant activity context to OpenAI. That permission can be disabled in the application or ended by signing out. Consent is not proof of a configured or available AI service. Outputs can be wrong; no result or improvement is promised.

If Google Calendar authorization succeeds, the application stores access/refresh tokens and uses read-only Calendar access. Disconnecting removes the stored connection through the implemented flow; revocation can also be managed in the user's Google Account. Deleting a Holos account does not delete Google Calendar events.

Apple Health, Fitbit, Google Fit and Android Health Connect are not supported product integrations in this implementation. Video demonstrations do not prove that these connections are working.

When configured, Google Analytics measures pageviews and interactions. Replit analytics event hooks can send events when a tracker is present on the published website. The custom-event wrapper limits event names and properties; it does not forward names, emails, account IDs, health values or free-form content through those custom events. This restriction is not a claim that automatic analytics collects no technical identifiers.

Page paths may be sent by analytics, including snapshot share identifiers contained in paths. Google Analytics initialization is not gated by the separate AI-consent control. Analytics consent requirements and actual provider configuration need review for the intended audience and markets.

Creating a snapshot stores its selected name, date and wellness values with a share identifier and view count. A person with the link can view the snapshot without signing in and may retain copies.

Android image export writes a snapshot image to private application cache and opens the system share sheet. The selected destination application receives the image if you share it. The application attempts to remove its cached image at sign-out and successful account deletion; this is not a guarantee of secure erasure or deletion of recipient copies.

AI concern reports

The in-app report control submits a fixed concern category and associates it with the account and time in the application's event records. It does not request medical details or send the report as a third-party analytics event.

The code can record reports but does not implement a staffed review service or guarantee a response. Operator review and support procedures need confirmation.

Account deletion and retention limits

Settings → Security & Privacy → Delete Account requires a signed-in session, the current account password and the literal confirmation DELETE. The server additionally checks the request format and confirmation header and rejects cross-origin browser deletion requests.

If the deletion transaction completes successfully, it removes the account's live wellness records, mood entries, preferences, streaks, AI recommendations, task suggestions, tasks, local schedule entries, snapshots, stored Calendar credentials, linked app events where that table exists, and associated sessions, then removes the account. Snapshot links no longer resolve from those live records. A foreign-key or database failure rolls back the transaction; the application must not report success when deletion cannot be confirmed.

Account deletion does not delete Google Calendar events or recipient copies and does not automatically erase third-party analytics, provider logs or backups. No backup lifetime, retention period, legal exception or third-party deletion commitment has been verified.

Automatic deletion is unavailable without a valid session and current password. Legacy/passwordless accounts and people who cannot sign in need an owner-approved identity-verification and support-deletion process, which is not established by this page. See the account-deletion information page for the current limitations.

Intended use and unresolved legal facts

Holos presents wellness and productivity information. AI suggestions and derived scores should not be treated as medical advice, diagnosis or treatment. For medical concerns, consult a qualified healthcare professional; do not rely on this application for emergencies.

This notice does not assert medical-device classification, regulatory approval, clinical efficacy, compliance certification, a no-sale policy, a minimum age, or a response deadline. Those statements must not be inferred from marketing descriptions.