operational policy
Privacy Policy
Last updated (Asia/Jerusalem).
Overview
facoolta provides a student operating layer for academic life. This policy explains how we handle account data, campus context, LMS connections, support requests, and optional social features.
Local-first where practical
Semester configuration, preferences, cached materials, and feature state stay on the device when the product can safely support that behavior. Server processing is used for account operations, support, institutional reporting, synchronization, and services that require shared infrastructure.
LMS and Moodle tokens
Moodle connection is optional and follows campus policy. When you connect, LMS tokens are stored in secure device storage and used for the academic features you authorize. facoolta uses Moodle Mobile webservice patterns; universities can review the LMS integration kit.
Authentication
Sign-in methods depend on the active app release, platform channel, and institutional configuration. Public marketing and legal copy should describe only authentication methods that are verified in the current release.
studate
studate is optional, age-gated at 17+, and covered by separate consent. Academic features do not require studate permissions, and dating or social graph data is not mixed into LMS grade or coursework surfaces.
Website access requests
The marketing site access and partner forms collect the contact fields you submit, such as name, email, institution, role, platform, and message. We use those details to respond to student, faculty, IT, and institutional deployment questions.
Marketing claims
Customer stories, adoption figures, and distribution URLs should match approved business records. Real universities are not presented as customers without explicit approval.
Cookies
See Cookies for marketing-site cookie and local storage practices.
Contact
Privacy questions: support@facoolta.com