Privacy Policy

Summary

SeshLog is an on-device tool for safety instructors to log course participants. All participant data — names, ID numbers, phone numbers, personal photos, and ID-card photos — is stored only on the device where it was entered. SeshLog does not operate any server that receives, stores, or processes this data. Nothing is uploaded, synced, shared, sold, or analyzed.

Who this policy is from

SeshLog ("we", "the app") is published by Ali Alrwaished. For questions about this policy, contact alibnsami7@gmail.com.

Who is responsible for participant data

The instructor or organization using SeshLog (the "operator") is the data controller for the participants they enroll. The operator is responsible for obtaining each participant's consent before recording their name, ID number, phone number, photo, and ID-card image, and for complying with applicable local privacy laws (e.g. GDPR, CCPA, PDPL). SeshLog is a tool provider and does not have access to participant data.

What SeshLog collects

When the operator enrolls a participant, SeshLog stores on the device:

• Full name
• ID number (as entered by the operator)
• Phone number (optional)
• Personal photo (captured by camera or chosen from gallery)
• Photo of the ID card (captured by camera or chosen from gallery)
• Attendance records linked to the operator's courses

SeshLog does not collect device identifiers, location, contacts, microphone audio, advertising IDs, crash analytics, usage analytics, or any other telemetry.

Where the data is stored

All data is stored in the device's local browser storage (IndexedDB) sandboxed to the SeshLog app. When the operator taps EXPORT, the ZIP file (roster PDF + original photos) is generated on the device itself — no server is involved in building it. The resulting file stays on the device until the operator chooses to share or save it (for example, sending it via WhatsApp, saving to Files, or emailing it). SeshLog never uploads participant data, and there is no SeshLog backend that receives it.

Permissions used

• Camera — to capture participant and ID-card photos. Requested only when the operator taps the Camera button.
• Storage — to save records locally on the device.
• Photos / Gallery — only the single image the operator picks is read; SeshLog cannot see other photos.

SeshLog does not use Location, Contacts, Microphone, Bluetooth, SMS, Call Logs, background data, or push notifications.

Third-party sharing

None. SeshLog includes no advertising SDKs, no analytics SDKs, no crash-reporting SDKs, and no third-party trackers. No participant data is sold, rented, or shared with any third party by SeshLog.

Children

SeshLog is not directed at children. Operators are responsible for ensuring they have appropriate parental or guardian consent before recording any participant who is a minor.

Data retention

Data persists on the device until the operator deletes individual records, taps DELETE ALL, manually clears the app's browser site data, or uninstalls / removes the app from the device's home screen.

Your rights

Because all data is on the operator's device, the operator can exercise the following rights immediately, without contacting us:

• Access / export: tap EXPORT to download a ZIP containing a roster PDF and the original photos.
• Correction: tap any row to edit the record.
• Deletion: open a record and tap the Delete button, or tap DELETE ALL to wipe the device's log.

Security

Data is sandboxed by the browser to SeshLog's origin and cannot be read by other websites or apps. Because nothing is transmitted, there is no in-transit risk. We recommend operators protect the device with a screen lock and device encryption, and avoid using SeshLog on shared or unmanaged devices.

Changes to this policy

We may update this policy from time to time. The effective date above will reflect the latest revision. Material changes will be surfaced in the app's user guide.

Contact

Questions or requests: alibnsami7@gmail.com.

See also: Data Safety summary.