BrushUpOn
Privacy Policy
Last updated: October 27, 2026
This page explains what data BrushUpOn needs to run the learning service and how you can control it.
Data we process
To create an account and operate the service, we process your email address, selected role, profile settings, learning groups, decks, cards, and review results. If you add files or attachments, their contents are also processed to display learning materials and perform the action you request.
Why we use it
Data is used only to provide BrushUpOn features: account sign-in, organizing learning, showing cards, saving personal progress, collaboration in groups, and protecting the service from abuse.
Who can see your data
Students can see their own progress. Teachers can see data from the groups they manage and their students’ progress in those groups. Data from other groups is not made available merely because you have an account.
Storage and security
Data is retained for as long as it is needed to operate your account and learning materials. The service uses technical access protections, but you should not share passwords, invite codes, or private materials with others.
Who else processes data
The BrushUpOn server is rented from a hosting provider in the European Union. File attachments and database backups are stored in Cloudflare R2. Service emails (email confirmation, access recovery, sign-in codes) are sent through an email delivery service. When a teacher runs AI card generation, the text of the uploaded learning material is sent to the AI provider (Google Gemini) only to draft cards; student data and review results are not sent there. If a teacher picks a file from Google Drive, BrushUpOn gets access to that one file only: the teacher’s browser downloads it, and the Google access token is not stored on the server. These providers process data only to deliver their service to BrushUpOn and do not use it for advertising.
Children and parental consent
Students under 14 may use BrushUpOn only with the consent of a parent or other legal guardian. In school groups the teacher or school collects this consent before classes start. Only the minimum is collected for students: a sign-in email, the name the teacher sees and review results; there is no advertising and no sale of data. Parents can ask, through the teacher or the service administrator, to see, export or delete a child’s data, or to withdraw consent - the child’s account is then deleted together with its learning data.
Anonymous site traffic
To understand how the service is used, we collect the time of a page view, a section name without the full URL, interface language and device type. These analytics do not record emails, IP addresses, card content, invitation codes or full URLs; the exception for short campaign tags is described below. A random short session code is kept in tab storage and changes after 30 minutes without navigation; it is not linked to an account. Administrators see aggregate statistics for the last 90 days. Records older than 90 days are removed during daily cleanup. Collection is skipped when the browser sends Do Not Track or Global Privacy Control signals
Marketing campaign sources
When you follow a campaign link, only the short utm_source, utm_medium and utm_campaign tags are kept, without the full URL or other parameters. The first valid campaign is stored locally in your browser for up to 30 days and is not replaced by subsequent links. These tags may accompany anonymous page views retained for up to 90 days and, at registration, the new account profile. Profile data is included in your account export and removed with the account. Tags are not used to identify you across devices. Do Not Track and Global Privacy Control signals skip collection and clear the local campaign tag when detected. Only the administrator can view aggregated campaign reports
Technical diagnostics
To identify failures, the service groups technical errors by type and area, recording first and last occurrence times and the number of reports received. Server failures include a technical request ID to locate details in server logs. Browser reports contain no error message or stack, full URL, entered text, email, passwords or tokens and are sent without account cookies or an authorization header. Repeated browser reports are limited; Do Not Track and Global Privacy Control signals are respected. Summaries are available only to the administrator. Issues with no recurrence for over 90 days are removed during daily cleanup
Service administration history
To investigate issues and track changes, the administrator has a journal of their actions: time, action type, administrator and object IDs, technical request ID and outcome. Group ownership changes include the previous and new owner IDs. Card and report text, email addresses, passwords and tokens are not copied. Records are accessible only to the administrator, retained for up to 365 days and may remain after the related object or account is deleted
Your control over data
In account settings, you can export personal data and start permanent account deletion. Deleting a teacher account can also remove groups created by that teacher and related learning data; the service shows those consequences before confirmation.
Policy changes
We may update this policy as the service evolves. The current version is always available at this link, with its update date shown at the top of the page.