TechDash (com.alextricity.tdb) is an IT-operations tool used by the technicians and administrators
who manage technology for an organization — typically a school district or similar institution — whose IT is
run by a managed service provider (MSP). It is a staff application: it is not a consumer product, it is not
advertised to the public, and it is not directed at children. This policy explains what the app handles, why,
and where that data lives.
TechDash is used only by authorized staff — the IT technicians and administrators of an organization that runs the TechDash dashboard — to carry out their day-to-day work. Access is granted by the organization and controlled through the staff member's Google Workspace account and an assigned role (admin, technician, or viewer). There is no public sign-up, and members of the general public cannot create accounts or use the app.
The app is published by Alextricity Technologies, LLC, a managed service provider that operates the TechDash dashboard for its customer organizations. Each organization's data is held on that organization's own TechDash server.
TechDash does not ship with a list of organizations. When you first open the app, you enter your work e-mail
address. The app uses only the domain of that address (the part after the @) to look
for your organization's TechDash server: it requests a small public discovery file
(/.well-known/techdash-tenant.json) over HTTPS from your organization's own domain. That request
carries no credential and no personal data — the domain name is the only thing sent. The app then shows you the
organization's name and server address and asks you to confirm before anything is saved. The e-mail address you
typed is used to pre-select your account on Google's sign-in page and is not stored by the app.
TechDash does not run its own data collection for advertising, profiling, or analytics. It handles two kinds of information, both in service of your IT work:
| Data | Why it's used |
|---|---|
| Your Google email | To identify you and keep you signed in. |
| Your name | Shown in the app and attributed to your actions (e.g. ticket activity). |
| Your role | Admin, technician, or viewer — determines what you can see and do. |
| Your profile picture | If your Google account provides one, it is displayed in the app. |
| Session credential | A session identifier issued by your organization's server after you sign in, stored securely on your device together with the address of the server it belongs to (see below). No password is ever stored by the app. |
| Your organization's server address | Remembered on the device after a successful sign-in so the app knows which server to talk to. Cleared when you choose Switch organization. |
Once signed in, and depending on your role, the app lets you view and work with your organization's IT-operations data, which may include:
This operational data is the organization's own information. The app is a window onto the organization's server that stores it — the app does not collect it for its own purposes or copy it anywhere else.
You sign in with your organization's Google Workspace account. The app opens Google's sign-in flow in a secure
in-app browser; Google authenticates you and returns you to the app. TechDash never sees or stores your Google
password. After a successful sign-in, your organization's server issues a short-lived, single-use code to the
app, which the app exchanges for a session credential; the credential is kept on your device using
expo-secure-store (backed by the Android Keystore / iOS Keychain). When you log out, that credential
is removed from your device.
All TechDash data is stored on a server operated for your organization — the one the app discovered from your e-mail domain and showed you at sign-in. The app talks only to that server (and to Google for the sign-in you initiate). It does not send your data to any third-party analytics, advertising, cloud-storage, or data-broker service.
On your device, the app keeps only what it needs to function: your session credential (stored securely as above), the address and display name of your organization's server, and small local bookkeeping values — for example, which alerts it has already shown you, so it does not notify you twice. These local values contain no advertising identifiers and are cleared when you log out or switch organization.
The only outside services involved are Google (for the sign-in you initiate) and — once push is enabled — Google's push-delivery service acting purely as a delivery pipe, described next.
Today, TechDash uses local notifications only. On a periodic background check, the app asks your organization's server whether anything relevant to you has changed — for example a new helpdesk ticket, a network node going down, or a switch going offline — and if so it raises a notification on your device. No push tokens are used, and nothing about these checks leaves the connection between your device and your organization's server.
When push notifications are enabled in a future release, the app will use Firebase Cloud Messaging (FCM), part of Google Play services, as the transport that delivers alerts to your device. In that case:
The version of TechDash distributed through Google Play uses these Android permissions:
| Permission | Why it's needed |
|---|---|
RECEIVE_BOOT_COMPLETED |
So the app can resume its background alert checks after the device restarts, without you having to reopen it. |
| Camera / photo library | Only when you choose to attach a photo to a helpdesk ticket. The app never reads your photos or opens the camera on its own; the photo you pick is sent to your organization's server as a ticket attachment and nowhere else. |
The app also uses standard notification and network access to show alerts and talk to your organization's server.
Google Play build does not self-update. Updates to the Play build come through Google Play. The
Play build does not request the REQUEST_INSTALL_PACKAGES permission. (An organization may separately
receive a direct-install build from its MSP that updates itself from the organization's own server; that build is
not distributed through Google Play.)
Your account and the operational data you work with are retained by your organization for as long as you are an authorized staff member with access, and thereafter in line with the organization's and the MSP's normal records-retention practices (records such as helpdesk history and timeclock entries are the organization's business records). When your employment or access ends, your access to the app is revoked.
On the device, logging out clears your stored session credential and the app's local bookkeeping values; Switch organization additionally forgets the server address.
Because all data lives on your organization's server, deletion is handled there — not through any app-store mechanism. If you are a staff user and want your account or associated personal data reviewed or removed, contact your organization's IT team or the MSP at tdbapp@alextricity.com. Requests are handled subject to the organization's legal and records-retention obligations.
TechDash is a staff tool and is not directed at children. It is not offered to students and has no features intended for a general or child audience.
Where the organization is a school, authorized administrators can, as part of their duties, view student directory records drawn from the organization's student information system and Google Workspace (for example a student's name, school email, grade, school, and account status). These are the organization's own education records, governed by applicable law — in the United States, the Family Educational Rights and Privacy Act (FERPA) — and by the organization's policies. They are accessed by authorized staff through the app, not collected by the app for its own purposes, and they are never shared with third parties or used for advertising. Questions about student records should be directed to the organization.
Traffic between the app and your organization's server uses encrypted HTTPS; the app never downgrades to plain HTTP. Sign-in uses a short-lived single-use code bound to your device (PKCE), so a session credential is never carried in a link. Your session credential is stored in the device's secure keystore rather than in plain application storage, and is only ever presented to the server it was issued by. Access to data inside the app is scoped to your assigned role, and administrative functions (such as student lookups) are restricted to administrator accounts. No method of storage or transmission is perfectly secure, but access is limited to your organization's authorized staff.
We may update this policy as the app evolves — for example when push notifications are turned on. When we do, we will revise the "Last updated" date at the top of this page. Material changes affecting staff users will be communicated through your organization or the MSP.
This app is published and operated by Alextricity Technologies, LLC on behalf of the organizations it serves. For privacy questions, deletion requests, or any concern about how TechDash handles data, contact:
Alextricity Technologies, LLC
Email: tdbapp@alextricity.com