Classroom Writer Privacy and Data Processing Notice

Last updated: 14 October 2026

This notice explains how Classroom Writer handles account, teacher, school, student, worksheet, and service data.

Who we are

Classroom Writer is provided by Class Room Writer Pty Ltd, an Australian private company (ABN 53 700 840 348; ACN 700 840 348).

Australia is our home jurisdiction. We serve schools and educators internationally. Additional privacy and education requirements depend on applicable territorial rules, school arrangements and actual processing. This notice does not claim universal compliance solely because our website can be accessed worldwide.

Privacy questions can be sent to info@classroomwriter.com.

Summary

Teachers and schools choose what content they add, what student links they create, what student information is entered, and how student work is reviewed.

We do not sell teacher or student data. We do not claim ownership of teacher, school, or student content. We do not routinely review classroom content.

Data we may process

Depending on use, we may process account details, school details, subscription records, worksheet drafts, worksheet settings, student link information, student responses, drawings, tables, graphs, PDFs, activity records, and technical security data.

Google Classroom and Google Drive

When a teacher connects Google Classroom, Classroom Writer reads their own Google account identity and email address, their active classes, student names and Google identifiers. It uses this information to show the teacher's existing classes, share the chosen worksheet with the whole class or selected students, and match each student's work to the correct Classroom assignment. Classroom Writer requests permission to manage coursework to create these assignments and receive student hand-ins; it does not change grades through this integration.

Students sign in with their own Google account when opening a Classroom task. When Google Drive saving is enabled, Classroom Writer creates an editable draft and a final PDF in that student's Google Drive. It accesses the files it creates for this feature using Google's limited drive.file permission. It does not request access to all files in the user's Drive. Draft content passes through Classroom Writer's server to save and restore work; final PDF bytes are uploaded directly from the student's browser to Google Drive. The final PDF is attached to the matching Google Classroom submission and shared with the teacher through Classroom before hand-in.

Classroom Writer stores encrypted Google access and refresh tokens, account identifiers, class and assignment mappings, Drive file identifiers, save revisions, assessment timing, submission summaries and activity records needed to operate and secure this integration. Full editable drafts in this Drive-backed flow are stored in Google Drive and browser recovery storage rather than Classroom Writer's database. Files count against the storage available to the Google account that owns each file. Classroom Writer also creates a recovery copy of a successfully saved draft in the assigned teacher's Google Drive. The student cannot delete this teacher-owned copy through their own Drive. Classroom Writer stores its file identifier, save revision and checksum, and can use it to restore a missing or damaged student draft. Recovery requires an available valid copy and working authorised connections; it cannot guarantee recovery of unsaved work or permanently deleted copies.

When the Google Classroom portfolio pilot is enabled for an authorised teacher, Classroom Writer uses the student's authorised Google connection to retrieve the latest saved draft for that student's assigned teacher. Unsaved keystrokes are not available to the teacher. Teachers can create checkpoints and final archives in their own Google Drive using limited drive.file access. Classroom Writer stores archive file identifiers and checksums, feedback notes, quoted passages used to anchor feedback, replies, release settings and a history of feedback changes in its database. Private and unreleased teacher notes are not shown to students. Released feedback may appear in the student's workspace and selected exports.

Disconnecting a connection with portfolio archives removes Classroom Writer's stored Google credentials while preserving portfolio identity links and feedback history. Disconnecting does not revoke the Google Account permission grant; users can revoke that grant in Google Account permissions. Deleting a local project does not delete copies in student or teacher Google Drive. The portfolio pilot has no automatic retention or purge schedule. Schools and teachers must agree retention and deletion instructions with Classroom Writer before wider use, including separate handling of Google Drive files and Classroom Writer's records.

Users can revoke Classroom Writer's Google access in their Google Account permissions. Teachers can also disconnect Google Classroom in Classroom Writer. Revoking or disconnecting access does not automatically delete existing Classroom assignments or files in Google Drive; students and schools can manage and delete these in Google. For requests concerning data retained by Classroom Writer, contact info@classroomwriter.com. Student data requests may need to be handled through the school.

Classroom Writer's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used to provide this educational integration, not sold, used for unrelated advertising, or used to train or improve general-purpose AI models. Human access to Google user data is limited to access permitted under that policy, such as support with the user's permission, security investigation, or legal obligations.

Assessment Builder plugin and compiler

When a teacher connects the official Classroom Writer Assessment Builder plugin or connected compiler, Classroom Writer uses OAuth to confirm the teacher's account and paid-access status. After the teacher approves an assessment in ChatGPT, the educational blueprint is sent to Classroom Writer only to validate it and create a protected .cwriter download. The OAuth and fair-use records store account identifiers, token hashes, dates, and file-size metadata, but do not store the assessment content, ChatGPT conversation, password, payment-card details, student answers, or existing worksheets. OpenAI processes the teacher's ChatGPT conversation under OpenAI's own terms and privacy policy. Approved protected downloads are stored temporarily as encrypted packages so the assistant can attach the .cwriter file. The download link expires after ten minutes; expired database records are processed by a bounded scheduled cleanup as well as cleanup during package creation. Cleanup may be delayed by outages or backlog; access expiry is not a guaranteed ten-minute physical storage purge. These packages are not used for model training. Other AI services chosen by a teacher process the material sent to them under their own terms; the teacher should check school approval before sharing content.

Why we process data

We process data to provide Classroom Writer, allow teachers to create worksheets and writing links, allow students to complete assigned work, generate submissions and PDFs, manage accounts and subscriptions, provide support, protect security, and comply with legal obligations.

Schools and student data

Classroom Writer is intended for school-directed educational use. Teachers and schools should not ask students to enter unnecessary personal data.

Schools and teachers arrange the authorisations required for their educational use. Classroom Writer remains responsible for obligations that apply to its own processing. A student task acknowledgement does not establish parental consent or replace a school data agreement. Where US COPPA applies and school authority is relied upon, the required school notice and verified educational authority must cover that use; uses outside that route need their own applicable authority.

Sharing

We may share limited data with service providers that help us operate Classroom Writer, such as hosting, authentication, database, payment, email, analytics, security, and support providers.

We do not sell student data.

User rights

Depending on your country, you may have rights to access, correct, delete, restrict, object to, or receive a copy of certain personal data. If student data is controlled by a school, requests may need to go through the school.

To make a request, contact info@classroomwriter.com.

Portfolio Hub, feedback and saved work

Teachers set project headings and classes; students supply their own titles, goals, report content and optional project details. Classroom Writer stores project overviews, supporting-file references, progress notes, teacher approvals and locks, change requests, sticky notes, colours, headings, positions, replies and revision history in its database. Some retained versions or submitted records can contain report content. A Google-backed editable report is saved to Drive; this does not mean all portfolio information is stored only in Google. Non-Google work and submissions may be stored in Classroom Writer's database and storage, with browser recovery copies where supported.

The assigned teacher can review saved work and add feedback. Students can manage their own sticky notes and reply to teacher feedback, but cannot remove teacher-owned notes. The normal final submission preserves the submitted work. A separately generated feedback PDF may contain released teacher feedback and student replies; distributing or downloading it creates an additional copy managed by the recipient.

Activity records and academic integrity

Where enabled, we record task timing, saves, submissions, input type/counts/timing and insertion size, clipboard attempts, permission requests and decisions, tab visibility, focus changes and window-layout observations. Activity locations may contain excerpts from the relevant question or answer. Teacher-approved CW dictation is distinguished from ordinary input and excluded from the rapid-input review rule. Rapid input can create a teacher review alert; it is not proof of AI use. Save work, final-copy saving and a PDF download request are different events. A browser delivery request does not establish that a file completed downloading or was handed in to the school. Alerts are not guaranteed to arrive immediately or make a sound. Assigned teachers can review relevant records and integrity reports. Window dimensions or focus changes cannot reliably establish split-screen use, use of another app, AI use or misconduct. We do not capture the student's entire screen or the contents of other applications through these observations. Integrity signals require human review and are not an automated determination of misconduct.

Optional browser monitoring

An optional CW Integrity Monitor prototype can report limited observations, such as browser-reported automation, a debugger attached to the assessment tab, or a screen-sharing request initiated by the CW page. These are client-reported review signals. It cannot identify every AI operator, screenshot, recording, external application or screen-sharing session. Its reviewed source does not record screen pixels, audio, browsing history or other apps' contents. Legitimate assistive or developer tools may produce similar signals.

The reviewed v0.2 prototype defaults off, shows its monitoring notice and requests debugger-status permission separately when that option is enabled. Its retry queue has a selected one-, 24- or 72-hour expiry, checked when extension code runs. Local clear/disable controls do not erase server activity records. Source behaviour is not a guarantee that an installed extension is connected or effective; deployment and school authorisation must be checked.

Training and external specialist tools

The public practice sandbox keeps its exercise state in the page and does not submit practice work to a real class or Google Drive. Account-based training uses account and progress information. GeoGebra and external simulations, video resources or links selected by the teacher may contact third-party services when opened or loaded, disclosing network/browser information and any content intentionally entered there. Schools should review those services separately. Avoid real student personal information in public AI chats or practice exercises.

Collection, roles and lawful bases

We collect information from account holders, students, teachers and schools, connected Google accounts and services, and technical events produced when the service is used. Account credentials, necessary session cookies and task identifiers support authentication and recovery. A user may use a school-approved student identifier where permitted; required account, connection or task details cannot be omitted without affecting the relevant feature.

For account administration, billing and our own security or support decisions, Class Room Writer Pty Ltd acts as a controller where applicable. For school-directed student content, we generally act as processor on the school's documented instructions. A school's controller responsibilities do not remove our own obligations as processor.

Where GDPR applies, account and subscription processing may be necessary for our contract with the account holder; security and support may rely on legitimate interests, subject to an assessment and safeguards; statutory records may rely on legal obligations. Optional consent-based processing can be withdrawn without affecting prior lawful processing. Schools determine and document their lawful basis for educational processing; we do not assume that every child's consent is required or sufficient. A school processing agreement should define its instructions before student data is used.

Retention, deletion and recovery copies

Retention depends on the record, the school's instructions and legal requirements. A task expiry or submission lock stops or limits editing; it does not automatically erase the task. There is currently no automatic universal age-based purge for portfolio records. We do not promise a 90-day purge that is not implemented. Authorised users should export required records, use available deletion controls and contact us for deletion across related systems.

Deleting a live task can remove its associated Classroom Writer student records and history. Deleting the last published link can leave its source draft available. These actions do not remove Google Classroom posts, student Drive files, teacher recovery/checkpoint copies, downloaded PDFs or recipients' copies. Disconnecting Google access removes stored credentials according to the connection workflow; it does not erase those external files or revoke the Google permission grant. Schools should manage those copies in Google and ask us to coordinate related Classroom Writer records. Browser recovery copies may remain on the device until cleared. Infrastructure backups may retain deleted records until provider rotation; the applicable backup period must be confirmed for the live service rather than assumed. Limited billing, incident and request records may be retained where required by law.

International processing and providers

We use Supabase for backend database/authentication/storage, Vercel for hosting and Stripe for payments. Google provides the optional Classroom/Drive connection. Account notification email may use Resend where configured; business correspondence uses our email service. Teachers may separately choose OpenAI or other AI services and external specialist resources. These services have different roles; a school-authorised Google service or independently chosen AI service is not automatically our subprocessor for every activity.

Providers can process data outside your country, including in the United States, and other locations used by their services. Read-only inspection on 14 October found the named CW Supabase primary database in Stockholm, Sweden, and the CW Vercel function setting in Washington, D.C., United States. The exact production mapping, other storage/log/backup and support-access countries remain to be confirmed; we do not claim Australian-only or EU-only hosting. Contact info@classroomwriter.com for the current provider and transfer details before an international school deployment. Where GDPR applies, an appropriate transfer mechanism and any required transfer risk assessment must be established before a restricted transfer; merely mentioning standard contractual clauses in this notice does not establish that they have been executed.

Security, incidents and requests

We use access controls, authenticated teacher accounts, MFA where required, owner checks, encrypted Google credentials, protected connections and verified recovery checksums. A checksum detects whether a copy matches the expected saved content; it is not encryption. Backups support recovery but do not guarantee that work can never be lost. We investigate personal data breaches, assist affected schools and make notifications required by the applicable law.

For access, correction, erasure, restriction, objection or portability where applicable, contact info@classroomwriter.com. We verify identity proportionately and coordinate school-controlled requests with the school. GDPR requests must normally be answered within one month; a legally available extension will be explained within that first month. Requests are generally free, subject to lawful exceptions. You may complain to the competent data protection authority; Australian privacy concerns may be taken to the OAIC.

To complain to us, email info@classroomwriter.com with the concern and relevant account or task details, without including unnecessary sensitive student data. We will acknowledge the complaint, investigate it and aim to provide an outcome within 30 days, or explain the delay and next steps. If unresolved, you may contact the OAIC or your competent local supervisory authority.

Australian Privacy Act status and policy changes

We do not claim confirmed OAIC registration through voluntary Privacy Act opt-in. Australian business registration does not by itself determine Privacy Act coverage; relevant statutory coverage and any completed opt-in apply according to law. This notice describes our data practices and does not exclude obligations or rights that apply to us or our users. This is not an OAIC endorsement or GDPR certification. We review this notice when features, providers or processing practices change, and communicate material changes through appropriate account notices or email.