Device and station data
Battery, slot status, rental state, returns, uptime, location of station and maintenance events used for network reliability.

This page explains how Soudian plans to protect charging data, limit personal information use and keep AI operations understandable for users, venues and partners.
Battery, slot status, rental state, returns, uptime, location of station and maintenance events used for network reliability.
Phone, payment token, order, support and safety records used only when needed to complete the charging service.
De-identified usage summaries and point performance used to improve availability, placement and merchant service planning.
Soudian privacy-safe charging protocol is designed around notice, purpose limits, data minimization, encryption, access control and user choice.
AI learns primarily from device health, station activity, maintenance records and aggregated network trends.
Personal information is limited to charging, payment, support, safety and features the user chooses.
The charging protocol should not sell personal data or require face, voice or biometric data for ordinary charging.
Designed to align with applicable privacy principles and regulations such as GDPR, CCPA/CPRA and UAE PDPL.
Soudian should explain what data is needed, why it is needed, how it is protected and what users can control without turning every product page into a legal document.
Use the minimum data required for charging, payment, support and safety.
Apply encryption, access control, retention limits and internal review.
Provide clear terms, user requests and opt-in choices for optional features.