Account and organization
WorkOS user, organization, membership, role, invitation, and session references needed to authenticate and authorize access.
Minimal information. Clear boundaries.
Effective August 31, 2026. This notice describes the controlled Frontline Access Hub pilot and will be reviewed before any real-customer launch.
Information Frontline handles
Hub configuration
Approved destination metadata, branding, configuration versions, member layout, order and visibility choices, and destination-verification records.
Security and operations
Administrative audit events, bounded webhook receipt metadata, Hub-session events, approved tool IDs, launch outcomes, rate-limit events, and service-health data.
Device-only preferences
Display, launch-mode, browser, biometric-unlock, and offline preference fallbacks may remain on the member's device. Secure session tokens use operating-system protected storage in the native app. If the member creates a Frontline PIN, the app stores a salted derived verifier—not the PIN itself—on that device and keeps bounded failed-attempt and temporary-lock information.
Information Frontline is not designed to receive
Frontline must not receive patient or clinical records, dispatch or criminal-justice data, payroll or email content, vendor credentials, MFA codes, passkeys, vendor pages, or activity performed inside an external system. External destinations have their own privacy practices.
Why information is used
- Authenticate members and enforce organization, role, and authorized-Hub boundaries.
- Display the correct approved Hub and synchronize the member's active Hub and personal tool organization across signed-in website and mobile clients.
- Launch an approved external destination and diagnose a bounded launch failure.
- Protect the service, investigate misuse, maintain audit evidence, and restore service.
- Improve the controlled pilot using aggregate, non-vendor activity measurements.
Service providers and disclosure
Frontline uses WorkOS for identity, Cloudflare and OpenAI Sites for hosting and database services, Expo for private native builds and updates, and Apple for iPhone signing and distribution. Information is disclosed only as needed to operate, secure, comply with law, or protect rights. It is not sold.
Retention and security
Retention periods are defined in the project's data-retention policy and limited by record type. Frontline uses access control, organization-scoped queries, encryption provided by its platforms, audit records, monitoring, backups, and recovery procedures. No system can guarantee absolute security.
Your choices and requests
Members can adjust supported preferences and can ask their organization administrator to review membership or configuration. For access, correction, deletion, or privacy questions, contact fajardovictor@frontlineaccesshub.com. Frontline will verify the requester and preserve records when legally or operationally required.
Changes
The effective date will change when this notice materially changes. A real-customer launch requires a final legal review, named business entity, and any organization-specific notices or agreements.