for students, parents, and campus IT

Security at facoolta

How we handle device data, optional Moodle tokens, feature boundaries, and campus due diligence without overstating certifications or uptime.

security posture

Principles

  • Local-first where practical - do not centralize what the device can hold safely.
  • Least privilege LMS - optional connection with scoped tokens in secure device storage.
  • Mobile WS integration - behave like a proper mobile client and respect campus policy.
  • Feature separation - studate is separately consented; academic features do not inherit dating permissions.
  • Status clarity - support and incident information should use verified operational data.

student controls

For students

  • You choose whether to connect Moodle features.
  • You can use facoolta without studate.
  • Report and block tools support social features.

campus review

For universities

facoolta Moodle Mobile integrationStudent device with facoolta talks to Moodle Mobile webservice, which talks to campus Moodle. Not scraping.Student deviceLocal-first featuresMoodle Mobile WSOfficial mobile endpointsCampus MoodleCourses, files, calendar
We integrate like a well-behaved mobile client — not by scraping the web UI. Open Mobile WS checklist

operations

Operational status belongs in support channels.

Public claims should be backed by verified logs, incident records, and customer approval. Security review starts with the LMS kit and privacy policy.

Support: support@facoolta.com

Read Privacy