Skip to main content
Classwise AI is now officially 1EdTech certifiedClasswise AI is now officially 1EdTech certified

Reference • Teachers • School admins • District admins

How Classwise handles classroom use, access, and privacy

Schools do not adopt a grading product just for features. They need to understand how it fits the classroom model, how access works, and how AI is being used.

What this page covers

Give schools and educators a practical understanding of how Classwise fits the classroom model, how access works in-product, and where formal trust review should continue elsewhere.

Expected outcome

Readers understand the responsible-use model inside Classwise and can separate day-to-day product behavior from formal legal or procurement review.

For

Teachers • School admins • Implementation owners

Before you begin

Separate practical product questions from formal legal or procurement review questions before you use this page.

What you will need

A clear sense of whether you are evaluating day-to-day classroom workflow, LMS access, or school-level trust review.

Applies to

Identity • LMS access • Institution-managed account restrictions • Product trust review

Last verified: 2026-03-25

One of the main trust questions schools ask is whether AI is being used in a way that keeps student work authentic. Classwise is designed so students can still complete work in an AI-free, paper-based classroom while AI handles grading and feedback behind the scenes.

Classroom trust model at a glance

Area

How Classwise handles it

Student work mode

Students can stay on paper while AI works on grading and feedback behind the scenes.

Teacher judgment

Teacher review remains the control point before results are treated as final.

Sharing control

Completed results are not automatically equivalent to published or emailed results.

Key points

  • Students can keep working on paper instead of being pushed into a screen-first workflow
  • Teachers stay in control of review and sharing decisions
  • The product is designed to support teacher judgment, not replace it

Notes

  • Use this section to explain how Classwise fits a paper-first classroom model. Use formal policy documents for legal review.

Security questions often show up in day-to-day product areas: connected logins, LMS provider access, institution-managed accounts, and who can see billing or admin tools.

Key points

  • Classwise supports both OAuth-style LMS connections and token-based LMS connections depending on the provider.
  • Teachers manage connected logins and passwords from profile settings where applicable
  • Institution-managed members may have school-scoped access and billing visibility
  • School-scoped LMS restrictions and provider-account conflict checks are part of the real access model.
  • LMS connections are visible in-product so teachers can understand what is connected

Common blockers

  • OAuth-style LMS connections and credentials-style LMS connections do not behave the same way.
  • Institution-managed LMS restrictions affect which providers users can even see.

Classwise shows a cookie banner the first time someone opens the site. Strictly necessary cookies (sign-in, security, and remembering the choice) are always on. Analytics cookies, which power product analytics and error diagnostics, are on by default in the United States and in Canada outside Quebec, and visitors can turn them off. In Quebec, everywhere else, and on student feedback pages, analytics stays off until the visitor accepts it.

Step by step

  1. On your first visit, select Agree in the cookie banner in the bottom-left corner of the page, or select Customize to turn analytics off. The banner stays until you choose, and other panels and the product walkthrough move up so they never sit behind it.
  2. To change your choice later, open Profile → Cookie preferences → Manage cookies, or select Cookie settings in the site footer.
  3. Turn Analytics on or off, then select Save preferences.

Keep in mind

  • Rejecting analytics does not limit any feature of Classwise.
  • Browsers that send a Global Privacy Control signal are treated as having rejected analytics until the visitor accepts it.
  • Student feedback links never turn analytics on by default, and students are never identified in analytics.
  • The choice is stored in a first-party cookie on this browser for 12 months, then Classwise asks again.
  • If you turn analytics off, Classwise shows the banner again after two weeks. After three times it stops asking.
  • If you turned analytics off, the banner also appears once more when Classwise changes how it uses cookies. Analytics stays off unless you agree.
  • Classwise does not use advertising cookies.

Keep in mind

The choice applies to one browser. Signing in on another browser or device, or clearing cookies, shows the banner again.

Public docs should explain the practical trust model, but deeper procurement or legal review should still be handled through the school evaluation process. The docs should clarify what the product does without over-claiming.

Decision checklist

  • Use the workflow docs when the school wants to understand how grading, review, and sharing work day to day.
  • Use the public privacy policy and terms when the school moves into policy review.
  • Escalate to formal procurement or trust review when the question goes beyond what the in-product docs can prove.

Key points

  • Use docs to explain workflow, review controls, and classroom model.
  • Use the public privacy policy and terms pages for policy-level review before moving into school-specific conversations.
  • Use product and institutional conversations for procurement-specific questions.