Data Use Agreement

RFSL Data Use Agreement

Version RFSL-DUA-2026-11-10.1 | Standard text published November 10, 2026

1. Parties, purpose and applicable version

This Data Use Agreement (DUA) is between Crudspa Foundation (Crudspa) and the legal organization identified in the parties' signed Program Order (Customer). It governs the identifiable student, family, staff and program information lawfully provided for READS for Summer Learning (Customer Data). It applies when the parties execute a DUA signature schedule identifying this version, or execute another agreement expressly incorporating this version. Publishing or reading this page, completing an interest form or supplying planning information does not execute a DUA. A later website revision does not change an executed agreement.

Customer retains lawful direction and control of Customer Data, subject to the rights of individuals and originating schools or other lawful controllers. No agreement transfers ownership of an individual's privacy rights. Crudspa receives only permission necessary to deliver the agreed RFSL services under documented Customer instructions and applicable law.

2. Authority to disclose and process

Before identifiable student data is transferred, the parties complete the data/authority schedule identifying Customer's legal entity and signer, jurisdiction, data source, purposes, categories, authorized recipients, term and permitted disclosure basis. Customer represents that it has the authority recorded in that schedule and will supply evidence through the approved secure channel on reasonable request. Signing this DUA does not itself create that authority.

Where an educational agency or institution relies on FERPA's school-official exception, it must establish the applicable school-official relationship, legitimate educational interest, direct control over use and maintenance, and required limits on use and redisclosure. Crudspa performs only the specified institutional service and remains subject to those limits. Customer must identify the responsible school/agency and the applicable written instructions; a community organization cannot designate itself a school official merely by selecting an organization type.

For a community organization, the signed Community Data Authority Rider must establish either a documented school-authorized service/contractor chain that permits Crudspa's processing, or an appropriate direct parent/guardian or eligible-student authorization for the program's collection and use. Educational records obtained from a school require the school's lawful disclosure basis as well. A club registration, general membership waiver or reminder opt-in is not a substitute. Required notices, verification and consent for children's online collection must be addressed before access is enabled; neither party transfers away an operator's own legal obligations.

Customer will not provide data beyond its authority. If authority is missing, disputed or withdrawn, the affected transfer/processing is paused while the parties determine lawful instructions. The parties cooperate to restrict access, correct inappropriate data, meet preservation obligations, and return/delete data as required. The remaining program is not automatically canceled by an individual's decline of optional reminders.

3. Data minimization and permitted use

The signed schedule specifies the minimum data required: student identifier, name, grade, participating school/site/classroom, program enrollment, assigned survey responses and relevant reading measure; implementation/teacher contact information; and parent/contact information and consent evidence only for approved communication workflows. School/site packing destinations may be used for fulfillment. Home addresses, full dates of birth, Social Security numbers, health/disability records, immigration information and unrelated education records are excluded unless separately justified, expressly agreed and lawfully authorized.

Crudspa uses Customer Data only to provide contracted program access, validate rosters, administer assigned surveys, select books, prepare authorized fulfillment, support approved communications, provide authorized operational reporting and support, and protect the service. Data must not be used for targeted advertising, sale, unrelated profiling, unrelated AI/model training, or independent research without separate lawful authority and written agreement. Staff access follows least privilege and the agreed program scope.

4. Vendors, partners and disclosure

Crudspa may use service providers for hosting, secure transfer, support, messaging and fulfillment. Providers may access only data needed for their assigned function and must be bound by appropriate confidentiality, security and use/redisclosure obligations. Supplier manifests contain the minimum school/classroom/student/book packing information; contracts, invoice details, survey answers and internal recommendations are not supplier fields.

Harvard/READS RFSL planning and content administration does not include identifiable student or family data. Properly de-identified aggregate information may be shared only consistently with applicable law and Customer requirements, with no re-identification or unauthorized onward disclosure. Identifiable research disclosure requires a separate written authorization or other applicable legal basis and approved terms; this DUA is not a blanket research release.

Crudspa may disclose information to the extent legally required, providing notice when permitted and reasonably assisting Customer in responding. Customer may request the current service-provider/data-flow information needed for its review. A vendor's technical availability alone is not permission to disclose Customer Data.

5. Security and incident response

Crudspa maintains reasonable administrative, technical and physical safeguards appropriate to the data, including encryption in transit using TLS 1.2 or higher, strong encryption at rest, role-based least-privilege access, privileged-system multi-factor authentication, access logging/monitoring and incident-response procedures. Customer Data is stored in cloud environments in the continental United States unless Customer approves another arrangement in writing. The parties use approved secure transfer channels for student/family data and sensitive authorization evidence; ordinary inquiry forms and public pages are not roster-upload channels.

Crudspa notifies Customer without unreasonable delay and no later than twenty-four hours after confirming unauthorized access to or disclosure of Customer Data, with known facts and continuing containment/remediation updates. Any shorter mandatory legal deadline controls. The parties reasonably cooperate on required notices and response. Available security/assessment summaries may be supplied under appropriate confidentiality and third-party restrictions; this DUA does not assert a particular certification or guarantee that no incident can occur.

6. Individual requests, reminders and data quality

Customer maintains an accountable privacy contact and coordinates access, correction, export, withdrawal and deletion requests. Crudspa assists with authorized requests and verifies the requester and relevant controller before disclosing data. For direct community participation, the schedule must identify how a parent/guardian or eligible student can contact Customer and Crudspa; the absence of a school district must not eliminate those rights.

Reminder enrollment is voluntary and separate from authority for participation data. Preserve the presented consent text/version, identity match, timestamp and current opt-out/suppression. Consent to RFSL or this DUA is not permission for recurring SMS. Withdrawal from reminders does not withdraw a student's survey, license or books.

7. Retention, return and deletion

Retain Customer Data only for the agreed service and applicable legal/contractual requirements. Unless a different lawful period is agreed in writing, student-level data is not retained longer than two years after the RFSL service relationship ends. On Customer's authorized request after expiration/termination, return or securely destroy Customer Data within thirty days and provide written certification of destruction, subject to mandatory retention and properly documented legal holds. Identify any required retained subset and restrict its use. Backup copies follow documented protected expiry/destruction procedures and are not restored for unrelated use.

Customer's request cannot authorize deletion contrary to an originating school's obligations or individual rights; resolve the responsible controller and required preservation before action. Confidentiality, permitted-use restrictions and post-termination data handling survive while data is held.

8. Contract administration

The executed signature/data schedule records the program, version, parties, authorized signers, instructions and notices. Customer-supplied DUA terms or state riders replace or supplement these terms only when both parties execute the specifically identified version and reconcile conflicts. The executed DUA controls privacy/security conflicts with the services agreement. Governing law, dispute terms and any lawful liability allocation follow the executed packet; nothing here waives nonwaivable rights or permits an unlawful disclosure. Amendment requires written agreement, not an unannounced page edit.

Privacy questions: support@crudspa.org. The general privacy policy describes website and service practices; it does not replace the program's executed DUA or the required data/authority schedule.