Privacy and data choices

Updated October 12, 2026. This notice describes Mayomumah and the supporting services operated by Programming Securely.

Information used by this site

Parent accounts can create child profiles, choose learning activities, and store child learning progress, test answers and results. Child sign-in information and parent-child relationships are used to control access. Parents can upload teaching materials and create lessons or quizzes; uploaded materials are stored in AWS S3. Choosing a community-sharing feature makes the selected material available beyond your family, subject to its visibility and moderation settings. Administrators can review records for operation and moderation.

Parents sign in through Supabase Auth. Child profiles use the separate parent-managed account flow. Session information is stored in the browser. Parents should provide only the information needed for learning and avoid entering unnecessary identifying information about a child.

Site analytics and technical logs

We use self-hosted Umami to understand visits and page usage. Where enabled, the site sends page paths and technical browser/device information through its analytics endpoint; URL query strings and fragments are excluded by the tracker configuration. Hosting, authentication and security services also process technical request information, which can include IP addresses, timestamps and failure details.

Software error reports

We use self-hosted Bugsink to investigate technical failures. The integration is configured to remove user identity fields, request headers, cookies, request bodies, URL queries and interaction breadcrumbs from error reports while retaining stack traces. Session replay and performance tracking are disabled. Error messages can still contain information produced by the application, so avoid including private information in report titles.

Support and feature requests

The Support / Feature Request form sends your request type, title, description, optional contact email and technical page context to our central support system. When a verified signed-in session is supplied, the report can also include your account identity. Administrators review requests, and an internal Slack notification can contain the request title and reference. Do not submit passwords, payment credentials, or private information about other people.

Storage and sharing

Information is processed by the application and its hosting, authentication, storage and notification providers as needed for the features described above. Information you deliberately share is visible to the recipients allowed by the relevant feature. Linked third-party services have their own data practices. Access controls help restrict records; they do not make a deliberately public post or shared item private.

Retention and your choices

Use the application’s available delete and sharing controls to manage your own content. Removing a browser session or disconnecting an integration is different from deleting server-side content. To request access, correction, account deletion or removal of a support submission, use Support / Feature Request and include a contact email and any request reference. We verify ownership before acting; do not send a password. Shared records belonging to other people may need to be preserved or transferred rather than removed.

There is not currently one automatic expiration period for all records. Backups, operational logs and notification copies are separate from active application records and may persist after an item is deleted. We do not promise immediate removal from every copy. Downloaded files and information already received by other people are outside the app’s deletion controls.

This page will be updated when the service or its data controls change.