Privacy Policy

• Account data — your full name, e-mail address, a hashed password (nobody, us included, can read the original), your role (student, teacher or administrator), the date the account was created, and the one-time invitation or access code redeemed to open it.
• Profile details you add yourself — on My profile you may add a short about you line and a profile picture. Both are entirely optional and empty until you choose to fill them in; you can change or remove either one at any time on that page. Who may see them is deliberately narrow: the picture fills the corner of the app you use, and the teachers of a course you joined see a small card with your picture, your name, your about line and the month you joined when they point at your name on their own roster, attendance sheet or message list — the same people who already see your name there. There is no public profile page, no page of other people's pictures, and no list of them. Nothing is shown to a person you do not share a course with, and students are not shown anyone's card. The picture is stored on our own server, is cropped and shrunk on the way in, and any camera data attached to the file (date, place, device) is discarded whenever the server can process images.
• Course activity — the courses you joined, how far you have read each material, how many seconds of each video you watched, and the lessons you completed.
• Assessments — the quizzes on your lessons, the answers you saved, your score and whether you passed.
• Attendance and live-class data — when you entered and left a live class, whether your hand was raised, the last time your browser checked in, and the IP address stored with an attendance entry (so an attendance record can be shown to be genuine).
• Messages — the text you send to a teacher or student, and when it was read.
• Certificates — the certificate code, the course, the issue date and the name printed on it. Certificates are publicly verifiable at verify_certificate.php by anyone holding the code — that is what a certificate is for.
• Content uploaded by teachers — the materials, files and video links added to a course, shared with the students enrolled in it.
• Technical data — the login session cookie (see the Cookie Policy) and the log entry written when something goes wrong, which can contain an IP address and a file name. We run no advertising, analytics or tracking scripts.

We never sell, rent or trade personal data, and we make no automated decisions about you — no profiling, no scoring, no data brokers.

The list of outside services is as short as the feature list allows, and each one receives only what its job needs:

• Our web host stores this site and its MySQL database, so all of the data above lives on their servers under our account. The data/ folder (error log, generated admin credentials) is blocked from the web.
• An e-mail delivery service (Brevo, SendGrid or Resend — whichever our administrator configured) receives the recipient address and the message so it can be delivered, and may keep delivery statistics. Mail can also go out through the hosting server's own mail service.
• Cloudflare Turnstile — only when the administrator has switched the human check on. It sees your IP address and browser signals and answers "human or robot"; the cookies it may set are listed in the Cookie Policy.
• Google Fonts — the page fonts come from Google's CDN, so your browser contacts Google and your IP address is visible to them. No cookies are involved.
• YouTube (privacy-enhanced mode) and Vimeo — a lesson that uses a video link embeds their player; only then do they see your request, and the player may set its own cookies once you press play.
• Jitsi / 8x8 — live classes run on the Jitsi server our administrator configured, so your display name and connection data pass through that service while a class is open.
• Authorities and auditors — only where the law, TESDA rules or a valid order require it, and only the records actually asked for.

Where a provider is outside the Philippines we rely on that provider's lawful transfer safeguards, such as the standard contractual clauses in its data-processing terms. Ask us for the details of the services in use on this installation.

• Passwords are stored only as one-way hashes, so a database copy does not reveal them.
• The session cookie is HttpOnly and SameSite=Lax, and it turns Secure on automatically over HTTPS — scripts cannot read it and a cross-site form cannot ride on it.
• Every form is protected against cross-site request forgery, and each page checks that the signed-in account is allowed to see it (a student cannot open a teacher's or another student's records).
• In lists shown to teachers, students' e-mail addresses are displayed partially masked.
• A profile picture is a photograph, so it gets the same treatment as the rest of the uploads folder: it is kept in a folder the web server refuses to serve directly and is streamed back one picture per request to the account it belongs to, to an administrator, and to the teacher of a course that account joined — never to anybody else, and never as a list. Knowing a user number is not enough: the signed-in session decides every time. Anyone refused, including a visitor who is not signed in, gets "not found" rather than a log-in prompt or a refusal that explains itself, so nothing is disclosed about who has a picture.
• Error details are written to a web-blocked file instead of being printed to visitors, and uploads are stored on the server, never on a public file-sharing site.

As a data subject under RA 10173 you may:

• be informed that your data is being processed (this page is part of that),
• object to processing based on legitimate interest, and to direct marketing — we send none,
• access the personal data we hold about you,
• have it corrected if it is wrong — most of it you can see, and a teacher or the administrator can fix the rest,
• ask us to erase or block it, subject to records we must keep (a certificate, a training record required by law),
• claim damages for a violation of your rights,
• obtain a copy in a portable form where the data was given electronically, and
• complain to the National Privacy Commission (privacy.gov.ph).

If you are in the EU, EEA or UK you have the equivalent GDPR rights, including restriction of processing, withdrawal of consent at any time (it does not affect what was already done lawfully), and a complaint to your local supervisory authority.

How to ask: e-mail fttccatbalogan@gmail.com with the subject "Data privacy request", or ask at the school office. Tell us which right you are using and from which e-mail address; we may ask one or two questions to satisfy ourselves that the request really comes from you. We answer within 30 days, and tell you if we need longer.

Training programmes often include minors. A guardian's consent is relied on for a trainee under 18 — the enrolment form at the school office is where that is given, and this page tells the guardian exactly what the system stores. A guardian can ask us to correct or remove a trainee's data at any time using the contact details above; we may need to keep the assessment and attendance records of a training programme that has already been completed.

The "Last updated" date at the top of this page always shows the current version. If a change is material — a new purpose, a new recipient — we will say so here and, where the law requires it, ask for your consent again the next time you sign in. Every account keeps the version it actually accepted, so we can always tell which text applied to you.