Privacy Policy

What this policy covers

This policy describes what Pschola does with personal data in the student app, the teacher app, and the related websites. It replaces the text dated 21 October 2024.

Data we collect

• Name, email, phone number, profile photo, country, and language
• Date of birth, when it is provided, so we can tell if an account is under 18
• Messages, session bookings, exam results, and files you upload
• Device, IP address, and how the app is used
• Payment amount, currency, and the Tap charge reference for a paid lesson

Children

A student account with a date of birth under 18 is a minor. A missing date of birth is not treated as a minor. A parent creates the child account and records consent: who consented, when, and the terms version. A child may message teachers. The parent cannot read those conversations. The parent may add a profile photo for the child. Meta App Events and Adjust stay off while an under-18 account is logged in.

Who else receives data

ServiceAMX does not sell personal data. The services below receive data so the product can run. Each one processes it under its own terms, which can include storage outside Egypt and Saudi Arabia.

• Tap. For a card or local-method payment: the payer's name, email, phone, amount, and currency, so Tap can take the charge. A manual receipt, when that method is on, stays with ServiceAMX for staff to confirm.
• Zoom. For an online lesson: the teacher's display name in the meeting title, and the session time, so people can join. Pschola sets Zoom cloud recording to off.
• Google Meet and Google Calendar. Only for a teacher who connects a Google account: see "Google user data" below.
• Meta App Events. In both apps, when an adult allows tracking in Settings, and on iOS only after the Apple tracking prompt is allowed. Used to measure whether an install or sign-up came from an ad. Off for under-18 accounts.
• Adjust. In the student app only, on the same consent rules as Meta, including an install event. The teacher app does not include Adjust. Off for under-18 accounts.
• Firebase and Google. Sign-in, push notifications, analytics, crash reports, and performance data.
• Amazon Web Services. Account data and uploaded files are stored there. The configured region is eu-central-1 (Frankfurt).

Google user data

This section applies to teachers who connect a Google account in the teacher app (Settings, Teaching, Meeting links) to teach on Google Meet. Students and parents never connect a Google account for this. Signing in to Pschola with Google is separate and only gives us your name, email and profile photo.

What Google data we access

• Your Google account email, so the app can show which account is connected.
• Google Meet (scope meetings.space.created): we create a Meet room for each lesson you teach and read back its joining link. We cannot see or join your other meetings.
• Google Calendar (scope calendar.events.owned), only if you allow it: we add, update and remove events for your Pschola lessons. We only touch events Pschola created; we do not read your other events.
• A Google refresh token that lets the server do the above while you stay connected.

How we use it

• To create the Meet link for each booked lesson and show it to you and the student who booked it, during the lesson window.
• To keep your booked lessons in your Google Calendar: each event has the lesson time, the student's or group's name, and the Meet link.
• We do not use Google user data for advertising, we do not sell it, and we do not use it to train AI models. People at Pschola do not read it, except when you ask support for help, for security, or when the law requires it.
• Pschola's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements.

Who we share it with

The Meet link is shared only with the student, parent or group members booked into that lesson, so they can join. Google processes the data as the provider of Meet and Calendar. We do not share, transfer or disclose Google user data with anyone else, except if the law requires it.

How we protect it

• The refresh token is encrypted before it is stored and is never shown in the apps or the admin panel.
• All traffic to Pschola and to Google uses HTTPS (TLS).
• Data is stored on Amazon Web Services (eu-central-1), and only staff who run the service can reach the servers.

How long we keep it and how to delete it

• We keep the token and email only while your Google account is connected.
• When you switch back to Zoom in the teacher app, or delete your Pschola account, we remove your upcoming Pschola lessons from your Google Calendar, revoke Pschola's access with Google, and delete the token and email straight away.
• You can also remove Pschola's access at any time at myaccount.google.com/permissions.
• Meet links of past lessons stay in the lesson history. You can ask for any remaining Google-related data to be deleted by emailing support@pschola.com.

Deletion and what we keep

You can delete your profile in the app after you confirm your password, or after you sign in again with Google or Apple. You can also ask by email when that address can receive mail. If the message cannot be sent, the request is refused.

• The account is marked inactive.
• The email and username are replaced so the original address is not readable.
• The phone number is cleared.
• Name, profile photo, and date of birth are removed.
• The student, teacher, or parent profile is marked inactive.
• Messages, session history, exam results, and payment records stay so existing bookings, payouts, and payment disputes can still be answered.

There is no fixed number of days after which those remaining records are erased.

Your requests

To ask for access, a correction, or a question about this policy, email support@pschola.com.

This policy was last updated on 7 November 2026 (version 2026-09-24, with the Google user data section added).