Privacy at Koko Learning

Information the service handles

• Accounts and access: names, email addresses, account and role identifiers, password hashes, school/appearance choices, sign-in and reset records, session and authorization identifiers, device labels, expiration and revocation records.
• Classes and participation: class and semester associations, enrollment, attendance/check-in times and confirmation, class history, selections, quiz and ranking answers, ideas, drawing content, votes and other submitted class responses.
• Review games: saved Exam Review answers, teams, points and results.
• Communications and safety: student/professor conversations, associated read/retry records, support correspondence, reports, blocking choices, moderation decisions and account-request receipts.
• Images: photos or other images uploaded through enabled account or classroom web features. Uploading an image is different from scanning a class QR invitation.
• Choices and security: the age-threshold declaration and policy acceptance, request timing/rate limits and information needed to prevent abuse and protect accounts.

Our hosting provider, ICDsoft, reports that HTTP access logs include IP addresses, request time, URI, status, referrer and user agent, and an HTTP-authentication username when that protection is used. FTP and mail-delivery logs contain related operational metadata. A hashed or opaque identifier is not necessarily anonymous.

Why information is used and who can see it

We use information to sign you in, authorize the right classes, operate attendance and activities, show class history and results, provide conversations and support, handle account and safety requests, and keep the service secure and working.

Your professor can see authorized enrollment, attendance and responses for their class. Student/professor conversations are scoped to that student’s class conversation. Class activities can share results or content with the class or a projector under their sharing rules. Others may recognize something you write or draw even when a result does not show your name.

Authorized Koko operators may access information for service, support, safety and account handling. Hosting, email and other service providers process information needed for the features they provide. An optional integration can involve its provider when that feature is used; a configured provider does not mean it receives every student’s records. We do not describe school colors as school sponsorship or blanket authorization to disclose records.

Your device, cookies and camera

The web application uses sign-in session cookies. The native student app uses protected device storage for its rotating sign-in credential and remembers the selected class ID for that account. Unsent drafts stay in memory and are not automatically queued for delivery after reconnection.

QR scanning begins when you choose it. QR codes are decoded on your device; confirming an invitation sends the information needed to review or join that class. A scan does not automatically check you in. An uploaded check-in/profile photo is separately stored by the service.

Signing out of the app does not sign out a separate web session. Closing or uninstalling the app does not delete server-side accounts or class records. Sign out on shared devices and check which account is shown before approving a connection.

Questions, corrections and account deletion

For attendance corrections, enrollment or class results, contact your professor. For account access, corrections or privacy questions, contact Koko support. We may need to verify your identity before discussing account information.

Eligible signed-in students can start a deletion request at Account deletion. The form explains the scope and requires password and request confirmation. You do not have to email or call to initiate the request. Keep the receipt and use the available request status while the account is active.

Requests are handled manually by the authorized operator. Our commitment is to handle a verified request concerning the active Koko account and associated application data within 30 calendar days of the original request and communicate the verified outcome. Specific records that must be retained, and their reason and handling, must be explained rather than silently treated as deleted.

A queued request, disabled sign-in, removed enrollment, hidden response or prepared notice is not completed account deletion. The operator sends the verified outcome by manual email confirmation; automatic deletion emails are not enabled. If you need help with an outcome, contact support with your private receipt. Deleted accounts do not retain ordinary signed-in access.

School-record responsibilities may also apply to course records. This notice does not replace a school’s authorized access, correction or records process, or promise a blanket exception for every academic record.

Retention, completion records and backups

Account, class, communication and security information is retained for the service purposes described above and any specifically applicable record obligation. Account deletion is reviewed against the actual records and dependencies, not just an account-name change. Required retained data must have a specific reason, limited access and appropriate disposition.

Our approved completion-record schedule limits the completion contact to 30 days after verified completion and the minimal completion audit to 90 days after verified completion. This is a manually operated schedule, not a claim of automatic background cleanup. These periods are separate from the 30-day request-handling commitment and the hosting periods below.

Restricted recovery/suppression records are kept separately to prevent a restored backup from recreating a deleted identity, records or valid sign-in authority. The minimal completion-audit period does not mean those recovery protections are erased. They are not ordinary class records or an advertising dataset.

ICDsoft reports retaining HTTP and FTP logs for 24 months and mail-delivery logs for 6 months. It reports daily automatic account-file and MySQL snapshots retained for up to 15 days. Saved/manual exports are separate; the automatic snapshot period does not establish their expiry.

Data removed from the active service may remain in restricted pre-deletion backups. Before a restored service is reopened, completed deletions and credential revocations must be reconciled. Neither request handling nor the periods above are a promise that every backup, provider log or physical copy is immediately erased.

Safety and security

Use the available report, hide and block controls for a classroom-content or communication concern. You can also contact Koko support. The operator reviews the moderation inbox daily. Reporting is not an automatic email alert or an automatic finding that someone broke a rule.

Role, enrollment, sign-in, moderation and technical safeguards help restrict access and handle concerns. They cannot guarantee that objectionable content or a security incident will never occur. Avoid placing unnecessary personal information in class responses or shared images.

Audience and changes

The student service is intended for people aged 13 or older in the United States. Its age declaration is a self-declaration, not verified age or identity. The App Store’s content rating is a separate assessment. Do not create or use a student account if you are under 13; contact support if you believe an under-13 account needs attention.

We update this notice when service practices change and show its current date here. Where a changed policy requires a new account choice, the service’s current-policy acceptance process applies.