1. Scope and contact
This policy applies to the Easy BMS app and its remote monitoring service. The developer and operator of Easy BMS (“we”) explains here how account, battery, collection-phone and notification information is handled.
Contact for privacy and support: easy_bms@163.com. This policy covers our services. If you send exported files to another person or organization, review that recipient’s handling of the information as well.
2. Information we process
| Category | Information and source | Purpose |
|---|
| Account and identity | Your registration email and password; the generated account ID and login-session information. The server stores a salted password hash, not a plain-text password. | Sign-in, account verification, authorization and separation of account data. |
| Battery profiles and settings | Names, chemistry, cell count, optional rated capacity, software alert settings and collection authorizations you provide. | Battery profiles, collection-device matching and alert configuration. |
| Battery readings and records | Voltage, current, SOC, cells, temperatures, balancing, MOS status, protection information and capacity fields supplied by the BMS; sample times, data quality, history, charging sessions and alert evidence. | Remote viewing, records, alerts and export. Missing fields are not treated as measured values. |
| Collection and diagnostic information | The Android collection-phone name, service status, battery level, power, network and BLE status, heartbeats, thermal status where supported, upload queue and errors. BLE names, addresses and connection settings support local connections; raw diagnostic frames are stored locally. | Collection-device identification, uploads, troubleshooting and backfill. |
| Notification registration | Installation IDs, push tokens or registration IDs, platform, push environment, language and notification status when you enable notifications. | Alerts and test notifications to your device. |
| Operational and security information | Request times, paths, IP addresses, errors and account-operation audit information. | Service operation, troubleshooting, security and abuse prevention. |
| Feedback you send | Contact details, issue descriptions, screenshots, logs and diagnostic files you choose to email. | Support and information-access or deletion requests. |
Simulated readings are labeled and associated with the account for feature demonstrations; they are not real battery states. The monitoring features do not access vehicle location, contacts, your photo library or microphone recordings, or use battery readings for cross-app advertising tracking. Third-party SDK handling is described in section 5.
3. Purposes and necessity
We use the information for sign-in, access to your battery data, collection authorizations, history, alerts, notifications, exports, troubleshooting and account deletion. Information necessary to perform the service is limited to those purposes. Optional features and permissions are your choice. Where consent is legally required, we obtain the relevant authorization.
Email and password are required for account services. Without rated capacity, available readings can still be viewed, but some capacity or time estimates may be unavailable. Denying notification permission does not prevent viewing existing readings, but system alerts may not appear. We do not sell personal information or use this information for targeted advertising.
4. Permissions and background collection
| Permission or mechanism | Scope and purpose | Your control |
|---|
| Bluetooth scan and connect | Android collection: find the selected BMS, connect and read its status. The iOS viewer does not request Bluetooth permission for collection. | Revoke in system settings; real BLE collection will be unavailable. |
| Location permission on older Android | Android 11 and earlier may require it for BLE scanning. It is used for scanning, not collecting or uploading vehicle coordinates. | Deny or revoke; BLE scanning on those systems may be unavailable. |
| Notifications | Viewer: alerts and tests. Android collection: the ongoing service notification. | Manage in system settings; notification display and collection behavior may be affected. |
| Network access and status | Sign-in, uploads, remote queries, backfill and notification registration. | Remote updates stop offline; Android can cache pending readings within limits. |
| Foreground service, wake and background settings | After you start Android collection, a connected-device foreground service, ongoing notification and wake mechanism support it; settings may allow background operation or fewer battery restrictions. | Stop collection, revoke its authorization or change system settings. |
| Recovery after startup or updates | Where the system permits, Android may resume collection you previously enabled after boot, an app update or reopening the app. | Manual stop or authorization revocation prevents automatic resumption. Force-stop is not bypassed. |
Changing permissions does not delete stored data. You can stop collection and revoke its authorization under Account → Batteries & gateways. System restrictions, power and connectivity may interrupt collection or notifications.
5. Third-party services and sharing
System notifications use the services below according to platform. A service is involved only in versions that actually include and enable it. We do not use a third-party advertising service for cross-app tracking.
| Service and provider | Platform and purpose | Information and policy |
|---|
Apple Push Notification service (APNs)
Apple | iOS alerts and test notifications. | Push tokens, device-routing information, notification content and delivery status. Notifications may include a battery name, alert title and event ID, and may appear on the lock screen. Apple Privacy Policy. |
JPush SDK
Shenzhen Hexun Huagu Information Technology Co., Ltd. | Optional Android push notifications, where included and enabled. | Registration IDs, device identifiers such as Android ID or OAID subject to system and SDK settings, device and OS information, network information including IP address, and push logs. The provider also discloses optional identifier and network processing; actual scope depends on the final integration and permissions. Jiguang Privacy Policy. |
Cloud servers and network infrastructure provide storage and transmission. Providers may process relevant data as necessary to deliver those technical services. When you export or share a file, the recipient and selected app receive the information you share; review the content and recipient first.
We do not provide personal information to unrelated third parties except as necessary for the service, at your direction, with the relevant authorization or as required by law. New services or changes to processing purposes, methods or categories will be disclosed, with renewed consent where required.
6. Retention and local data
| Data | Retention |
|---|
| Account, battery profiles and notification registrations | Kept while the account or feature remains active; deletion removes the corresponding data from the live service. |
| Raw battery samples | Normally the most recent 30 days. |
| Completed charging sessions | Normally 180 days after the session ends. |
| Resolved alerts | Normally 180 days after recovery. Unresolved active alerts remain stored. |
| Processed notification tasks and operation audits | Normally 180 days. Pending tasks remain until processed. |
| Server-generated exports | Normally 24 hours. Downloaded or shared copies are managed by you or their recipients. |
| Pending Android readings | Local limits are approximately 72 hours, 50,000 samples and 128 MiB of payload. Older data may be discarded at the limits. |
| Raw local diagnostic frames | A bounded rolling cache; currently up to the latest 500 frames. |
| Operational logs and support correspondence | For the time needed for troubleshooting, security and your request. You can ask about retention or request deletion by email. |
Scheduled cleanup may be delayed; the periods above do not mean every copy is erased immediately at expiry. Legally retained information is restricted to the applicable purpose. If server backups exist, residual backup data is handled separately from the live database; contact us for backup-retention and deletion arrangements.
Account deletion does not automatically remove downloaded or shared files, or local files and caches on collection phones. Login credentials use system secure storage, and Android collection authorizations are stored locally. Uninstalling the Android app or clearing its app data removes local caches and diagnostic data. You are responsible for exported files and copies held by recipients.
7. Data protection
Account authorization checks limit access to your own data. User sessions and collection authorizations are separate, and passwords are salted and hashed. Login credentials use system secure storage; the production service uses HTTPS. We apply access controls and operational measures appropriate to the service.
No network, device or software can guarantee absolute security. Protect your password and collection phone, and do not share login tokens or collection credentials with unrelated parties. Contact us if you suspect unauthorized access or disclosure. We will handle personal-information incidents and provide notifications as required by applicable law.
8. Your rights and account deletion
- Access: View your account, profiles, readings, history and alerts in the app. Email us for other information-access requests.
- Correction: Edit supported profile fields under Account → Batteries & gateways, or contact us about information you cannot correct yourself.
- Export: Use Account → Export last 24 hours, or email us about other requests for your personal information.
- Withdraw authorization: Manage optional system permissions, stop collection or revoke collection-device authorization. This does not affect previous lawful processing.
- Delete your account: Use Account → Delete account & data and confirm. The live service removes the account and associated batteries, readings, records and alerts; collection authorizations become invalid. Deletion cannot be undone.
- If you cannot sign in or have another request: Email easy_bms@163.com. We verify ownership as necessary to process access, correction, deletion or complaints. Do not send your password.
Export needed records before deletion. Uninstalling or signing out does not delete your cloud account, and signing out of the viewer does not stop independently authorized Android collection. If information cannot be deleted immediately or a request cannot be fulfilled, we explain the reason and available next steps.
9. Storage and cross-border processing
Accounts and uploaded battery data are processed and stored on servers providing Easy BMS. You can email us to ask about storage regions, service providers and backup arrangements. Notifications involve Apple or an enabled Android push provider, subject to that provider’s privacy rules and applicable law.
Where processing constitutes a cross-border transfer regulated by applicable law, we will meet the required notice, authorization and other legal requirements. Use of the service alone is not treated as separate consent to an undisclosed cross-border transfer.
10. Children and minors
Easy BMS serves users of battery-monitoring equipment and is not specifically directed at children. Users under 14 should use the service with a guardian’s guidance and consent. If you believe a minor’s personal information has been processed without necessary authorization, contact us so we can verify and take appropriate action.
11. Policy updates
We may update this policy for feature changes, service changes or legal requirements. The revised version and date will appear here. Material changes to processing purposes, methods or information categories will be disclosed, and renewed consent obtained where required.
12. Website and contact
These support and privacy pages require no login, include no advertising trackers or third-party analytics, and collect no information through web forms. The hosting service may log IP addresses, request times and browser request information for delivery and security. Email buttons only open your mail app; you decide whether to send a message.
For questions about this policy, personal information or account deletion, contact easy_bms@163.com. Use your registered email where possible, describe your request, and do not send passwords, verification codes or unrelated sensitive information.