This draft describes the application architecture. Your operator must review it against the deployed infrastructure and actual provider contracts before accepting customer data.
Account identifiers, hashed passwords and session tokens, encrypted MFA secrets, hashed recovery codes, organization membership, repository metadata, scoped source snapshots, audit evidence, usage and payment-provider references are processed to operate reviews. Restricted telemetry uses route templates and status without source, request bodies or account identifiers.
Selected source and security context are transmitted to the configured model provider. Payments are handled by the configured payment provider; payment card details should not pass through GeniusGuard. Provider contracts govern their independent processing.
Source and evidence retention settings are organization-scoped. Deletion jobs, artifact storage lifecycle, and backup expiry must be configured by the operator. A deletion request hides affected records while exact object versions and derived data are removed. Encrypted backups may retain older copies until expiry; signed tombstones are replayed before restored service access. Account deletion anonymizes identity and revokes credentials while organization-owned audit, comment and accounting history follows organization retention.
The My account page offers protected personal-data export and account deletion, subject to sole-owner and subscription safeguards. Contact Code4genius Limited through its official site for other privacy enquiries. Identity and organization authority must be verified before access, export, or deletion requests are fulfilled.
The final policy requires verified controller contact details, lawful bases, processor disclosures, international transfer provisions, retention schedules, and applicable rights under the actual deployment.