Built for children, schools and parent trust.

Oyku collects and processes information needed to provide the service to schools, teachers, parents and students. This may include school account details, approved classroom photos or videos, class/activity metadata, parent contact details, teacher/staff account details, approval records and basic engagement logs.

Purpose of processing

• ✓To organise and share approved school memories with authorised parents.
• ✓To help schools prepare school-approved content drafts for public channels.
• ✓To support teacher and student recognition features.
• ✓To maintain security, access controls, audit logs and support workflows.

Children's information

Children's photos, videos and related school activity data are handled with additional care. Oyku is designed to support school approval, parent permission, visibility controls, opt-outs and deletion requests.

Contact

Privacy contact: privacy@oyku.app · General contact: hello@oyku.app

For school deployments, the school is expected to decide the purpose and scope of use, including which classes, teachers, parents and content types are enabled. Oyku processes data only to provide the agreed service and support approved school workflows.

School responsibilities

• ✓Define rollout scope, authorised users and approval roles.
• ✓Obtain or manage parent consent where required by law or school policy.
• ✓Maintain an opt-out list for students whose parents do not permit photo/video sharing.
• ✓Approve public sharing before content is posted externally.

Oyku responsibilities

• ✓Process school data only for agreed purposes.
• ✓Maintain reasonable technical and organisational safeguards.
• ✓Support access correction, deletion and export requests where feasible.
• ✓Notify the school of relevant security incidents according to the incident response process.

Oyku should be deployed using a clear parent consent workflow. Schools may use their existing photo/video consent forms, or use an Oyku-provided template adapted to the school's jurisdiction and policies.

Recommended parent choices

• ✓Allow approved private sharing with the child's parent/guardian account.
• ✓Allow inclusion in class/group memories shared with authorised families.
• ✓Allow school-approved public use on official school channels.
• ✓Opt out of public use while still allowing private parent memories.
• ✓Opt out of photo/video processing where required.

AI-assisted child matching

If Oyku uses AI-assisted child matching in the future, it should be optional, consent-led, controlled by the school and available only where appropriate under local law. Public-facing language should focus on “child-specific parent feed” and “school-approved tagging” unless consent and legal review are complete.

Oyku is designed around the principle that schools remain in control of sharing. Classroom photos and videos should be reviewed under the school's approval workflow before being shared with parents or drafted for public channels.

Content that should not be shared

• ✓Children on opt-out lists, unless cropped/removed or otherwise permitted.
• ✓Images involving injury, distress, disciplinary situations or private information.
• ✓Content showing sensitive documents, addresses, medical information or personal records.
• ✓Anything that could embarrass, target or unfairly single out a child.

Approval standard

Before sharing, staff should ask: Is this safe? Is it kind? Is it school-approved? Is it appropriate for the intended audience?

Oyku should retain school content only as long as needed for the service, legal requirements, school instructions and parent memory features. Schools should be able to request export and deletion according to agreed terms.

Oyku may use carefully selected third-party service providers to host, process, secure, communicate or support the service. Each vendor should be reviewed for security and data protection suitability before use.

Oyku should use practical security controls appropriate for a school platform handling children's photos and parent access.

Oyku should maintain an incident response process for suspected unauthorised access, accidental disclosure, system compromise, data loss or misuse of school content.

Response steps

1. 1Identify and triage the incident.
2. 2Contain affected systems or access.
3. 3Assess affected schools, users, data types and severity.
4. 4Notify affected schools according to legal and contractual obligations.
5. 5Remediate, document lessons learned and improve controls.

Different users should have different levels of access. A parent should not have the same visibility as a teacher, and a teacher should not have the same approval rights as a principal or authorised admin.

Oyku may help prepare public content drafts for official school channels, but public sharing should require approval from the school's authorised person.

Recommended workflow

1. 1Teacher or staff captures a school moment.
2. 2Oyku organises and prepares parent/social-ready content.
3. 3System checks visibility rules and opt-outs.
4. 4Authorised school user reviews the draft.
5. 5Content is approved, edited, rejected or rescheduled.
6. 6Only approved content is posted or exported for public sharing.