Terms of Service for Academies

This agreement is for the organisation that runs an academy on Alethris. A learner, and each member of your own staff, holds their own account under separate terms, and the two documents do not depend on each other.

1. Who this agreement is between

These Terms are an agreement between iSoterik Limited (iSoterik, we, us), a company registered in Nigeria with number RC 9910229, whose registered office is at No 22 Benin Street, Malali, Kaduna, and the organisation that holds an academy on Alethris (the academy, you).

The person who starts an academy accepts these Terms on the organisation's behalf by ticking the box when creating it, and confirms that they have authority to do so. We record which version was accepted, and when.

Alethris is the product. iSoterik is the company that builds it. iSoterik Academy is an academy that runs on Alethris like any other, and its presence gives it no standing under your agreement.

Learners are not parties to these Terms. Every person on the platform — your learners and your own staff — holds an Alethris account under the Terms of Service for Account Holders, and what we do with their personal data is described in the Privacy Notice for Account Holders. What we do with the data you are responsible for is described in the Privacy Notice for Academies. Your own relationship with your learners — what you teach, what you charge and what you promise them — is yours alone.

2. Definitions

Academy address — the platform address your academy receives when it is created, and any custom domain you connect to it.

Alethris Hub — the area where a person manages their account, sessions, Skills Passport and academy memberships across every academy they belong to.

Credential — the record, issued by your academy, that a learner completed one of your programmes and, for an assessed credential, of the competencies assessed on the way, together with the certificate generated from it.

Learner — a person who applies to or enrols in one of your programmes. Where you allow it, a person may apply without an Alethris account, but holds one before an offer is made to them.

Managed payment fee — the percentage of a learner payment collected through Alethris that we charge for operating the payment flow, taken when the payment is split.

Member — a person holding a membership of your academy with one or more roles.

Plan version — a published version of a plan, stating its monthly price, its limits and its managed payment fee. Your subscription is attached to one plan version.

Programme version — a published version of a programme, including its curriculum, rubrics, completion rules, refund policy and application form.

Skills Passport — the page a learner controls, on which they may show credentials, competency evidence and projects from their learning.

3. Accounts and identity

An Alethris account belongs to a person, not to an academy. A person may belong to several academies, with different roles in each, and may leave any of them.

Before an account can sign in, its holder must confirm the email address on it by opening a link we send, which lasts twenty-four hours. We do this so that an academy cannot create accounts in other people's names, and so that a person's credentials cannot be attached to an address they do not control.

People sign in at Alethris Hub, and your academy's address signs them in by passing their session across from the Hub. Each address then holds its own session.

Unless you choose otherwise in your academy's admission settings, people may apply to your programmes without an Alethris account. They give their name and an email address, which they confirm with a code we send to it. When you accept such an applicant, we find the account that address already has or, if it has none, make one in the name and address they applied with, and then either email them a link to set it up or invite them to sign up, as you choose there. An account made this way cannot be signed in to until its holder sets it up, which confirms the address and accepts the Terms of Service for Account Holders; if the offer lapses before then, we erase it.

You may invite people to your academy. An invitation is issued to one email address, names the roles it grants, lasts seven days, and may be accepted only by the person signed in as that address. Accepting it grants membership of your academy with those roles; it does not give you access to that person's account, their password, their sessions, or anything they do at another academy. Removing a membership does not touch the person's account. When a member leaves or you remove them, any place they hold that has not finished, and any application still waiting, ends; nothing is refunded automatically. Removing someone does not stop them applying again, or enrolling again on a programme that takes direct enrolment; they come back as a learner only.

You are responsible for the conduct of your members, and for withdrawing a membership promptly when a person should no longer have access.

4. Your academy, its address and its members

Any person with an Alethris account can start an academy from Alethris Hub, and becomes its owner. While Alethris admits academies by invitation, only a person we have invited can start one, signed in with the email address the invitation was sent to. An invitation lasts thirty days, starts one academy, and can be withdrawn by us until it is used.

Your academy receives a permanent platform address when it is created. It cannot be changed, and it is never given to another academy, even after yours closes.

On a plan version that includes custom domains — Growth, Scale and Enterprise do, and Starter does not — an owner or administrator may connect one subdomain of a domain you control. Connecting it requires proof of control through DNS, and we manage its certificate. Exactly one address is your academy's main address at any time. A connection that is not proven within seven days lapses. A connected domain that stops working is disabled after repeated failed checks, and your platform address becomes the main address again; anyone signed in at the custom domain is signed out. If you move to a plan without custom domains, a working domain is kept for fourteen days and one still being connected is disabled at once. We do not disconnect a working domain merely because our own billing records are briefly unavailable.

Your academy has an operational status, separate from its billing: active; read-only, in which its records can be read by its members and its pages by the public, but nothing in it can be changed; suspended, in which nothing opens for anyone; and cancelled, once it has been closed.

Roles inside your academy are owner, administrator, finance administrator, instructor, mentor, assessor and learner. A membership may hold several, and must always hold at least one. What each role may do is defined by Alethris, not by the academy; we may refine those definitions as the product changes, and bring your academy's roles back into line with them. The owner role changes hands only through the transfer of ownership, which the current owner confirms with their password and which is possible only while the academy is active. The last owner cannot be suspended or removed, and cannot leave.

Your academy's pages and workspace say "Powered by Alethris", and the emails we send for you arrive as from your academy "via Alethris". You cannot remove either. Anyone can stop your announcement emails from the link in each one; they still see your announcements in Alethris. Your learners can add your academy to their home screen as an app bearing its name, colours and description.

5. Subscription, fees and billing

Plans. Alethris publishes the Starter, Growth and Scale plans, each with a monthly price and stated limits, on its pricing page. Enterprise is agreed with us directly: we record an agreement and issue an invoice, and the agreement takes effect when that invoice is confirmed as paid. What applies to you is the plan version your subscription is attached to.

The trial. A new academy starts a thirty-day trial on the Starter plan automatically, with no card, and receives 25,000 AI credits that can be used during those thirty days. We tell your owners and finance administrators a week before the trial ends, unless the academy is closing. Nothing is charged when the trial ends; your academy's growth is restricted, as described below, until you subscribe. Subscribing during the trial ends it, and your first paid month starts that day. Closing the academy sets the trial to end, as clause 16 describes.

Paying. You choose a plan on the Billing page and pay the first month through Paystack, which then charges the same card each month. You can change the card from the Billing page. Enterprise agreements are invoiced on their own terms. When an Enterprise agreement takes effect, Paystack stops charging your card, and a plan payment we cannot apply — one that lands after that, or for a checkout or an upgrade since replaced — is refunded to you. Where online payment is not yet available, plans, AI credits and video hours cannot be bought from the Billing page, and we arrange payment with you directly. Plan changes, cancellations and purchases are confirmed with a password. Owners and finance administrators manage billing; administrators can see it.

Prices. Prices are stated in naira and are the whole price: any value added tax is part of the price, never added to it. Where a price includes VAT, the pricing page, your Billing page and the invoice say so, and the invoice shows the VAT it includes.

A plan version does not change underneath you. We may move subscriptions to a new version of their plan; a new price then applies from your next renewal, never part-way through a period you have paid for, and we will tell you at least thirty days before it does. A change that alters only a plan's limits, and not its price or fee, may apply sooner. A lower limit never takes away anything you already have; it only refuses growth beyond it. We may also grant an academy temporary limits or a different managed payment fee.

If a renewal fails, owners and finance administrators are told, and you keep full access for a grace period of seven days from the start of the unpaid period. You can pay from the Billing page at any point, with the same card or another, and a new month starts that day. Enterprise agreements have no grace period once their paid-through date passes. After that your academy's growth is restricted: no member of staff can be invited, no programme can be published for the first time, the homepage cannot be published, no cohort can be created or scheduled, no new offer can be made and no invitation to enrol can be accepted, your staff cannot upload files or video, no edition that adds hosted video can be published, learners cannot start a payment through Alethris, and no new credential can be issued. Offers already made can still be taken up.

Everything already in your academy keeps working. Teaching, learners handing in work with its files, assessment, attendance, video playback, credential revocation, public verification and your learners' Skills Passports all continue, as do recording payments you received directly, issuing refunds and spending AI credits you have bought. A billing problem restricts what your academy can take on; it never stops it honouring what it already has. The same restriction applies when a trial ends without a subscription, and when a cancelled subscription reaches the end of its period.

Changing and cancelling. An upgrade takes effect as soon as the prorated difference for the rest of the period is paid; its quote is valid for fifteen minutes. A downgrade takes effect at your next renewal, and you can keep your current plan until then. Cancellation takes effect at the end of the period you have paid for, and you can resume the subscription before then; paying to keep or restart your plan also clears the cancellation. A renewal Paystack charged before your cancellation took effect is honoured for that month, and the plan then ends. Cancelling it on Paystack's own page has the same effect. A subscription can also be cancelled after a renewal has failed, even while your academy is read-only; the period paid for has then already ended, so the cancellation takes effect at once and cannot be resumed. The renewal left unpaid stays on your invoices as due; choosing a plan again starts a new month and replaces it.

Limits. Your plan sets limits on staff, learners holding a place, open cohorts, published programmes, storage, hours of video in your library, hours of video delivered each period, and first credentials issued each period, and says whether custom domains are included. A learner holds a place from the offer of it until they complete, withdraw or their place ends. We warn you as you approach a limit and refuse only the action that would cross it, before any payment is taken for it: a place a learner has paid for is never withdrawn because of a limit, and a video is refused before it is uploaded rather than after. A learner's work is accepted even when storage is full, and counts toward it. You are never charged for going over a limit.

AI credits are bought separately, as prepaid purchases. Each purchase expires 365 days after it is paid, and credits are spent soonest-expiring first. They are recorded in a ledger that cannot be edited, and they are not cash, not a wallet and not transferable. A purchase none of which has been used, and which has not expired, may be refunded on request. If a payment for credits is reversed or refunded after some were spent, if an answer already under way costs more than the credits you have left, or if we remove credits that have already been spent, the shortfall is owed and is taken from the next credits you buy. Running out of credits stops AI requests; it never stops assessment, credential issuance, payments or any other core function.

Video delivery hours can be bought for the current billing period. They raise that period's delivery allowance, end with it, and are not refundable; hours paid for after a period has ended apply to the next one; if the payment for them is reversed, they end early. Reaching the delivery allowance never interrupts playback; it pauses new video uploads and the publishing of new hosted video until the next period.

6. Learner payments and settlement

Your settlement account. An owner or finance administrator gives us your bank and account number, and Paystack confirms the account name. A change to an account already in use waits twenty-four hours, and we then review every submission before it goes live. When you submit an account, Paystack creates a subaccount in the business name you give, and from then on we keep only the account number's last four digits; payments settle to it once any wait and our review are complete. We may reject a submission or suspend a settlement account, with a recorded reason, where we suspect fraud or a mistake, and we tell your owners and finance administrators why, in Alethris and by email. Where online payment is not yet available, there is no settlement account to set up and learners cannot pay through Alethris: they pay you directly, and you record each payment as this clause describes, with no Alethris fee on it.

This is provider-directed settlement, not escrow. Paystack settles to your account. iSoterik does not hold, control or have access to your learners' money at any point, and the platform provides no wallet, no withdrawable balance and no payout mechanism. The only amount we can owe you is a credit of our own fee under clause 7, which we pay by taking less fee. What the product shows you is what is pending with the provider and what the provider has settled — never an amount available to withdraw.

What learners pay. Learners pay the price you publish, less any discount you give, in full and in one payment; there are no instalments. Prices are in naira. A place your staff offer — by accepting an application, enrolling a learner by hand or through an invitation — is held for seven days from the offer, even after the cohort's enrolment has closed. A place a learner takes for themselves must be paid for within seven days and before enrolment closes. A place not paid for by its deadline is released; a payment made before the deadline still counts if Paystack confirms it later. When a cohort is cancelled or completed, offers still unanswered and places still unpaid are withdrawn, and the people holding them are told.

Fees. Two fees come out of what settles to you, and neither is added to what the learner pays:

• Paystack's processing fee, set by Paystack's own schedule and borne by your subaccount. We record the schedule each quote used. The verified fee and your actual net are recorded once Paystack confirms them, and they supersede the estimate; where an actual fee falls outside the range we quoted, we open a case for review rather than adjusting a figure.
• The Alethris managed payment fee: 3% on the Starter plan and during the trial, 2% on Growth, 1% on Scale, and the rate in your agreement on Enterprise. It is charged on the price after any discount, and fixed when the checkout is created, so a later rate change never rewrites a payment already quoted.

While you owe Alethris a recovery, Paystack also sends part of each payment to Alethris until it is cleared; while Alethris owes you a credit, it takes less fee (clause 7). There is no Alethris fee on payments you record yourself, on sponsored places or on free places.

How learners pay. A learner pays by card on Paystack's own page or, where it is available, by bank transfer to a temporary account issued for that one attempt and that exact amount, which lasts about twenty minutes. While an earlier attempt can still be collected, a second one is not offered. A price so low that the fees could equal it cannot be paid online.

Payments you take yourself. You may record a bank transfer a learner made to you directly. The amount must equal what is due, and an owner, administrator or finance administrator confirms it with their password. You are responsible for that judgement; we do not verify manual transfers. You may also record a sponsor who is paying for a place, give a place free of charge, or enrol a learner by hand.

Discounts. Owners and administrators may create discounts: a percentage or a fixed amount, applied automatically or through a code, across the academy or to named programmes or cohorts, with optional dates, caps, a limit to new learners and a minimum price below which a discount does not apply. Each place receives at most one discount — the best one for the learner — and it is recorded on the place and never revised. Once a discount has started, what it is worth, its code, what it covers and who qualifies for it cannot change; its end date and overall cap can. A code entered on an application is honoured even if the discount ends before the offer is made, unless you archive it; a discount's cap is claimed when the offer is made.

Keeping the record straight. We observe Paystack's settlements and match them against the payments we recorded. Where they do not match, we record a mismatch for review rather than adjusting a figure. Refunds, reversals, disputes and settlements are recorded as new entries, not as edits to the payment.

Disputes. Where a learner disputes a payment with their bank, Paystack's notice is recorded against your academy and a case is opened. You are responsible for responding to the dispute and for any amount reversed as a result.

7. Refunds and recovery

Each programme version carries a refund policy: a window of up to 365 days after payment within which you will refund, and whether you may refund part of a fee within it. Payment records that policy into the payment's quote, so the policy that applies is the one in force when the learner paid.

Owners, administrators and finance administrators can issue a refund, with their password and a recorded reason, which the learner sees on their payment, in the refund email and on its receipt. Outside the window, only an owner or finance administrator can. A full refund may also end the learner's access, if you choose. Where Alethris can return a payment through Paystack, it does; otherwise you refund the learner directly and record the refund against the payment. If a place that has been paid for is refused — because its deadline had passed, its cohort had ended, or your academy was read-only, closing or suspended when the payment arrived — the payment is refunded in full automatically where Paystack refunds are available.

The Alethris managed payment fee and Paystack's processing fee are not refundable. Where a refund is issued, the full amount refunded comes out of your academy's earnings and both fees stay spent. We may, on review, credit part or all of the Alethris fee on a payment. That is a decision of our finance team, made with a recorded reason and a re-entered password, and recorded as its own entry. A credit first clears any recovery you owe us. The rest is paid to you through Paystack with your later learner payments, each taking up to its own Alethris fee less, until the credit is cleared; we have no other way to pay it, so it waits while no learner pays through Alethris.

Where Alethris returns a payment through Paystack, the refund comes out of what Paystack has yet to settle to you from that payment. Whatever that cannot cover, because Paystack has already settled the payment to you, is first set against any credit Alethris owes you; the rest becomes a recovery owed to Alethris, and a case is opened. Paystack withholds it from what settles to you from your later payments through Alethris until it is cleared — payments you record yourself do not reduce it — and it is shown to you on Payments & earnings. A refund you make to the learner yourself, and record against the payment, reduces only your earnings.

Sponsored places are an arrangement, not a payment. Where you record a sponsor, the platform holds the committed amount, your own reference and, when you mark it settled, the date and payment reference; a commitment is released if the place never goes ahead. It moves no money, takes no fee and has no refund path. You and the sponsor settle between yourselves.

Nothing in this clause limits any refund right your learners have under the Federal Competition and Consumer Protection Act 2018, and your refund policies must allow for those rights.

8. What your academy publishes

Your academy has one public homepage, composed from a set of section types: hero, about, programmes, upcoming cohorts, image and text, team, outcome statistics, testimonials, gallery, logo cloud, frequently asked questions, call to action and contact. Until it is published, your academy's address shows a holding page, and no programme or application page opens. Once published, it is listed by search engines unless you turn that off. Programme pages, including their application questions, and cohort pages are public too; a cohort page names the instructors and mentors assigned to it and shows its sessions. You choose the content and you are responsible for it, including any that our assistant drafted for you.

Four kinds of content carry claims that only you can substantiate: team members, testimonials, logos, and outcome figures you state yourself. When you publish a page containing any of them, you confirm that "the outcomes, team members, testimonials and logos on this page are accurate, and everyone shown has agreed to appear", and publication is refused without that confirmation. On your public page those sections say that your academy states them and that Alethris does not check them. Figures that Alethris counts from your records are marked as counted by Alethris instead. We will not remove either label on request.

You must not describe a credential as a degree, a National Diploma, a Higher National Diploma, or any other award the law reserves for accredited or statutory institutions. Alethris refuses a credential title that names a degree (including a bachelor's, master's or doctorate), a Higher National Diploma, a National Diploma, a National Innovation Diploma, a national vocational, technical or business certificate, or a National Skills Qualification, when a programme is saved and again when it is published. It refuses them whether or not you are authorised to make such an award, because it cannot check that authority. The check recognises the usual forms of those titles only; you remain responsible for every title you choose.

Your registration, if you give it. Giving us your academy's registration with the Corporate Affairs Commission is optional. An owner or administrator may enter whether it is registered as a company, a business name or incorporated trustees, its registration number and its registered name, and may change or remove them at any time. A person on our support or security staff compares them with the Commission's register and records whether they match; where they do not, we say what did not match so that you can correct it. Either way, we tell your owners and administrators the outcome, by email and in Alethris, unless you have changed or removed the details since we checked them. Once a registration is verified, the verification page of every credential your academy has issued, and every page of your academy's public site, shows a "Verified academy" mark with the registered name, the number, when we checked it and any accreditation whose evidence we saw. A learner's own page for one of your credentials shows the mark with the registered name and number, and a Skills Passport shows the mark beside each of your credentials. The mark confirms who issued a credential; it says nothing about the quality of your teaching or your assessment. Changing the details removes the mark until we have checked them again, and removing them removes it at once. The details you give must be accurate and must be your academy's own. An academy without a registration is not marked down: its credentials verify in full, without the mark.

We do not verify your programme descriptions, outcome claims, prices or staff credentials. We may remove content that is unlawful, that infringes someone else's rights, or that breaches clause 12.

9. Learning records, assessment and credentials

Published programme versions and their curricula are fixed. A cohort is attached to the version it was created from, so a later publication cannot change what a learner enrolled in.

A learner's handed-in work is stored as versions that cannot be changed. A learner can hand work in again only when a reviewer asks for changes, and only as many times as the assignment allows.

Only a person holding the assessor role and assigned as an assessor to the cohort can approve or reject work. Self-paced work follows its programme's staff list in the same way: once you have seated anyone on it, only an assessor seated there can approve or reject the programme's self-paced work, and only the people seated there, with your owners and administrators, can see it; while nobody is seated, anyone holding the assessor role can. Owners, administrators, instructors, mentors and assessors can ask for changes. The decision is recorded with the name of the person who made it, and nobody may assess their own work. A decision may be replaced, by a person with the same authority, who gives a reason and re-enters their password; the record keeps the earlier decision, who replaced it, when and why. Attendance corrections need a reason and keep the earlier mark, competency evidence can be superseded only by replacing the assessment behind it, and intervention notes keep every revision. Nothing is overwritten.

Completion is determined by the rules published on the programme version — how much of it a learner must finish, attend and pass, and, for a cohort, that the cohort has ended — and there is no administrative override. Where attendance is corrected or an assessment is replaced and the learner no longer meets those rules, completion is withdrawn, and so is any credential already issued on it; both are recorded as history, not erased.

A programme that issues credentials says what they certify. An assessed credential can be published only when every required assignment must be completed in full, at least one required assignment needs an approved assessment against a competency rubric, and every competency the programme's outcomes promise is assessed that way; it carries the competency evidence behind it. A certificate of completion records that the completion rules were met, carries no competencies, and says that it does not certify assessed skills.

When an assessor approves work, they record how they judged it: by reviewing the evidence, by live observation, by oral interview or by practical demonstration. Before a credential is issued, a second person who may finalise assessments, and who assessed none of the learner's work, may confirm the evidence behind it. A confirmation covers only the evidence approved before it; if more is approved later, or the confirmer judges any of the learner's work, the credential is issued without it unless the evidence is confirmed again.

Credentials are issued by an owner or administrator as a separate decision, with a re-entered password, once a learner has completed; they are never issued automatically, and each counts towards your plan's limit on first credentials. The person issuing it confirms the learner's name against your records. The certificate carries your academy's name and logo, the learner's name as confirmed, the programme, the credential's title, its dates, a verification code and, if you add them, up to two signatories — each with a name, a role and a signature image — and one sentence of your own. A certificate keeps the signatories and sentence it was issued with, and anyone holding the code can download it. Anyone holding the code can verify the credential. They see what it certifies; for each competency, who assessed it, how, when, and the wording your academy used for the competency, criterion and level as it stood at issue; whether the assessor had taught the learner's cohort, or whether a second assessor confirmed the evidence, and if so who; and that your academy checked the learner's name. Assessors' and confirmers' names are therefore shown to anyone holding the code. We count how often each credential's record is looked up, but never record who looked; the learner and your staff can see the count and when it was last looked up.

A programme may give its credentials an expiry period. You may replace a credential with a new one, confirming the learner's name again, or revoke it, each with a re-entered password and a recorded reason. Revocation changes what verification says, but does not delete the record, because a person who relied on the credential is entitled to know that it existed and that it was withdrawn. A certificate already downloaded does not change; verification is where the current status is shown.

Assessment integrity is yours. We provide the mechanism; the judgement, and responsibility for it, remains with the person who made it and with your academy.

10. Skills Passport and learner control

A learner may add the credentials, competency evidence and projects from their learning to their Skills Passport. The Passport belongs to the learner. They choose, for each item, whether it is public, reachable only by a link they share, or private, and they can change that at any time and revoke a link they have shared.

A learner cannot alter what a credential says. You cannot see a learner's Passport beyond what they make public or share, you cannot make them display a credential, and you cannot remove an item from their Passport. An item shows the current state of the credential behind it, so revoking or replacing a credential shows there.

A learner may also choose to show, on a credential's verification page, up to five pieces of the assessed work it was earned on, exactly as they handed them in: their text, their files, which anyone holding the code can download, and their links. That choice is theirs, not yours, and they can change it at any time. Group work cannot be shown, because it is not one learner's alone. A credential that is revoked, withdrawn or replaced shows none. An assignment may ask for a recorded walkthrough: a link to a video in which the learner shows and explains their work.

If a learner leaves your academy, their credentials remain valid and remain on their Passport.

11. AI assistance

Alethris includes two optional AI assistants, one for your staff and one for your learners. Each is off until an owner or administrator switches it on with their password, and either can be switched off the same way; switching one on does not switch on the other. Once an assistant is on, every one of its tasks is available, including tasks we add later, and you can turn off any task. You can also turn the learner assistant off for a single programme.

Staff tasks draft programmes, their skills, assignments, rubrics and your homepage from the material you give them; give an assessor a private checklist of what to look for in a piece of work, drawn from the assignment's brief and rubric; summarise a learner's risk record and propose a check-in; draft messages; and answer staff questions about your academy's records. Learner tasks answer a learner's questions, explain and summarise lessons, plan their study, clarify assignments and explain code, all within their own programmes at your academy. We also provide Alethris Help, which answers anyone's questions about Alethris from the Alethris Guides and does not read your academy's records.

AI never makes an authoritative decision. Assessments, competency approvals and credentials are made by people. An AI proposal changes nothing until a person applies it; when they do, the platform checks their permissions again and applies it as them. Most of what it applies is a draft for them to review; a proposed check-in, once applied, is recorded as a check-in. The marking checklist does not read the learner's submitted work, suggests no level, score or decision, and is shown only to the assessor. The product works fully with AI turned off.

Each task uses a provider — OpenAI or Anthropic — and a quality tier, which you can change. We choose the model behind each tier and may move it to a newer one. We never move a task silently to the other provider when yours fails. AI tasks consume prepaid credits from your academy's balance, and only a complete answer is charged: a run that fails, is cut off, comes back empty, or is refused by our safety or size checks costs nothing. You may limit how much each learner can use each day. Where an answer to a learner draws on your material, it cites its sources by default.

To answer, a task sends the provider what it needs: the question; the relevant passages of your material — published or, for a drafting task, the draft being worked on; the text of any document a member of staff gives it to draft from, up to ten documents and 250,000 characters of each; and records the person asking is allowed to read. For staff, that can include learners' names, progress, attendance, fees and risk flags, and, when drafting your homepage, its team and testimonial text; for learners, their own feedback and the names of the people who assessed them. Your published programmes are indexed on our own servers so that they can be searched, whether or not AI is turned on.

You set how long conversations are kept, from not at all to 365 days after the last message; thirty days unless you choose otherwise. A change applies at once to the conversations already held, counted from each one's last message, so shortening the period clears any conversation whose last message is older than the new period. One-off drafting requests, such as a programme draft, are kept with your academy's records. Conversations are encrypted, and they are readable only by the person who had them — not by other staff, not by owners, and not by our staff.

AI can be wrong, and it must not be treated as a substitute for the professional judgement your learners are paying you for. You remain responsible for every decision recorded under your academy's name.

12. Acceptable use

You must not use Alethris to publish unlawful content; to infringe intellectual property; to impersonate a person or an institution; to issue credentials for competence that was not demonstrated and assessed; to sell or transfer credentials; to misdescribe a credential in breach of clause 8; to get around access controls, the separation between academies, or rate limits; to probe or attack the service; or to process personal data in breach of the law.

You must not put passwords, answer keys, private rubrics or confidential governance material into the instructions you give the AI assistants. Those instructions shape behaviour; they are not a security boundary and they are not secret.

Issuing credentials that misrepresent assessment is a material breach. The credibility of every credential on the platform depends on this clause, and we enforce it.

13. Data protection

Who is responsible. For the personal data your academy collects and records — about applicants, learners and your own staff in their work for you — you are the controller, and we process it for you as your processor. For each person's Alethris account, and for keeping credentials verifiable, we are the controller, as the Privacy Notices describe.

What we commit to as your processor. We will:

• process your academy's personal data only to provide Alethris to you, on your instructions — which are these Terms and what you and your staff do in the product, including an Owner allowing a support session as clause 14 describes — unless the law requires otherwise, in which case we will tell you unless the law forbids that;
• make sure everyone who processes it for us is bound to keep it confidential;
• protect it with the measures described in clause 14 and in the Privacy Notice for Academies;
• use only the providers listed in the Privacy Notice for Academies, under written terms that protect the data at least as well as these, and tell you at least thirty days before adding or replacing one, so that you can object;
• help you answer requests from the people concerned — mostly through the self-service tools the Privacy Notice for Academies describes — and with any impact assessment or consultation with the Nigeria Data Protection Commission that concerns our processing;
• tell you without undue delay, and within forty-eight hours of becoming aware of it, of any breach of security affecting your academy's personal data, with what we know and what we are doing about it;
• transfer it out of Nigeria only as the Privacy Notice for Academies describes;
• when you close your academy, delete it as clause 16 describes, except what that clause says we keep and what the law requires us to keep; and
• give you the information you reasonably need to show that these commitments are met, and allow audits the law requires, on reasonable notice and at your cost.

What you commit to. You will have a lawful basis for everything you ask and record about people, tell them what you collect and why, ask only for what you need, and register with the Nigeria Data Protection Commission where the law requires you to.

14. Security and our access to your academy

Your records are kept apart from every other academy's by the database itself, not only by our code, and every request is checked against your academy's current state rather than against a cached decision.

Our staff work through named roles, and none of them can see everything. They cannot sign in as one of your members or learn their password, and they cannot change an admission, enrolment, assessment, completion or credential decision. Looking up a person's details needs a recorded reason and a re-entered password, and looking at a summary of their records at your academy also needs an open support case; both are written to registers that cannot be edited or deleted. Outside a support session, no staff role can see your learners' submissions, the feedback on them, your private notes or the content of notifications, and none can ever see AI conversations or outputs.

Support sessions. To sort out a problem raised in a support case, a support operator may ask to see your academy as one of your members sees it. A session enters your academy only when an Owner allows it — by switching on "Let Support look without asking", which covers cases your academy or its members raise, or by allowing a request with their password — and while the member allows it too. A session can only view, unless changes were allowed. When the fix is in your academy's setup — its settings, courses, cohorts or templates — the operator may ask to make that change as the member, for at most 24 hours; an Owner and the member must both allow it each time, and the switch never covers it. Such a change is made through the product as the member would make it, is yours as if they had made it, and shows in your audit log as made by Alethris Support as that member. Whatever was allowed, a session cannot send, pay, publish, decide or accept anything in your academy's name, cannot change a price or a refund policy, and cannot change who belongs to it. It lasts at most an hour, your Owners are told when it starts and can end it, or withdraw the academy's permission, at any time, switching the setting off ends every session it allowed at once, and each one is listed in your settings with the changes it made and recorded in a register that cannot be edited or deleted.

What our staff can do to your academy:

• retry work that definitely failed — an undelivered email, a learner's place that was not set up, a certificate that did not render, a file that could not be inspected, a video that did not process — through the same paths the product uses;
• make your academy read-only, suspend it or restore it, as clause 15 describes;
• keep your academy open while a closure is pending, with a recorded reason and a re-entered password — for example, where the owner has lost access and asks us to;
• check the registration you give us against the Corporate Affairs Commission's register and record whether it matches, with a re-entered password, as clause 8 describes;
• bring your academy's roles back into line with Alethris's definitions of them, with a recorded reason;
• review your settlement account, credit the Alethris fee on a payment, adjust or refund AI credits, manage invoices, and set temporary limits or fees, each with a recorded reason and a re-entered password;
• set aside an upload or a message that cannot be completed, with a recorded reason, and replay messages a service could not process;
• record Enterprise agreements and move subscriptions between versions of a plan;
• open a support case that your owners and administrators can see, and send announcements to your owners or staff.

Governance actions our staff take on your academy — making it read-only, suspending or restoring it, keeping it open, and bringing its roles back into line with Alethris's definitions — appear in your academy's own audit log.

A small number of engineers who run the platform have technical access to its systems, and use it only to operate, repair and secure the service. The Privacy Notice for Academies describes how the personal data in your academy is handled.

15. Suspension, read-only and termination

We may make your academy read-only, or suspend it, where you are in material breach of these Terms — including by leaving charges unpaid — where the law requires it, or where continuing normal operation presents a risk to learners, to other academies or to the platform. Our security staff do this under a case, with a recorded reason and a re-entered password.

Where circumstances allow, we will tell you first and give you an opportunity to put things right. Where they do not — typically an active security or legal risk — we will act first and tell you promptly afterwards. Owners and administrators are told of the change unless we record a reason for not telling them.

Suspension deletes nothing, and restoration returns your academy to exactly the state it was in. It does not touch your financial history, your enrolments, your credentials or the history your learners hold, and credentials already issued remain verifiable, because a learner should not lose evidence of their competence because of a dispute between us and you. Suspension does not cancel your subscription.

You may end these Terms by cancelling your subscription, which takes effect at the end of the period you have paid for. Closing the academy outright is a separate step, described in clause 16.

We may end these Terms by notice if you materially breach them and do not put the breach right within thirty days of our telling you, or at once where the breach is one clause 12 calls material. Ending these Terms does not end your learners' accounts, their Skills Passports or the verifiability of the credentials you issued.

16. Closing your academy: what you can take out, and what we keep

You can close your academy yourself, from its Profile settings. Only an owner can, and only with their password.

Two things must be settled first, and the page names them rather than counting them: a paid subscription that renews each month, or whose last renewal failed, must be set to end, and any cohort still teaching — one with learners enrolled or places awaiting payment — must finish. An Enterprise agreement holds a closure back until the date it is paid through, because its term is the one agreed with us and it cannot be cancelled from the Billing page. Self-paced enrolments do not hold a closure back: their learners keep their records, their work and their credentials. Nor does a free trial: closing the academy sets it to end on the date it was due to, and nothing is charged; if the academy is kept before that date, the trial runs on as before. Nor does a subscription that will not renew: closing leaves it to run to the end of the period already paid for, and nothing more is charged for it. A plan paid for while the academy is closing, through a payment begun before it closed, runs to the end of the month paid for and is not renewed, whatever the academy's subscription was when it closed; if the academy is kept, the plan renews as before. An academy that is suspended cannot be closed.

Closing makes the academy read-only immediately, and every member is told by email and in Alethris Hub. The owner can keep the academy at any point in the thirty days that follow, and so can our support staff at the owner's request. After those thirty days, the following are removed and cannot be brought back:

• its homepage, its custom domain, pending invitations, its registration and any "Verified academy" mark, and the description, contact details, colours and logos on its profile;
• the files it uploaded — branding, homepage media, programme covers, lesson files and images, signatures for its certificates, and documents given to the assistants — and all of its videos;
• its certificate signatories, the contact details and notes it kept on its sponsors, and its notes on sponsorships, including why one was released;
• its announcements, notification templates, staff summaries and messages not yet sent;
• its assistant settings, instructions, indexed material, conversations and usage records;
• its analytics and its search index; and
• what its staff recorded privately about learners: risk policies, and the cases, flags, check-ins and interventions raised under them, and assessment drafts never sent.

What survives is not a matter of our choice. The academy's name and address are kept, and never given to anyone else. Its programmes and their lesson text, cohort staffing, applications and their answers, enrolments, handed-in work, assessment decisions, attendance and credentials stay, because the credentials it issued are built on them, and a credential that cannot be traced is worth nothing. Certificates already issued keep what was printed on them, and its sponsorships and their commitments stay, without the sponsors' contact details. Memberships and roles stay on record but grant nothing once the academy has closed. Notifications already delivered, support cases, and financial and billing records are kept, and so is the audit record of significant actions, which is kept for at least seven years.

Alethris does not yet have an academy-wide export. We would rather say so than describe a facility you would go looking for. What exists today is what the product itself offers: the learner, announcement and search lists can be downloaded as CSV files of the rows on screen, credential certificates can be downloaded one at a time, and everything else can be read in the product for as long as your academy can be read — which, once you have closed it, is thirty days. If an owner asks us in writing before those thirty days end, we will send the academy's learner, enrolment, assessment, attendance and payment records as files a spreadsheet can open, within thirty days of the request.

Your learners are a separate matter. Each of them can take a copy of their own data whenever they want, without asking you or us, and your owners and administrators are told when one does. That copy is theirs, not yours: it holds nothing about your academy's fees, your share of a payment, or what your staff wrote about them.

Learner-owned data does not leave with you. Accounts, Skills Passports and issued credentials belong to the learner and to the platform record, and they survive the closure of your academy and the end of these Terms.

17. Intellectual property

You own your programme content, curriculum, rubrics, branding and published pages, including what you publish from an assistant's draft. You grant us a licence to host, process, transmit and display that content strictly to operate the service for you and for your learners.

Learners own the work they submit. You obtain from your learners whatever rights you need to assess, store and — where relevant — display that work. Where a learner puts a project on their Skills Passport, that choice is theirs to make and to undo.

We own Alethris, including its software, design system, the Alethris Guides and its documentation. Nothing in these Terms transfers it. If you send us suggestions, we may use them without owing you anything.

18. Confidentiality

Each of us will keep confidential the other's non-public information that it receives under these Terms, use it only to perform them, and share it only with people who need it for that purpose and are bound to keep it confidential. This does not apply to information that is public through no fault of the receiver, that the receiver already had or developed independently, or that the law requires the receiver to disclose. The treatment of personal data is governed by clause 13 and the Privacy Notices.

19. Warranties and disclaimers

We will provide the service with reasonable skill and care, and substantially as the Alethris Guides describe it.

We do not warrant that the service will be uninterrupted or free of errors, that analytics and summaries will be complete at any given moment, that AI output will be accurate, or that third-party providers — including Paystack and our video, email, storage, hosting and AI providers — will be available.

Where a figure is out of date or unavailable, the product says so rather than presenting an unknown figure as zero. You should not treat a partial figure as a final one.

Apart from what these Terms state, and to the extent the law allows, we give no other warranty about the service, including any implied warranty that it is fit for a particular purpose.

20. Limitation of liability

Nothing in these Terms limits or excludes either party's liability for death or personal injury caused by negligence, for fraud, or for anything else that the law does not allow to be limited or excluded. Nor does anything limit your obligation to pay what you owe us, including any recovery owed to Alethris, or your obligations under clause 21.

Subject to that:

• neither party is liable to the other for loss of profit, revenue, business, goodwill or anticipated savings, or for any indirect or consequential loss;
• we are not liable for your decisions or your learners' — admissions, assessments, credentials, fees and refunds — or for the content you publish;
• we are not liable for a failure or delay caused by something outside our reasonable control, including the failure of a payment, hosting, email, video or AI provider, or of the public internet; and
• each party's total liability to the other arising out of or in connection with these Terms, in any period of twelve months, is limited to the total fees you paid us in the twelve months before the event that gave rise to the claim.

The platform never holds your learners' money, so these Terms do not make us responsible for it.

21. Indemnity

You will indemnify us against claims brought by third parties, and the losses and reasonable costs that follow from them, arising from content you publish, from credentials you issue, from your relationship with your learners — including your teaching, admissions, fees and refunds — from personal data you collect or instruct us to process without a lawful basis, and from your breach of clause 12.

We will tell you promptly of any claim, let you conduct its defence if you choose to, and give you the help you reasonably ask for at your cost. We will not settle a claim covered by this clause without your agreement, which you will not unreasonably withhold.

22. Changes to these Terms

We may change these Terms. We will publish each new version here with the date it takes effect and, where a change materially affects your rights, give you at least thirty days' notice. Where a change is to your material detriment, you may end these Terms without penalty before it takes effect, and we will refund the unused part of any period you have paid for.

Changes to plan prices take effect at your next renewal, never part-way through a period, as clause 5 describes.

23. Governing law and disputes

These Terms are governed by the laws of the Federal Republic of Nigeria.

A dispute is first raised in writing with the other party, and people with authority on each side will try to resolve it within thirty days. If they cannot, either party may refer it to arbitration under the Arbitration and Mediation Act 2023, before a single arbitrator, seated in Abuja and conducted in English. The award is final and binding.

Either party may ask a court for urgent interim relief, and either may go to court to recover a sum that is not disputed. Nothing in this clause limits the powers of the Nigeria Data Protection Commission or any other regulator.

24. General

These Terms, with the Privacy Notices and any Enterprise agreement, are the whole agreement between you and us about your academy; where an Enterprise agreement differs from these Terms, the agreement prevails. We may use the providers named in the Privacy Notice for Academies to deliver the service, and we remain responsible for them. We may transfer these Terms to a company that takes over Alethris, and will tell you if we do; you may not transfer them without our agreement. If a court finds part of these Terms unenforceable, the rest still applies. If either party does not enforce a term straight away, it can still enforce it later. Nothing in these Terms makes either party the other's partner or agent. We send notices to your academy's owners by email or through Alethris; you send notices to legal@alethris.com. Clauses 7, 13, 16, 17, 18, 20, 21 and 23 continue after these Terms end.

25. Contact

iSoterik Limited, No 22 Benin Street, Malali, Kaduna.

• General and legal: legal@alethris.com
• Support: support@alethris.com
• Privacy: privacy@alethris.com
• Security: security@alethris.com