Useful data, restrained by design.
This draft describes intended boundaries for Qurmmius prototypes; it is not a verified inventory of every deployed route or provider. It does not replace legal review or a customer-specific data-processing agreement.
Apex Academia beta-interest request
The compatibility page’s optional beta-interest form asks for a name, email address, PC racing-game title, and optional version/discipline so Qurmmius LLC can respond about Apex Academia beta participation. The form is processed through Netlify Forms. The form does not connect to a PC, collect simulator telemetry, or enroll someone in a paid service. Qurmmius has not yet verified a specific retention/deletion period for these interest requests; do not include sensitive, confidential, or telemetry data. The checkbox is limited to this beta-contact purpose and is not consent to unrelated marketing.
Apex Academia simulator data
Live telemetry is processed in the browser for the practice session. Up to 5,000 recent live samples may be saved in this browser and expire 30 days after their last update. Saved session summaries and local coach plans expire after 90 days; local preferences and the optional driver name remain until cleared. CSV imports remain in the active tab and are not auto-saved. A QI brief shares up to 12 selected recent telemetry rows only after a separate consent action and sign-in. Cloud progress is optional, requires a separate Sync action and QI sign-in, excludes raw sample rows, and expires after 90 days. The Apex screen provides a separate action to delete synced progress; local clearing does not delete cloud data. Automated cleanup runs daily, and storage-provider propagation may delay complete removal.
What the QI prototype may receive
Some QI routes may accept bounded text, a selected product skill, session context, and operational metadata such as a request ID and usage counters. A provider-backed request may send its text to an external model provider. The applicable provider, its retention and training terms, and each route’s exact behavior must be confirmed before any customer-data workflow is enabled. Use synthetic or redacted inputs only.
What we avoid storing in pilot paths
- API keys, card numbers, invite codes, and other credentials.
- Raw prompts, media, precise personal locations, biometric identifiers, or unredacted telemetry in browser history or audit records.
- Automated decisions about a person. Consequential outputs require human review.
Operational records and retention
Protected routes may retain a request ID, signed workspace identity, adapter, mode, redaction count, bounded usage metadata, and timestamp for audit and troubleshooting. Retention and deletion controls are product-specific; a single verified schedule has not been approved for all routes. Customer-specific retention, export, and deletion must be agreed in writing before intake; do not infer that a deletion request automatically removes every provider or backup copy.
Voice and transcripts
Do not submit or record a multi-party conversation through a Qurmmius prototype. Voice capture, transcription, provider routing, consent state, and deletion behavior must be documented and tested before the feature is offered to customers. The conservative operating gate is clear advance notice and affirmative agreement from everyone whose conversation would be captured, subject to qualified counsel review of the exact implementation and applicable exceptions.
Your controls
The Stripe-hosted customer portal and deletion-request workflow are not verified as active for this prototype. A future customer agreement must identify the monitored support/privacy contact, the request-verification process, and response/deletion timelines. Do not email secrets or raw personal data. The address displayed on this draft must be confirmed as monitored before this notice is published or relied on.
Product boundaries
DeepFake Shield remains local-preview and purpose-limited. LegacyVault remains synthetic dry-run only. EraWeaver and Qurmmius Palimpsest preserve provenance and uncertainty but do not establish historical fact. QI outputs are decision support and are not guarantees.
For customer operating steps, see the QI customer quickstart. For formal agreements, use the applicable order form, MSA, SLA, and published terms.