Privacy Policy

Last updated September 27, 2026

Visor helps teachers see how a student group project was done, using meeting recordings and the edit history of the group's Google Docs or Slides. This page says exactly what Visor stores, why, and who else handles it.

What Visor stores

• Your account: first and last name, email address, whether you are a student or teacher, the school you chose (if any; picking one is optional), an optional icon color, and either a salted hash of your password (never the password itself) or, if you used Sign in with Google, no password at all.
• Projects: each project's name, its teacher and students, and its project code.
• Recordings that a project member uploads or records, their transcripts, and the names members assign to each voice.
• Document reports: for a Google Doc or Slides file added to a project, the file's title and link and, for each person who edited it, their name and email as shown in the file's history and counted figures: characters added and deleted, edit counts, typing and pasting measurements, writing sessions and edits per hour, and for each paste or deletion who made it, when, and how many characters (and whether a paste came from inside or outside the document). Visor does not store the text of the document, or the text that was pasted or deleted.
• Analysis reports a teacher runs for a project.

Where document data comes from

• The Visor Chrome extension. When someone clicks Send to Website and enters a project code, the extension sends the counted figures above to that project. It does not send the document's text, pasted text, or deleted text.
• Google Drive. If you choose Connect Google Drive, Google asks you to allow Visor the drive.file permission, and you pick one file in Google's own file picker. Visor can only access files you pick this way, never the rest of your Drive. Visor then reads that file's saved revisions, compares their text to count who added and removed how much, and stores only the counts. The text is discarded as soon as the comparison is done. The Google access token is used for that one request and is not stored.

Google user data

Visor'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 Drive data is used only to show revision history inside the project you added it to. It is never sold, never used for advertising, and never used to train AI models.

Who else handles the data

• Google Firebase (Google Cloud) hosts the website and runs Visor's server. Accounts, projects and reports are kept in Cloud Firestore, and recordings in private Cloud Storage, in the United States.
• Google's Gemini API transcribes recordings and writes the analysis report. Recordings, transcripts, and the counted figures in document reports are sent to it for that purpose only.

Visor does not sell data and does not use advertising or analytics trackers.

Who can see what

A project's recordings, transcripts, and document reports are visible to its teacher and students. The analysis report is visible to the teacher, and to students only if the teacher turns that on. Recordings can only be played by signed-in project members.

Signing in with Google

If you use Sign in with Google, Google confirms your identity and shares your name and email address with Visor so we can create or find your account. Visor does not receive or ask for your Google password, and this is separate from the drive.file access described above — signing in this way does not give Visor access to your Drive.

Cookies

Visor sets one cookie to keep you signed in. It contains no tracking information.

Keeping and deleting data

Data stays until it is deleted. The person who added a resource, or the project's teacher, can delete it at any time; deleting a recording deletes the audio file. Deleting a project deletes all of its recordings, reports, and analysis. To delete your account, contact the support email shown on Visor’s Google sign-in screen.

Students and recordings

Visor is meant to be used by schools. Teachers are responsible for any consent their school requires, and everyone who is recorded should know they are being recorded.

Changes and contact

If this policy changes, the date at the top changes too. Questions: the support email shown on Visor’s Google sign-in screen.