Privacy Policy
Courses can contain names, grades, messages, submissions, and other private information. Before Morrow sends course records to your assistant, it replaces known student identifiers with course labels.
Student Privacy
Your assistant does not need a student’s identity to help with most course work.
Morrow first confirms the course and builds a complete identity list for the records it will read. When the course provides them, this list includes current, former, and deleted enrollments. Morrow keeps names, parts of names, aliases, email addresses, usernames, and school or course account IDs on your computer. It replaces them with labels such as Student A1 before course information reaches your assistant. If it cannot identify and protect every student in those records, it stops.
This protection applies to known student identifiers in the course records that pass through Morrow. It covers fields and text in discussions, messages, comments, submissions, pages, and other course records. It does not cover identifiers that Morrow does not know. Your assistant receives labels such as Student A1 with the protected course facts needed for your request. For an approved course action, Morrow matches a label back to the exact student only on this computer and in the selected course.
Use a real name inside Morrow Private Chat.
Ask your assistant to start Morrow Private Chat. Choose the course in Morrow Bridge. List every student name or ID used in your message, then type the message in the local drawer. Morrow checks each listed identity against a fresh, complete course roster. It replaces known identity text with labels such as Student A1 before it sends the message to your assistant. If a listed identity is missing, unclear, or outside the selected course, Morrow does not send the message.
For example, you can type “Review Michaela Adams’s missing work, recent scores, and submission history” inside Private Chat and list Michaela Adams. Your assistant receives “Review Student A1’s missing work, recent scores, and submission history.” You can also compare that learner’s participation with the course pattern, draft a message for you to review, or prepare an approved course action. You can close Private Chat at any time to clear the local conversation.
Three requests, and what your assistant receives.
Each request below is typed in Private Chat, with Michaela Adams listed as the identity. Each one does real work on one student, and none of them sends her name to your assistant.
Missing work: you type “Michaela Adams has not submitted the lab report. Draft her a short note with one next step.” Your assistant receives “Student A1 has not submitted the lab report. Draft a short note with one next step.” It writes the note. You read it and send it to Michaela.
A comparison: you type “Compare Michaela Adams’s discussion posts with the rest of the section this month.” Your assistant receives that question with Student A1 in place of her name, together with the course facts it needs to answer it. It never learns whose posts these are.
A course action: you type “Send Michaela Adams a message about the lab report.” Your assistant receives “Send Student A1 a message about the lab report.” It drafts the message. When you approve it, Morrow matches Student A1 back to Michaela Adams on your computer and sends it to her.
The label does not depend on how you write the name.
Morrow builds the identity list from the course roster, so it matches Michaela Adams written as “Adams, Michaela”, written as “Michaela”, written as her email address, written as her username, and written as the ID number her school or your course platform gives her. Every one of them becomes the same Student A1.
The replacement also reaches the words students wrote. If a classmate posts “I agree with Michaela,” your assistant reads “I agree with Student A1.” A name inside a discussion post, message, comment, or submission is replaced the same way as a name in a roster field.
You can also use the protected label Morrow returned.
Ask your assistant to use Morrow to read the selected course. When that result calls a learner Student A1, keep using Student A1 in the same course. The real identity stays on your computer.
Student A1 stays bound to one course.
Your assistant gets the protected label and the course facts needed for the request. The student’s name, email address, school IDs, course account IDs, usernames, and aliases stay on your computer. Morrow resolves Student A1 to the exact person only for an approved course action on this computer and in that selected course. The same label in another course does not identify the same person.
Your course sign-in stays in Chrome.
Morrow Bridge works through the Canvas or Moodle tab where you are signed in. Your password, cookies, and other sign-in details stay in Chrome. Morrow and your assistant do not receive them.
Your school connects Blackboard.
Blackboard does not use Chrome. Your Blackboard administrator connects Morrow to your school. You then add that approved connection on your computer.
You choose what to share.
When you ask ChatGPT, Claude Desktop, Claude Code, or Gemini CLI to use Morrow, the course information needed for your request goes to that assistant. Morrow first replaces known student identifiers in records that pass through it. Other course information can still be confidential, so follow your school’s rules. Your assistant has its own privacy terms and settings.
What if I type a real name or upload a named file directly to my assistant?
That name or file reaches your assistant. It bypasses Morrow, so Morrow cannot replace the identity inside it. Use Morrow Private Chat or a protected label from a Morrow course result when you want this protection. Do not type a real student name or upload a named student file directly to ChatGPT, Claude, or another assistant and expect Morrow to filter it.
Work records stay on your computer.
Morrow keeps plans and change records on your computer so you can return to them. Treat the Morrow folder like any other folder that contains course information.
You control access to course files.
Course files need a separate Chrome permission that you can remove. Morrow keeps a temporary copy only while it prepares a file change.
This website does not track you.
This site has no tracking cookies, account sign-in, or contact form. Cloudflare delivers the pages. Email to hello@meetmorrow.app goes through Cloudflare Email Routing to a Morrow Gmail mailbox and stays there until it is deleted. Do not email student records, passwords, sign-in details, or screenshots that show student information.
Chrome Web Store Limited Use.
The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
You can remove access.
You can disconnect a course, remove Edit access, remove course file access, and clear Morrow’s records from your computer. This stops new requests. It cannot remove information already sent to your assistant or undo a course change.