Posibl Life & Gym AppJoin the waitlist
[ SECURITY / TRUST / PRIVACY ]
Your members share their most personal data with you. We protect it.
Health metrics, injury histories, biometric check-ins, payment records — Posibl handles sensitive data across every layer of the platform. Here is exactly what we do to keep it safe.
Contact security teamEvery gym operates in its own isolated schema. Row-level security on every table means a coach at one affiliate can never read, write, or infer data belonging to another gym — by design, not by policy.
Five defined roles — platform owner, gym owner, coach, personal trainer, member — each with fine-grained permission guards on every server action. Role enforcement is tenant-scoped, not global.
Members choose exactly which coaches see their HRV, sleep, and nutrition data. Toggling a data source off removes it from the AI Coach and coach dashboards instantly. No hidden overrides.
Neon Postgres row-level security applies the gym's tenant ID before any query resolves. Cross-tenant data is invisible at the database layer.
The five-tier role model applies fine-grained guards on every tRPC procedure. A member account cannot call coach or owner procedures.
Before the AI Coach or a coach dashboard reads a health metric, the consent record is checked. Revocation takes effect on the next request.
GDPR export packages all personal and health records as JSON or PDF. Deletion requests are processed with no support queue — triggered directly from account settings.
[ DATA ARCHITECTURE / ISOLATION ]
Posibl uses Neon Postgres with tenant-scoped row-level security across all tables. Every query carries the gym's tenant ID. There is no application-layer filtering that could be bypassed — the database itself refuses cross-tenant reads.
Tenant ID enforced at the database row level on every table
Complete data isolation between affiliate gyms
Cross-gym network features use a separate, explicit shared schema layer
Coach at Gym A cannot access Gym B — by database constraint, not middleware
[ HEALTH DATA / PRIVACY CONTROLS ]
Members can ask the AI Coach "what data are you using?" and get a plain-language answer. Every wearable and health source feeding the AI is listed in account settings and can be revoked individually.
[ AI COACH / DATA CONSENT ]
AI-powered personalisation requires training history, health data, and goals. Members grant that access deliberately. The AI Coach surfaces which data sources it is drawing on, answers transparency questions directly, and respects revocation instantly.
[ ACCESS CONTROL / AUTHENTICATION ]
Authentication uses OAuth providers — Google, GitHub, Microsoft, Okta. No passwords stored in the Posibl database. Credential management stays with the identity provider you already trust.
Platform owner, gym owner, coach, personal trainer, and member — each role carries explicit permissions enforced on every server action. Roles are tenant-scoped: coach access is always gym-specific.
[ INJURY DATA / PRACTITIONER ACCESS ]
Coaches log injury records — body region, severity, mechanism, treatment notes, return-to-training dates, and movement restrictions. Physiotherapists access injury data only with member opt-in consent. Notes and protocols are visible to the assigned coach and no one else.
Physio access requires explicit member opt-in
Movement restrictions enforced in programme delivery automatically
Rehab protocols visible only to member and their coach
Return-to-training clearance is a tracked, logged event
[ PLATFORM / MULTI-TENANT SAFEGUARDS ]
Posibl runs multiple affiliate gyms on a single platform. That architecture demands separation be correct from the first query. The schema was designed multi-tenant from day one — not adapted after launch.
Gym owners using the affiliate onboarding flow operate in their own fully isolated tenant. Their members, programming, billing, and community data never intermingle with the host gym or other affiliates.
Cross-gym features — drop-in booking, alumni maps, network leaderboards — use a controlled shared schema that exposes only the data explicitly shared. Private gym data is never in scope.
[ FREQUENTLY ASKED / SECURITY ]
[ CONTACT / SECURITY TEAM ]
If you have a security question, a data request, or have found a potential vulnerability, email us at sf-core-org-support-posibl-life-gym-app@saas-factory.ai — we will respond. No automated deflection.
Email the security team
HRV, sleep, resting heart rate, readiness, strain, and nutrition macros feed into a single normalised schema. Members control which coaches see it. Removing consent removes access — no delayed sync, no cache.
Members request a full export of their personal data as a JSON or PDF package from account settings. Deletion requests remove all personal and health records. Consent is captured granularly — health data, AI coaching, community visibility.
Separate consent toggles for health data sharing, AI coaching use, coach visibility of wearable data, nutrition logs, and community profile. Members change these at any time — no support ticket required.
Coaches flagged on concerns — only with member consent
Proactive AI insights shared with member first
AI answers "what do you know about me?" accurately
Physio access to injury data requires explicit opt-in
New gym members join via a time-limited invite token. No open registration endpoint. Access to a gym's data begins only after the gym owner or coach issues the invite.
Inngest background jobs — readiness scoring, churn risk, injury alerts — compute per member within their gym's tenant context. A job for member A at Gym X cannot read or write data for Gym Y.
Automated churn intervention messages, injury risk alerts, and AI-drafted check-ins route only to the assigned coach within the same gym. Cross-gym routing is not architecturally possible.
[ WAITLIST / EARLY ACCESS ]
Posibl is opening to gym owners and coaches in limited cohorts. Get on the list to be among the first.
