CareHub | HIPAA Security Detail

Executive Summary

CareHub is taking a phased approach to security and privacy. The beta platform is deliberately scoped to avoid broad health-data capture, while the production architecture is being shaped to support stronger HIPAA-aligned controls when those workflows are activated.

Data Scope

Minimal beta collection by design.

Transport Security

HTTPS and hardened authentication.

Continuity

Daily backups and multi-path recovery.

User Rights

Access, correction, deletion, portability — see Privacy Policy.

Production Path

HIPAA-ready controls staged for launch.

Reality Check

Current state: privacy-first beta architecture with active authentication, encrypted transport, invite controls, and backup discipline.
Not current state: this page does not pretend that every production-grade control is already fully enforced everywhere.
Guiding principle: collect the minimum necessary data, limit unnecessary exposure, and be explicit about what is live versus what is still being hardened.

Why This Matters

Trust is earned by clear scope, not inflated claims. This page explains the current implementation plainly — including continuity and recovery — and separates beta reality from the production control path.

CareHub does not provide diagnosis or treatment. The platform is intended for information, coordination, research translation, and community support, with sensitive health-data workflows staged for more rigorous production controls.

Formal policy language (collection, use, rights, cookies, international) lives in the Privacy Policy.

What We Collect, and What We Deliberately Avoid

The beta system is intentionally narrow. This is the operational summary; the formal statement is in the Privacy Policy.

Current data categories

Account and login data: email-based authentication, verification flows, and associated security metadata.
Optional user-provided content: profile, wellness, or support entries that users voluntarily submit.
Operational analytics: pseudonymous usage signals used to improve reliability and debug issues.

Deliberate exclusions

No Social Security numbers or government ID documents in the beta scope.
No payment-card processing inside the current public beta posture.
No broad PHI intake by default until production-grade controls are activated.

Access, correction, deletion, portability, and related rights are defined in the Privacy Policy. Verified deletion requests are intended within 30 days, subject to legal and fraud-prevention exceptions; backup rotation detail is under Current Security Measures below.

Current Security Measures

CareHub’s current security posture is built around authentication discipline, encrypted transport, scoped access, and operational hygiene — not broad claims of finished compliance.

Authentication stack: Supabase-backed auth flows with email verification and hashed password handling.
Encrypted transit: HTTPS and SSL protect data moving between users, services, and infrastructure.
Session protection: secure session token handling with expiry and revocation logic being progressively tightened.
Registration controls: invite-oriented access and validation measures reduce unnecessary exposure during beta.
Secret management: operational credentials are kept out of source content and managed through environment configuration.
Audit visibility: application logging and access-trace infrastructure exist today, with broader enforcement still being hardened.

Security philosophy

Narrow risk before scaling surface area. CareHub would rather phase features responsibly than claim a larger compliance perimeter than the implementation currently supports.

Current continuity safeguards

Daily automated backups: scheduled backup activity is documented at 3 AM.
Multi-platform redundancy: recovery pathways span Google Sheets, Supabase PostgreSQL, Google Drive, and local CLI archives.
Multiple restoration options: recovery is not dependent on a single store or a single sync path.
Documented retention boundaries: backup copies may persist temporarily before normal overwrite cycles complete.

Deletion and backup rotation

Verified deletion requests are intended within 30 days unless data must be retained for legal, fraud-prevention, or security reasons. Removal from live systems and removal from rotating backups do not necessarily happen at the same instant; older backup copies age out through the normal overwrite schedule.

What this means in practice

If a system issue occurs, CareHub is not relying on a single database snapshot. The continuity model uses redundant stores and documented recovery paths to reduce the chance of permanent loss.

HIPAA Strategy and Production Controls

HIPAA readiness is a production activation path, not a blanket claim over the beta environment. The architecture direction is serious; the items below are staged controls.

Controls intended for production health-data workflows

Business Associate Agreements: vendor BAA templates are part of the production plan and are expected to be executed when covered workflows go live.
Expanded audit and breach response: comprehensive audit logging, incident handling, and notification procedures are part of the intended production perimeter.
Role accountability: privacy and security officer responsibilities are defined for launch-stage governance rather than claimed as fully operational today.
Workforce controls: training, access discipline, and procedural compliance are expected to tighten alongside any PHI activation.

Plain-English position

CareHub is building toward HIPAA-ready production controls, but this page does not present roadmap items as if they are already universally enforced in beta. That distinction matters.

AI Governance and Sensitive Features

AI is used to accelerate research compression, drafting, and support workflows. Strategic judgment and privacy-sensitive decisions remain human responsibilities.

Current use: language models can help compress research, support drafting, and improve coordination workflows.
Human review: important trust, policy, and product decisions are not delegated to unsupervised AI outputs.
No diagnosis claim: AI surfaces are not positioned as medical diagnosis or treatment engines.
Future-sensitive features: voice cloning, legacy preservation, or blockchain-linked systems would require explicit consent, stronger governance, and separate security review before deployment.

If blockchain or zero-knowledge features are pursued

Sensitive data would remain off-chain, with privacy-preserving proofs used only if they improve trust without exposing protected information.

I’m Rupert, Daddy’s goldendoodle, and I answer with help from Google Gemini™. I do my best, but I can still get things wrong, so please double-check anything important.

How I answer

Interface: Ask Rupert is delivered from the Next.js application layer at Ask Rupert.
Model: the current API route is configured to call gemini-2.5-flash.
Processing: CareHub brokers the request through its API layer before any model response is returned.

When to get human help

You can ask about anything at all — not just medical topics. If something is urgent, dangerous, or needs clinical judgement, speak to a qualified professional or emergency services right away.

When I can save what you tell me

Until you sign in, input is not recorded in CareHub’s database for auditing or follow-up. Chats are processed by Google Gemini and are subject to Google’s Privacy Policy. CareHub’s formal policy is the Privacy Policy.

Cookies

Cookies in the product

We use cookies to keep the experience secure and to understand usage where consented. The formal policy statement is in the Privacy Policy.

Essential cookies

Required for security
Always on

Analytics cookies

Help us improve the app when enabled / consented.

Consent actions

Accept All — essential and analytics
Decline Non-Essential
Customize / Save Preferences
Learn more in the Privacy Policy

Known Gaps

Trust improves when gaps are named. Several controls still need hardening before any production-scale protected health-data workflow would be acceptable.

JWT hygiene: fallback secret behavior and related token hardening need to be fully removed before sensitive production use.
MFA and lockout enforcement: these controls need stronger boundary enforcement before health-data launch.
Row-Level Security: RLS rollout is not yet the final production posture across every sensitive table.
Invite validation and Google Sheets integration: these flows are being hardened and should be described as in progress, not fully solved.
Lookup and verification efficiency: some verification endpoints still need more rigorous indexed or production-grade query patterns.

Why publish the gaps

A beta product can tolerate staged hardening; a PHI-bearing production product cannot. This page keeps those categories separate.

Contact

Questions about privacy, trust, or platform posture: info@globaloutcomes.press.

Primary principle: minimum necessary data, explicit scope, and honest staging.
Formal policy: Privacy Policy.
Current posture: this page reflects both the live beta implementation and the production control trajectory without blending the two.

Material changes to controls, scope, or production rollout should be reflected here and in the linked Privacy Policy.

HIPAA Security Detail

Podcast Summary