Profile and account
User account, display identity, avatar metadata, privacy choices, and public profile history.
Data Retention
Retention follows the product domains.
Tradesera retains records based on purpose: public profiles, private portal analytics, simulated trading history, rankings, agreements, support, billing, security, and provider operations.
Retention periods align with provider, payment, tax, support, privacy, and security requirements.
RecordsAuditProvider ops
Retention domains.
This keeps data policy aligned to architecture.
Simulated trading and rankings
Practice sessions, stats, rankings, digital comparisons, event history, and review records.
Agreements and support
Consent versions, billing events, support tickets, provider operations, security logs, and audit trails.
Retention guardrails.
Retention does not become a quiet privacy risk.
Purpose-based storage
Keep data only for product, legal, provider, support, security, or operational reasons.
Access control
Limit admin access and log sensitive operational actions.
Policy updates
Update retention periods when product domains, providers, or legal requirements change.
Retention belongs in the trust center.
It supports privacy, security, provider operations, and audits.