DATA PROTOCOL.
// Telemetry handling, localized data storage, and external AI network communications.
1. Localized Execution
BenchCore is fundamentally designed to be a localized hardware platform. We do not run central servers that aggregate your power usage, hardware test cycles, or component telemetry. By default, the MQTT data stream exists entirely between your ESP32 hardware and your configured browser client. If you configure a public broker (like HiveMQ Cloud), your data transit falls under their respective privacy protocols.
2. Firebase Identity & Storage
If you utilize the Cloud Dashboard features (Account Login, Review Systems), BenchCore utilizes Google Firebase for Authentication and Firestore for database logging.
- User Identity (Email/Password hashes) are managed strictly by Firebase Auth.
- Public reviews and system evaluations are stored in plaintext in Firestore.
- Firestore Security Rules strictly prohibit unauthorized cross-account reading of private telemetry configurations.
3. AI Reasoning Module (DeepSeek)
Engaging the "Eva" AI telemetry reasoning system requires transmitting your real-time hardware metrics to external Large Language Model APIs (e.g., DeepSeek R1).