Effective date: July 17, 2026
App: TCC Coordinator (com.tcc.coordinator)
Developer: Alfonso Davila (DynMEP)
Contact: dynmep@gmail.com
TCC Coordinator is an engineering tool for time–current coordination (TCC) studies of protective devices. This policy explains what data the app collects, why, and what your choices are.
When you sign in with Google, we receive your Google account email address, display name, and a user ID through Firebase Authentication. This is used solely to identify your account and associate your synced data with it.
Your coordination projects — project names, protective device settings, one-line diagram data, and study session data — are synced to Cloud Firestore (a Google Firebase service) so they are available on your other devices. If you never sign in, this data stays on your device only.
The app uses Firebase Crashlytics to collect crash reports and diagnostic information (device model, OS version, app version, and stack traces) so we can find and fix bugs. Crash reports are not linked to your identity by us.
The app uses Firebase App Check with Google Play Integrity to verify that requests to our backend come from a genuine copy of the app. This involves sending an integrity token from your device to Google.
Reports you export as PDF files are generated on your device and saved or shared only where you choose. They are not uploaded by the app.
Cloud data is stored in Google Firebase (Firestore) and protected by Firebase security rules so that only your authenticated account can access your projects. Data is encrypted in transit (TLS) and at rest by Google's infrastructure.
The app uses the following Google services, which process data as described above under their own privacy policies: Firebase Authentication, Cloud Firestore, Firebase Crashlytics, and Firebase App Check / Google Play Integrity — see the Google Privacy Policy and Firebase Privacy and Security.
TCC Coordinator is a professional engineering tool and is not directed at children under 13.
If this policy changes materially, the updated version will be posted at this URL with a new effective date.
Questions or requests: dynmep@gmail.com