Security and Data Boundaries.
Classroom records stay on your device. This page explains where data lives, what Tabora Technologies receives to operate its services, and what you are responsible for securing.
Grades, lesson plans, student records, and intervention notes live on your device — not Tabora's servers.
Tabora Technologies never receives student names, grades, or identifiers from the desktop app.
Only billing, license, and account data goes to Tabora — kept strictly separate from classroom data.
Local database files, exports, and backups are your responsibility — secured by your own device and practices.
Classroom records stay on your device. Tabora Technologies receives only what is needed to operate accounts, subscriptions, licensing, updates, and support — not Educational Data from the desktop app. You are responsible for securing your device, local databases, and backups.
What stays on your device
The desktop app is local-first. The following data is stored on your machine or in systems you control and is not transmitted to Tabora Technologies: student names and identifiers, grades and assessment results, attendance records, behavior notes, intervention records and support plans, parent or guardian communications, locally stored gradebooks, local databases, local exports, and local backups.
What Tabora Technologies receives
To operate account, subscription, licensing, update, and support services, Tabora Technologies may receive:
- Account information: name, email, organization, subscription tier, license key, activation state, and account status.
- Payment metadata: customer identifier, subscription status, billing portal status, transaction status, tax status, refund status, and card-brand information if provided by the payment processor. Full payment-card numbers are not stored.
- Licensing and device metadata: installation identifier, app version, operating-system family, license-validation timestamps, and validation results.
- Update and download metadata: update request status, release channel, download authorization status, and server logs associated with update and download services.
- Support information: messages, contact information, screenshots, diagnostic logs, crash reports, and support bundles you voluntarily submit. Do not include student personally identifiable information in support submissions.
- Security and operational logs: IP address, authentication events, rate-limit events, session records, CSRF events, and request timestamps for account, licensing, and download services.
Account and session security
Account and dashboard services use HTTPS, session authentication, CSRF protections, and rate limiting. You are responsible for keeping your account credentials secure. If you suspect unauthorized account access, change your password and contact support immediately.
Your security responsibilities
Because the desktop app stores classroom data locally, you are responsible for: device access controls and physical security, operating-system and software updates, antivirus and malware protection, secure storage of local database files and exports, regular backups appropriate to your professional and institutional requirements, compliance with your school or district data security policies, and determining what data may lawfully be entered into the Software.
Support access
Support interactions are voluntary. When you submit a request, you choose what to include. Do not submit support bundles or screenshots containing student personally identifiable information. Support staff access the minimum information needed to resolve your issue.