Effective date: 1 October 2026
1. What these terms cover
1.1. These terms govern participation in beta programmes run by MB Uncascade (referred to as Edukamentas or we) and the use of clearly marked beta features. They apply on the website and in the Edukamentas app where the relevant access is provided.
1.2. A beta feature is a feature still being developed or tested that we clearly identify as beta, experimental, trial or early access before making it available. We may also offer a separate pilot or demonstration, clearly stating which parts are subject to these terms.
1.3. A feature is not beta merely because it is available only to teachers, schools, a particular plan, selected users or certain devices. A beta label also does not change the terms of an earlier purchase retroactively.
1.4. These terms supplement the Terms of Service. The Privacy Policy explains personal data processing, and the Subprocessor List identifies the providers used for data processing services. A school or other organization’s order, pilot terms or data processing agreement may contain more specific provisions. The relevant data processing agreement takes priority for data processed on the school’s behalf; the confirmed order takes priority for the scope purchased. Mandatory law applies in all cases.
2. Access and participation
2.1. Beta access may be provided free, as part of a paid plan or under a separate school or organization order. We may set participant selection criteria, usage limits, supported devices, a testing period and conditions for using a particular feature. We explain restrictions relevant to participation before granting access.
2.2. Taking part in a general beta programme does not itself provide access to every beta feature. Some features may require a separate invitation or activation. Using one beta feature does not automatically enrol you in other programmes.
2.3. Free or discounted beta access may be provided in return for agreed participation in testing: trying a feature, completing questionnaires, reporting errors, submitting work samples or speaking with our team. Before enrolling you, we explain the participation tasks, what data we will record, how we will use it and how long we will keep it. Where consent is required for particular personal data processing, we separate it from general acceptance of the beta terms. If you decline agreed testing activities that are objectively necessary, the relevant test or additional free access provided for it may end; declining optional additional data use alone does not have that consequence.
2.4. Beta access is not itself a promise of future public access, a discount, a free plan or payment to participants. Such benefits apply only when expressly offered in the particular programme’s conditions.
3. Operation, changes and paid plans
3.1. A beta feature may contain errors, produce inaccurate or incomplete results, run more slowly, be unavailable, fail entirely or differ from the eventual version. We do not promise a particular uptime, response time or result unless expressly agreed. This does not affect the core non-beta features of a purchased plan or mandatory consumer rights.
3.2. We may correct, change, combine, rename, limit, suspend or discontinue beta features at any time. They may disappear without becoming public; after testing, we may also offer them in other plans or for a separate fee. We do not promise advance notice of a beta feature’s change or end unless required by law or a particular order.
3.3. Including a beta feature in a paid plan does not itself mean that we will maintain it throughout the plan period. When changing or ending a beta feature, we preserve the agreed scope of the core non-beta features. If a beta feature is sold separately, its test status, known restrictions and applicable conditions are stated in the particular offer; mandatory consumer rights remain in effect.
3.4. Where a particular beta characteristic does not meet the quality requirements normally applicable to that service and the law permits a separate agreement on it, we clearly identify the characteristic before purchase and obtain the consumer’s separate express consent. General acceptance of these terms does not replace that consent.
3.5. If a beta change is legally considered a modification or lack of conformity of a purchased digital service in a particular case, the statutory information and consumer-remedy rules apply. These terms also do not restrict the 90-day money-back guarantee for Schools in section 4.3 of the Terms of Service, including its application to beta add-ons purchased under an order.
3.6. The end of free beta access does not itself create a payment obligation. Paid use begins only under a clearly presented and accepted order for a paid offer. Previously agreed trial conditions for a paid plan apply according to that order.
4. Beta data and its use
4.1. Using a beta feature may involve processing the content submitted to it, such as texts, answers, essays, requests and files. Generated responses, assessments, feedback, usage actions, error records and context supplied with a support request may also be processed. Each feature processes only the data it needs.
4.2. We use data to provide the particular feature, identify and fix errors, offer support, maintain security and investigate misuse. Where lawful, we may analyse beta tests, assess and improve the quality of the product, tasks, assessment rules or AI instructions, conduct scientific research, document findings, answer customer questions and communicate with participating schools about their service. For each use, we apply an appropriate legal basis, provide the required information and limit the data to what is needed. We do not treat product analysis or sales activities as scientific research simply by naming them as such. Section 6 also applies to data processed on a school’s behalf; sections 4.7 and 9.3 apply to anonymous findings.
Within the scope of a particular beta programme, this may include:
- comparing the accuracy of AI responses, assessment criteria, instructions and model versions;
- reproducing errors, investigating their causes and retesting to ensure that the error does not recur in a new version;
- assessing task clarity and difficulty, writing quality and handwriting recognition quality;
- studying changes in learning and use across several school years under a predefined research purpose;
- improving usability, accessibility and operation on different devices;
- supporting customers, reviewing previous correspondence or particular work, and resolving recurring problems;
- discussing pilot results with a participating school, planning implementation and training teachers to use the service;
- keeping records of agreed participation, free access granted, consents, notices and their versions;
- investigating security incidents, misuse, complaints and specific legal claims;
- verifying, substantiating or reproducing research methods, findings and published results;
- preparing anonymous case studies, statistics, demonstrations, reports and sales presentations under section 4.7.
This list applies only to data needed for the particular programme and collected lawfully. Identifiable public testimonials, use of a school’s name or logo, and direct marketing are subject to separate permissions and requirements.
4.3. The Privacy Policy and, where needed, the notice for a particular beta feature set out the purposes, legal bases, recipients and retention conditions for personal data processing. Access to a beta feature, acceptance of these terms or the content licence in section 5 is not itself consent to any and all personal data use.
4.4. Where processing requires consent, we ask for a specific, clear choice. Consent can be withdrawn as described in section 8. If we cannot provide a particular beta feature without certain lawful processing, we explain which access will be unavailable as a result. Refusing optional additional data use does not itself remove access to a purchased plan.
4.5. We do not sell identifiable beta participant data, student work, records or named results, or use them for advertising profiling. General acceptance of the beta terms does not authorize their publication in sales presentations or advertising. We give access only to our staff and service providers who need it for lawful work. Section 4.7 describes the use of anonymous research results and findings about product operation.
4.6. As far as the particular purpose allows, we reduce the amount of data used, remove direct identifiers or use aggregated data. Pseudonymized or masked data remains personal data if a person can reasonably be identified. We apply the same lawfulness and retention rules to it. Personal data retention periods cease to apply only to data from which a person can no longer reasonably be identified.
4.7. From data that we are entitled to process in this way, we may prepare irreversibly anonymized summaries, statistical indicators, research findings and examples of feature operation. We may use them for scientific research, product improvement, support, communication with schools, public reports and commercial or sales presentations without disclosing identifiable user data. Removing a name alone is not enough if the text, a small group or other circumstances can identify someone. Publishing a school’s confidential information, name, logo or identifiable testimonial requires an appropriate separate right; this provision does not itself grant that permission.
5. Your content and feedback
5.1. You retain rights to your original content. To the extent that you are entitled to grant them, you give Edukamentas a non-exclusive, royalty-free licence to store, copy and process the content, display it to you or authorized users in your organization, generate feature outputs and perform other actions necessary to provide the agreed beta feature and fulfil the purposes lawfully described in this document.
5.2. We may give service providers only the usage rights they need to perform the services we assign to them. The licence does not authorize selling your content, publishing it for advertising or using it outside the stated purposes. The restrictions in sections 4 and 6 apply to personal data and school content.
5.3. We may use voluntarily submitted suggestions, error descriptions and other feedback to improve the product without additional payment. If you also submit personal data, student work or other material subject to use restrictions, this provision creates no additional basis for using it. Do not submit other people’s data unless needed to explain the issue.
5.4. Feedback provided for an ordinary non-beta feature is governed by the general Terms of Service and Privacy Policy. A support request, comment or error report alone does not make your account or its content part of a beta programme.
5.5. When content remains saved in your account, we use it to provide that account feature under the general terms and Privacy Policy. The end of beta access does not itself authorize continued use of that content for a separate product-improvement purpose.
6. Schools, organizations and minors
6.1. Beta access for schools may be provided under the Schools plan, its selected add-ons or the conditions of a separately agreed pilot. The scope, participants and period are stated in the particular order or pilot terms.
6.2. Protection of student work, answers and progress data depends on the actual purpose of use and the parties’ roles. It does not depend solely on the plan name, payment method or whether a teacher signed in through a personal account. A person acting for a school does not give Edukamentas broader rights to student data simply by using an individual account.
6.3. When a school or organization determines the processing purposes and Edukamentas acts as its processor, we follow its documented instructions and the data processing agreement. Data that we lawfully process for our own purposes, such as contract administration, is subject to the relevant roles and bases stated in the Privacy Policy.
6.4. We do not use student work, answers or named assessment data processed on a school’s behalf to improve the general product or models beyond the agreed school service, support, security, error correction or other lawful documented instructions. Other use requires a separately assessed lawful basis, the necessary information and applicable agreements. A teacher’s or student’s acceptance of these terms alone does not replace the school agreement.
6.5. The school or organization ensures that its representatives have the necessary authority and that users are properly informed. Edukamentas remains responsible for its own duties under law and contract. These terms do not transfer all data-processing responsibility to a teacher or student.
6.6. The participation rules in the general Terms of Service apply to minors. Where parental or guardian consent is required for particular personal data processing, the child’s choice alone is not enough. A teacher’s participation in the programme does not itself replace parental or guardian consent required by law.
7. Artificial intelligence and service providers
7.1. Beta features may use artificial intelligence to create text, tasks, explanations or learning feedback. We identify AI use in the relevant feature. Results may need checking: they may contain factual, language, calculation or assessment errors.
7.2. Edukamentas improves product operation, AI instructions, assessment criteria and task presentation. Permission to use data for these purposes is not general permission to train third-party general-purpose AI models. We do not use identifiable user texts, answers or files for such training without a separate lawful basis, the necessary information and, where applicable, express consent or an organization agreement. Accepting these terms alone is not enough.
7.3. Data needed for a feature may be shared with infrastructure, AI, support and other necessary service providers under the Privacy Policy, Subprocessor List and applicable agreements. Changing a provider does not itself allow us to give it broader content rights than these terms and the law permit.
7.4. An AI assessment, including a result for essays, open answers, VBE or PUPP tasks, is not itself an official grade, examination result or school decision. The teacher or other competent institution independently reviews the student’s work and decides under the applicable rules. This provision does not reduce Edukamentas’ duties concerning operation of the system itself.
8. Ending participation and withdrawing consent
8.1. You can end participation in a beta programme or withdraw consent to data processing by writing to [email protected]. Identify your account and the programme, feature or consent concerned. You can also use a relevant account control if one is available. Email contact is available at every participation stage.
8.2. When processing is based on consent, withdrawing it stops further processing on that basis. Withdrawal does not invalidate earlier lawful processing. If some data must continue to be processed under another independent lawful basis, we apply only the scope and retention conditions needed for that basis; acceptance of the beta terms alone does not justify it.
8.3. Ending participation and deleting an account are different actions. Leaving beta does not itself delete your account, cancel a paid plan or remove ordinary access. It is also not an automatic request to delete all data saved in your account. You can use the same email address to request erasure or exercise other rights.
8.4. Beta access may end when the agreed test or pilot ends, a feature is removed, eligibility ends or the terms are breached. Section 3 applies when the ending affects a purchased service. We explain a planned ending and its consequences for access and data with regard to the nature of the service, agreements and legal requirements.
9. Retention of beta records, archives and research findings
9.1. Beta record retention depends on its purpose. Ending participation does not itself require deletion of every lawfully used research, support or programme-history record. We keep identifiable data only for as long as a specific lawful purpose requires it, and delete or irreversibly anonymize it earlier when that need or basis ceases. A beta label, archive name or possibility of future reuse is not a sufficient retention basis on its own.
9.2. We do not automatically delete beta work and conversations saved in an account solely because of their age while the participant continues to use the Account; the three-year inactivity rule in sections 7.7–7.8 of the Terms of Service applies to them. Identifiable samples, records, transcripts and assessment data kept separately for research, quality evaluation or programme administration are reviewed according to their purpose. Normally, we delete or irreversibly anonymize them when no longer needed or three years after the participant’s last website sign-in, authenticated mobile-app use or, if they have no account, participation in a test. Selected records may be needed longer for an ongoing study across several school years or verification of its findings, a defined AI-quality comparison and error regression tests, an unresolved support request, an ongoing school agreement, evidence of consent or access granted, or investigation of a security incident, complaint or legal claim. In each case, we specify the purpose, lawful basis, necessity, scope of data retained and next review or deletion date or clear trigger. When the need ceases, we delete or anonymize without waiting three years. For scientific research, we apply the safeguards in GDPR Article 89 where relevant. More specific criteria appear in the Privacy Policy, research notice or applicable agreement.
9.3. We may retain indefinitely irreversibly anonymized research findings, statistical summaries and examples from which a person can no longer reasonably be identified, and use them for the purposes in section 4.7 even after the original data or account is removed. An exported file, closed archive, changed name or pseudonymous identifier does not itself mean anonymization. If records can still be linked to a person, personal data rules apply to them and their exported copies. Anonymization itself must be a processing operation we are entitled to perform; confidentiality and content-use restrictions also continue to apply.
9.4. Retention decisions also apply to separately saved exports and quality-evaluation copies. Backup removal follows a reasonable backup cycle; backups are not used for continued daily product improvement simply because the original was deleted. Archiving, copying or renaming a programme does not reset the participant’s last-activity date or replace review of the need for retention.
9.5. When we act as a school or organization’s processor, the data processing agreement, lawful documented instructions and the law determine return, erasure, anonymization and retention. General beta participation does not authorize keeping a school’s student work or named results in our research archive contrary to those requirements. Records processed for our own lawful purposes must be kept separate from data processed on the school’s behalf.
9.6. We may retain data needed for accounting, a legal obligation, or establishing, exercising or defending a specific legal claim for the applicable period. This does not authorize continued use of the entire beta archive for other purposes. The effects of withdrawing consent and exercising other data-subject rights are assessed under section 8 and the law.
9.7. Work and personal learning history saved in an account are processed for the purpose of the relevant feature and under sections 7.7–7.9 of the Terms of Service. The account’s three-year inactivity period runs from the later of the last website sign-in and last authenticated mobile-app use; if neither occurred, it runs from account creation. An active personal subscription, organizational access and accounts with special rights are not automatically removed under section 7.7 of the Terms. Identifiable copies held separately for research or quality evaluation are kept only as long as needed for a specific purpose, applying the review in section 9.2. To request a copy of the data held, write to [email protected].
10. Confidentiality of private programmes
10.1. If we state before participation that a programme or particular non-public information is confidential, do not publish its screens, recordings, pricing, testing instructions or technical details without our consent. Restricted access alone does not mean that all information about a feature is confidential.
10.2. Confidentiality does not apply to lawfully public information, information obtained independently without a confidentiality duty or information that must be disclosed by law. It does not prevent you from defending your rights, contacting regulators or a court, reporting a breach or consulting a lawyer, parent or guardian confidentially.
11. Misuse and changes to these terms
11.1. Beta access does not authorize bypassing limits, sharing personal sign-in credentials, automating requests or collecting other users’ data without permission, trying to obtain non-public system instructions, attacking infrastructure or violating others’ rights. Authorized invitations to school users, seat assignments and agreed feature use do not constitute prohibited account sharing.
11.2. For a breach, we may proportionately restrict or suspend beta access and, where justified, apply the measures in the general Terms of Service. We may act immediately for an urgent security or misuse threat. A restriction does not itself remove the consumer’s rights concerning a purchased service.
11.3. We may update these terms because beta features, service delivery, security or legal requirements change, or to explain participation more clearly. We notify users of changes in accordance with the general Terms of Service and the law. Updating the terms alone is not enough for a new personal-data purpose or broader use: we separately assess the lawful basis, provide information and, where required, request new consent.
11.4. Send questions about beta access, data use or these terms to [email protected].
