FACTS Data Protection Terms

The FACTS Data Protection Terms describe how Nelnet Business Solutions, Inc. d/b/a FACTS Management Company (“FACTS”) protects the personal information it handles in providing its services, and the rules that apply to organizations that receive that information at a customer’s direction. They are a set of separate documents. Each document applies to a particular role, has its own definitions and version number, and is accepted and updated on its own.

This page is an overview to help you find the right document. It is not part of any document and does not change any of them. If anything on this page differs from a document, the document controls.
Document Version Last updated
Data Processing Addendum (with Annex 1) 1.0 November 20, 2026
Data Access Terms 1.0 November 20, 2026
API and Integration Terms 1.0 November 20, 2026
AI Feature Terms 1.0 November 20, 2026

Prior versions of each document are available here on this page.

Answers to common questions are available here on this page.

Which Documents Apply

An organization is bound only by the documents that match the role it holds in a particular arrangement. Accepting a document does not, by itself, give any organization access to another organization’s data, and the documents do not determine any organization’s legal status under privacy laws (see Section II(B)(1) of the Data Processing Addendum).

Document Applies to When it applies
Data Processing Addendum (with Annex 1) A Customer: any organization that contracts with FACTS for Services, such as a public or private school, school district, diocese, school network, or scholarship granting organization When FACTS processes Personal Information to provide Services to that Customer
Data Access Terms A Recipient: any organization that receives a Customer’s Personal Information at that Customer’s direction for a limited purpose permitted by the Data Access Terms When FACTS gives that Recipient access to a Customer’s Personal Information, whatever the type of Customer or Recipient
API and Integration Terms An Integration Vendor: a Customer’s own software vendor or service provider that connects to the Services through an API or other integration When FACTS makes a Customer’s Personal Information available to that vendor through an integration that FACTS enables at the Customer’s direction
AI Feature Terms A Customer that uses AI features in the Services When the Customer subscribes to, enables, or instructs FACTS to enable an AI feature

One organization can hold more than one role. For example, a scholarship granting organization can be a Customer for its own scholarship program and a Recipient of a school’s data. Each document then applies separately to the data that role covers.

Common arrangements.

The following examples are illustrative, not exhaustive. The documents control.

Arrangement What applies
A school (parochial, independent, charter, or public) contracts with FACTS for itself The Data Processing Addendum. FACTS follows the school’s instructions (Section II(B)(2)(a) of the Data Processing Addendum).
A school or district has signed an NDPA or other state student data privacy agreement with FACTS That agreement governs within its scope (Data Processing Addendum, Section X(B)). The Data Protection Terms apply only to matters it does not address, such as the Data Access Terms for sharing the school directs.
A Group Customer (such as a diocese, school network, association, or charter management organization) contracts for its schools, and the Agreement provides that each school directs its own data The Data Processing Addendum. Each school directs its own data and is a Customer for it (Section II(B)(2)(b) of the Data Processing Addendum). The Group Customer may give instructions on a school’s behalf unless the school says otherwise.
A Group Customer contracts for its schools and directs their data The Data Processing Addendum. FACTS follows the Group Customer’s instructions (Section II(B)(2)(a) of the Data Processing Addendum), and the schools perform school-level duties (Section II(F) of the Data Processing Addendum).
A scholarship granting organization or other organization contracts for its own program The Data Processing Addendum. FACTS follows that organization’s instructions for its program (Section II(B)(2)(a) of the Data Processing Addendum).
Any Customer (a school, Group Customer, or scholarship granting organization) directs FACTS to give its data to another organization for a limited purpose, for example a school to its diocese, or a diocese to a scholarship granting organization, or a scholarship granting organization to a participating school that receives scholarship payments The Data Access Terms for the receiving organization. FACTS continues to follow the directing Customer’s instructions for that data. Any further sharing needs that Customer’s own authorization (Section 6.3 of the Data Access Terms).
A parent or guardian uses information from an earlier FACTS application, such as a school’s tuition assistance application, in an application to a scholarship granting organization Section II(B)(10) of the Data Processing Addendum. The family directs the carry-forward, and the school must first permit it.
A Customer connects its own software vendor or service provider through an API or other integration The API and Integration Terms for the vendor, which must also have its own agreement with the Customer covering the data. The Customer remains responsible for its vendor (Data Processing Addendum, Section II(B)(7); API and Integration Terms, Section 4).

Accepting and Updating the Documents

Customers accept the Data Processing Addendum when they sign an agreement with FACTS that links to it or accept it through the FACTS platform. Recipients accept the Data Access Terms, and integration vendors accept the API and Integration Terms, once, before they first receive access. Customers accept the AI Feature Terms when they subscribe to, enable, or ask FACTS to enable an AI feature.

FACTS posts each update to a document with a new version number and date, gives advance notice of material updates to the organizations that document applies to, and keeps every prior version here. An update to one document does not change any other.

Negotiated Terms

FACTS offers each document on the same basis to every organization it applies to. Where FACTS agrees to a change for a particular customer, it does so only in a signed amendment or a signed data privacy agreement, as the Data Processing Addendum describes.

Version 1.0 | Last Updated: November 20, 2026

(see Section IX(E) below regarding previous versions)

This Data Processing Addendum (“DPA”) is one of the FACTS Data Protection Terms published by Nelnet Business Solutions, Inc. d/b/a FACTS Management Company (“Company”), and is an addendum to each Agreement between Company and a Customer. It applies to each Customer with respect to Personal Information that Company Processes under its Agreement. The overview explains how the FACTS Data Protection Terms fit together. Capitalized terms used but not defined in Section I have the meanings given in the Agreement.

Whereas, Company (i) provides Services to the Customer under the Agreement; and (ii) may Process Personal Information on behalf of the Customer in connection with the Services;

Now therefore, in consideration of the mutual covenants and agreements in this DPA and the Agreement, and for other good and valuable consideration, the sufficiency of which is hereby acknowledged, the Customer and Company agree as follows:

I. Definitions

A. “Access Authorization” means a Customer’s written direction, given under Section VIII, that authorizes Company to give a Recipient access to Covered Data.

B. “Account Data” means information provided to Company to establish, administer, or maintain an account for accessing the Services, including administrator contact information, billing details, and authentication credentials.

C. “Agreement” means the professional services agreement, provider agreement, group-level professional services agreement, order form, platform terms, or other agreement under which Company provides Services to a Customer and that incorporates this DPA.

D. “Aggregated Data” means information that relates to a group or category of individuals, from which individual identities have been removed, and that is not linked or reasonably linkable to any individual or household.

E. “Authorized User” means an individual whom a Customer permits to use the Services, such as the Customer’s or a School’s personnel, and students, parents, guardians, and applicants using the Services for themselves.

F. “COPPA” means the Children’s Online Privacy Protection Act, 15 U.S.C. §§ 6501-6506, and its implementing regulations, 16 C.F.R. Part 312.

G. “Covered Data” means a Customer’s Personal Information, and data derived from it, that Company makes available to a Recipient under an Access Authorization, in aggregated, de-identified, or identifiable form.

H. “Customer” means any organization that enters into an Agreement with Company to receive Services, whatever its type, such as a public or private school, school district, diocese, archdiocese, school network or association, charter management organization, scholarship granting organization, or foundation, and each School that directs its own Personal Information under Section II(B)(2)(b). References to “the Customer” with respect to any Personal Information mean the Customer whose instructions Company follows for that Personal Information under Section II(B).

I. “Customer Agent” means a person that receives a Customer’s Personal Information from Company at the Customer’s direction in order to perform services for, or on behalf of, the Customer, such as the Customer’s own vendor, service provider, advisor, or auditor. An Integration Vendor is a Customer Agent. A Customer Agent that uses Personal Information for any purpose other than performing services for the Customer is a Recipient for that use.

J. “Data Breach” means a confirmed unauthorized access to, or acquisition, use, modification, or disclosure of, Personal Information in Company’s possession or control that compromises its security, confidentiality, or integrity.

K. “De-identified Data” means information that cannot reasonably identify, relate to, describe, be capable of being associated with, or be linked, directly or indirectly, to a particular individual, household, or School, provided that Company (a) takes reasonable measures to ensure that the information cannot be so associated, using methods consistent with NIST de-identification standards or U.S. Department of Education guidance; (b) commits, by this DPA, to maintain and use the information in de-identified form and not to attempt to re-identify it, except to test whether its de-identification processes meet this definition; (c) contractually obligates any recipient of the information to meet clauses (a) and (b); and (d) meets any additional conditions that applicable Privacy Laws impose, such as making its de-identification processes available for review by a School.

L. “Executed Privacy Agreement” means a student data privacy or data processing agreement signed by Company and a Customer, such as the National Data Privacy Agreement, a state-specific data privacy agreement, or a negotiated version of this DPA, including one adopted through a general offer Company has signed.

M. “Feedback” means suggestions, comments, feature requests, enhancement ideas, or other feedback about the Services provided by a Customer, a School, or an Authorized User.

N. “FERPA” means the Family Educational Rights and Privacy Act, 20 U.S.C. § 1232g, and its implementing regulations, 34 C.F.R. Part 99.

O. “Group Customer” means a Customer that enters into an Agreement for the use and benefit of one or more Schools, such as a diocese, archdiocese, school network or association, charter management organization, or school district.

P. “Integration Vendor” means a Customer Agent that connects to the Services through an application programming interface, file transfer, or other automated integration to send or receive a Customer’s Personal Information.

Q. “Personal Information” means information that identifies, relates to, describes, is capable of being associated with, or could reasonably be linked, directly or indirectly, with a particular individual or household, that Company Processes in connection with the Agreement, including information about students, applicants, and their parents or guardians. Personal Information does not include De-identified Data, Aggregated Data, Account Data, Feedback, or Usage Data that does not identify a student or family.

R. “Privacy Laws” means laws that regulate the processing, privacy, or security of Personal Information and that apply to the relevant party in connection with this DPA.

S. “Process” (and its derivatives) means any operation or set of operations performed on Personal Information, whether or not by automated means, such as collection, use, storage, disclosure, analysis, deletion, or modification.

T. “Recipient” means any person, of any type and including a Customer, to which Company gives access to, or transmits, a Customer’s Personal Information at that Customer’s direction for a limited purpose permitted by the Data Access Terms, rather than to perform services on the Customer’s behalf, other than that Customer, its Authorized Users, its Customer Agents, or a Sub-Processor.

U. “School” means a public or private school, school district, or other educational institution to or for which Company provides Services under an Agreement, including where a Group Customer enters into the Agreement for its use and benefit.

V. “SGO” means an organization that awards scholarships, tuition assistance, or tax-credit funded grants to students.

W. “Services” means the services Company provides under the Agreement.

X. “Sub-Processor” means a person that Company engages to Process Personal Information on Company’s behalf in providing the Services.

Y. “Usage Data” means technical and operational data generated through the use of the Services, such as system logs, performance metrics, feature usage statistics, session data, error reports, and similar telemetry.

Z. The terms “Business,” “Business Purpose,” “Processor,” “Sell,” “Share,” and “Service Provider” have the meanings given to them in applicable Privacy Laws.

II. Roles and Responsibilities of the Parties

(A) Company’s Role and Processing Obligations

(1) Company’s role. Except as provided in Section II(A)(7), Company Processes Personal Information on behalf of, and on the instructions of, the Customer identified under Section II(B), and acts as that Customer’s service provider or processor to the extent Privacy Laws use those terms.

(2) Instructions. Subject to applicable Privacy Laws, Company will Process Personal Information only in accordance with the Agreement, Annex 1, and the instructions of the Customer or of a party authorized to give instructions under Section II(B). Company will notify the Customer if it believes an instruction violates Privacy Laws.

(3) Restrictions. Except as described in Section II(A)(4), Company will not (a) Sell or Share Personal Information; (b) retain, use, or disclose Personal Information for any purpose other than the Business Purposes in the Agreement and Annex 1, or outside the direct business relationship between the Customer and Company; or (c) combine Personal Information with Personal Information received from or on behalf of another person, or collected from Company’s own interactions with individuals, unless permitted by applicable Privacy Laws. Company certifies that it understands and will comply with these restrictions, and will notify the Customer if it determines it can no longer meet its obligations under this DPA or applicable Privacy Laws.

(4) Permitted internal uses. To the extent permitted by applicable Privacy Laws, Company may retain, use, or disclose Personal Information (a) to engage Sub-Processors under Section III; (b) for internal use to maintain, support, secure, diagnose, repair, build, improve, or otherwise preserve the quality and functionality of the Services, provided that Company will develop and improve its products and services using De-identified Data or Aggregated Data, and that the use does not include building or modifying household or consumer profiles for use in providing services to another business, or correcting or augmenting data acquired from another source, and is subject to Section II(A)(6)(c); (c) to detect security incidents or protect against fraudulent or illegal activity; (d) to comply with law, or with a civil, criminal, or regulatory inquiry, investigation, subpoena, or summons, subject to Section VI(B); (e) to cooperate with law enforcement concerning conduct Company reasonably and in good faith believes may violate law; or (f) to exercise or defend legal claims.

(5) De-identified and Aggregated Data. Company may create De-identified Data and Aggregated Data from Personal Information and use them for research, analytics, and the development and improvement of educational products and services, and to demonstrate the effectiveness of the Services. Company will not attempt to re-identify such data, will not disclose De-identified Data to a third party other than a Sub-Processor bound to equivalent terms unless the Customer directs or permits it, and will obtain the Customer’s approval before publishing any material that names a Customer or School. Company’s rights under this Section survive any instruction to delete or return Personal Information.

(6) Student data protections. Company will not use or disclose Personal Information:

(a) to inform, influence, or enable targeted advertising to students or their families;

(b) to build a profile of a student or family for any purpose other than providing the Services, except as the Customer directs; or

(c) to train a generative artificial intelligence system or service, or to develop an artificial intelligence system, except De-identified Data used in accordance with Section II(A)(5) and applicable Privacy Laws.

Any artificial intelligence features in the Services are also subject to the AI Feature Terms.

(7) Company’s own data. Company Processes Usage Data, Account Data, and Feedback for its own purposes, not on behalf of a Customer, and may use them to operate, maintain, secure, support, and improve the Services, develop new products and features, and produce benchmarking and analytics, provided that outputs do not identify any Customer, School, or individual. Usage Data that identifies a student or family is Personal Information and is subject to Sections II(A)(5) and II(A)(6).

(8) No ownership. As between Company and the Customer, Company claims no ownership of Personal Information Processed under this DPA in its capacity described under this Section II(A).

(9) Personnel. Company will ensure that personnel who Process Personal Information are subject to a duty of confidentiality and are trained on their obligations.

(10) Assistance. Taking into account the nature of the Processing, Company will reasonably assist the Customer in responding to requests from individuals under Privacy Laws and in meeting its obligations relating to security, breach notification, and data protection assessments.

(B) Whose Instructions Company Follows

(1) General; no status determination. Company Processes Personal Information on the instructions of the Customer identified, and given, under this Section II(B). This Section II(B) identifies whose instructions Company follows. It does not determine, and Company does not determine, any party’s status under Privacy Laws, such as whether a party is a “controller,” “business,” or “educational agency or institution.” Each Customer is responsible for its own determination, and Company may rely on this Section II(B) regardless of it.

(2) Whose instructions Company follows.

(a) Contracting Customer. Unless the Agreement provides otherwise, Company follows the instructions of the Customer that entered into the Agreement for all Personal Information Processed under it, whether that Customer is a School, a Group Customer, an SGO, or another organization.

(b) Schools that direct their own data. Where a Group Customer enters into an Agreement for the use and benefit of one or more Schools, and the Agreement provides that those Schools direct the Processing of their own Personal Information, each such School is a Customer for its own Personal Information, and Company follows that School’s instructions. Company also follows instructions given on a School’s behalf by the Group Customer unless the School notifies Company in writing that the Group Customer may not give them.

(c) Changing whose instructions apply. The Customer that entered into the Agreement and a School may jointly designate either of them as the party whose instructions Company follows for specified Personal Information, by written notice to Company from both. The designation takes effect when Company receives it, and this DPA continues to govern that Personal Information.

(3) Authorized representatives. A Customer may authorize another party, including a Group Customer or a School, to give instructions on its behalf, generally or for specified matters, by written notice to Company or by any method described in Section VIII, including enabling it in the Services.

(4) Conflicting instructions. An instruction to restrict, suspend, or end access to or Processing of Personal Information, or to place or maintain a litigation, audit, or regulatory hold, takes effect when given by any party entitled to give instructions under this Section II(B) and prevails over any conflicting instruction. Otherwise, the instruction of the Customer identified under Section II(B)(2) prevails. Where Company receives conflicting instructions or a bona fide dispute about authority arises, Company may suspend the affected Processing or access, or decline to act, pending resolution, and will follow the more restrictive instruction in the meantime. Doing so is not a breach and does not give rise to liability to any party.

(5) Reliance. Company may rely on the Agreement, on any designation under Section II(B)(2)(c), and on any instruction or authorization from a party entitled to give it under this Section II(B), without inquiry into that party’s internal authority or governance, and is not liable for acting in reliance on them. The Customer that entered into the Agreement represents and warrants that each party that gives instructions, or is authorized to give instructions, under this Section II(B) in connection with its Agreement has the authority to do so.

(6) Access for others. Company will give a Recipient access to a Customer’s Personal Information, or to the Services, only (a) on an Access Authorization from that Customer or from a party authorized under Section II(B)(3), and (b) where the Recipient has accepted the Data Access Terms or another written agreement with Company that is no less protective. A Recipient is not a Sub-Processor, and Company is not responsible for a Recipient’s use of Covered Data except to the extent caused by Company’s failure to give, limit, or end access as authorized.

(7) Customer Agents, integrations, and required disclosures. A Customer may direct Company to make its Personal Information available to a Customer Agent, or to a governmental authority or other person to which the Customer is required by law to disclose it, or with which the Customer must exchange it to administer a government program, such as a federal or state tax credit scholarship program. Company will connect an Integration Vendor only where the vendor has accepted the API and Integration Terms. Other Customer Agents and legally required recipients need no agreement with Company. In each case the Customer is responsible for the person’s handling of the Personal Information and for having an appropriate agreement with it, and Company is not responsible for the Personal Information after making it available as instructed.

(8) Successors and transfers. Where a School closes, merges, consolidates, changes ownership, or moves to a different Group Customer, or a Customer otherwise ceases to exist, the Customer may direct Company to transfer its Personal Information, or the right to give instructions for it, to a successor that accepts this DPA. Absent such a direction, Company will continue to hold the Personal Information under this DPA and may act on the instructions of a party that reasonably demonstrates authority to give them, subject to Section II(B)(4).

(9) Arrangements not otherwise addressed. Where this DPA or the Agreement does not address whose instructions Company follows, or whether a person may receive Personal Information: (a) Company follows the instructions of the Customer that entered into the Agreement; (b) no person other than that Customer, its Authorized Users, Customer Agents, and Sub-Processors receives Personal Information except under an Access Authorization and the Data Access Terms or under Section II(B)(10), and no Integration Vendor connects except under the API and Integration Terms; and (c) Company may require written instructions from each affected party, or decline to act pending resolution, under Section II(B)(4).

(10) Information carried forward. Where the Services allow it and the Customer for which information was first submitted has permitted it, through the Services or its Agreement, Company may, at the direction of the individual who submitted the information, use it in an application that individual submits to another Customer, such as an SGO. The copy used in that application is Personal Information of the receiving Customer, and the first Customer’s Personal Information is unaffected.

(C) Customer Obligations

(1) Compliance. The Customer represents and warrants that it has complied in all material respects with applicable Privacy Laws in relation to Personal Information made available to Company, including ensuring its accuracy, quality, and legality, providing required notices, and obtaining required consents, including for any sharing it directs under Section II(B)(6). The Customer will ensure that its instructions do not violate Privacy Laws or put Company in breach of applicable law.

(2) Account security. The Customer will protect usernames, passwords, and other means of access to the Services, and will notify Company within seventy-two (72) hours after confirming unauthorized access to its account or to Personal Information through its account.

(3) Rights. To the extent permitted by Privacy Laws, the Customer may take reasonable and appropriate steps to ensure that Company Processes Personal Information consistently with the Customer’s obligations, and, upon notice, to stop and remediate unauthorized Processing.

(4) Customer-configured data. The Customer is responsible for the information it collects through fields, forms, questions, and document requests it creates in the Services, including providing required notices, obtaining required consents, and collecting only what it needs. The Customer will not use those features to collect payment card data outside the payment features Company provides, or information that applicable Privacy Laws prohibit the Customer or Company from collecting. Company may disable a field or delete information that it reasonably believes violates this Section, after notifying the Customer where practicable.

(D) FERPA

(1) School official designation. Where Company has access to education records under FERPA, the Customer designates Company as a “school official” with a “legitimate educational interest” that performs an institutional service or function for which the Customer would otherwise use employees, and that is under the direct control of the Customer with respect to the use and maintenance of education records. Company will use and disclose those records only as this DPA and FERPA permit.

(2) Annual notification. Where FERPA applies, the Customer will include criteria for determining who is a school official with a legitimate educational interest in its annual notification of rights, and warrants that it has the right to make available to Company the education records it provides.

(E) Children’s Data and COPPA

(1) Services not directed to children. Unless Company agrees otherwise in writing, the Services are not directed to children below the applicable age of consent under Privacy Laws and are not designed to collect Personal Information directly from them. Information about such children is intended to be provided by adults acting on their behalf, such as parents, guardians, or authorized personnel of a Customer or School.

(2) Customer responsibility. The Customer is responsible for complying with Privacy Laws relating to children’s data, including providing required notices and obtaining any required parental consent in its capacity as agent for parents. Company is not responsible for obtaining that consent unless it agrees to do so in writing.

(3) COPPA. Where COPPA applies: (a) Company will Process Personal Information collected from children under 13 only for educational purposes; (b) the Customer represents that it has reviewed Company’s COPPA direct notice at https://factsmgt.com/childrens-online-privacy-protection/ and Privacy Policy at https://factsmgt.com/privacy-policy/, and will make them available to parents of children under 13 from whom Company collects Personal Information (“Participating Parents”); (c) the Customer acts as agent for Participating Parents in authorizing that collection, use, and disclosure, and confirms it has authority to do so; and (d) that Personal Information is under the direct control of the Customer with regard to Company’s use and maintenance of it.

(F) School-level obligations where the Customer is not the School. Where the Customer whose instructions Company follows is not the School at which the relevant students are enrolled, or to which the relevant applicants have applied, references to the Customer in Sections II(C), II(D), and II(E) include that School to the extent the context requires. The Customer will cause each such School to perform the obligations in those Sections that must be performed at the School level, and represents and warrants that it has authority to make the designation in Section II(D)(1) on that School’s behalf, on which Company may rely.

III. Sub-Processors

Company will (a) enter into a written agreement with each Sub-Processor that requires it to protect Personal Information in a manner no less protective than this DPA; (b) maintain a list of Sub-Processors and provide it to Customer on reasonable written request, under reasonable confidentiality terms; (c) to the extent required by Privacy Laws, give the Customer notice of a new Sub-Processor and an opportunity to object before it Processes Personal Information; and (d) remain responsible for each Sub-Processor’s performance of its obligations.

IV. Security

(A) Safeguards. Company will maintain administrative, physical, and technical safeguards appropriate to the risk of the Processing and designed to protect Personal Information from unauthorized access, acquisition, destruction, use, modification, or disclosure, under a security program aligned with a recognized industry security framework.

(B) Assessments. Company will conduct a security assessment at least annually. On reasonable written request, and subject to reasonable confidentiality terms, Company will provide the Customer with an executive summary of its most recent SOC 2 Type II report or an equivalent independent assessment, which may be redacted.

(C) Location. If Company stores Personal Information outside the United States, it will identify the countries upon reasonable written request.

(D) Customer verification. To the extent required by Privacy Laws, and no more than once per year except following a Data Breach, Company will make available information reasonably necessary to demonstrate its compliance with this DPA. Company may meet this obligation by providing the materials described in Section IV(B) and responses to a reasonable security questionnaire. Company is not required to permit on-site audits or to disclose commercially confidential information or information about other customers.

V. Data Breach

(A) Notice. Company will notify the Customer within seventy-two (72) hours after confirming a Data Breach, unless prohibited by applicable law or law enforcement requests a delay, in which case Company will notify the Customer within a reasonable time after the prohibition is removed or the delay ends.

(B) Content. To the extent known to Company, and as it becomes available, the notice will describe the date or estimated date of the Data Breach, its nature, the categories of Personal Information involved, the approximate number of affected individuals, the steps Company has taken to contain it, and a contact for further information.

(C) Response. Company will investigate the Data Breach, take reasonable steps to contain and remediate it, maintain a written incident response plan, and cooperate with the Customer in meeting its obligations under Privacy Laws. Unless the parties agree otherwise or the law requires Company to do so, the Customer will notify affected individuals.

VI. Individual Requests and Compelled Disclosure

(A) Requests. If Company receives a request from a student, parent, guardian, or other individual to access, correct, delete, or otherwise exercise rights under Privacy Laws with respect to Personal Information, Company may direct the individual to the Customer and, where Company can reasonably identify the Customer, will notify the Customer of the request, unless prohibited by law. Taking into account the nature of the Processing and the information available to it, Company will use commercially reasonable efforts to cooperate with the Customer, at the Customer’s request, in helping the Customer fulfill its own obligations under Privacy Laws to respond to such requests. This DPA does not prevent students, parents, or guardians from downloading or exporting content they created in the Services, where the Services offer that feature.

(B) Compelled disclosure. If a court order, subpoena, warrant, or other legal process requires Company to disclose Personal Information, Company will notify the Customer in advance unless the law or the process prohibits it, and will disclose only what is required.

VII. Retention, Return, and Deletion

(A) On instruction. Upon the Customer’s written instruction, Company will delete Personal Information, or make it available for return, within sixty (60) days, unless applicable law or the Agreement requires Company to retain it.

(B) On termination. Within sixty (60) days after the Agreement ends, Company will delete Personal Information unless the Customer instructs otherwise or applicable law or the Agreement requires retention. During the Agreement, Company will retain Personal Information in accordance with its standard retention schedule, or any retention period the Agreement states, which it will provide on request.

(C) Scope. These obligations do not apply to De-identified Data or Aggregated Data, or to Personal Information in backup systems that is deleted in the ordinary course and remains protected under this DPA until then. Company will certify deletion in writing on request.

VIII. Authorizations Given Through Company

(A) Methods. A Customer, or a party authorized under Section II(B)(3), may give, change, or withdraw an Access Authorization, or any other authorization or instruction this DPA allows to be given through Company, by the method Company makes available or accepts, which may include a feature of the Services, an electronic acknowledgment, email, or another written communication. Company may add, change, or discontinue methods at any time without amending this DPA, and may require that an Access Authorization be given or confirmed through a particular method. An Access Authorization given by any such method satisfies any requirement in this DPA that it be in writing.

(B) Authority. The Customer is responsible for controlling which of its personnel may give Access Authorizations. Company may rely on an Access Authorization given through the Customer’s account in the Services, or by a communication that reasonably appears to come from personnel authorized to act for the Customer, as provided in Section II(B)(5).

(C) Content. Each Access Authorization will identify, at a minimum, the Recipient and the Covered Data or access authorized, and may include other details such as the Schools covered, the purposes permitted, types of access, required program reporting, and duration.

IX. Acceptance, Scope, and Updates

(A) Acceptance. A Customer accepts this DPA by (a) signing an Agreement that incorporates it, (b) accepting it through the FACTS platform, or (c) signing or electronically accepting a form that refers to it. Acceptance creates an agreement only between Company and that Customer.

(B) Scope. This DPA applies to an organization only in its capacity as a Customer. An organization may also hold another role, for example a scholarship granting organization that is a Customer for its own scholarship program and a Recipient of a School’s data. Personal Information that an organization receives as a Recipient or an Integration Vendor is governed by the Data Access Terms or the API and Integration Terms, and does not become Personal Information that Company Processes for it as a Customer.

(C) No rights in other Customers’ data. This DPA does not create an agreement between Customers, and does not give any Customer access to, or rights in, another Customer’s Personal Information, except access a Customer directs under Section II(B)(6) and information an individual directs Company to carry forward under Section II(B)(10).

(D) Authority. The individual who accepts this DPA represents that they are authorized to bind the Customer. Where a Customer enters into an Agreement for the use and benefit of one or more Schools, the Customer represents and warrants that it has authority to enter into the Agreement and this DPA on behalf of each such School.

(E) Updates. Company may update this DPA from time to time to reflect changes in applicable law, regulatory guidance, or the Services. Company will post each updated version at https://factsmgt.com/data-protection-terms/ with a new Version number and “Last Updated” date, and will keep prior versions available at https://factsmgt.com/data-protection-terms/. An update that is not material takes effect when posted. For a material update, Company will give each Customer to which it applies reasonable prior written notice before it takes effect. The Version in effect when a Customer accepts this DPA governs until it is superseded under this Section IX(E).

X. Precedence and Negotiated Terms

(A) Precedence. In the event of a conflict, the following order applies, highest first: (a) a Negotiated Amendment; (b) an Executed Privacy Agreement, within its scope; (c) this DPA; and (d) the Agreement. This DPA controls over the Agreement, and over any terms of service, privacy policy, or other writing, only with respect to the Processing of Personal Information.

(B) Executed Privacy Agreements. Where a Customer and Company have an Executed Privacy Agreement covering the Services, it governs the Processing of the Personal Information within its scope, and this DPA applies only to the extent consistent with it and to matters it does not address, including Sections II(A)(7), II(B), and VIII. A Customer may ask Company to enter into, or may adopt through a general offer, an Executed Privacy Agreement where its state’s law or practice calls for one.

(C) Negotiated terms. Company may agree to vary this DPA for a Customer only in a written amendment signed by an authorized representative of Company that identifies each provision varied (a “Negotiated Amendment”), or by entering into an Executed Privacy Agreement. A Negotiated Amendment or Executed Privacy Agreement applies only to the Customer that signs it, and this DPA continues to apply to all matters it does not address. Unless it states otherwise, an Executed Privacy Agreement that replaces this DPA is not affected by later updates to it.

(D) Separate documents. This DPA is one of the FACTS Data Protection Terms. Each of those documents is a separate agreement with its own definitions and Version, and an update to one does not change another. A reference in this DPA to another of those documents is to the version of it that applies to the relevant party.

XI. General

(A) Notices. Notices under this DPA must be in writing. Email is sufficient. Notices to Company are governed by the Agreement. Notices to a Customer go to the contact in its acceptance record or account, which the Customer will keep current.

(B) Liability. Each party’s liability under this DPA is subject to the limitations and exclusions of liability in the Agreement.

(C) Governing law. This DPA is governed by the law that governs the Agreement.

(D) Severability; waiver. If any provision is held unenforceable, it will be enforced to the maximum extent permitted and the remaining provisions remain in effect. A delay or failure to exercise a right is not a waiver of it.

(E) Public entities. Where a Customer is a public entity, (a) its obligations to indemnify or to accept a governing law or forum apply only to the extent its governing law permits; and (b) it may disclose this DPA, or information it receives under it, as required by public records laws, after notifying Company where practicable so that Company may seek protection of its confidential information.

(F) Survival. Sections II(A)(5) and VII survive for so long as Company retains Personal Information or De-identified or Aggregated Data derived from it. Other provisions that by their nature should survive do so for as long as Company retains Personal Information.

Annex 1: Scope of the Personal Information Processing

This Annex 1 forms part of the DPA between the Customer and Company.

Nature and duration of the Processing of Personal Information

Company Processes Personal Information on behalf of the Customer to provide the Services, including tuition management, payment processing, financial aid and scholarship application administration, donation processing, scholarship award and payment administration, preparing reports and acknowledgments for the Customer to issue or submit, admissions and enrollment, and school information system services, as applicable to the Services the Customer receives.

The Processing continues for the term of the Agreement and until deletion or return under Section VII.

Categories of individuals

Students and applicants; parents, guardians, and other household members; donors; and personnel of Customers and Schools.

The Processing concerns the following categories of Personal Information:

Depending on the Services and the information made available by the Customer, a School, parents or guardians, or students:

  • Identifiers, such as name, mailing address, telephone number, email address, and student and account identifiers.
  • Financial and household information, such as income, tax documents, assets, expenses, donation and designation records, and payment account information.
  • Educational and enrollment information, such as school, grade, enrollment status, and education records.
  • Internet or electronic network activity, such as IP address, device identifiers, browser characteristics, and usage logs.
  • Other information entered into the Services, such as uploaded documents and user-generated content.

Customer-configured data. Where the Services allow a Customer to create its own fields, forms, questions, and document requests and to collect information through them, Company does not select, review, or control that information and may not know what it includes, so the categories above may not describe it. Information collected this way is Personal Information under this DPA to the extent it meets that definition, and Company protects it as such. See Section II(C)(4).

The Processing concerns the following categories of Sensitive Data:

Where provided: government-issued identifiers; financial account information; date of birth, age, and gender; religious affiliation; photographs; and health-related information. Company’s standard forms do not request information about reproductive or sexual health, immigration status, or sexual orientation or gender identity, and Section II(C)(4) applies to fields a Customer creates.

Company Processes Personal Information for the following Business Purposes, in accordance with the Agreement:

Performing the Services on behalf of the Customer, including maintaining and servicing accounts, customer service, processing transactions, donations, and payments, preparing acknowledgments and program reports for the Customer, verifying information, financial aid and scholarship analysis, analytics, and storage; helping to ensure security and integrity; debugging; internal research for technological development; and maintaining and improving the quality and safety of the Services.

This document is one of the FACTS Data Protection Terms. It stands on its own, with its own definitions and Version. The overview explains how the documents fit together. Version 1.0 | Last Updated: November 20, 2026 | Prior versions

These Data Access Terms are published by Nelnet Business Solutions, Inc. d/b/a FACTS Management Company (“Company”). These Data Access Terms apply to each Recipient with respect to Covered Data, whatever the type of Customer that directs the access (for example, a School, a Group Customer, or an SGO) and whatever the type of Recipient. A Recipient accepts these Data Access Terms once, and they then apply to every Access Authorization under which Company gives that Recipient access, from any Customer. Where a Recipient is also a Customer, its Agreement and the Data Processing Addendum govern the Services Company provides to it, and these Data Access Terms govern Covered Data. Capitalized terms are defined in Section 1.

1. Definitions

In these Data Access Terms:

“Access Authorization” means a Customer’s written direction, given as described in Section 3.1, that authorizes Company to give a Recipient access to Covered Data.

“Agreement” means any agreement under which Company gives a Recipient access to the Services or to Covered Data. Where a Recipient has no other agreement with Company, these Data Access Terms are the Agreement.

“Covered Data” means a Customer’s Personal Information, and data derived from it, that Company makes available to a Recipient under an Access Authorization, in aggregated, de-identified, or identifiable form.

“Customer” means any organization that enters into an agreement with Company to receive Services, whatever its type, such as a public or private school, school district, diocese, archdiocese, school network or association, charter management organization, scholarship granting organization, or foundation, and each school that directs its own Personal Information under its agreement with Company. References to “the Customer” for Covered Data mean the Customer whose instructions Company follows for the Personal Information from which it is derived.

“FERPA” means the Family Educational Rights and Privacy Act, 20 U.S.C. § 1232g, and its implementing regulations, 34 C.F.R. Part 99.

“Group Customer” means a Customer that enters into an agreement with Company for the use and benefit of one or more Schools, such as a diocese, archdiocese, school network or association, charter management organization, or school district.

“Personal Information” means information that identifies, relates to, describes, is capable of being associated with, or could reasonably be linked, directly or indirectly, with a particular individual or household, that Company processes in providing Services to a Customer, including information about students, applicants, and their parents or guardians. Personal Information does not include de-identified or aggregated data that cannot reasonably be linked to an individual or household.

“Privacy Laws” means laws that regulate the processing, privacy, or security of Personal Information and that apply to the relevant party in connection with these Data Access Terms.

“Recipient” means any person, of any type and including a Customer, to which Company gives access to, or transmits, a Customer’s Personal Information at that Customer’s direction for a limited purpose permitted by these Data Access Terms, rather than to perform services on the Customer’s behalf.

“School” means a public or private school, school district, or other educational institution to or for which Company provides Services, including where a Group Customer contracts for its use and benefit.

“SGO” means an organization that awards scholarships, tuition assistance, or tax-credit funded grants to students.

“Services” means the services Company provides to Customers, and any access to them that Company gives a Recipient.

“Sub-Processor” means a person that Company engages to process Personal Information on Company’s behalf in providing the Services.

The terms “Sell” and “Share” have the meanings given to them in applicable Privacy Laws.

2. Role of Company and the Recipient

2.1 Company makes Covered Data available solely on behalf of, and on the instructions of, the Customer for that Covered Data. The Recipient receives Covered Data on that Customer’s authority, not as Company’s Sub-Processor, and is responsible for its own compliance with Privacy Laws in receiving and using it. Company makes Covered Data available only as a service to, and at the direction of, the Customer. Company does not sell Covered Data. Any fees a Recipient pays Company are for the Recipient’s use of the Services, such as a platform subscription, and not for Covered Data.

2.2 These Data Access Terms give the Recipient no rights in the underlying data from which Covered Data is derived, and no right to give instructions to Company about the Customer’s Personal Information.

3. Access Authorizations

3.1 Giving an Access Authorization. A Customer gives, changes, or withdraws an Access Authorization by a method Company makes available or accepts, which may include a feature of the Services, an electronic acknowledgment, email, or another written communication. Each Access Authorization identifies, at a minimum, the Recipient and the Covered Data or access authorized, and may include other details such as the Schools covered, Permitted Purposes, types of access, required program reporting, and duration. Company may rely on an Access Authorization that reasonably appears to come from the Customer.

3.2 Implementing. Company will make Covered Data available in the form, scope, and cadence stated in the Access Authorization, and will implement a new Access Authorization, or a change to or withdrawal of one, within a commercially reasonable time.

3.3 Withdrawal and suspension. The Customer may narrow or withdraw an Access Authorization at any time. Company may suspend or limit a Recipient’s access on reasonable prior written notice, or immediately where necessary to prevent or respond to a security incident or to comply with law. An Access Authorization lapses automatically if these Data Access Terms ends for the Recipient.

3.4 SGO default. Unless the Access Authorization states otherwise, Covered Data made available to an SGO is limited to students whose families have applied to that SGO.

3.5 Recipient authority. The Recipient represents and warrants that it has, and will maintain for as long as it holds Covered Data, all authority, consents, and agreements, including with the Customer, required for it to receive and use Covered Data for the Permitted Purposes, and that any information it gives Company or the Customer in seeking an Access Authorization is accurate. The Recipient will notify Company promptly if any such authority, consent, or agreement ends or is narrowed.

4. Permitted Purposes

The Recipient may access and use Covered Data only as necessary for the specific purposes stated in the Access Authorization (the “Permitted Purposes”). Permitted Purposes must benefit the Customer, its Schools, or their students and families, and may not include any use prohibited by Section 5. Examples include system-level oversight and reporting by a Group Customer, but not decisions about individual students or families; scholarship or aid administration by an SGO or other funder; and accreditation, audit, research, or program evaluation for the benefit of the Customer or its Schools. Any other purpose requires a new Access Authorization and Company’s written consent.

5. Use Restrictions

The Recipient will not:

(a) Sell or Share Covered Data, or use it for any commercial purpose, for marketing, or to build or enrich a profile of any individual;

(b) use Covered Data as the basis for a decision affecting an identifiable individual, other than a decision the Access Authorization expressly permits, such as an SGO’s decision on eligibility for, or the amount, terms, or conditions of, a scholarship it funds or administers;

(c) use Covered Data, or information derived from it, for donor solicitation, stewardship, or reporting that identifies or could reasonably identify a student or family, or disclose Covered Data to a donor or funder in identifiable form;

(d) use or disclose Covered Data to train, develop, fine-tune, test, or evaluate an artificial intelligence system;

(e) attempt to re-identify any individual from Covered Data that does not itself identify that individual, or link or combine Covered Data with other data to do so; or

(f) create, edit, or delete records in the Services except within the scope the Access Authorization permits.

6. Onward Disclosure

6.1 The Recipient may disclose Covered Data only to (a) Company and the Customer for that Covered Data; (b) the student, parent, or guardian to whom it relates, with respect to that individual’s own information; (c) its personnel, contractors, and professional advisors who need it for the Permitted Purposes and are bound by written confidentiality and use obligations at least as protective as these Data Access Terms, for whose compliance the Recipient is responsible; (d) a governmental authority, only under Section 6.2; and (e) any person, only under Section 6.2. Any other disclosure, including any voluntary disclosure, is prohibited. The Recipient is responsible for the compliance of any onward recipient described under this Section 6.1.

6.2 The Recipient may disclose Covered Data to a governmental authority for reporting required by a bona fide scholarship, tax-credit, or other program in which it participates, where the Access Authorization identifies that reporting and the categories of Covered Data involved. Where a subpoena, court order, warrant, or other legal process from any person compels disclosure, the Recipient will, unless legally prohibited, notify Company and the Customer promptly and before disclosing, so that the Customer may seek a protective order or other remedy, and will cooperate with those efforts. In either case, the Recipient will disclose only the minimum Covered Data required, use aggregated or de-identified data wherever the requirement permits, comply with any redisclosure limits under FERPA or other Privacy Laws that apply, and keep a record of each disclosure, which it will provide to Company or the Customer on request.

6.3 Further sharing. The Recipient may not give Covered Data to any person except as Section 6.1 permits, including another Recipient, and may not issue an Access Authorization for Covered Data. Any further sharing, such as a Group Customer passing a School’s data to an SGO, requires a separate Access Authorization from the Customer for that data, and Company will provide the access directly.

7. Security and Incident Notice

7.1 Safeguards. The Recipient will maintain reasonable administrative, physical, and technical safeguards appropriate to the nature of Covered Data, including (a) limiting access to named individuals with a need to know; (b) multi-factor authentication for any account used to access the Services; (c) encryption of Covered Data in transit and, where the Recipient stores it, at rest; (d) logging and periodic review of access; and (e) secure retention and disposal. The Recipient will not share credentials, and will notify Company within one (1) business day after any named individual no longer requires access.

7.2 Incidents. The Recipient will notify Company in writing within seventy-two (72) hours after confirming any unauthorized access to, or acquisition, use, loss, or disclosure of, Covered Data in its possession or control; will supplement the notice as information becomes available; will investigate and remediate; and will cooperate with Company and the Customer. Company may share the notice with the Customer. Each party will consult the other in good faith before any external communication about the incident, except as required by law.

8. Retention and Return

The Recipient will retain Covered Data only as long as necessary for the Permitted Purposes or as required by law. Within thirty (30) days after an Access Authorization is withdrawn or lapses, or after these Data Access Terms ends for the Recipient, the Recipient will return or securely destroy the affected Covered Data, including copies exported or downloaded from the Services, and will certify that it has done so on request.

9. Responsibility and Remedies

9.1 Warranties. The Recipient represents and warrants that it has authority to accept these Data Access Terms, and that it will comply with applicable Privacy Laws in its receipt, use, and disclosure of Covered Data.

9.2 Indemnity. The Recipient will indemnify, defend, and hold harmless Company and its affiliates, and their officers, directors, employees, and agents, from third-party claims, and related losses, damages, penalties, and reasonable attorneys’ fees, arising from the Recipient’s breach of these Data Access Terms or from an incident involving Covered Data in the Recipient’s possession or control, except to the extent caused by Company’s breach of these Data Access Terms, gross negligence, or willful misconduct.

9.3 Equitable relief. Misuse of Covered Data may cause irreparable harm, and Company may seek injunctive or other equitable relief in addition to its other remedies.

9.4 Disclaimer. Covered Data is provided “as is.” Company makes no warranty as to its accuracy, completeness, or fitness for a particular purpose, and does not review or validate any determination the Recipient makes using it.

10. Compliance Verification

The Recipient will maintain records sufficient to demonstrate its compliance with these Data Access Terms, make them available to Company on reasonable request, and provide a written certification of compliance on request no more than once per year, except where Company reasonably suspects non-compliance or an incident. Where Company reasonably suspects non-compliance, Company may, on reasonable notice and during normal business hours, review the Recipient’s relevant records and controls. The Recipient will promptly correct any material deficiency at its own expense.

11. Term

These Data Access Terms apply to a Recipient from acceptance until it no longer holds any Covered Data. The Recipient may end its acceptance of these Data Access Terms by written notice, in which case all of its Access Authorizations lapse. Sections 5 through 10 survive for so long as the Recipient holds Covered Data.

12. Authority, Updates, and Precedence

12.1 Authority. The individual who accepts these Data Access Terms for an organization represents that they are authorized to bind it.

12.2 Updates. Company may update these Data Access Terms from time to time to reflect changes in applicable law, regulatory guidance, or the Services. Company will post each updated version at https://factsmgt.com/data-protection-terms/ with a new Version number and “Last Updated” date, and will keep prior versions available at https://factsmgt.com/data-protection-terms/. An update that is not material takes effect when posted. For a material update, Company will give each Recipient to which these Data Access Terms apply reasonable prior written notice before it takes effect. The Version in effect when a Recipient accepts these Data Access Terms governs until it is superseded under this Section 12.2.

12.3 Precedence. These Data Access Terms control over the Agreement, and over any other writing, with respect to Covered Data. Company may vary them for a Recipient only in a written amendment signed by an authorized representative of Company.

12.4 Separate documents. These Data Access Terms are one of the FACTS Data Protection Terms. Each of those documents is a separate agreement with its own definitions and Version, and an update to one does not change another. A reference in these Data Access Terms to another of those documents is to the version of it that applies to the relevant party.

13. General

13.1 Notices. Notices under these Data Access Terms must be in writing. Email is sufficient. Notices to Company go to the contact stated in the Agreement or, if there is none, the contact Company designates in the Services. Notices to a Recipient go to the contact in its acceptance record or account, which the Recipient will keep current.

13.2 Liability. Where the Recipient has an Agreement with Company other than these Data Access Terms, each party’s liability under these Data Access Terms is subject to the limitations and exclusions of liability in that Agreement. Otherwise, Section 9 applies

13.3 Governing law. These Data Access Terms are governed by the law that governs the Agreement. Where the Recipient has no Agreement with Company other than these Data Access Terms, they are governed by the laws of the State of Nebraska, without regard to its conflict of laws rules.

13.4 Severability; waiver. If any provision is held unenforceable, it will be enforced to the maximum extent permitted and the remaining provisions remain in effect. A delay or failure to exercise a right is not a waiver of it.

13.5 Public entities. Where a Recipient is a public entity, (a) its obligations to indemnify or to accept a governing law or forum apply only to the extent its governing law permits; and (b) it may disclose these Data Access Terms, or information it receives under them, as required by public records laws, after notifying Company where practicable so that Company may seek protection of its confidential information.

This document is one of the FACTS Data Protection Terms. It stands on its own, with its own definitions and Version. The overview explains how the documents fit together. Version 1.0 | Last Updated: November 20, 2026 | Prior versions

These API and Integration Terms are published by Nelnet Business Solutions, Inc. d/b/a FACTS Management Company (“Company”). These API and Integration Terms apply to each Integration Vendor with respect to its use of the API and the Documentation, and with respect to Personal Information that Company makes available to it, or that it sends to Company, through an integration that Company enables at a Customer’s direction. An Integration Vendor accepts these API and Integration Terms once, for example when it registers for API access or receives credentials, and they then apply to every Customer that enables its integration. An individual who accepts these API and Integration Terms for an organization represents that they are authorized to bind it. Capitalized terms are defined in Section 1.

1. Definitions

In these API and Integration Terms:

“Customer” means any organization that enters into an agreement with Company to receive Services, whatever its type, such as a public or private school, school district, diocese, archdiocese, school network or association, charter management organization, scholarship granting organization, or foundation, and each school that directs its own Personal Information under its agreement with Company.

“Integration Vendor” means a Customer’s own software vendor or service provider that connects to the Services through an application programming interface (“API”), file transfer, or other automated integration to send or receive the Customer’s Personal Information.

“Personal Information” means information that identifies, relates to, describes, is capable of being associated with, or could reasonably be linked, directly or indirectly, with a particular individual or household, that Company processes in providing Services to a Customer, including information about students, applicants, and their parents or guardians. Personal Information does not include de-identified or aggregated data that cannot reasonably be linked to an individual or household.

“Privacy Laws” means laws that regulate the processing, privacy, or security of Personal Information and that apply to the relevant party in connection with these API and Integration Terms.

“Recipient” means an organization that receives a Customer’s Personal Information at that Customer’s direction for a limited purpose under the Data Access Terms, rather than to perform services on the Customer’s behalf.

“Services” means the services Company provides to Customers.

“Sub-Processor” means a person that Company engages to process Personal Information on Company’s behalf in providing the Services.

The terms “Sell” and “Share” have the meanings given to them in applicable Privacy Laws.

2. Role of the Integration Vendor

2.1 The Integration Vendor acts for the Customer that authorized the integration, not for Company. It is not Company’s Sub-Processor, and Company is not responsible for the Integration Vendor’s handling of Personal Information after Company makes it available as the Customer directed.

2.2 If the Integration Vendor uses a Customer’s Personal Information for any purpose other than providing services to that Customer, it is a Recipient for that use, and the Data Access Terms apply to that use in addition to these API and Integration Terms.

2.3 Where Company itself engages a vendor to provide part of the Services, that vendor is a Sub-Processor under Section III of the Data Processing Addendum, not an Integration Vendor.

3. Customer Authorization

3.1 A Customer authorizes an integration by any method Company makes available or accepts, including by enabling it in the Services or instructing Company to enable it. The authorization defines the data, functions, and scope available to the Integration Vendor for that Customer.

3.2 The Integration Vendor will access only the Personal Information of Customers that have authorized its integration, within the scope each has authorized. The Customer may instruct Company to narrow or disable the integration at any time, and Company will implement the instruction within a commercially reasonable timeframe.

3.3 The Integration Vendor represents and warrants that, for each Customer whose Personal Information it accesses or sends through an integration, (a) the Customer has authorized that access; (b) its access stays within the scope the Customer authorized; and (c) it will stop accessing that Customer’s Personal Information, and notify Company promptly, if the authorization is withdrawn, narrowed, or expires. Company will act only on authorization received from the Customer, through the Services or in writing, and not on the Integration Vendor’s statement alone.

4. Agreement with the Customer

The Integration Vendor represents and warrants that, before receiving any Customer’s Personal Information, it has a written agreement with that Customer that:

(a) limits its use of the Personal Information to providing services to that Customer;

(b) prohibits it from Selling or Sharing the Personal Information, using it for targeted advertising or to build profiles other than for that Customer, or using it to train or develop artificial intelligence systems other than as applicable Privacy Laws allow;

(c) requires reasonable security safeguards, notice to the Customer of security incidents, and deletion or return of the Personal Information when its services end; and

(d) meets the requirements of Privacy Laws that apply to it, including state student privacy laws that apply to entities acting on behalf of an operator.

The Integration Vendor will provide Company with a certification that such agreements are in place on request.

5. License

Subject to these API and Integration Terms, Company grants the Integration Vendor a limited, revocable, non-exclusive, non-transferable, non-sublicensable license to access and use the API and its documentation (the “Documentation”) solely to provide services to Customers that have authorized its integration. Company retains all rights in the API, the Documentation, and the Services, and grants no other rights by implication or otherwise.

6. Terms of Use

The Integration Vendor will use the API only as the Documentation describes and will not: (a) access data of any Customer that has not authorized its integration, or exceed the scope authorized; (b) exceed rate limits, or scrape, crawl, or circumvent any access control, security measure, or usage limit; (c) collect or store end users’ Company login credentials, or have users authenticate other than through Company’s authentication flow; (d) decompile, reverse engineer, or attempt to derive the source code of the Services or the API; (e) conduct load, penetration, or vulnerability testing without Company’s written consent; (f) share, sell, or transfer its credentials, or allow any third party to use the API through its integration; (g) use the API, or data obtained through it, to build a product that replicates the Services’ core functionality, or for advertising, marketing, data brokering, or training artificial intelligence systems; (h) introduce malicious code, or interfere with the Services or other users; or (i) misrepresent its relationship with Company, or imply that Company endorses or certifies its integration.

7. Use, Separation, and Retention

The Integration Vendor will use each Customer’s Personal Information only to provide services to that Customer, and will not combine it with the Personal Information of any other Customer or person except as that Customer’s agreement permits. It will not attempt to re-identify de-identified or aggregated data obtained through the integration. It will request and retain only the data its services require, will not cache or store data obtained through the API longer than those services require, and will refresh cached data as the Documentation specifies.

8. API Access and Credential Security

The Integration Vendor will (a) request and use only the API scopes and data needed for the services the Customer has authorized; (b) keep credentials secure, not share them, and rotate them as the Documentation requires; (c) not scrape the Services, circumvent access controls or rate limits, or access data beyond its authorized scope; (d) maintain reasonable administrative, physical, and technical safeguards, including encryption of Personal Information in transit and at rest; (e) keep logs of its API activity sufficient to investigate a security incident; and (f) promptly report to Company any vulnerability it discovers in the API or the Services, and not exploit or disclose it.

9. Incident Notice

The Integration Vendor will notify Company within seventy-two (72) hours after confirming a compromise of its credentials, or any unauthorized access to or acquisition of Personal Information obtained through the integration, in addition to any notice it owes the Customer. It will cooperate with Company and the affected Customers in investigating and remediating the incident. Company may share the notice with affected Customers.

10. Documentation, Changes, and Support

Company may change, version, deprecate, or discontinue the API or the Documentation at any time. Company will give reasonable advance notice, ninety (90) days where practicable, of changes that require the Integration Vendor to change its integration, except where a change is needed for security, legal, or operational reasons. The Integration Vendor is responsible for keeping its integration current. Company has no obligation to provide support or service levels unless a separate agreement says otherwise. Section 17.2 does not apply to changes to the API or the Documentation.

11. Names and Branding

The Integration Vendor will not use Company’s names, logos, or trademarks without Company’s prior written consent, except to state accurately that its integration works with the Services.

12. Monitoring and Verification

Company may monitor use of the API to operate and secure the Services and to verify compliance with these API and Integration Terms. On reasonable request, no more than once per year except where Company reasonably suspects non-compliance or an incident, the Integration Vendor will certify its compliance with these API and Integration Terms and provide information reasonably necessary to demonstrate it.

13. Suspension and Termination

Company may suspend or revoke credentials, or disable an integration, immediately where reasonably necessary to protect the Services, Customers, or Personal Information, or where the Integration Vendor breaches these API and Integration Terms, and will notify the Integration Vendor and affected Customers. Either party may end the Integration Vendor’s acceptance of these API and Integration Terms on thirty (30) days’ written notice. The Integration Vendor’s access to a Customer’s Personal Information ends automatically when the Customer disables the integration, when the Integration Vendor’s agreement with that Customer ends, or when these API and Integration Terms ends for the Integration Vendor. The Integration Vendor will notify Company promptly when its agreement with a Customer ends. On termination, the Integration Vendor will stop using the API and delete its credentials. Deletion or return of Personal Information the Integration Vendor holds is governed by its agreement with the Customer.

14. Warranties, Disclaimers, and Limitation of Liability

14.1 Warranties. The Integration Vendor represents and warrants that it has authority to accept these API and Integration Terms and will comply with applicable Privacy Laws in its handling of Personal Information obtained through the integration.

14.2 Disclaimers. The API, the Documentation, and any data made available through them are provided “as is” and “as available,” without warranties of any kind.

14.3 Limitation of liability. Neither party is liable for indirect, consequential, special, or punitive damages, or lost profits. Company’s aggregate liability to an Integration Vendor under these API and Integration Terms will not exceed $100. These limits do not apply to the Integration Vendor’s breach of Sections 4 through 9 or its indemnity obligations.

15. Indemnity

The Integration Vendor will indemnify, defend, and hold harmless Company and its affiliates, and their officers, directors, employees, and agents, from third-party claims, and related losses, damages, penalties, and reasonable attorneys’ fees, arising from its breach of these API and Integration Terms, its use of the API in breach of Sections 5 and 6, its services to Customers, any claim by a Customer or individual about its handling of Personal Information, or from a security incident involving its credentials or systems, except to the extent caused by Company’s breach of these API and Integration Terms, gross negligence, or willful misconduct.

16. General

Company may use any feedback the Integration Vendor provides about the API without obligation. Use of the API is free of charge unless a separate agreement provides otherwise. The Integration Vendor may not assign these API and Integration Terms without Company’s prior written consent. The parties are independent contractors. These API and Integration Terms are governed by the laws of the State of Nebraska, without regard to its conflict of laws rules, unless the Integration Vendor has a separate agreement with Company that provides otherwise. Notices under these API and Integration Terms must be in writing, and email is sufficient. Notices to an Integration Vendor go to the contact in its developer account, which it will keep current. If any provision is held unenforceable, it will be enforced to the maximum extent permitted and the remaining provisions remain in effect. Where an Integration Vendor is a public entity, its obligations to indemnify or to accept a governing law or forum apply only to the extent its governing law permits. Sections 4 through 9, 14, and 15 survive for so long as the Integration Vendor holds credentials or Personal Information obtained through an integration.

17. Separate Documents, Updates, and Precedence

17.1 Separate documents. These API and Integration Terms are one of the FACTS Data Protection Terms. Each of those documents is a separate agreement with its own definitions and Version, and an update to one does not change another. A reference in these API and Integration Terms to another of those documents is to the version of it that applies to the relevant party.

17.2 Updates. Company may update these API and Integration Terms from time to time to reflect changes in applicable law, regulatory guidance, or the Services. Company will post each updated version at https://factsmgt.com/data-protection-terms/ with a new Version number and “Last Updated” date, and will keep prior versions available at https://factsmgt.com/data-protection-terms/. An update that is not material takes effect when posted. For a material update, Company will give each Integration Vendor to which these API and Integration Terms apply reasonable prior written notice before it takes effect. The Version in effect when a Integration Vendor accepts these API and Integration Terms governs until it is superseded under this Section 17.2.

17.3 Precedence. These API and Integration Terms control over any other writing with respect to the API, the Documentation, and Personal Information obtained through an integration. Company may vary them for an Integration Vendor only in a written amendment signed by an authorized representative of Company.

This document is one of the FACTS Data Protection Terms. It stands on its own, with its own definitions and Version. The overview explains how the documents fit together. Version 1.0 | Last Updated: November 20, 2026 | Prior versions

These AI Feature Terms are published by Nelnet Business Solutions, Inc. d/b/a FACTS Management Company (“Company”). They apply to a Customer, and to its Authorized Users, when they use AI Features in the Services. They add to the Data Processing Addendum and do not reduce any protection it gives Personal Information. A Customer accepts these AI Feature Terms as described in Section 13.1, and they apply to each AI Feature the Customer enables or instructs Company to enable.

1. Definitions

In these AI Feature Terms, the defined terms below have the meanings given, and other capitalized terms have the meanings given in the Data Processing Addendum that applies to the Customer. These AI Feature Terms supplement that addendum, so its definitions apply to them.

“AI Feature” means a feature of the Services that uses generative artificial intelligence, machine learning, or similar technology to generate content, summaries, recommendations, predictions, scores, classifications, or other outputs, and that Company identifies as an AI Feature in the Services or in its documentation.

“AI Laws” means laws that regulate the development, provision, or use of artificial intelligence systems and that apply to the relevant party in connection with an AI Feature.

“AI Provider” means a third party whose model or service Company uses to provide an AI Feature.

“Consequential Decision” means a decision that has a legal or similarly significant effect on a student, applicant, parent, guardian, or employee, including a decision about admission or enrollment, tuition assistance, financial need, scholarships or grants, discipline, grades or academic placement, or employment.

“Input” means information that a Customer or its Authorized Users submit to an AI Feature, including prompts, questions, and files, and Personal Information that an AI Feature retrieves from the Services at the Customer’s direction.

“Output” means content or other results that an AI Feature generates from Inputs.

2. Identifying and Controlling AI Features

2.1 Identification. Company will identify each AI Feature in the Services or its documentation.

2.2 Customer control. Company will make an AI Feature that Processes Personal Information available to a Customer’s Authorized Users only after the Customer subscribes to it under an order form, enables it, or instructs Company to enable it. The Customer may choose not to use an AI Feature at any time. Where the Services allow, the Customer may also instruct Company to disable an AI Feature for its Authorized Users, and Company will implement the instruction within a commercially reasonable timeframe. Some AI Features cannot be disabled separately from the Services they are part of. Choosing not to use, or disabling, an AI Feature does not end the subscription term for that AI Feature or for any other part of the Services, and does not relieve the Customer of its obligation to pay the fees for the remainder of that term, unless the Agreement provides otherwise.

2.3 New AI Features. A new AI Feature that Processes Personal Information is subject to Section 2.2.

2.4 Preview features. Company may offer an AI Feature as a beta, pilot, or preview. A preview AI Feature is subject to these AI Feature Terms and the Data Processing Addendum, is otherwise provided as is, and may be changed or withdrawn at any time.

3. How Company Handles Inputs and Outputs

3.1 Data Processing Addendum applies. Personal Information in Inputs and Outputs is Personal Information under the Data Processing Addendum, and Company will Process it only as that addendum permits, including the student data protections in Section II(A)(6) of the Data Processing Addendum.

3.2 No model training. Company will not use Inputs, Outputs, or other Personal Information to train a generative artificial intelligence system or service, or to develop an artificial intelligence system, except De-identified Data used in accordance with Sections II(A)(5) and II(A)(6) of the Data Processing Addendum and applicable Privacy Laws.

3.3 AI Providers. Each AI Provider that Processes Personal Information is a Sub-Processor, and Section III of the Data Processing Addendum applies to it. Company’s written agreement with each such AI Provider will (a) prohibit it from using Inputs or Outputs to train or improve its models or services; and (b) limit its retention of Inputs and Outputs to what is necessary to provide the AI Feature and to monitor for abuse.

3.4 Usage Data. Company may use Usage Data about AI Features, such as feature usage, error rates, and ratings an Authorized User gives an Output, to operate, secure, and improve the AI Features, provided that Usage Data used for that purpose does not identify a student or family.

4. Outputs

4.1 Nature of Outputs. Outputs are generated automatically and may be inaccurate, incomplete, out of date, or biased, and similar Inputs may produce different Outputs. The Customer is responsible for reviewing Outputs before relying on them or sharing them with students, families, or others.

4.2 Ownership. As between Company and the Customer, Outputs generated from the Customer’s Inputs are the Customer’s data under the Agreement.

4.3 Outputs in records. Where the Customer keeps an Output in a student’s record or uses it to make a decision, the Customer is responsible for that record and decision under applicable law, including FERPA where it applies.

5. Human Review of Consequential Decisions

5.1 Customer review. The Customer will not use an AI Feature as the sole basis for a Consequential Decision. Before making a Consequential Decision, a person with appropriate authority will review the Output and the other relevant information and may decide differently from the Output.

6. Acceptable Use

The Customer will not, and will ensure its Authorized Users do not, use an AI Feature to:

(a) submit payment card data, Social Security numbers, other government identifiers, health information, or other sensitive information that the AI Feature is not designed to handle;

(b) generate content that is unlawful, harassing, discriminatory, sexually explicit, or that impersonates or depicts a real person without that person’s consent;

(c) infer a person’s sensitive characteristics, such as race, ethnicity, sexual orientation, immigration status, or disability, except where applicable law permits it and the Services require it;

(d) bypass or disable safety features, filters, or usage limits, or attempt to extract an AI Feature’s underlying model, prompts, or training data; or

(e) violate applicable law, including Privacy Laws and AI Laws.

Company may apply filters and other safeguards to Inputs and Outputs, and may suspend an Authorized User’s access to an AI Feature where reasonably necessary to address a violation of this Section 6. Company will notify the Customer of a suspension.

7. Students and Children

7.1 Student-facing features. Company will identify each AI Feature that students may use directly in the relevant order form or documentation, and will apply commercially reasonable age-appropriate safeguards to it.

7.2 Customer decision. The Customer decides whether to make a student-facing AI Feature available to its students and is responsible for giving any notices and obtaining any consents applicable law requires, including under COPPA as described in Section II(E) of the Data Processing Addendum.

8. Transparency

8.1 Disclosures. Where AI Laws require, Company will tell Authorized Users when they are interacting with an AI Feature or viewing AI-generated content.

8.2 Customer notices. The Customer is responsible for notices to its students, families, and personnel about its own use of AI Features.

9. Compliance with AI Laws

Each party will comply with the AI Laws that apply to it: Company as the developer or provider of AI Features, and the Customer as the organization that decides whether and how to use them. Company will respond to the Customer’s reasonable requests for information about an AI Feature that the Customer needs to meet its obligations under AI Laws.

10. Disclaimers

Except as expressly stated in these AI Feature Terms or the Agreement, Company does not warrant that Outputs will be accurate, complete, or suitable for a particular purpose. Liability under these AI Feature Terms is subject to the limitations and exclusions of liability in the Agreement.

11. Changes to AI Features

Company may change, replace, or discontinue an AI Feature or an AI Provider. A change of AI Provider that Processes Personal Information is subject to Section III of the Data Processing Addendum.

12. Relationship to the Data Processing Addendum

These AI Feature Terms govern the use of AI Features. If they conflict with the Data Processing Addendum on the Processing of Personal Information, the provision that gives Personal Information more protection controls.

13. Acceptance, Updates, and General

13.1 Acceptance. A Customer accepts these AI Feature Terms by signing an Agreement that incorporates them, by accepting them through the FACTS platform, or by subscribing to, enabling, or instructing Company to enable an AI Feature. The individual who accepts them for a Customer represents that they are authorized to bind it.

13.2 Updates. Company may update these AI Feature Terms from time to time to reflect changes in applicable law, regulatory guidance, or the Services. Company will post each updated version at https://factsmgt.com/data-protection-terms/ with a new Version number and “Last Updated” date, and will keep prior versions available at https://factsmgt.com/data-protection-terms/. An update that is not material takes effect when posted. For a material update, Company will give each Customer to which these AI Feature Terms apply reasonable prior written notice before it takes effect. The Version in effect when a Customer accepts these AI Feature Terms governs until it is superseded under this Section 13.2.

13.3 Negotiated terms. Company may vary these AI Feature Terms for a Customer only in a written amendment signed by an authorized representative of Company.

13.4 Separate documents. These AI Feature Terms are one of the FACTS Data Protection Terms. Each of those documents is a separate agreement with its own definitions and Version, and an update to one does not change another. A reference in these AI Feature Terms to another of those documents is to the version of it that applies to the relevant party.

13.5 General. Notices under these AI Feature Terms are given as the Data Processing Addendum provides. These AI Feature Terms are governed by the law that governs the Agreement. If any provision is held unenforceable, it will be enforced to the maximum extent permitted and the remaining provisions remain in effect. A delay or failure to exercise a right is not a waiver of it.

Frequently Asked Questions

About the Terms

They are the terms that govern how FACTS protects the personal information it handles for its customers, and how other organizations may use that information when a customer asks FACTS to share it. They replace the separate data processing addendums FACTS has used with different types of customers. The Terms are a set of separate documents: the Data Processing Addendum, the Data Access Terms, the API and Integration Terms, and the AI Feature Terms. Each applies to a particular role and has its own definitions and version number. The overview explains how they fit together.

When FACTS processes personal information on a school’s behalf, privacy laws such as FERPA, COPPA, state student privacy laws, and state consumer privacy laws expect written terms that limit how that information is used and protected. The Terms set those limits in one place. They also set the rules FACTS follows when a customer asks it to share data with a diocese, a scholarship granting organization, or a software vendor.

Posting one set of Terms lets FACTS keep the same protections in place for every customer and keeps contracts short. Your agreement with FACTS links to the Terms, and each version of each document stays available as prior versions, so you can always see the version that applies to you.

FACTS offers the Terms on the same basis to all of its customers and does not generally modify them for individual customers. The Terms are written specifically for FACTS’s products and services and for the ways schools, dioceses, and scholarship granting organizations use them. If your state’s law or practice calls for a student data privacy agreement such as the National Data Privacy Agreement (NDPA), FACTS can discuss entering into one, and it will govern within its scope.

The core protections are modeled on the NDPA, which many states use in the public K-12 market. They include 72-hour breach notice, deletion within 60 days of a request or the end of the agreement, sub-processor contracts that are no less protective, no targeted advertising or profiling, and limits on de-identified data. The Terms also cover arrangements the NDPA does not, such as diocesan and scholarship granting organization access and vendor integrations.

How the Terms Apply

It depends on your role. A school, diocese, or scholarship granting organization that receives FACTS services is a Customer, and the Data Processing Addendum applies. An organization that receives a customer’s data at the customer’s direction, for a limited purpose the Terms permit, is a Recipient under the Data Access Terms. A software vendor that connects to FACTS for a customer is an Integration Vendor under the API and Integration Terms. One organization can hold more than one role. The table on the Data Protection Terms shows common arrangements.

You accept the Terms when you sign an agreement with FACTS that links to them, or when you accept them through the FACTS platform. No separate signature is required.

Your signed agreement governs within its scope. The Terms apply only to matters it does not address, such as sharing data with another organization at your direction.

Your existing addendum stays in place until you accept the Terms, for example by acknowledging the updated Terms through the FACTS platform, or when you renew or sign a new agreement.

Your Data

FACTS does not claim ownership of the personal information it processes for you. It processes that information on your instructions. The Terms explain whose instructions FACTS follows, for example when a diocese contracts for its schools, but they do not decide any organization’s legal status under privacy laws. Each organization makes that determination for itself.

No. FACTS does not sell or share personal information. Organizations that receive your data at your direction may pay FACTS for their use of FACTS services, such as a platform subscription, but not for your data. FACTS does not use personal information for targeted advertising, or build profiles of students or families other than to provide the services. FACTS does not use personal information to train or develop artificial intelligence systems, except properly de-identified data as the Terms and applicable law allow.

You authorize FACTS to share it, using the method FACTS makes available, such as a setting or acknowledgment in the FACTS platform. The receiving organization must first accept the Data Access Terms, which limit what it can do with the data. You can narrow or withdraw the authorization at any time.

Your vendor accepts the API and Integration Terms and must have its own agreement with you that protects your data. You direct FACTS to enable the integration, and you can instruct FACTS to turn it off at any time.

Yes. You are responsible for what you collect through fields, forms, and questions you create, including giving any required notices and collecting only what you need. FACTS protects that information like any other personal information under the Terms.

Yes, where the school allows it. A parent or guardian can choose to carry forward information they submitted, such as a tuition assistance application, into a scholarship application.

For any period the customer’s agreement or the law requires. Otherwise, FACTS follows its standard retention schedule and deletes data on the customer’s instruction or at the end of the agreement.

Security and Updates

FACTS will notify you within 72 hours after confirming a data breach involving your personal information, unless the law or law enforcement requires a delay, and will cooperate with you in responding.

Depending on how a school uses the services, FACTS may receive personal information online from children under 13. Under the Terms, the school acts as the agent for parents in authorizing that collection. For more information, see the FACTS COPPA Direct Notice at https://factsmgt.com/childrens-online-privacy-protection/ and the FACTS Privacy Policy at https://factsmgt.com/privacy-policy/.

Each document has its own version number. FACTS posts each update with a new version number and date and keeps prior versions available. An update to one document does not change the others. For a material update, FACTS will give you reasonable advance notice before it takes effect.

Contact your FACTS account representative.

Prior Versions

ach document in the FACTS Data Protection Terms has its own version number. Every version of every document stays available here, so any organization can see the version that applied to it.

Document Version Effective Summary of changes
Common Terms 1.0 November 20, 2026 Initial publication Current
Data Processing Addendum 1.0 November 20, 2026 Initial publication Current
Data Access Terms 1.0 November 20, 2026 Initial publication Current
API and Integration Terms 1.0 November 20, 2026 Initial publication Current