Classroom policy and data-use notes

Effective policy is the authority

The server resolves organisation defaults, stored rules, per-member overrides and forced safeguards. Rules from multiple applicable organisations can combine using the stricter result; locks are retained. Read the person's effective policy before presenting a feature and still handle server refusal when an action is submitted.

The policy API uses full replacement of a stored rules object. Preserve settings the administrator did not intend to change. Unknown keys, invalid enum values and organisation-only keys in member overrides are rejected. A feature listed in a policy schema is not an assurance every client implements it.

Rule	Class default / behavior
`sharingOutsideOrg`	Off. Sharing with the allowed organisation or its members has separate target checks; arbitrary email is not an account-discovery mechanism.
`publicLinks`	Off. Do not invent a public-link API from this policy key.
`webhooks`	Off for applicable member policy. Organisation-owned webhook administration is a separate privileged Developer workflow in current source.
`thirdPartyApps`	Off. A personal OAuth integration is not automatically allowed for a student.
`apiAccess`	Managed: applicable members use organisation-issued managed keys; off blocks API keys/OAuth.
`liveEditing`	On as a default, but admission still requires document access and an eligible plan.
`usageVisibility`	All, an organisation-level setting; classroom administrative usage is not the team's default document-only view.
`exemptAdmins`	On by default. Teacher/admin exemption is considered when resolving personal feature policy; API off and staff blocks still apply.
`developerAccess`	Admins by default in current source. Class students never gain access through everyone.
`audioMonthlyCharacters`	Zero means no extra monthly audio policy cap, not unlimited provider capacity or plan allowance.
`dailyRequests`	Stored and returned, but not currently enforced by the public request counter. The wrapper uses the global daily cap, not this organisation policy value.

In minors mode, applicable member policy forces outside sharing, public links, webhooks and third-party apps off and API access to managed. A staff-provisioned school cannot turn minors mode off. Teacher/admin exemptions and organisation-owned credentials are separate paths, so do not claim a student policy setting blocks every possible administrative integration.

Stored protections can survive a plan lapse; cancelling a plan is not a way to remove safeguards. Staff suspension is enforced through the member-credential policy path. Current-source org-owned tokens use a different path that omits that common staff-block gate, so their revocation must be checked separately; see identity and roles. Expose the policy source and an appropriate support/admin action, rather than repeatedly retrying forbidden calls.

Student-facing explanation of activity

The implemented usage dataset contains counts of requests/errors, speech characters, edits, inserted/deleted characters and live-session seconds, plus relevant organisation document IDs. It is not document text, raw keystrokes, device IDs or IP history. In classrooms, administrative usage can include all app usage under classroom collection rules; do not promise it is limited to documents owned by the class.

Responses provide collection and retention descriptions. Source defaults are 48 hours for minute usage, 90 days for day totals and 365 days for collaboration aggregates. These are dataset-specific retention rules, not a claim that all school data or all backups disappear on those schedules. Document deletion, school closure and your integration's cached copies have different handling.

Teachers/co-teachers see full collaboration insights; students see their own share. Billing can read usage but not collaboration insights. Do not present contribution share as a grade, attention score or proof of learning. Show missing data honestly and preserve role-based visibility when exporting or caching results.

Integration data handling

Request only the scopes and documents needed for the feature. Keep managed tokens and one-time secrets in appropriate server-side storage, not browser source or screenshots. Avoid copying student names or roster exports into general support logs. Track request IDs and counts instead of content.

Explain to the school and student what your separate integration stores and sends for processing. Handwrite's application behavior is not a certification of your integration's privacy, consent or legal compliance. Follow the school-approved use and retention requirements for the actual deployment.

Source basis: org-policy-keys.ts, policies.ts, events.ts, usage-org.ts, insights.ts, schools.ts and developer.ts.

Classroom policy and data-use notes

Effective policy is the authority#

Student-facing explanation of activity#

Integration data handling#

Effective policy is the authority

Student-facing explanation of activity

Integration data handling