Terms for a one-assignment pilot

These terms apply between Eklipse Technologies (Eklipse) and a higher-education institution (the institution) that requests a pilot through the site or by email. They are a summary of the offer. Where the institution and Eklipse sign a pilot agreement or a data processing agreement, the signed document governs and this page does not. Learners are not party to these terms; what applies to a learner is the privacy notice their institution adopts.

Verifi adds a short, submission-specific conversation to a written assignment or discussion post, records the learner's explanation (spoken, typed or faculty-led), and gives designated faculty an organised, sourced summary and the evidence behind it to read before they decide what happens next.

• No output of the service is a mark, a verdict or a classification of a learner, and the institution agrees not to use any output as one. The decision of record is always a named member of faculty's, recorded with their reason.
• The service performs no AI-content detection, plagiarism detection, proctoring, biometric identification or behavioural analysis, and produces nothing that may be presented as evidence of any of these.
• The service is not for use with minors, in admissions or in employment screening, and must not be the sole basis for any decision with a legal or similarly significant effect on a learner.

• The institution designates the faculty who may sign in and the administrator who may export, erase and configure. Access is closed by default and there are no self-service accounts.
• Faculty access during a pilot uses a closed demonstration gate: an access code and a participant allowlist supplied out of band. Institutional single sign-on is planned and not built; the institution accepts the gate for the pilot or declines the pilot.
• Learners reach a verification from the LMS or a secure link. No learner account or password exists.
• The institution keeps its credentials confidential and tells Eklipse without delay if it suspects they are compromised.

• The institution owns all data it and its learners put into the service and everything the service derives from it. Eklipse processes it only to provide the service, on the institution's documented instructions, under a data processing agreement on Article 28 terms offered before any learner session.
• Eklipse does not use the institution's data to train models, does not sell or share it, and sends no learner name or email to a language model.
• The subprocessors that may process the data are listed in the trust pack. A new subprocessor is added there and in the DPA annex before it receives any data, and the institution is notified in advance.
• On request at any time, and in any case at the end of the pilot, the institution's data is exported to it in an open format and then erased, and the erasure is logged. Faculty decisions and the audit trail can be kept as the institution's record of review with learner identity removed, if the institution asks.
• Eklipse will notify the institution's contact within 24 hours of confirming an incident that affects the institution's data, with what is not yet known stated as such, and will support the institution's own notification duties.

• The institution informs learners before their first session, using or adapting the privacy notice, and records that it has.
• A learner may always choose a typed explanation instead of a recording where the instructor's policy allows it, without penalty. The institution configures that choice per activity.
• Accommodations (extended time, audio without video, a faculty-led conversation) are configured by the institution through its own disability services process; see the accessibility statement.

• Use the service only for the purpose in these terms and within the institution's own academic policy.
• Do not attempt to derive a detector, a classifier or a ranking of learners from the service's outputs or data, and do not represent any output as one.
• Do not test the service's security without written agreement; report a suspected vulnerability to [email protected] and we will not act against a good-faith report.
• Do not upload work that the institution does not have the right to process, or content unrelated to the assignment being verified.

Either party may end the pilot with 14 days' written notice to the other's named contact, and Eklipse may suspend access immediately where continuing would breach these terms or the law, telling the institution why. At the end, the institution decides whether to go further; there is no automatic renewal and no obligation. Export and erasure follow the data section above regardless of who ended the pilot or why.

The pilot is provided without charge and, to the extent the law allows, without warranty of uninterrupted or error-free operation. Each party remains liable for its own breach of data protection law and its own confidentiality duties; neither party is liable to the other for indirect or consequential loss arising from the pilot. Nothing in these terms limits a liability that cannot be limited by law. The signed pilot agreement contains the negotiated terms and prevails over this section.

Eklipse may update this page and moves the review date when it does; a change does not apply to a running pilot without notice to the institution's contact. Governing law and venue are set in the signed pilot agreement. This page is offered to speed up a review; it is not legal advice, and the institution's counsel will adapt the signed agreement as needed.

Pilot requests, contract questions and the DPA template: [email protected]. A person replies within two working days.