Security & privacy

Private by construction

A coaching product only works if people trust it with the hard stuff. Here is exactly who can see what, and how the system enforces it.

Who sees what

The privacy contract

DataCoacheeOrganization adminHuman coach
Conversations and messagesOwnNoNo
MemoriesOwnNoNo
Profile, goals, session metadata, commitmentsOwnAggregates and rosterConsented scopes only
Assessment responses and scoresOwnAggregate deltas onlyNo
Practice runs and program progressOwnNoNo
Coach notesOwnNoOwn as author
Usage (session counts, tokens)OwnWorkspace aggregatesNo

The platform founder sees curriculum, usage statistics, and aggregate coaching health — never transcripts or memories.

How it is enforced

Security practices

Your own database

Hydelogix runs on a dedicated database project. Product data — profiles, goals, sessions, commitments, conversations, memories, content — lives in its own schema with row-level security enabled on every table.

Tenant isolation

Every read and write is scoped to your workspace. Semantic search over content and memories runs through database functions that enforce workspace membership; cross-workspace reads are impossible by construction.

Encryption

Data is encrypted in transit (TLS) and at rest by the hosting provider. Third-party OAuth tokens (for example a founder's Google Drive connection) are encrypted with a separate application key before storage.

Authentication

Email and password sign-in with password reset, plus optional Sign in with Arcasya. Sessions are httpOnly cookies. Administrators never see passwords.

Billing

Payments are processed by Stripe. Hydelogix stores the subscription status and seat counts, never card details.

No training on your data

Your conversations and content ground your coach and nothing else. They are never used to train external AI models.

Retention

Cancelling a subscription suspends the workspace and keeps the data. Deletion requests are honoured on request through support.

Human oversight

Aggregate metrics for organizations, consented scopes for human coaches, and a founder training console that sees curriculum and usage statistics — never coachee transcripts.

Need a security review?

We're happy to walk your security or compliance team through the architecture.