Getting Evident Capture approved at your school

For the teacher: three steps

1. Try to install it first. Open the Chrome Web Store listing. If it installs, you are done. Many teacher accounts are not locked down, and this takes ten seconds to find out.
2. If Chrome blocks it, request it. Districts using the common setting see a Request button right on the store listing. Clicking it puts the extension in your administrator's approval queue. Your request is stronger with a sentence about why you want it, so send the email below too.
3. Send your administrator this page. The link is evidentk12.com/extension/it-approval. It answers the questions they would otherwise have to research, which is usually what turns a two-week wait into a same-week approval.

Subject: Extension approval request — Evident Capture: IEP Data Collection

Hi,

I'd like to use a free Chrome extension called Evident Capture for IEP progress monitoring with my caseload. It lets me record a data point without leaving the tab I'm teaching in, which is the difference between recording a moment and losing it.

Extension ID: cncdhkidcikbapnogikhmbmokgmgnnkj
Chrome Web Store: https://chromewebstore.google.com/detail/cncdhkidcikbapnogikhmbmokgmgnnkj

Everything you'd normally ask me for is on one page, including the permission list with justifications, the data-handling summary, and the Admin console steps:
https://evidentk12.com/extension/it-approval

The short version: it requests no host permissions, so it cannot read the sites I visit. It reads a page only at the moment I click a capture button. It contains no ads, no trackers, and no third-party analytics, and student data goes only to our Evident account.

If it's easier to ask them directly, their privacy contact is privacy@evidentk12.com.

Thank you,

For the administrator: what this is

Evident Capture is a companion extension for teachers who already have an Evident account. It records IEP progress-monitoring data points and, when the teacher explicitly asks it to, attaches a quoted passage of student work or a screenshot as evidence. It is a capture surface for a system the teacher is already using, not a new store of record.

Extension name

Evident Capture: IEP Data Collection

Extension ID

cncdhkidcikbapnogikhmbmokgmgnnkj

Chrome Web Store

chromewebstore.google.com/detail/cncdhkidcikbapnogikhmbmokgmgnnkj

Publisher

Evident (evidentk12.com)

Manifest version

Manifest V3

Category

Education

Cost

Free. No in-extension purchases.

Privacy summary

evidentk12.com/extension/privacy

Privacy contact

privacy@evidentk12.com

Permissions requested, and why

These are the five permissions declared in the manifest, which you can verify in the Admin console, with the same justifications submitted to Google in the store review. Chrome's own install prompt warns on fewer than this: install warnings are driven by site access, and the extension requests none.

activeTab

Reads the current tab's title, address, selected text, or a screenshot only at the moment the teacher clicks a capture button in the popup. It grants no standing access and no access to other tabs.

scripting

Reads the teacher's highlighted text on the active tab, only on an explicit "Quote selection" click. No content scripts are injected on page load.

storage

Holds the sign-in session, a cached student list, display preferences, and the offline entry queue on the teacher's device.

alarms

Retries syncing queued offline entries about once a minute until they reach the teacher's Evident account.

identity

Opens the Evident sign-in and consent page so the teacher can connect their own account (Chrome's launchWebAuthFlow). No Google account scope is requested: the manifest declares no OAuth2 client, and the sign-in page is on evidentk12.com, not Google's authorization server.

What it cannot do

The usual review questions, answered directly. Each of these is a property of what the extension requests, not a policy promise, so it is verifiable from the manifest in the store listing.

• No host permissions. The extension requests no permission to read any website, so it cannot read pages you visit.
• No content scripts. Nothing is injected into pages as you browse.
• No access to browsing history, bookmarks, downloads, cookies, or credentials.
• No remote code. All executable code ships inside the reviewed package.
• No advertising, no third-party analytics, and no trackers inside the extension.
• No access to Google Drive. The extension requests no Drive scope and makes no Google API call of any kind.
• No access to student information systems or email.
• Nothing is read from any page except the text a teacher has highlighted, at the moment they click to attach it.

How student data is handled

What is captured

Progress-monitoring values the teacher enters (trials, frequency, duration, or met/not-met, with prompt level) against students on their own caseload, plus any passage of text the teacher highlights, or a screenshot of the active tab that the teacher chooses to attach. The title and address of the page a capture came from are saved with it, so each piece of evidence can be traced back to its source.

Where it goes

Only to the teacher's Evident account, over encrypted connections. A screenshot captures the visible area of the active tab; the teacher then either drags a region to crop, in which case only that region is uploaded, or chooses to send the full capture. The cropping happens on the device, so whatever the teacher excludes is never transmitted.

What stays on the device

The sign-in session, a cached student list, and any entries made while offline, which sync when the connection returns. Signing out of the extension deletes everything tied to the teacher's account. Two items are kept deliberately: a count of entries synced and a flag for whether the review prompt has been shown, neither of which identifies a student. The display preference is stored in Chrome's synced settings, so it follows the teacher to their other signed-in Chrome profiles; no student data is stored there.

Sub-processors

The extension introduces none beyond those already listed for the Evident platform. See the compliance overview.

Retention and deletion

Identical to data entered on evidentk12.com. Records a teacher keeps are retained for the life of the account. When a teacher deletes an evidence note it is hard-deleted, with any attached screenshot, 30 days later; an upload that is started but never attached is removed after 7 days; and deleting the account removes the records and their screenshots. See the privacy policy.

Displaying names in class

An initials-only mode replaces student names in the popup, so a teacher projecting their screen does not disclose a caseload to the room.

Allowlisting it in the Google Admin console

In the Google Admin console, go to Devices → Chrome → Apps & extensions → Users & browsers, select the organizational unit that should have it, then add the extension by ID:

cncdhkidcikbapnogikhmbmokgmgnnkj

Set it to Allow install so teachers choose whether to add it, or Force install to deploy it to a team. If your policy is "block all apps, admin manages allowlist, users may request," approving the teacher's pending request achieves the same thing. Because the extension holds no host permissions, there is no site-access decision to configure alongside it.

Access is revocable from your side and ours. Extension sessions are separate from web sessions and can be revoked independently. Deactivating an account ends the sessions it already holds, so a deactivated teacher's extension stops syncing rather than running on until its token expires. An organization can also disable extension access for all of its members at once, without affecting their use of the web app.

Privacy and compliance posture

Evident's program is built around FERPA requirements and GDPR-aligned practices, with COPPA considerations for younger students. Schools remain responsible for their own FERPA determinations, directory information policies, and parent rights processes; the extension is a tool inside that program, not a substitute for it. Evident's security documentation is organized against the SOC 2 Trust Services Criteria as a self-assessment; it is not a SOC 2 certification, and we do not describe it as one.

• Security overview — infrastructure, access control, encryption, and incident response.
• Compliance overview — regulatory posture and sub-processor disclosures.
• School procurement packet — data protection agreement, accessibility, rostering, and support detail for a full district review.
• Extension privacy summary — the plain-language version of this section.

For a data protection agreement, a completed vendor questionnaire, or anything not answered here, write to privacy@evidentk12.com. A person answers, and district reviews are the reason that address exists.