4.0 Labs · Privacy & Security
Student data protection.
Defined access. Limited use.
Our policy prohibits selling student records or using them for targeted advertising. School information is limited to the service uses described in our Privacy Policy, and school access requires the applicable permissions.
Rules for access, use and family privacy.
Student information has a purpose.
Our policy limits school information to the service uses described in our Privacy Policy. It prohibits selling student records or using them for targeted advertising.
School passwords stay with the school.
For API connections, any school sign-in happens with the school or its sign-in provider. The connection uses permitted access rather than your family’s school password.
Permission comes first.
A subscription does not replace required parent, eligible-student, school, School District or platform authorization.
Clear information, clear expectations.
Available records depend on the school app and permissions granted. Connecting one app does not guarantee access to every record or another app.
What information is involved?
The Command Center’s purpose is to organize available schoolwork for the authorized family. Different parts of the service need different information.
Family and account information
Account, child and school identifiers support enrollment, family organization and access. School records may include assignments, due dates, submission information and grades, depending on the approved connection.
Connection and service information
API permissions, connection references and update times support school connections. Billing providers handle payment details; service providers support hosting, account functions and communications.
Our Privacy Policy identifies providers and describes information uses. A provider’s involvement does not mean it receives every student record.
Your family’s privacy choices.
You can ask to review information, request a correction or deletion, or stop future collection. Use our support form and choose “Privacy Request” as the subject. Please do not include passwords, full payment details or sensitive school records in your initial message.
Stopping updates and deleting information
Disconnecting a school connection, deleting stored information and closing an account are different requests. Tell us which outcome you need so the scope is clear.
Privacy and billing are separate
Stopping school access does not automatically cancel a subscription. A deletion request may involve records with different retention requirements, including limited billing or legal records.
A shared responsibility with schools.
Our API model keeps School District and platform permission central to school access. For each School District integration, we define the permitted connection, participating families and intended information uses with the school and its providers.
COPPA concerns children’s online privacy; FERPA concerns access to and disclosure of education records. The applicable responsibilities depend on the service and school relationship. A data protection agreement describes the parties’ commitments; it does not replace those responsibilities.
Explore School & School District CollaborationPractical answers.
Do API connections require sharing a school password with 4.0 Labs?
No. In our API connection model, any required school sign-in happens with the school or its sign-in provider. Earlier connection setup used a different method; our Privacy Policy explains how previously collected information is handled.
Does a school connection provide every message and grade?
No. Availability depends on the app, connection and granted permissions. Schoolwork and official grades can come from different sources.
How do I ask about retention, providers or security?
Contact Support with your question. Do not send school passwords or private student records. Our Privacy Policy explains retention, providers and privacy requests.