How SoloOps processes information

Effective and last updated: 21 August 2026. SoloOps processes professional profile, service, schedule, client contact and appointment data; sessions, security and rate-limit hashes; support and communication records; Push device registrations; and billing state. Infrastructure providers, Migadu Email, connected Telegram, opted-in Google Firebase Push, Stripe and verified Google Play billing process only data needed for their service roles. Essential session and language cookies are used; no non-essential analytics cookies are currently implemented. Verified deletion immediately disables access, public publication, sessions, provider links and future delivery, then schedules final anonymization or deletion after 30 days. Operational, accounting, security or legal records may be retained where necessary. Exports exclude passwords, factor and recovery secrets, sessions, Push tokens and internal credentials.