PDF Tools for Schools 2026 (FERPA-Conscious)

A special-education coordinator in a mid-size district is wrapping up the school year. Twelve students with IEPs are moving to a new grade level or new building. For each, she needs to share an IEP summary with the receiving general education teacher — the parts they need to teach effectively, with the parts that don’t need to be widely disseminated kept private. The IEPs are scanned PDFs from the contracted evaluation provider, 18-30 pages each, with PII on every page (student name, DOB, parent contact, diagnoses, evaluation scores). She has two hours before the staff meeting. She searches “redact PDF online”, drops in the first IEP, draws black rectangles over names and identifying details, downloads, repeats for the next eleven, and emails them to the receiving teachers.

In those two hours, she has done two things at once. First, she has uploaded twelve complete IEPs — each one a federally protected education record under FERPA — to a third-party server that has no Data Privacy Agreement with her district. That upload itself is the disclosure event under 34 CFR Part 99, and the school official exception under § 99.31(a)(1) likely does not apply because the vendor isn’t under the district’s direct control. Second, she has “redacted” each IEP by drawing black rectangles, which — as the 2019 Manafort federal court filing famously demonstrated — does not actually remove the underlying text. Any receiving teacher who copy-pastes from the “redacted” region recovers the original content.

She doesn’t know any of this. The redactions look right when she opens the file. The vendor’s privacy page mentioned GDPR and ISO 27001. The IEPs got to the receiving teachers on time. From her perspective, the workflow worked.

This guide is for educators, school administrators, special-education coordinators, registrars, and district-level technology leaders who want the convenience of modern PDF tools without creating FERPA exposure or inadvertently sharing PII through botched redaction. A practical evaluation of the PDF tools available in 2026 against the criteria that actually matter for K-12 and higher-education work — FERPA compliance, the School Official Exception requirements, COPPA for under-13 students, state-specific student privacy laws, true redaction for IEPs and evaluations, and the cases where the structurally simplest answer is a tool that never receives the student record in the first place.

Why PDF tools are a FERPA question, not just an IT question

For most professions, the choice of a PDF compressor is a productivity decision. For schools, it’s a regulatory-compliance decision because student education records are protected by a layered framework:

FERPA — Family Educational Rights and Privacy Act (20 U.S.C. § 1232g; 34 CFR Part 99). Protects the privacy of student education records maintained by any educational agency or institution receiving federal funding. This effectively covers all public K-12 schools, the vast majority of private K-12 schools that take federal funds for any program (Title I, IDEA, etc.), and virtually all colleges and universities. FERPA prohibits the disclosure of personally identifiable information (PII) from education records without prior written parental consent (or eligible student consent if the student is 18+ or in post-secondary), except in defined exceptions.

School Official Exception — 34 CFR § 99.31(a)(1)(i)(B). Allows disclosure to contractors, consultants, volunteers, or other outside parties to whom the school has outsourced institutional services, but only when the party (1) performs an institutional service the school would otherwise use employees for, (2) is under the school’s direct control regarding use and maintenance of records, (3) is subject to use restrictions and re-disclosure prohibitions under § 99.33(a), and (4) has a legitimate educational interest. The practical mechanism is the Data Privacy Agreement (DPA) — an executed contract that establishes the vendor as a school official for the limited scope.

COPPA — Children’s Online Privacy Protection Act (15 U.S.C. §§ 6501-6506; 16 CFR Part 312). Federal law governing the online collection of personal information from children under 13. For schools, COPPA intersects with FERPA when EdTech tools are used with K-6 and middle-school students. The FTC’s revised COPPA Rule, with updated parental consent requirements, took effect with full compliance required by April 2026 — making 2026 a heightened-attention year for K-12 EdTech compliance.

State Student Privacy Laws. Many states have layered student privacy statutes that go beyond FERPA. The most notable:

• New York Education Law § 2-d — requires districts to publish a Parents’ Bill of Rights for Data Privacy and Security, adopts the National Institute of Standards and Technology Cybersecurity Framework, and imposes specific data security requirements on vendors. Penalties for non-compliance range from $1,000 for a first violation to $10,000 for repeated violations.
• California SOPIPA (Student Online Personal Information Protection Act, 2014) — prohibits operators of K-12 online services from selling student data, using it for targeted advertising, or commercial profiling. Has become a model adopted (in modified forms) by 20+ states.
• Connecticut Public Act 16-189 — requires school districts to execute specific contract provisions with EdTech vendors, including data security, breach notification, and parental notification.
• Illinois SOPPA, Texas Student Privacy Statute, Colorado Student Data Transparency Act, Maryland Student Data Privacy Act — each adds state-specific requirements on top of FERPA.

IDEA (Individuals with Disabilities Education Act, 20 U.S.C. § 1400 et seq.). Layers additional confidentiality obligations on top of FERPA for special education records — IEPs, 504 plans, evaluations, behavior plans. The IDEA confidentiality requirements at 34 CFR §§ 300.610-300.626 incorporate FERPA standards plus additional restrictions specific to special education data.

The practical implication: for schools, the threshold question for any PDF tool is not “is it good?” but “is there a DPA, and what does the DPA actually cover?” A tool that processes the file locally on the educator’s device, with no upload, sidesteps the analysis — there’s no third-party disclosure to fit into the School Official Exception because no records leave the device.

The realistic enforcement picture

FERPA enforcement runs through the Family Policy Compliance Office (FPCO) at the U.S. Department of Education. The most severe sanction is loss of federal funding — which is the regulatory equivalent of the death penalty for a public school district. In practice, FPCO uses funding loss as a backstop and typically resolves issues through technical assistance and corrective action plans.

What changed in recent years is state enforcement and parent litigation:

• New York’s § 2-d has documented enforcement actions against districts for vendor contract failures.
• California’s SOPIPA has been the basis for both regulatory action and private litigation against EdTech vendors.
• The 2020 Illinois SOPPA implementation created district-level disclosure obligations that have led to public listings of vendors and have produced parent inquiries and (in some cases) litigation.
• Class action litigation under state student privacy laws has emerged, often piggybacking on data breach incidents.

The pattern: the most expensive incidents for districts tend to involve high-profile breaches at vendors that had inadequate DPAs (or no DPA at all). The discovery in those incidents usually finds that the district had been using the tool informally without a fully executed vendor contract.

For day-to-day PDF processing, the lesson is direct: if a tool processes student education records, the tool needs a DPA. If you don’t have a DPA, either get one before using the tool with student data — or use a tool that doesn’t receive student data in the first place.

The “true redaction” problem in education

Before evaluating individual tools, one technical point that comes up repeatedly in school PDF work: redaction of student PII.

Educational PDFs frequently need redaction for legitimate reasons — sharing IEP excerpts with new teachers, releasing records to parents while redacting other students’ information, providing transcripts to colleges with sensitive disciplinary notes removed, redacting student names from work samples used for staff training, redacting third-party information from records released under state public records laws (FOIA at the state level). The temptation, in every case, is to draw a black rectangle in a generic PDF editor.

This fails. The 2019 Manafort federal court filing remains the most-cited example: black rectangles drawn over text are visual overlays in the rendering layer, not removals from the content stream. The underlying text is still in the PDF and can be recovered by anyone who copy-pastes from the redacted region, opens the file in a different viewer, or runs a basic text-extraction tool. In a school context, this can mean a student’s name, diagnosis, disciplinary record, or evaluation scores recovering from what looks like a properly redacted document.

True redaction has three steps:

1. Mark the content using a tool that targets the underlying text and image streams (not just a drawing layer).
2. Apply the redaction — the tool removes the content from the file and replaces it with an opaque region in the actual content stream.
3. Sanitize the document — strip metadata (author, title, edit history, XMP fragments, OCR text layers from scanned originals), remove form fields, flatten layers.

For records released outside the district (transcripts to colleges, records released under state public records laws), many districts add a fourth step: rasterize the redacted page as an image so no original text layer survives.

For IEPs specifically, many special-education coordinators prefer to produce a separate clean summary document rather than redact a complex multi-page IEP. Creating new text in a fresh file is structurally safer than trying to redact a heavily formatted document where redaction misses are easy.

The criteria we evaluate against

For each tool, we look at:

1. DPA availability — does the vendor offer a Data Privacy Agreement compliant with FERPA’s School Official Exception, and what does the DPA scope cover?
2. Architecture — where does the file go? In-browser (local processing) or server upload? If server, what country, what retention, what subprocessors?
3. True redaction — does the redact feature remove underlying content, sanitize metadata, and survive a copy-paste test?
4. E-signature with parent-friendly workflow — does it support permission slips, photo releases, and parent signature collection with an audit trail?
5. Integration with student information systems (SIS) and learning management systems (LMS) — PowerSchool, Infinite Campus, Skyward, Schoology, Canvas, Google Classroom.
6. State student privacy law compliance — particularly NY § 2-d, California SOPIPA, Connecticut PA 16-189, Illinois SOPPA.
7. Pricing for single school, small district, and large district.

The tools — evaluated

1. imisspdf — in-browser, no education record ever leaves the device

• DPA availability: Not applicable — no records ever reach our infrastructure, so no third-party disclosure occurs and the School Official Exception analysis doesn’t apply.
• Architecture: 100% in-browser via WebAssembly. Files never upload. Student records stay on the educator’s device.
• Redaction: Visual redaction with optional flatten/rasterize, which is the forensically secure path. Metadata removed during flatten.
• E-signature: Individual signing supported (typed, drawn, image). No multi-party routed signing or parent-collection workflow — use a dedicated platform (ParentSquare, DocuSign, Adobe Sign) for permission slips.
• Integration: Works alongside any SIS or LMS because there is no integration — it’s a webpage that processes files locally.
• Pricing: Free for individual use across the district, no signup, no per-seat licensing.

Best for education: routine educator document work where files contain student PII — sharing IEP excerpts with new teachers, compressing transcripts for archival, OCR on scanned permission slips, drafting redacted record excerpts before release, watermarking confidential meeting notes, password-protecting record deliverables. Not the right tool for: parent-facing permission slip workflows (use ParentSquare, DocuSign, or your SIS’s parent module), high-volume registrar-office records management (use Adobe Acrobat Pro on registrar machines), or integrated LMS workflows.

2. DocHub — popular K-12 PDF editor, varying DPA posture

• DPA availability: DocHub offers FERPA-conformable terms for K-12 customers; districts should verify the current DPA template against state-specific requirements (NY § 2-d, Illinois SOPPA, California SOPIPA) before signing.
• Architecture: Cloud-based; documents upload to DocHub servers.
• Redaction: Basic redaction features; verify metadata sanitization before relying for external release.
• E-signature: Yes, with audit trail.
• Integration: Google Workspace and Microsoft 365 integration; available in Google Workspace Marketplace.
• Pricing: Free tier with limited features; Pro tier ~$7/user/mo; education pricing available.

Best for education: classroom-level document workflows where the district has executed a current DPA — teacher worksheets, student-completed forms collected via Google Classroom, basic signature collection. Caveats: confirm the DPA is current and covers all the use cases your educators will exercise. For confidential records (IEPs, evaluations, disciplinary files), the architectural concern of upload remains — an in-browser tool keeps those files local.

3. Adobe Acrobat Pro — enterprise standard, education licensing available

• DPA availability: Yes, on Adobe Acrobat for Enterprise and Adobe for Education tier. Confirm scope with Adobe education sales — standard Pro for Teams does not automatically include education-specific FERPA terms.
• Architecture: Desktop app processes locally; optional Document Cloud sync uploads to AWS US servers. For confidential records work, disable Document Cloud sync.
• Redaction: Industry-standard true redaction with content removal, metadata sanitization, Sanitize Document action. Strongest redaction feature in the evaluated set.
• E-signature: Adobe Sign / Acrobat Sign with multi-party routing, audit trail. Adobe Sign for Education has FERPA-conformable configuration available.
• Integration: Works with Microsoft 365 (Word/Excel/PowerPoint to PDF), Google Workspace, and most LMS platforms via standard PDF workflows.
• Pricing: Adobe Acrobat for Education ~$14.99/user/mo (district pricing). K-12 Education volume licensing through Adobe Value Incentive Plan.

Best for education: registrar offices, district central offices, special-education coordinators who need true redaction for IEP releases and transcript management, and any role producing high-volume official record products. Caveats: this is desktop software with a learning curve; many classroom teachers won’t use most features. License only the roles that need it.

4. DocuSign for Education — gold-standard parent-signature workflow

• DPA availability: Yes, DocuSign offers a dedicated Education tier with FERPA-conformable configuration. Major districts have negotiated DocuSign DPAs covering NY § 2-d, California SOPIPA, and other state laws.
• Architecture: Cloud-only. Documents upload to DocuSign infrastructure with US regional residency.
• Redaction: Not a focus — DocuSign is signing-only.
• E-signature: Industry standard — permission slips, photo releases, medication consent forms, IDEA prior written notice acknowledgments, FERPA disclosure consents, tech use agreements. Multi-party routing, conditional logic, court-admissible audit trail.
• Integration: PowerSchool, Infinite Campus, Skyward, Workday, and most major SIS platforms have DocuSign integrations.
• Pricing: Education tier custom-quoted; typically lower per-envelope cost than commercial DocuSign. Annual contracts at district level.

Best for education: any district that has moved away from paper permission slips and needs an audit trail for parent signatures on consent forms, with state-law-specific configuration available. Use alongside, not instead of, a PDF editor — DocuSign doesn’t merge, compress, OCR, or redact. A typical school stack pairs DocuSign for Education with imisspdf for daily editing.

5. ParentSquare — parent communication platform with built-in signing

• DPA availability: Yes — ParentSquare has earned iKeepSafe COPPA Safe Harbor, FERPA, and California Student Data Privacy Certifications, and publishes a standard DPA used by districts across the country. ParentSquare does not sell personal data or share for targeted advertising.
• Architecture: Cloud-based parent communication platform with integrated form-and-signature workflows.
• Redaction: Not a feature — this is a communication platform, not a PDF editor.
• E-signature: Built-in form and signature collection with parent-friendly interface, especially strong for permission slips, photo releases, and home language preferences. Lower friction than DocuSign for parents who already have ParentSquare for communication.
• Integration: PowerSchool, Infinite Campus, Skyward, ClassDojo data sync, Google Classroom, Microsoft 365 Education.
• Pricing: Annual district licensing; varies by enrollment.

Best for education: K-12 districts that already use ParentSquare for family communication and want a unified form-and-signature experience for parents. The certification stack (iKeepSafe COPPA Safe Harbor + FERPA + California Student Data Privacy) gives a clean compliance posture for the family communication and signature layer specifically. Caveats: like DocuSign, this is the signing layer, not the PDF editing layer. Pair with a PDF tool for document content work.

6. Bloomz — parent communication alternative

• DPA availability: Bloomz offers a standard DPA for K-12 districts; verify current terms against your state’s specific student privacy requirements before adopting.
• Architecture: Cloud-based parent communication platform with permissions slip and form workflows.
• Redaction: Not a feature.
• E-signature: Built-in form and signature collection for routine parent authorizations.
• Integration: Various SIS integrations; verify with current Bloomz technical documentation.
• Pricing: Tiered pricing for schools and districts.

Best for education: schools and small districts seeking an alternative to ParentSquare with similar parent-facing functionality. Caveats: same architectural notes as ParentSquare — this is signing and communication, not PDF editing.

Quick comparison matrix

Tool	Architecture	FERPA fit	True redaction	Parent e-sign workflow	Pricing
imisspdf	In-browser (local)	No third-party disclosure	Yes (with flatten)	Individual only	Free
DocHub	Cloud	DPA required and available	Basic	Yes (audit trail)	Free / $7/user/mo
Adobe Acrobat Pro	Local desktop + optional cloud	DPA on Enterprise/Education	Yes (industry standard)	Yes (Adobe Sign)	~$14.99/user/mo (Education)
DocuSign for Education	Cloud	DPA available	N/A	Yes (gold standard)	Custom district
ParentSquare	Cloud	iKeepSafe FERPA + COPPA certified	N/A	Yes (built-in)	District licensing
Bloomz	Cloud	DPA available	N/A	Yes (built-in)	Tiered

Common educator PDF workflows and the right tool for each

These mappings are starting points. Your district’s existing vendor relationships, DPA inventory, and SIS choice will shift the calculus.

Sharing IEP excerpts with new teachers at year transition

• In-browser tool (imisspdf) for creating a redacted excerpt or building a new summary document. No upload means no third-party disclosure.
• Avoid uploading the full IEP to a tool without a current DPA covering special-education records.

Permission slips, photo releases, medication consent

• ParentSquare or DocuSign for Education for parent signature collection with audit trail. Both have certifications and DPAs that fit the routine consent workflow.

Transcripts for college applications

• Registrar-level Adobe Acrobat Pro for batch generation, redaction of sensitive notes, PDF/A archival of permanent records.
• Final delivery via official transcript service (Parchment, eScrip) or secure portal; not via consumer cloud tools.

Public records requests (state FOIA equivalents)

• Adobe Acrobat Pro desktop for true redaction of third-party PII before release. Document each redaction.
• In-browser tool for staff drafting and quality-check passes that don’t require enterprise-grade redaction.

Disciplinary records released to parents under FERPA Section 99.10

• In-browser tool for the redaction pass to remove other students’ PII from the record before release.
• Final release via secure portal or password-protected delivery.

Classroom handouts and instructional material

• Any tool is fine — no PII involved. Teacher convenience drives the choice.

Staff evaluations and HR documents

• These are personnel records, not education records — different framework (state HR confidentiality, not FERPA). In-browser tools still simplify the analysis.

The 7-question checklist before adopting any PDF tool

Before your district standardizes on a PDF tool — or before an individual school adopts something at building level — answer these seven questions in writing. Keep the answers in your vendor file. If a state student privacy regulator or a parent ever asks how the district vetted the tool, this is the documentation.

1. Does the vendor execute a Data Privacy Agreement compliant with FERPA’s School Official Exception and our state’s specific student privacy law? Get the DPA in writing before any educator uses the tool with student records. Confirm scope covers all the use cases.

2. For DPAs specifically, does the agreement bind the vendor on the four points required by 34 CFR § 99.31(a)(1)(i)(B)? (1) institutional service the school would otherwise perform, (2) direct school control over use and maintenance, (3) use restrictions per § 99.33(a), (4) re-disclosure prohibition.

3. What state-specific student privacy laws does the vendor address in their DPA template? For NY districts, NY § 2-d. For California districts, SOPIPA. For Illinois districts, SOPPA. For Connecticut districts, PA 16-189. Vendors with strong K-12 posture have state-specific addenda or matrices.

4. What is the vendor’s posture on the revised COPPA Rule (effective April 2026) for use with under-13 students? Districts using EdTech tools with K-6 and middle-school students should confirm verifiable parental consent mechanisms or the school-acts-on-behalf-of-parent framework is in place.

5. What is the vendor’s documented breach history? Check state attorney general breach archives, the K-12 SIX breach map, and reputable EdTech security publications. Absence of a breach isn’t a guarantee; pattern of breaches is a warning.

6. For the redact feature: does it remove underlying content, sanitize metadata, and survive a copy-paste test? Test on a non-student document before relying on it for actual records release.

7. What is the exit path? How does the district get its data out if the contract ends? Are there summer-purging requirements (some state laws require deletion of records at end of contract)? Can records be exported with audit logs intact for state-required retention periods?

If a vendor’s answers are weak — especially on 1, 2, and 6 — reconsider whether they belong in the district stack. For routine educator daily work, an in-browser tool that creates no third-party disclosure dramatically simplifies all seven questions.

A note on the DPA versus DPA confusion

Two unrelated documents share the acronym “DPA” and educators encounter both:

• Data Privacy Agreement (the FERPA-specific contract for K-12) — establishes a vendor as a school official under § 99.31(a)(1), commits the vendor to FERPA-compliant use and re-disclosure restrictions, and addresses state-specific student privacy law requirements. This is the document school districts care about.

• Data Processing Agreement (the GDPR-specific contract for EU work) — establishes a processor as bound to controller instructions under EU data protection law. Different framework, different binding standards.

Many international vendors publish a Data Processing Agreement (GDPR-style) and use it as their generic “DPA” template. That document does not by itself satisfy FERPA’s School Official Exception. Districts need either a specific Data Privacy Agreement template or a vendor’s executed addendum covering the FERPA points.

The major K-12-focused vendors (DocuSign for Education, ParentSquare, PowerSchool, ClassDojo, Schoology, Canvas, Google Workspace for Education) have FERPA-specific DPAs available. Many smaller-scale or international tools do not.

Recommended stacks by school type

These are starting points, not absolutes. Your existing SIS, LMS, and parent communication choices will shift the calculus.

Single private school or small charter, K-8

• Daily PDF work: imisspdf (free, in-browser) for all teachers and administrators
• Parent permission slips and photo releases: ParentSquare or Bloomz (district licensing)
• Registrar / transcripts: Adobe Acrobat for Education on the registrar’s machine
• Total monthly cost: parent communication platform pricing only

Mid-size K-12 district (3-15 schools)

• Daily PDF work: imisspdf for all educator-level use; Adobe Acrobat for Education on registrar and central office machines
• Parent communication and signing: ParentSquare district-wide; DocuSign for Education for IDEA prior written notices and other formal consents
• Special-education records: in-browser redaction for excerpt creation; Adobe Pro for full record management
• Total per-educator cost: minimal; most cost is at registrar and central office

Large district (15+ schools)

• Daily PDF work: imisspdf as district default; Adobe Acrobat for Education licensed to roles that need power features
• Parent communication: ParentSquare or equivalent integrated with SIS
• E-signature: DocuSign for Education with district-wide DPA and state-law-specific addenda
• Records management: dedicated records DMS plus Acrobat for processing
• Add: dedicated student privacy officer per state requirements (NY § 2-d requires Data Protection Officer)

Higher education

• Daily PDF work: imisspdf for routine work; Adobe Acrobat for Education for power features. Each faculty member’s own laptop is the security perimeter for confidential student work.
• Registrar / official records: enterprise records management with full audit trail; Acrobat Pro for redaction work
• Student-facing signing: DocuSign or Adobe Sign for enrollment, financial aid, and academic policy acknowledgments
• Research with student data: IRB-supervised; tools depend on institutional review

The honest verdict for schools

The “best PDF tool for schools” is not a single tool. It’s a stack that matches the regulatory profile of each document type to the architecture that handles it best. The framework is:

• For routine educator work involving student PII — in-browser tools (imisspdf) eliminate the upload step and the School Official Exception analysis entirely. Free, fast, and the structurally simplest answer to FERPA’s third-party disclosure concern.
• For permission slips, photo releases, and parent consent collection — dedicated communication and signing platforms (ParentSquare, DocuSign for Education) with executed DPAs are the right tool because parents need a friendly signing interface and the audit trail is the evidence.
• For records office, registrar, and special-education coordinator power work — Adobe Acrobat for Education on dedicated machines provides true redaction, batch processing, PDF/A archival, and the feature depth registrars need.
• For non-PII classroom material — any tool teachers prefer is fine; the regulatory framework doesn’t apply to instructional content without student identifiers.

The frame to hold: decide per document, not per tool. An IEP excerpt and a multiplication worksheet are not the same regulatory category just because they happen to be PDFs. Use the architecturally appropriate tool for each.

A note on summer transitions: many districts purge or archive records at end of school year per state law (NY § 2-d has specific provisions; California, Illinois, others have similar). Make sure whichever cloud tools you use have configurable retention and clear audit logs to support that obligation.

Try the in-browser tool for your next student record

If the architectural reasoning above is compelling, imisspdf runs every common PDF tool in your browser — merge, split, compress, convert, OCR, sign, edit, watermark, redact, page numbers, and the rest. No upload, no signup, no daily limit, no file-size cap beyond your device’s RAM. Free, with no premium tier gating the core features. Because no education record ever reaches our servers, there is no third-party disclosure to fit into the School Official Exception, and no DPA to negotiate for routine in-browser use.

The fastest way to test: take a non-PII document — a classroom worksheet, a generic school calendar — run it through imisspdf, then run the same document through your current cloud tool, and time the difference. Open imisspdf →

Frequently asked questions

The FAQ block at the top of this article covers the most common questions K-12 and higher-education staff ask before adopting a new PDF tool. For deeper analysis of specific cloud tools, see our iLovePDF safety review, imisspdf vs Adobe Acrobat Online, and our adjacent industry guides for healthcare HIPAA and legal practice ABA Rule 1.6 considerations. For procurement-ready compliance prep, see our PDF Security Checklist for Business — 50+ items aligned with FERPA + COPPA + state student-privacy acts.

Sources

• eCFR — 34 CFR Part 99 (FERPA regulations)
• Cornell LII — 34 CFR § 99.31 conditions for prior consent
• US Department of Education — Protecting Student Privacy
• Studentprivacy.ed.gov — FERPA Exceptions Summary
• FTC — Children’s Online Privacy Protection Rule (COPPA)
• eCFR — 16 CFR Part 312 COPPA Rule
• US Code — 15 U.S.C. § 6501 COPPA Definitions
• NY State Senate — NY Education Law § 2-d
• NYSED — Education Law Section 2-d Definitions
• Parent Coalition for Student Privacy — State Student Privacy Laws
• Public Interest Privacy Center — State Student Privacy Laws
• Public Interest Privacy Center — FERPA Exceptions
• ParentSquare — iKeepSafe COPPA Safe Harbor + FERPA Certification
• ParentSquare — Data Privacy & Security
• Manafort redaction failure — ABA Journal analysis
• DocuSign Trust Center

Frequently asked questions

Related articles