TalaKlasi · v3.1
Privacy Policy
Last updated: 21 October 2026
This notice explains how TalaKlasi handles information through talaklasi.com, its student portal, installed web app and Messages. It covers the service described here; your school's own privacy notices and recordkeeping rules may also apply.
1. Service and school responsibilities
The school or program using TalaKlasi is responsible for decisions about its academic records. Ask your school for the identity and contact details of its personal information controller or Data Protection Officer, its basis for processing your educational data, and its specific record-retention schedule.
TalaKlasi provides the platform's technical administration. Your teacher or school handles questions about enrollment, grades, attendance corrections and official academic decisions. For platform privacy and security concerns, use the contact below.
Service and privacy contact: Jeff Bernadas — System Administrator / IT. contact TalaKlasi Support. Ask for a secure channel for a privacy request. Do not post passwords, PINs, private conversations or complete academic records in a public comment.
2. Information the service processes
- Accounts and enrollment: names, student or employee IDs, account contact details where supplied, department, school year, semester, class, section, role and account approval/access settings.
- Academic records: attendance marks and session dates, assessment scores, grades, teacher remarks, quizzes and answers, submitted project files, rubrics and other records entered by authorized users.
- Communication: message text, sender/recipient identifiers, delivery and read timestamps, folders, friend requests and accepted connections, group names and membership, reply links, emoji reactions and edit timestamps, plus limited metadata for unsent messages. AcadHub stores your post text, optional photo, author and creation/expiry times, plus public comments and their author, request identity and time.
- School profile and Knowledge: an optional student profile photo and bio, the choice to display academic year/section, and Knowledge titles, explanations, code, tags, resources, visibility choices, comments, Helpful reactions and moderation records. Profile photos can appear in school community posts and conversations for other verified students and approved teachers or administrators. They are served through signed-in school access rather than a public photo directory.
- Preferences and notifications: appearance settings, notification state, optional push-subscription endpoints and keys, and the academic filters used for alerts.
- Security and operation: login/session identifiers, password or PIN hashes, access/error/rate-limit records, and technical details such as IP address, browser/device information or download activity where recorded by the application or hosting service.
Information comes from you, your school and authorized teachers or administrators, and from ordinary browser/server operation. Do not send passwords, PINs or unnecessary sensitive information in a chat.
3. Purposes and processing
The service uses information to verify access, manage classes, maintain academic records, show students their own results, deliver learning resources, run assessments, support school communication, save preferences, provide offline recovery and protect accounts.
Grades and attendance rates are calculated from saved marks and configured rules. Attendance intervention alerts identify recorded attendance of 60% or below for teacher review; they do not by themselves impose a disciplinary decision. Ask your teacher to review an incorrect mark or calculation.
Your school must identify the applicable basis for its educational processing, including the conditions required for sensitive educational information. Optional browser push requires browser permission. Accepting a friend request enables that chat connection; it does not authorize disclosure of academic records. This privacy notice is information about processing, not a blanket consent to unrelated uses.
4. Privacy within Messages
Messages are stored on the TalaKlasi server and are not end-to-end encrypted. The interface limits conversations to their participants. Authorized technical administrators can access stored data when necessary for operation, security, support or a lawful request. Do not treat this as an anonymous or confidential counselling service.
- Finding contacts: verified students can search other students by name or student ID for friend requests. Those search results show basic identity and connection state, not grades or attendance. Teachers are offered according to the student's enrollment; staff contact access follows the platform's permissions.
- Student friends: accepted friends can message each other. Removing a friend stops ordinary friend-based sends but preserves conversation history. A separate, unexpired AcadHub chat connection described below can still permit conversation.
- Story views and reactions: opening the full AcadHub reader records your verified student or approved staff identity and first-view time once per story. Thumbnail loading does not register a view, and the author's visits are excluded. Verified viewers can see the aggregate count; only the author can list viewer names through the feature. Emoji reactions store the selected emoji and student/staff identity, displaying aggregate counts and your own selection. View/reaction records are removed with subsequent expired/deleted-story cleanup; screenshots and backups can remain.
- AcadHub comments: comments are visible to the same student and staff audience as the story. The comment author, story author or an administrator can remove a comment. Removed comment text is cleared from the active comment record; limited request metadata and a text hash prevent duplicate retries. Comments are removed during expired/deleted-story cleanup. Reported evidence may remain separately for administrator review. Comment drafts are saved against the current account/story on the device.
- AcadHub chat replies: all verified viewers may send a private contextual chat reply to the author, even without friendship. Between students, sending a reply creates a temporary two-way chat connection until that story's expiry. Accepting friendship can permit continued student conversation afterward. Approved staff can also reply privately; continued staff conversations follow normal messaging permissions, including existing conversation history. The author receives your chat identity and reply text. Story text included in a delivered chat can remain in that conversation after the story expires. Chat drafts may remain in account-bound browser storage. Messaging and AcadHub bans are enforced separately.
- Group chats: a creator can invite available contacts, including teachers and accepted friends. All current group members can see member names and the group messages delivered to them, even if they are not individually friends. New members receive new deliveries only. Leaving or removal revokes access to the group, but other members keep their copies. Removing a direct friendship does not by itself leave a shared group.
- Replies, reactions and edits: participants can reply to visible messages and add an emoji reaction; the interface shows reaction counts and your own selection. Reply previews use the currently available original message. Only the sender can edit an available message, and an Edited label appears. This feature does not keep an edit-history transcript; an original-content hash remains for delivery checks, and earlier backups or recipients' copies may retain older text.
- AcadHub Day: approved text and optional photos are visible to all verified students and approved teachers/administrators, including students outside your friend list. Each student has one active Day. A valid new Day replaces the previous one, including while a new photo awaits moderator approval. Day posts become unavailable through the feed and photo endpoint after 24 hours, replacement or removal. Cleanup clears expired captions/photos; limited request metadata may remain during the original 24-hour window to prevent duplicate retries. Reports, saved chat replies, earlier backups or screenshots may remain. Uploaded photos are validated, resized and re-encoded to remove original metadata. When school photo approval is enabled, new Day and Knowledge post photos remain hidden until a moderator approves them. When it is disabled, new post photos can publish immediately for the selected audience. Existing pending photos still require review. Saved profile photos appear in school views without that post-review step. Avoid private educational records or another person's photo without permission. AcadHub feeds/photos are not stored in the shared offline cache; a text draft can remain in account-bound browser storage.
- Knowledge visibility and photo choices: Knowledge posts have no automatic Day expiry. Published community posts are available to verified school accounts; subject posts follow enrollment/faculty access, and private drafts remain with their author. The posting popup explains community rules before a new composer opens. The separate photo notice links to this policy before photo selection/upload. Disagree or Escape cancels that action; Agree allows the student to continue. These choices do not authorize unrelated uses of school records.
- Delete conversation: moves your conversation copies to Deleted, where you can restore them. It does not remove the other participant's copies.
- Delete for me: removes only your copy of the selected message. It is not a request to erase the server's entire record or the other participant's copy.
- Unsend for everyone: clears your message's text from the active message record and shows a placeholder to participants. Delivery identifiers, timestamps and a hash used to prevent replay can remain. This cannot undo a message already read, copied, exported, captured on a device, or retained in an earlier backup.
- Drafts and queued sends: are stored on the current browser/device against the verified account. Queued sends retry when the site is open or reopened online. Deleting an item from the local outbox does not retract a copy already delivered to the server.
Reports and moderation: use Report message, Report comment or Report AcadHub to send an accessible item and your explanation to approved administrators. The report includes your identity, the reported author's identity, category, details and a saved copy of the item text and any reported photo. Administrators see the report and saved evidence; the reported account does not receive your report or reporter identity through this feature. A report does not automatically restrict anyone.
Saved evidence may remain after the original item is edited, unsent, deleted or expires. Administrators can review or dismiss reports, remove reported AcadHub or comments, impose or lift feature-specific access bans and explicitly clear closed-report text/photo evidence. Report metadata, restriction reasons and administrator action history can remain for accountability under the school's retention arrangements. Ask your school or Support for the applicable schedule.
Messaging and AcadHub access restrictions are separate from academic-record access. The affected account sees the administrator's restriction reason and any expiry, but not the reporter identity. Contact Support for a review request or urgent help. Recipients can copy or screenshot content; reporting is not an emergency service or a promise of immediate monitoring.
5. Cookies, offline copies and notifications
Session cookies keep access associated with your browser. Student Portal sign-in also uses a random HttpOnly device cookie, with only its hash stored in the database against your student ID and PIN version. The remembered device lasts up to one year between renewals and is revoked by portal logout or a changed/reset PIN. A separate student app launches /portal. Verified academic records may be saved in the portal browser database for offline reopening; PINs, remembered-device secrets and project access grants are not stored in that offline record. Portal logout clears this saved view on the device and other open portal tabs. An offline logout blocks automatic sign-in locally until server revocation can finish when online. Local storage, IndexedDB and service-worker caches support settings, visited pages, selected academic filters, drafts and pending edits. Full chat history and backup ZIPs are excluded from the shared service-worker cache, but local drafts/outbox entries and previously loaded content may still be present on the device.
On a shared device, sign out and protect the browser profile. Sign-out must not discard unacknowledged work, so it does not erase every local draft or queued edit. After confirming required work has synced, you can use browser settings to clear site data. Clearing storage or uninstalling the app can lose unsynced work and does not by itself delete server records.
In-app alerts work through the site. Optional push delivery uses the browser/operating system's push service, which receives subscription/delivery information. Notifications may be visible on a device lock screen. You can change notification permission in the browser or operating system; installation and push permission are separate choices.
7. Retention and removal
Academic record retention depends on the school's recordkeeping schedule and applicable obligations. Ask your school for the specific period. This version does not configure a fixed automatic expiry for chat messages or friend records: they remain until an applicable deletion or administrator-managed retention action occurs. Folder deletion and account sign-out do not mean all records have been erased.
Technical logs, backup copies and exported records can have separate retention periods controlled by the host, school or person holding the copy. Request the applicable schedule through Support or your school. Local drafts and offline data may remain until synchronized, removed within the relevant feature, or cleared from browser storage.
8. Privacy rights and requests
Under applicable Philippine data-protection law, you may have rights to information, access, correction, objection, erasure or blocking, data portability, a complaint and remedies, subject to the conditions and exceptions that apply. A request does not automatically override required school recordkeeping or the rights of other people.
Contact your school for academic-record requests and Support for platform privacy requests. Describe the request and provide a safe contact channel; identity or representative authority may need verification. Parents or authorized guardians may coordinate requests for minors with the school.
For independent guidance or a privacy complaint, see the National Privacy Commission's data-subject rights information and right-to-be-informed guidance.
9. Safeguards and policy updates
The platform uses account checks, student PIN verification, request protections and access restrictions; server connections use HTTPS on the live site. No storage or network service can promise absolute security. Keep your credentials private and report suspected unauthorized access promptly.
The date and version identify this notice. Material changes should be communicated through the site or school before a new use that requires notice or a separate choice. The Terms of Service describe acceptable use; they do not remove statutory privacy rights.
10. Contact and requests
Service and privacy contact: Jeff Bernadas — System Administrator / IT. contact TalaKlasi Support. Ask for a secure channel for a privacy request. Do not post passwords, PINs, private conversations or complete academic records in a public comment.
For enrollment or academic-record questions, contact the teacher, school administrator or school privacy officer responsible for those records.
AcadHub knowledge and student profiles
Knowledge posts are lasting academic contributions, separate from the 24-hour stories. Community posts are visible to authorized accounts within the same department; My Subject posts require the selected class enrollment or authorized staff access. Private drafts are visible only to their author. Titles, formatted explanations, code, resources, tags, contributions, discussions and endorsements are stored on the server. Bookmarks are private to the student who saves them. Optional profile photos, bios and the choice to show year/section are stored against the verified student account; official academic records are not changed by profile settings.
Knowledge photos are resized and re-encoded. Academic files are kept in private storage and downloads check access again. External reference links are not fetched by the server to build previews. Your browser contacts the referenced site when you open its link. Do not upload private student information, unauthorized exam materials or resources you are not entitled to share.
Device drafts and a small amount of your own profile/subject metadata are stored in account-specific IndexedDB storage. They can contain your explanation and selected files. Portal logout clears this knowledge store. Knowledge feeds and attachments are not saved in the shared offline shell cache; previously loaded content can remain on the screen when a connection drops. Reopening uncached community posts requires online verification. Publishing requires a server confirmation.
Reports include your account identity, reason, details, a snapshot of the reported explanation or comment, and a reference to any reported resource. Approved faculty and administrators can review reports, hide/restore posts, remove attachments or comments, and record reasons in a moderation history. A faculty endorsement identifies a reviewed version; editing a post or changing its resources clears previous endorsements. Removal from the visible feed does not immediately erase retained reports, files or backups. Retained files count toward the account resource quota; ask Support about removal and the school's applicable retention arrangements. Relevant discussion, mention, endorsement and moderation updates use the existing notification inbox, with repeated low-priority updates grouped where practical.
School safety filtering and delegated moderation
Administrator-configured word rules block New Day captions/comments and mask matching terms in new or edited chat messages on the server. Knowledge contributions/comments and profile bios are not blocked by these word rules. Rules can include related words, spelling variants and academic exceptions. These checks can make mistakes; contact Support if legitimate academic work is blocked. They do not automatically understand every language, synonym or the content of an image or attached document.
New images in Day and knowledge posts remain hidden until a school moderator reviews them. Trusted students assigned by an administrator may review community knowledge and Day content, hide or remove it, and apply limited temporary AcadHub restrictions. This role does not grant access to private messages, private drafts, subject-only moderation content, private reports, administrator evidence or academic-record editing.
Administrator activity records identify the actor, target, time and reason for decisions and role/rule changes. Removing content through the safety tools retains a copy of its text, Day photo or protected knowledge resource references for administrator review. Retained knowledge resources remain in private storage. Student moderators cannot retrieve this administrator evidence. Administrators can revoke assignments and review restrictions. Evidence and action records follow the school's applicable retention arrangements; contact Support for a review or data request.
Department community and word filtering
Portal community feeds, contact discovery and conversations are restricted to the student’s latest active enrollment department and the staff member’s active assigned department. Administrators retain access to safety evidence for oversight. Unassigned departments need administrator correction.
School word rules block New Day captions and comments. Matching terms in new or edited chat messages are replaced with asterisks, and the message can still send. These word rules do not block AcadHub Knowledge posts, Knowledge comments or profile bios; school conduct rules, reports and moderation still apply.
Deleting or replacing a New Day removes it from the live feed and retains its text, photo, author information and deletion decision as administrator evidence. Student moderators can remove rule-breaking content within their department. Retained evidence and private message reports are restricted to administrators.