How Mimik handles account, session, security, and platform telemetry data during platform access. Final legal review is still required before public launch.
Mimik stores user profile data, session records, account connection metadata, subscription status, audit events, and locally sealed broker authorization artifacts needed to restore workspace access and integration state.
Data is used to authenticate users, enforce role and two-factor controls, restore authorized broker routes, generate audit trails, and support trade copier monitoring and analytics within the workspace.
Sensitive broker tokens are sealed locally. Session, audit, and billing records are retained to support security reviews, operational diagnostics, and account history. Formal retention schedules should be finalized before public launch.
Replace this review draft with final language covering processors, payment providers, retention windows, deletion requests, contact details, and regional compliance obligations before collecting customer data in production.