Export the district application report to CSV
Download a full snapshot of district applications, usage, governance status, and AI privacy scores.
In this article
The District Application Report provides a list of applications available to your organization, along with key details such as application name, URL, tags, usage across the organization, and most active users.
Use this report to see which apps are deployed, where they’re used, and privacy risk assessments.
Before you begin
- Role required: District Admin with permission to run reports.
- If your organization doesn’t yet have the District Application Report available, contact SchoolDay Support to request it.
Procedure
- In the PGC, go to Reports > District Application Report.
- (Optional) Use filters or search to narrow the list of applications.
- Click Export to CSV. The report will be prepared, and a CSV file will be downloaded to your computer.
/pgc-applications-export-to-csv.png?width=670&height=282&name=pgc-applications-export-to-csv.png)
Report field reference
The generated report includes the following fields.
Core application information
|
Field Header |
Format |
Description |
|---|---|---|
|
Name |
Text |
Application or website observed in use across the district, e.g. "Google Mail". |
|
URL |
Text — a full web address |
The app's primary web address; its unique identifier in PGC, e.g. "https://mail.google.com". |
|
Assigned Tags - All Tags assigned to the application (pipe separated) |
Tag names separated by |; blank when no tags are assigned |
Tags applied by district staff, drawn from your PGC tag groups, e.g. "Approved|High Priority". |
|
Privacy Shield - Yes/No |
Boolean |
Whether PGC tokenizes the PII sent to this app, so the vendor never receives real student data. |
Governance and review status
|
Field Header |
Format |
Description |
|---|---|---|
|
Risk Level |
Enum (Low, Medium, High, Not scored) |
Band of the composite 0–100 privacy score PGC synthesizes from all the metadata it holds about the app: Low (0–40), Medium (41–70), High (71–100). A higher band means more risk. Returns Not scored when your district has not scored the app, e.g. "Medium". |
|
Awaiting Review Status - Yes/No |
Boolean |
Approval workflow: queued for review, not yet picked up by a reviewer. |
|
In Review Status - Yes/No |
Boolean |
Approval workflow: a reviewer is actively evaluating this app. |
|
Approved for Use - Yes/No |
Boolean |
Approval workflow: reviewed and cleared for district use. |
|
Rejected for Use - Yes/No |
Boolean |
Approval workflow: reviewed and not permitted for district use. |
Risk Level replaces the numeric Risk Score used in earlier exports. The same band appears in the Risk Level column on the Applications page and in the Overall Risk Level card on an application's details page, so a file and the console always agree.
Usage and adoption metrics
|
Field Header |
Format |
Description |
|---|---|---|
|
Number of Active Users (last 12 months) |
Integer |
Distinct users who opened this app in 12 months, measured by the PGC extension, e.g. "1375". |
|
Usage time - in minutes (last 12 months) |
Decimal, two places |
Total active minutes spent in this app over 12 months, measured by the PGC extension, e.g. "35916.78". |
|
Most Active Schools - Top 5 listed |
Up to five school names separated by |
The schools with the highest usage of this app, e.g. "Lincoln Elementary|Washington Middle School". |
Detected PII usage
|
Field Header |
Format |
Description |
|---|---|---|
|
Detected PII Usage - First name |
Boolean |
The extension observed a user typing a first name into this app. |
|
Detected PII Usage - Last name |
Boolean |
The extension observed a user typing a last name into this app. |
|
Detected PII Usage - Email Address |
Boolean |
The extension observed a user typing an email address into this app. |
Suspected PII usage
|
Field Header |
Format |
Description |
|---|---|---|
|
Suspected PII Usage - First Name |
Enum (Likely, Unknown, Pending Evaluation, N/A) |
AI policy analysis suggests first names are collected. N/A means there is not enough data to say, e.g. "Likely". |
|
Suspected PII Usage - Last Name |
Enum (Likely, Unknown, Pending Evaluation, N/A) |
AI policy analysis suggests last names are collected, e.g. "Unknown". |
|
Suspected PII Usage - Email Address |
Enum (Likely, Unknown, Pending Evaluation, N/A) |
AI policy analysis suggests email addresses are collected, e.g. "Likely". |
|
Suspected PII Usage - Physical Address |
Enum (Likely, Unknown, Pending Evaluation, N/A) |
AI policy analysis suggests physical addresses are collected, e.g. "N/A". |
|
Suspected PII Usage - Phone Number |
Enum (Likely, Unknown, Pending Evaluation, N/A) |
AI policy analysis suggests phone numbers are collected, e.g. "Pending Evaluation". |
|
Suspected PII Usage - Social Security Number |
Enum (Likely, Unknown, Pending Evaluation, N/A) |
AI policy analysis suggests Social Security numbers are collected, e.g. "N/A". |
Privacy Policy AI Review scores
Every score is generated by AI analysis of the application's published privacy policy. A higher score always means a clearer, more protective policy. A column returns N/A when the app's policy has not been analysed.
|
Field Header |
Format |
Description |
|---|---|---|
|
Privacy Policy AI Review - Total Score |
Integer, 0–100, or N/A |
Sum of the ten category scores below, e.g. "78". |
|
Privacy Policy AI Review - Information Collected Score |
Integer, 0–10, or N/A |
How completely the policy states what data the app collects, e.g. "8". |
|
Privacy Policy AI Review - Data Sharing Score |
Integer, 0–10, or N/A |
How clearly the policy states who data is shared with, and why, e.g. "6". |
|
Privacy Policy AI Review - User rights Score |
Integer, 0–10, or N/A |
How well the policy explains rights to access, correct, delete, or export data, e.g. "7". |
|
Privacy Policy AI Review - Compliance with Laws Score |
Integer, 0–10, or N/A |
How specifically the policy addresses FERPA, COPPA, and state student-privacy law, e.g. "9". |
|
Privacy Policy AI Review - Overall Clarity & Transparency Score |
Integer, 0–10, or N/A |
How readable and unambiguous the policy is for a non-legal reader, e.g. "7". |
|
Privacy Policy AI Review - Use of Information Score |
Integer, 0–10, or N/A |
How clearly the policy states what data is used for, including secondary uses, e.g. "8". |
|
Privacy Policy AI Review - Security Measures Score |
Integer, 0–10, or N/A |
How specifically the policy describes encryption, access control, and breach response, e.g. "8". |
|
Privacy Policy AI Review - Retention Period Score |
Integer, 0–10, or N/A |
How clearly the policy states how long data is kept and when it is deleted, e.g. "6". |
|
Privacy Policy AI Review - Update to the Privacy Policy Score |
Integer, 0–10, or N/A |
How the policy changes over time and how users are notified, e.g. "9". |
|
Privacy Policy AI Review - Contact Information Score |
Integer, 0–10, or N/A |
Whether the policy gives a usable privacy contact for questions or requests, e.g. "10". |
Note: If you read the export with a script
As of September 28, 2026, three things changed in this file, and each one breaks a reader that assumes the old export:
- Risk Score is now Risk Level, and returns Low, Medium, High, or Not scored instead of a number. Anything that sorts on it or applies a numeric threshold must match on those text values.
- Row 2 is a description row, not an application. Start reading data at row 3.
- Columns have been added and split. Match on column names rather than position.
Next steps
- Manage application approvals: Review apps flagged in the report.
- Manage application tags: Update tags to reflect reviewed status.