In plain language
Read how AutoNexit limits collection, protects private automation project data, and handles identity, session, contact, and deletion records.
Data we process
Account identifiers, security/session records, authorized project content, service settings, contact messages, and limited operational logs support the requested workflows.
Acquisition and blog measurement
A pseudonymous first-party visitor hash, sanitized first/last touch, device class, country code, article/day aggregates, and verified registration outcome are retained for internal reporting. Raw IP addresses and full user agents are not stored; anonymous records expire after 13 months and account deletion removes personal attribution.
How data is protected
Projects are private by default; permissions, encryption boundaries, redaction, short-lived access grants, and audit controls limit exposure.
Your choices
Users can manage profile and offline data, request export or deletion, and review explicit sharing and QR publication decisions.