MobLab

TeachApp / Scope

Privacy Policy

This policy describes data handling in the current Android version of the app.

Last updated: Android · 1.2.9

01Who is responsible

TeachApp is developed by Smolanov Serhii. Privacy contact: smolanovsergey@gmail.com. This policy applies to the Android app com.schoolapp.teacher, not future releases or third-party websites and services.

02Data processed

The app processes information entered by the user and operational records needed for its features. Records and settings are stored locally on the device.

TeachApp: student names and contacts (phone, email, messenger), notes, languages and levels, groups and membership, lessons and attendance, rates, payment records, balances, lesson and minute packages, and change history. Payment records are bookkeeping entries, not bank credentials.

03Purposes

Information supports record keeping, scheduling or project management, calculations, history, settings and backups. The current implementation has no registration, advertising SDKs, integrated analytics or upload of the working database to the developer's server.

04Files and backups

Exports are initiated through Android's system file or folder picker. JSON and CSV exports do not have additional app-level encryption: someone with file access can read the information. Choose a trusted storage location.

TeachApp supports manual JSON backup and restore and financial CSV export. Restoration replaces the current database. Android automatic system backup is disabled in the app configuration.

05Device access and third parties

The app uses access granted to a selected file or folder. The inspected implementation does not access the address book, camera, microphone or location. If you choose cloud storage, its provider receives the file under its own terms; the app developer does not operate that storage.

TeachApp declares notification permission in its manifest. This does not grant access to other apps' content. Permissions can be managed in Android settings.

06Retention and deletion

Local records remain until the user removes or clears app data. Archiving or hiding a record is not complete erasure. To remove the whole local database, use Android's Clear storage function or uninstall the app. Exported files, cloud backups and copies on other devices must be deleted separately.

07Security

Android limits access to the app's internal files. No additional app-provided encryption of databases or backups is claimed. Use a device lock, keep the OS updated and protect exported files. The developer has no remote access to your local database.

08Other people's and children's data

The app is a work tool for adult users. A user entering student, client or other personal information is responsible for a lawful basis, required notices and appropriate data minimisation. Requests about those records should first go to the teacher or organisation that entered them.

09Requests and your rights

Use the app and device settings to access, correct or remove local data. The developer cannot remotely change data they do not hold. Emailing smolanovsergey@gmail.com provides your sender address and voluntarily supplied message content for responding to your request. Such correspondence is kept only as necessary for support and applicable obligations. Do not send entire databases unnecessarily. Subject to applicable law, you may request access, correction, deletion or restriction of data provided to the developer and complain to a supervisory authority.

10Policy changes

The current revision date appears on this page. Before cloud accounts, analytics, payments or other processing are introduced, this policy must be updated. This version covers the inspected Android implementation and does not imply an iOS release.

Privacy enquiries

Smolanov Serhii

smolanovsergey@gmail.com ↗