Log4Tutor (Tutor Session Log)
Effective Date: September 24, 2026
Developer: M-PAX Group · App: Log4Tutor (iOS, iPhone, iOS 17+, Bundle ID net.m-pax.Log4Tutor)
Log4Tutor gives a private tutor one fast record for their teaching business: log each session in seconds, send the parent a polished summary, and turn logged sessions into per-term invoices. It is designed so that we, the developer, do not operate a server, do not create accounts, and do not receive your tutoring records.
Short version:
We collect nothing automatically. Log4Tutor contains no third-party analytics, crash-reporting SDKs, advertising SDKs, session replay, or fingerprinting. We do not sell personal data and we do not share personal data with data brokers.
The only personal information we ever receive is what you choose to send us yourself, for example if you email [email protected] for support. We use such messages only to answer you, and we delete them on request.
Anything you record (tutor and business names, signature, student names, subjects, rates, parent names and contact details, session topics, ratings, notes, terms, invoices, summaries, settings) is stored in two places, both under your control:
TutorSessionLog-Backup-YYYYMMDD-HHmmss.tzbak: full record export in JSON plus a manifest with app version, schema version, record counts and checksum) in the app’s own folder (Documents/Tutor Session Log/Backups), keeping the 5 most recent. Backups count toward your Apple storage quota. If iCloud is unavailable, backups fall back to local Application Support.Apple processes iCloud Drive data under your Apple services relationship — please see Apple’s Privacy Policy for Apple’s handling. There is no CloudKit database, no developer backend, and no cross-device sync beyond your own iCloud Drive backup/restore.
| Category | Examples | Stored where |
|---|---|---|
| Tutoring content you enter | Student names, subjects, rates, parent names/phones/emails, session topics, ratings, notes, terms, invoices, summaries | Your device + your iCloud Drive backups. Never on a developer server. |
| Device-private settings | Currency, due-day defaults, reminder lead time, quiet hours, template text, footer toggle, appearance, diagnostics you choose to copy | Your device only (backed up as part of your archive). Never synced anywhere else. |
| Purchases | One-time-unlock entitlement status | Apple App Store / StoreKit; the device keeps a local unlocked flag. Payment, records and refunds are Apple’s. |
Log4Tutor deliberately does not ask for precise location, contacts upload, HealthKit data, or photo-library access. Student and parent details are exactly what you typed — there is no enrichment, matching, or profiling. In-app diagnostics (“Copy diagnostics”) contain only app/iOS/schema versions, record counts and backup status — no names or contact details.
.ics) file opened in the share sheet — it is a download, never calendar sync (no EventKit, no calendar access).Log4Tutor has no parent accounts, no parent portal, and no in-app messaging. Parent communication happens only through your explicit share-sheet actions: session summaries via your WhatsApp/SMS/email, invoice PDFs, CSV exports, .ics files, and the full JSON export. Nothing is transmitted anywhere by the app except through those actions you initiate.
Log4Tutor offers one StoreKit 2 non-consumable one-time unlock (tutorsessionlog.pro.unlock): the first 20 logged sessions are free with full features, then unlimited logging requires the single purchase. The exact price shown in the app comes from the App Store — it is never hard-coded. Payment, renewal records and refunds are handled by Apple, with a Restore Purchases button in the app. If you do not purchase, only new session logging is gated: existing sessions stay viewable, searchable, summarisable, invoicable and exportable, free, forever.
Use of the app is governed by Apple’s Standard Licensed Application End User License Agreement: https://www.apple.com/legal/internet-services/itunes/dev/stdeula/.
App Privacy: Data Not Collected applies to the developer. User-entered tutoring content is stored by the user on-device and in the user’s own iCloud Drive at the user’s direction and is not collected by the developer. Purchase handling is via Apple Commerce (StoreKit). The app declares no tracking and includes no third-party SDKs.
.ics files and “Export everything” (JSON of all records + CSVs) — available even without purchase.Because there is no developer account or database, privacy access/deletion requests are fulfilled by these in-app steps. If you need help, email us and we will walk you through them.
Records are protected by iOS file protection and Apple’s iCloud Drive transport/storage protections. Money is computed with decimal arithmetic (never floating-point) and paid-invoice immutability is enforced in the app’s service layer, not just the UI. Logs and diagnostics redact names, notes and contact details. Temporary export files are deleted after sharing or on next launch.
Log4Tutor is a record-keeping and communication aid: it records what happened and what is owed. It does not move money, does not sync calendars, and does not message parents itself. “Mark paid” records a payment you received directly (bank transfer, cash). Fee figures derive from rate × duration as shown in the app; bank details are intentionally not stored — communicate them to parents yourself.
Log4Tutor is intended for adult private tutors. We do not knowingly collect children’s data as a developer; any student names a tutor chooses to record are stored only on the tutor’s device / the tutor’s iCloud Drive as described above.
If privacy practices change (e.g. a future optional analytics feature), this page will be updated with a new effective date, and the app’s privacy manifest / App Privacy labels will be updated before release. Material changes will also be noted in release notes.
Developer: M-PAX Group.
Privacy / support: [email protected]
Support page: https://m-pax.net/log4tutor.html
If you are in the UK/EU and have a data-protection question, include “Log4Tutor privacy” in the subject line and we will respond. Since we hold no developer-side account data, most requests are resolved with the in-app export / delete steps in section 9.