Privacy Policy — Brickit for Classes

Who we are

“Brickit for Classes” is operated by Brickit Inc. (“we”, “us”).

Children, COPPA, and schools

Our Student Portal is intended for use in an educational context (e.g., classroom or supervised learning). We do not use behavioral advertising or third‑party analytics on Student Portal pages.

COPPA notice: we do not knowingly collect personal information from children under 13 for marketing purposes. In the Student Portal, we collect only the information reasonably necessary to provide the educational service (see “Student Portal data” below). Where required, we rely on the school/teacher (as the child’s agent) to provide consent for educational use.

FERPA

If a school or educational organization uses the Teacher/Student Portal, information about student participation (such as lesson progress) may be considered an education record under FERPA.

In that case, we act as a service provider to the school. We use portal data only to provide and maintain the service, at the direction of the school/teacher, and we do not sell it.

What we collect (by area)

A) Public website (marketing pages)

These are pages like /brickit/, /brickit/programs/, /brickit/pricing/, etc. They are intended for adults (teachers, school staff, partners) and may use cookies or similar technologies.

Analytics: we use Yandex.Metrika to understand website traffic and improve the website. It may collect device and browser information, approximate location (derived from IP), pages viewed, and interaction events.
Newsletter: if you choose to subscribe, we use Sender.net to collect and process your email address for newsletter delivery and related analytics (e.g., subscription event).

B) Teacher Portal

The Teacher Portal is designed to work without third‑party analytics scripts on portal pages. We process the following to provide functionality:

Teacher access code (used to load teacher-specific classes).
Class data (class code, class name, optional description).
Student progress and teacher feedback (e.g., lesson steps, answers, status, feedback fields) for classroom workflows.
Scan feature (optional): if you upload an image to scan bricks, the image is processed to generate model suggestions. We delete uploaded scan files from our server disk after processing.
Device and session storage: we use browser storage (such as sessionStorage/localStorage) to keep you signed in and keep the portal working during your session.

C) Student Portal

The Student Portal is designed to work without third‑party analytics scripts on student pages.

Class code (provided by the teacher) to join a class.
Pseudonymous student identifier (a random/technical identifier used to save progress). We do not require a child’s real name.
Lesson progress (steps/answers/status) to support the learning experience.
Scan feature (optional): if used, an image may be processed to generate model suggestions. For base64 scans, we do not store the image file on disk.
Device and session storage: we use browser storage (such as sessionStorage/localStorage) to keep the portal working during your session.

Third‑party services

Depending on what you use, we may use these providers:

Yandex.Metrika (marketing pages only): analytics and session metrics. Privacy policy
Sender.net (marketing pages only): newsletter subscription and delivery. Privacy policy
Brickit services (scan feature): we send an image (or derived part list) to Brickit APIs to generate model suggestions and instructions.

These providers process data under their own privacy policies. We do not control their independent processing.

How we use information

Provide and maintain Teacher/Student Portal functionality (classes, sessions, lesson progress, and feedback).
Operate, secure, and troubleshoot the service (including basic logs).
Improve the public website (marketing analytics on marketing pages only).
Send newsletter communications only if you opted in (marketing pages only).

We share information only:

With service providers described above to operate features you request.
To comply with law, lawful requests, or to protect rights, safety, and security.

Retention

We keep portal data only as long as needed for educational functionality and support. Schools/teachers can request deletion at any time.

Scan uploads sent as files are deleted from our server disk after processing.

Security

We use reasonable administrative, technical, and organizational measures to protect information. No method of transmission or storage is 100% secure.

Your choices and rights

Marketing analytics: you can limit cookies via browser settings; you can also use available opt-out tools provided by analytics vendors.
Newsletter: you can unsubscribe using the link in our emails.
Portal data: request access, correction, or deletion by emailing classes@brickit.app.

Changes

We may update this policy from time to time. Material changes will be reflected by updating the effective date and publishing the updated policy on this page.