Effective for invitation-only internal TestFlight testing. Version 2026-09-21-native-internal-pilot-2. This Notice applies only to authorized testers age 18 or older.

Certivo EMS Internal Native-Pilot Privacy Notice

Effective date: September 21, 2026.

1. Scope and contact

Certivo EMS (certivo_ems) is an invitation-only internal pilot for authorized adults age 18 or older. For internal-pilot privacy questions, contact paramedicine101@gmail.com. The final external contracting entity, public business address, and monitored Certivo-domain privacy contact are not established by this internal-pilot document.

2. Information processed

Account and authentication. The pilot processes full name, email address, account identifier, password authentication, confirmation status, and session/access timing. Native session credentials and limited pending-signup state are stored with device secure storage; the app does not intentionally store your password there.

Legal acceptance. The service records accepted Terms/Privacy versions, acceptance time, and signup source (certivo_native_signup).

Study activity. The pilot processes selected program/framework, learner status, optional target date, weekly study goals, selected study days, flashcard deck/session selection, card reveal, rating, and review-scheduling state so study activity can persist across sessions.

Operational/security records. Certivo services may process limited request, error, timing, access-control, and security records needed to operate and protect the pilot. No fixed retention period is promised unless technically enforced.

3. Providers

Certivo source is designed to use Supabase for authentication, sessions, and Certivo data; Vercel for web/API hosting; and Resend for confirmation/recovery email when required production configuration is available. This notice does not claim current delivery of confirmation/recovery messages without that runtime proof. Authorized Certivo operators may access information needed for support, security, service operation, or abuse investigation.

4. Information not collected for the enabled native learner workflow

The current native-pilot source does not implement active advertising, cross-app tracking, analytics SDKs, crash-reporting SDKs, location, contacts, photos, health data, payment/purchase processing, push-token collection, native assessment answers or scores, ItemGen interactions, or AI prompts. RevenueCat code is not an active commerce integration. Expo/EAS builds and distributes the app but the native source does not send Certivo account or study activity to Expo/EAS.

5. Current scheduled deletion and retention

A password-confirmed request schedules deletion, disables the Certivo product account, and revokes its active product session. You may cancel by signing in during the next 30 days. After that window, the current process makes Certivo product data eligible for a separately authorized maintenance purge; it does not promise automatic completion on a set day.

When the current maintenance purge completes, source removes Certivo goals, flashcard state, product sessions, recovery/challenge records, product operations, and product legal-acceptance records. It retains a deletion receipt with product identifier, a fresh non-linkable random digest, request time, and purge time. The current implementation also retains the underlying Supabase authentication identity, and provider backups or operational records may have separate retention cycles. This internal-pilot notice does not promise complete deletion or a fixed retention period for those remaining categories.

6. Changes

Materially new processing requires an updated versioned notice. A future external-release notice will require final operator/contact details, a defined retention policy, an Auth-identity authority decision, and the separately proposed 24-hour deletion-completion policy if that policy is implemented.

Related effective document: Certivo EMS Internal Native-Pilot Terms.