HealthLab Legal
Privacy Policy And Data Use
This policy explains what HealthLab collects, why it collects it, how it is used to operate HealthLab, and what controls members have over stored account and routine data.
- Last updated
- August 9, 2026
- Primary scope
- HealthLab accounts, routine workspace data, entitlement records, and support requests
1. Product And Privacy Scope
HealthLab is a direct-to-consumer supplement routine workspace. It is not a medical provider, telehealth service, clinical decision-support tool, prescription-management product, lab-interpretation product, or service operating on behalf of a HIPAA covered entity. Covered entities, clinicians, and other regulated healthcare organizations must not use HealthLab as a patient-management workflow or on behalf of patients unless Graysect separately enters the proper agreements.
HealthLab uses member-provided routine and account data to operate educational supplement planning surfaces. It does not sell personal data.
HealthLab may process supplement routine data, wellness preferences, timing patterns, goals, and behavioral context that may be considered consumer health data or sensitive personal information under some privacy laws. Graysect uses this data only to operate, personalize, secure, support, and improve HealthLab as described in this policy. Graysect does not sell personal data or consumer health data.
2. Information We Collect
- Account data, including email, authentication state, account status, and timezone context.
- Access entitlement state needed to confirm account-access status.
- Routine profile data, including supplement routine preferences, timing anchors, serving context, schedule patterns, and saved routine history.
- Supplement workspace data, including supplement names, label information, serving details, routine notes, comparison history, and saved results.
- Consent records, policy acceptances, safety acknowledgements, document versions, timestamps, IP-derived context, user agent context, and information needed to document agreement.
- Support, export, deletion, accessibility, security, dispute, and audit data needed to operate the service, respond to member requests, and enforce HealthLab policies.
3. Member Collection Boundaries
HealthLab member workflows are designed to avoid collecting the following categories. Do not submit them unless a future reviewed workflow asks for them explicitly.
- Diagnoses, treatment plans, lab values, acute symptoms, medication lists, pregnancy or lactation status, or detailed medical history.
- Clinician notes or clinician-in-loop status.
- Raw health payloads in application logs unless strictly necessary for a narrow operational reason.
4. How We Use Information
- Operate the HealthLab member workspace and keep your account available.
- Personalize timing, cycle, reminder, educational dashboard, and saved-result views.
- Use AI-assisted tools, where enabled, to process supplement information and support product features and quality workflows subject to posted review controls.
- Preserve appropriate history so prior saved information and decisions are not silently replaced when underlying information changes.
- Confirm account access and HealthLab entitlement state tied to the registered account.
- Maintain consent history, appropriate accountability records, security controls, and abuse-prevention measures.
- Improve product quality using limited operational information and member feedback.
- Send transactional account messages, including verification, invite, password reset, policy, and service notices.
- Investigate, document, resolve, or defend account, privacy, accessibility, security, legal, or policy issues.
5. AI-Assisted Processing
HealthLab may use AI-assisted systems to process supplement information and support product features and quality workflows. These systems are used to support HealthLab, not to provide medical advice, diagnosis, treatment, emergency care, or professional services.
AI-assisted outputs may be incomplete, outdated, incorrectly matched, or affected by source quality. They are proposals and do not create a member decision or change a member's active routine.
HealthLab preserves appropriate history so prior saved information and decisions are not silently replaced when underlying information changes. Graysect may also retain limited records needed to support accuracy review, safety boundaries, dispute handling, and legal compliance.
6. How We Do Not Use Information
- HealthLab does not sell personal data.
- HealthLab does not sell consumer health data.
- HealthLab does not use routine profile data, supplement stack data, saved runs, or member feedback for third-party targeted advertising.
- HealthLab does not provide member routine data to data brokers.
7. How HealthLab Is Operated
Graysect uses specialized services to operate HealthLab. Information is processed only for the applicable operational purpose described below.
Application operations
Infrastructure services used to host, secure, deliver, and operate HealthLab.
Data storage
Managed data services used to store HealthLab account and application data.
Transactional communications
Delivery services used for account verification, access, password, policy, and service messages.
AI-assisted processing
AI-assisted processing used in certain HealthLab features and quality workflows when enabled. Information submitted to those features and limited related context may be processed for that purpose. Its output is a proposal; it does not create a member decision or change a member's active routine.
8. Retention
Account data
Retained while the account is active and for operational or legal periods after closure.
Entitlement records
Retained as needed to enforce account access and support audit integrity.
Routine profile
Current and saved routine profile history is retained while the account is active; profile deletion removes or deactivates current profile information where technically available.
Saved supplement information and results
Retained while the account is active so reports, comparisons, and history remain available; removed through self-service deletion where available or through a verified support request.
Consent records
Retained with the applicable document version, time, and limited acceptance information for accountability, policy enforcement, dispute resolution, and legal defense.
Security and operational records
Limited records may be retained for debugging, security, and accountability; raw routine or profile content should be excluded from logs.
9. Export, Deletion, and Member Controls
Profile export should provide account-readable routine profile data, consent versions, and relevant saved results. Profile deletion removes or deactivates current saved profile information where technically available.
Some export and deletion controls may be handled through support while self-service controls are being completed. Members may request access, export, correction, or deletion by contacting support@graysect.com. Graysect will process requests according to this policy, applicable law, identity-verification requirements, and lawful retention needs.
10. Requests and Verification
Members may request access, correction, export, or deletion by contacting support@graysect.com. Graysect may require reasonable identity verification before acting on a request.
Some records may be retained where needed for security, fraud prevention, legal compliance, audit integrity, or enforcement of these Terms and policies.
11. Security and Logging
HealthLab uses operational security controls such as encrypted connections, network protection, authentication, authorization, managed infrastructure, and accountability records for important account and workspace changes.
Security and operational records are limited to information needed for accountability, reliability, and abuse prevention. They should avoid raw emails, tokens, session cookies, and full routine or profile content unless strictly necessary for a narrow operational reason.
12. Children and Geographic Scope
HealthLab is intended only for users who are at least 18 years old. Do not create an account or use HealthLab if you are under 18.
HealthLab is currently intended for the United States market. Graysect does not intentionally market HealthLab to EU or UK residents unless and until appropriate GDPR and UK GDPR controls are implemented.
13. Required Policies, Requests, and Disputes
Use of HealthLab requires agreement to the Terms of Service, this Privacy Policy, the Accessibility Statement, and applicable product notices. Graysect may keep limited records showing whether, when, and how required policies were accepted.
Privacy, deletion, export, correction, accessibility, account, and policy complaints should be sent to support@graysect.com with enough detail for Graysect to verify the request and investigate. Graysect may ask for identity verification before releasing, changing, or deleting account data.
Disputes related to this Privacy Policy, privacy requests, data handling, accessibility requests, account access, or HealthLab use are subject to the notice, limitation of liability, arbitration, class-waiver, venue, and claim-deadline provisions in the Terms of Service to the maximum extent permitted by law.
14. Contact
For privacy questions, data access, export, deletion, or account requests, contact support@graysect.com.