Funda

Privacy Policy

Last updated: 7 November 2026 · Version: 2026-11-07-feedback

Funda helps learners practise school subjects and lets authorised families follow their learning. This policy explains how personal information is handled when you use Funda, including its guest preview.

1. Who is responsible

Funda is operated by Sunnergy (Pty) Ltd, the responsible party for the processing described here.

Contact the Information Officer if you have a question, want to exercise a privacy right, or believe a child’s information was provided without appropriate authority.

2. Information we handle

Parent or guardian accounts. We handle your email address, account identifier, authentication information, account communications and the links between your account and learner profiles. Password authentication is managed through Supabase. When Google sign-in is offered and you choose it, Google may provide your account identifier, email address, name and profile image under the requested basic identity permissions. Funda does not ask for your Google password or access to your Gmail messages or Drive files.

Teacher registration pilot. When enabled, teacher registration collects an adult’s first name, optional middle name, surname, requested school association, a copy of their ID and a school confirmation letter. These documents may contain an identity number, photograph, signature and employment information. Provide only the requested documents and avoid unrelated personal information. Files are held in private Supabase storage, separate from public application assets. Registration records also include file type/size, receipt times and a server-recorded acknowledgement of the teacher notice. Teachers cannot browse other teachers’ documents, and documents are not shared with learners or published in school listings.

During this pilot, successful receipt of both supported uploads produces “Registration Successful with Document Review Pending.” This is an automatic pilot receipt outcome, not an AI verification of identity, employment or document authenticity. ID documents and school letters are not sent to an AI provider in this pilot. For this pilot, completing registration grants access to learner usernames, grades and learning progress at the selected active school while document review remains pending. This school-wide pilot access does not require a separate parent-to-teacher link. It does not grant parent credentials, learner access-code administration or permission to edit family profiles. Access is removed when registration is denied or a learner leaves that school. Class-based teacher access and parent class selection are planned for a later release. Review arrangements and any future external document processing require a separate implementation and appropriate notice. Contact the Information Officer to correct or withdraw a registration, request deletion, or ask about access and retention; account inactivity does not automatically delete documents. Do not upload a child’s ID for teacher registration.

Assessments and shared events. Where delivery features are enabled, authorised adults can publish a fixed assessment paper for eligible learners, with opening/due times and optional attempt timers. We store selected recipients, saved answers, written responses, private submission attachments, submission/deadline times, marking status, feedback and review records. Supported submission files are PDF/JPEG/PNG, up to five files, 10 MB each and 25 MB total per attempt. Completed submissions are locked; deadline expiry can submit previously saved answers automatically. Organiser extensions, reschedules, cancellations, result releases and review decisions are recorded. In-app notifications and bounded completion/start reminders contain the assessment title and lifecycle status. Learners can propose an event inside an already approved group; its parent organiser selects the paper and participants before it becomes an assigned event. Parent-approved group organisers may assign work to approved group members without gaining unrestricted family administration or unrelated practice history.

AI marking pilot. Paid AI calls are disabled. Submissions remain queued for marking; an absent AI result is not a zero mark. The server-side marking integration is prepared to send question/task/rubric content, submitted answers and supported submission files to OpenAI only after separate activation and appropriate processing arrangements. Teacher ID documents and school letters are excluded. This implementation does not activate that external processing. Before activation, we must confirm provider/model, spending controls, authority and notices for the intended learner processing. AI-generated feedback must be labelled; uncertain or incomplete work needs review. The organiser controls result release, and learners can request a marking review. Avoid unnecessary names, ID numbers or other personal information in written work, attachments, titles, instructions or rubrics.

Learner profiles. We handle a private learner identifier, chosen username, school, grade, school-derived curriculum, optional catalogue avatar and family/access links. School province and search selections help find the correct school. Use a nickname: do not put a real name, birthday, address, phone number, social-media handle or other identifying detail into a learner username or group name. Learners do not need their own email address for the access-code flow.

Learning and social activity. We handle quiz questions served, answers submitted, correctness, subject/topic and language pathway where used, scores, points, timestamps and saved-session information. Optional social features also involve group names, invitations, connection requests, approvals and membership records. These records are personal information even when a nickname is used.

Technical information. Hosting, authentication and content-delivery services may process IP addresses, browser/device information, request times and security/error logs. We also handle information you send in support requests and acknowledgements or permissions recorded during account setup. Do not send unnecessary sensitive information in support messages.

Optional private details (notice version 2026-11-04-optional-details). Adults may optionally store and edit their own or their linked learners’ first names, middle names, surnames, phone numbers, dates of birth and physical addresses as private profile records. Each field can be left blank, cleared individually or removed using “Remove all private details”. Email remains the only required personal detail for adult account registration; account authentication and applicable authority/terms acknowledgements are still required. These optional details are stored separately from usernames and learning records, accessible through the application only to the adult account that entered them, not to other linked parents, learners, teachers or social connections. Authorised service administrators and providers may access them as necessary to operate the service. Providing identifying details increases the impact of unauthorised access, including identification, unwanted contact and impersonation. Saving non-empty details requires a separate, unticked acknowledgement and authorisation; we record its notice version and server time. This acknowledgement does not waive your rights or our responsibilities. The details are not used for identity verification or authentication, and do not affect access to learning. Removing them deletes the active private record; backups follow the retention arrangements below.

Monthly learner access reporting (4 November 2026). When an authorised learner learning home is opened, we record its country, learner identifier, calendar month and first/last recorded opening times. Repeated openings count once per learner per month. This includes Zimbabwe parent-supervised learning. Authorised platform administrators see aggregate learner-access and school counts, not private profile details, through this report. This is first-party operational reporting; it does not add an advertising or third-party analytics tracker. Records are removed when the associated learner profile is deleted. Reporting began when this feature was enabled; earlier openings are not reconstructed as complete historical login records.

3. Where information comes from and why it is used

Information comes from you, an authorised adult managing a learner, the learner’s use of Funda, an identity provider you choose, and the services that operate the application. School-directory details come from public or supplied institutional records; linking a learner to a school creates a private profile relationship.

We use this information to:

Account email/authentication information and a learner’s school, grade and username are needed for the associated account/profile features. A character avatar and social participation are optional. You can use the guest preview without creating a family account, but it does not provide saved account progress. Funda does not use practice scores to make admission, employment or other legally significant eligibility decisions.

4. Children and adult permission

A person legally competent to act for a learner under 18 must authorise the learner’s personal-information processing. The parent setup flow asks for that authority and consent. A username-safety confirmation is separate from this permission. An adult managing a learner who is 18 or older must also have authority to do so.

You can ask us to review, correct or stop further processing of a child’s information, or withdraw consent. Withdrawal may mean the associated learner features cannot continue. We will consider authority, other lawful retention requirements and any rights of another authorised person before carrying out a request. Other processing may rely on operating the requested service, protecting legitimate interests or legal obligations where applicable; this notice is not blanket consent to unrelated uses.

5. Who can see or receive information

Family and learner access. Access controls are intended to limit family administration to authorised linked adults and learner sessions to the relevant learner. The teacher pilot separately permits registered teachers to view usernames, grades and learning progress for learners at their selected school, as described above. Keep parent credentials, student access codes and invitation codes private. Parents can copy a one-time learner sign-in link, use their device’s share options, or open a WhatsApp message composer to share it. The link contains an access code in its URL fragment and a learner identifier; it works once and expires after 24 hours. Share it only with the intended learner or a trusted adult. Choosing WhatsApp or another sharing app passes the link to that service under its own terms; Funda does not automatically select recipients or send the message. The app removes the access fragment from the address bar when opened. Once linked, that browser keeps a learner session and can reopen the profile without a new code, until access is reset, the session expires, or browser data is cleared. Another adult who is properly linked to the learner can access the associated family/learning features.

Optional friends and groups. Approved connections or group members may see the learner’s username and, where displayed, avatar and group points. Connection and membership approvals are separate from creating a learner profile. These features do not provide private student messaging or a public learner directory. Do not include identifying details in a group name.

School statistics. School views use aggregate Funda activity rather than a list of individual learner profiles. Detailed statistics are intended to be suppressed below ten participating learners in the selected reporting slice. A school’s Funda participation is not its total enrolment. Aggregation and nicknames reduce disclosure but are not a promise of absolute anonymity.

Service operation. Authorised support/administration personnel and service providers may process information as necessary for their roles. Supabase provides database/authentication services; Google Firebase provides hosting. Google sign-in, when used, operates under Google’s own account terms. The app also loads fonts from Google and a JavaScript library through jsDelivr; these network requests can disclose technical information such as an IP address to those providers.

We do not sell learner personal information or use learner profiles for targeted advertising. We may disclose information when legally required, to address misuse or protect rights, or to a successor operating the service subject to applicable safeguards and notice. We do not treat this as permission to publish family data.

Optional public app invitations and referrals. A signed-in parent, teacher or linked learner can request a public invitation code tied to their account or learner profile. A shared referral URL contains that opaque code, without a learner name, school, account identifier or sign-in credential. It opens the public application and grants no access to the sender’s account. WhatsApp or device sharing is initiated by the sender, who chooses the recipient and sends the message; Funda does not read contact lists or automatically send invitations.

A recipient’s browser tab can temporarily keep the invitation code for up to 24 hours during signup. The code may also be carried in signup metadata and confirmation redirects so that signing in after confirmation can complete attribution. We record at most one referring invitation for a new adult account that first claims it within 24 hours of account creation. Existing accounts, anonymous learner-device connections and self-referrals do not count. The referring user receives only an aggregate count of new accounts, without recipient names, emails or profile access. Invitation codes and attribution records are kept with the relevant accounts for this feature and are covered by the access/deletion request process below. We do not count WhatsApp messages sent or passive invitation-link visits.

Feedback. Signed-in users and linked South African learners can send optional feedback. We use the message, category, country and date to review issues and improve Funda. Reports sent from a question include its reference and curriculum details. We use an account-derived key to limit repeated submissions. Authorised Funda administrators can read messages and view aggregate counts. Leave out names, contact details and passwords.

6. Browser storage and guest previews

Funda uses browser storage for authentication/session continuity and preferences such as a remembered province or learner selection. The current application does not include an optional advertising or analytics tracker. Provider security and operational logging can still occur. You can clear browser storage or block it, but sign-in, remembered choices or session continuity may stop working. Sign out on shared devices.

Guest answers are held in the page while you practise and sent to the server when you submit for grading. A temporary server session holds the preview question set. Successful submission removes that session; expired sessions are cleaned up during subsequent service operations. Expiry does not guarantee that every backup or technical log is immediately deleted. Guest results are not added to a learner’s account score/history. Refreshing or closing the page can lose the guest’s in-page answers.

7. Retention, security and international processing

Account/profile records and learning history are kept to provide the ongoing service and handle legitimate support, security or legal needs. Inactivity alone does not automatically delete an account. Contact us to request closure, deletion, correction or restriction. Information no longer needed for a lawful purpose should be deleted, de-identified or restricted as appropriate. Backup copies follow their operational lifecycle and may not disappear immediately; any retained copies remain subject to applicable protection requirements.

We use access restrictions and service-provider safeguards to protect information. No online service or transmission is completely secure. Report suspected unauthorised access promptly; we will assess incidents and make notifications where required.

Cloud hosting, authentication, content delivery or support may involve processing outside South Africa. We must use an applicable lawful transfer basis and appropriate safeguards; contact the Information Officer for current arrangements. We do not promise that all information stays in South Africa or treat use of the site as unlimited consent to transfers.

8. Your choices and rights

Subject to applicable law and verification of authority, you may request access, correction, deletion or restriction, object to relevant processing, and withdraw consent where consent is the basis. Send the request to the Information Officer, describe the account/learner concerned and the action requested, and provide only the information reasonably needed to verify it. We will explain any lawful limitation or further information needed. Requests are handled through support; the app does not currently provide a self-service account-deletion button.

You may complain to South Africa’s Information Regulator. You do not have to waive that right or first accept our resolution. See the Regulator’s complaints page or email POPIAComplaints@inforegulator.org.za.

9. Changes and related terms

We will identify changes by updating the date/version and provide additional notice or seek renewed permission where appropriate. Materially different uses of children’s information require an appropriate lawful basis, not merely an edited policy. The Terms of Service explain permitted use and service limitations.