SEADS: Organization Agreement
Version 0.15, published 2026-11-07.
1. The parties and acceptance
1.1 This agreement (the "Agreement") is between APIOU Company LTD., doing business as SEADS Technology, a single-member limited liability company registered in the State of Ohio, United States (Ohio entity no. 3932422) ("SEADS"), and the organization (company, school, public body, association or other legal person) named in the order form (the "Organization"). 1.2 Online acceptance. A person who creates an organization on SEADS, or accepts an invitation to one, attests, in their own name and on behalf of the Organization, that they are of full age and authorised to bind the Organization, stating their name, role, the Organization's legal name, its country and its registration number, if it has one (annex 2). Online electronic signature. The accept button becomes active only after the person has opened every document (the Agreement and its annexes, the order form, the attestation). They tick three boxes (they have authority to bind the Organization; they have read the terms; the order form is correct), type their full name and title in the signature box, and confirm with a code sent to their professional email address. Typing the name and confirming by code is the Organization's electronic signature. The acceptance is recorded once for all the Organization's products (see 1.4). 1.3 If a person is not authorised, or the Organization disputes their authority, SEADS may suspend access until the position is regularised; an attestation made without authority binds its author. 1.4 Evidence. For each acceptance SEADS keeps: the SEADS account that accepts, the information attested, the name and title typed in the signature box, the version of the text and of the order form accepted (with their fingerprint), the language, the authority statement, the code confirmation, and the date and time. A sealed record guarantees that this information has not been changed. SEADS does not keep the signer's IP address for this acceptance. SEADS emails a signed PDF copy (the texts accepted, the signature block and the record number) to the signer and the Organization's administrators, who can also download it in the platform. These records are evidence of acceptance unless proven otherwise. 1.5 Handwritten signature and negotiated agreement. An organization whose rules require a handwritten signature, or that negotiates its terms, contacts support@seads.io: SEADS treats the request as an exception, by a signed agreement that replaces all or part of this text and then prevails.
2. Purpose, products and documents
2.1 SEADS makes available to the Organization and its members the SEADS products named in the order form: SEADS Academy, SEADS AI, SEADS BUILD and the common services (SEADS Identity) (the "Products"), under the product annexes (annex 4). 2.2 The Agreement consists of, in order of priority in case of conflict: (1) the order form (annex 1) for commercial variables (products, period, free or price, caps, settings); (2) the data processing agreement (annex 3) for personal data; (3) the product annexes (annex 4); (4) this text; (5) the terms of use and privacy notices of each product, which govern use by each member and which each member accepts online. 2.3 Members. A "Member" is a person the Organization invites or authorises on a Product. The Organization ensures that each Member is of full age (18 or over), follows the rules of use and accepts the Product's terms. The Organization is responsible for use made by its Members under its account.
3. Term, free access and price
3.1 Access is open for the period in the order form, from its start date to its end date. 3.2 The order form says whether access is free or paid. Free: no purchase commitment, no exclusivity, no automatic renewal; SEADS may end it under article 11. Paid: the price, currency, frequency and payment method are those of the order form; failing that, those of the Product's plans page; renewal and non-payment follow the Product's terms. 3.3 The caps (use, resources, number of members) and settings (for example allowed AI models, retention periods) are those of the order form. SEADS applies them when the organization is created.
4. Service level
4.1 The Products are provided without any guarantee of availability, unless the order form gives a written commitment. Planned maintenance is announced in advance. 4.2 Support: by support@seads.io. The order form may provide for first-level support by the Organization (for example its trainers). SEADS names no support person and commits to no response time under this agreement.
5. The Organization's obligations
5.1 Appoint an administrator and a contact for incidents and data protection. 5.2 Inform its Members of the rules of use and the privacy notices before their first sign-in. 5.3 Put into the Products only data it has the right to use; not put personal or confidential data into them without authorisation; not put in sensitive data or data the law forbids. 5.4 Follow the acceptable use rules (annex 5) and the Product's terms; not redistribute SEADS content or another organization's work. 5.5 Keep the information attested in article 1.2 up to date and report any change of representative, name or registration. 5.6 Report any security incident without delay to the contact named in article 6.4.
6. SEADS's obligations
6.1 Run the Products with a professional's diligence and configure them according to the order form. 6.2 Give the Organization, before opening, the information sheet for each Product (operator, hosting, subprocessors, data, purposes, access, retention, deletion, export, incident contact, use of data for model training) and keep it up to date. 6.3 Comply with the data processing agreement (annex 3). 6.4 Contact for incidents and data protection questions: privacy@seads.io and security@seads.io. 6.5 SEADS may change a Product. It gives 30 days' notice of any change that substantially reduces what the Organization is entitled to under the order form.
7. Personal data
7.1 Roles. For Members' content (conversations, documents, code, answers, applications and their data), the Organization is the controller and SEADS is its processor, under the data processing agreement (annex 3). For the account and sign-in (SEADS Identity), billing and security logs, SEADS is the controller, under the products' privacy notices. 7.2 SEADS does not sell data, does not use it for advertising and does not use it to train AI models. 7.3 Hosting: servers of OVHcloud in Canada (Beauharnois) and in the United States (Oregon; uploaded files of SEADS AI in Virginia); mail on SEADS's own mail server in Canada (OVHcloud); encrypted backups in the European Union (Hetzner Online GmbH, Germany); the AI model providers indicated in the order form are in addition. Personal data of an Organization, and of its learners, educators and administrators, located outside Canada and the United States is therefore transferred to Canada and to the United States, on the safeguards in the data processing agreement (annex 3, section 6). Any formalities with the data protection authority of the Organization's country are for the Organization as controller, which carries them out at its own discretion; SEADS helps by supplying the necessary facts. 7.4 Data breach: SEADS notifies the Organization without undue delay and in any case within 48 hours of becoming aware. 7.5 Deletion: at the Organization's written request, SEADS erases a member's records in its organization within 5 business days (except what the law requires to be kept).
8. Intellectual property
8.1 SEADS keeps ownership of the Products, their content (courses, exercises, datasets, templates) and documentation. The Organization receives a limited, non-exclusive, non-transferable right of use for the period and the Members in the order form. 8.2 The Organization and its Members keep their rights in their content and work; they allow SEADS to store, run and display it as the Product requires. Reuse of work as an example or teaching material needs separate authorisation. 8.3 Any public communication mentioning the other party needs its prior approval.
9. Confidentiality
Each party keeps the other's non-public information confidential. Not confidential: public information, information already known or lawfully obtained from a third party, and what the law requires to be disclosed.
10. Liability
10.1 SEADS has an obligation of reasonable care. Free Products: SEADS is liable only for proven direct damage resulting from its fault, excluding any indirect damage (loss of revenue, opportunity or data not backed up by the Organization). Paid Products: SEADS's liability is limited to direct damage and does not exceed the sums paid by the Organization for the Product concerned in the 12 months before the event. 10.2 Nothing here excludes liability for wilful misconduct or gross negligence, or what the law does not allow to be excluded. 10.3 SEADS is not responsible for third-party tools or licences the Organization uses with the Products, or for the content of the Organization's own platforms.
11. Term and end
11.1 The Agreement takes effect on acceptance and lasts until the end of the order form's period, unless renewed. 11.2 Either party may end it on 30 days' written notice (email is enough). Either party may end it immediately for a serious breach not corrected within a reasonable time after notice, and SEADS may suspend access immediately for a security risk or unlawful use. 11.3 Continuation and export. At the end, the Organization may export its data for 30 days; where SEADS ends the Agreement for a reason other than breach or risk, the members of a session already begun may complete it. The data is then erased under annex 3 and the order form's periods.
12. Governing law and disputes
12.1 Organization established in an OHADA state: the Agreement is governed by the OHADA Uniform Acts as applicable in that state, and any dispute is settled by arbitration seated in Ouagadougou, in French, under rules compatible with OHADA and the Common Court of Justice and Arbitration. 12.2 Any other Organization: the Agreement is governed by the law of the State of Ohio (United States), without its conflict-of-law rules, and any dispute goes to the competent courts of that State. 12.3 The governing law is shown in the order form. Rights of consumers and data subjects that the law does not allow to be excluded remain applicable.
13. General
13.1 The Agreement is the whole agreement on its subject. SEADS may change this text on 30 days' notice; the Organization may refuse by ending the Agreement at no cost before the change takes effect. SEADS emails the administrators at the start of the 30 days and when the new version is published. During the notice period access continues and a banner invites an administrator to accept the new version; if no one has accepted when the period ends, the Organization's administration actions (for example inviting new members or changing settings) are blocked until an authorised person signs the new version; members keep using the Product and the Organization can still export its data. 13.2 Assignment: not without the other party's prior written agreement, except by SEADS to a company of the same group or to its successor, with notice. 13.3 Notices: by email, for SEADS to legal@seads.io and privacy@seads.io, for the Organization to the administrator's and signer's address. 13.4 Languages: the French and English versions are equally binding.
---
Annex 1: Order form
The order form is shown with this agreement and accepted with it.
Annex 2: Attestation of authority
The attestation is shown with this agreement; the person who accepts makes it in their own name and on behalf of the Organization.
Annex 3: Data processing agreement
1. Parties and scope
This agreement is between the Organization named in the order form (the "Customer", the controller) and APIOU Company LTD., doing business as SEADS Technology, a single-member limited liability company registered in the State of Ohio, United States ("SEADS", the processor). It forms part of the SEADS Organization Agreement accepted between the same parties and applies whenever SEADS processes personal data on the Customer's behalf through a product listed in annex 1. If this agreement and the Organization Agreement differ on data protection, this agreement prevails.
2. Instructions
SEADS processes Customer personal data only on the Customer's documented instructions: the Organization Agreement, this agreement, and the Customer's choices in the product and in the order form (for example retention settings and the AI providers it enables). If an instruction seems to break the law, SEADS tells the Customer. SEADS may process data otherwise only where the law requires it, and then tells the Customer first unless the law forbids it.
3. Confidentiality
Everyone at SEADS who can access Customer personal data is bound by confidentiality. Access is given only where the work needs it (annex 2).
4. Security
SEADS applies the technical and organizational measures in annex 2 and keeps them at least at that level for the duration of the agreement.
5. Subprocessors
The Customer authorizes the subprocessors listed for each product in annex 3. SEADS gives 30 days' notice before adding or replacing a subprocessor, by email to the organization's owner and an update of the list in the product. The Customer may object on reasonable data-protection grounds; if the parties cannot agree, the Customer may end the affected service. SEADS puts in place, with each subprocessor, data protection obligations no less protective than these, and stays responsible for them.
6. Hosting location and transfers
Customer personal data is stored on servers of OVHcloud in Canada (Beauharnois: SEADS AI, SEADS Academy, and SEADS's own mail server) and in the United States (Oregon: SEADS BUILD, Academy labs and the sign-in service; Virginia: files uploaded to SEADS AI), as annex 1 states per product. Encrypted off-host backups are held in the European Union (Hetzner Online GmbH, Germany). Because the hosting is outside the European Union, personal data of a Customer, and of its members, established or located in the European Union, the European Economic Area, the United Kingdom or Burkina Faso is transferred to Canada and to the United States. It also reaches the other subprocessors in annex 3 that are outside the Customer's country (for SEADS AI, the model providers the Customer enables), and only when they are used. Where the law requires a safeguard, SEADS relies on standard contractual clauses or an equivalent approved mechanism, and provides a copy on request. Any formalities with the data protection authority of the Customer's country (in Burkina Faso, the CIL) are for the Customer as controller, which carries them out at its own discretion; SEADS helps by supplying the necessary facts.
7. Helping the Customer
SEADS helps the Customer, through the product's functions and on request, to answer people's requests to exercise their rights (access, correction, deletion, restriction, objection, portability). It also helps with security, breach notification, impact assessments and prior consultation, as far as SEADS has the information. Erasure of one member at the Customer's written request is done within 5 business days (Academy and SEADS AI). Help beyond the product's functions is charged at a reasonable rate, quoted before the work starts.
8. Personal data breaches
SEADS notifies the Customer's administrator by email, without undue delay and in any case within 48 hours of becoming aware of a personal data breach affecting Customer personal data. The notice is sent by the owner of SEADS or by a person he names, and says what is known: what happened, the data and people concerned, the likely consequences and the measures taken, and is updated as the facts emerge. SEADS follows its written breach-notification procedure (first assessment within 4 hours, a decision on notifying within 24 hours). Contact: privacy@seads.io and security@seads.io.
9. End of processing
When the service ends, SEADS deletes Customer personal data, or returns it first if the Customer asks within 30 days after the end. Exceptions: copies the law requires SEADS to keep, and encrypted backups, which expire on their own schedule (annex 2) and are not restored except to recover the service. Periods are in annex 1 and the order form.
10. Audits
SEADS makes available the information needed to show it meets this agreement: this agreement, the list of subprocessors and a description of its security measures. The Customer may audit, or have an independent auditor audit, once a year, with 30 days' notice, at its own cost, under confidentiality. SEADS has no third-party certification today.
11. Liability and term
Liability under this agreement is that of article 10 of the Organization Agreement. This agreement lasts as long as SEADS processes Customer personal data.
12. Law
This agreement is governed by the law designated in article 12 of the Organization Agreement, and any dispute goes to the court or arbitration provided there.
---
Annex 1: Processing per product
| SEADS AI | SEADS Academy | SEADS BUILD | |
|---|---|---|---|
| Subject and purpose | provide the AI workspace: conversations, knowledge, images, assistants | provide courses, SQL labs, results, trainer review | host and run the Customer's applications |
| Data subjects | the Customer's members; people named in their content | members (learners, trainers, administrators) | users of the Customer's applications; people named in their content |
| Personal data | prompts, conversations, answers, uploaded documents and their indexes, images, member profiles | anonymous account reference (Academy receives no name or email); saved code and answers, run results, pass results and attempts; list label (a name or number typed by the administrator, if the Customer enters one); audit record of trainer reads; IP address | what the application stores: for its users, email, name and sign-in codes, plus whatever the application collects |
| Special categories | none intended; the Customer may upload any document | none | not allowed without written agreement (acceptable use rules) |
| Duration | conversations 30, 90, 180 or 365 days after the last message (180 by default, set in the order form); knowledge as long as the Customer keeps it; closed organization 30 days; usage 24 months; routing records 12 months; security and audit 24 months | single learner: 12 months after last activity; organization learner: all work erased 12 months after the end date the Customer sets (adjustable in the order form); audit records 12 months; sign-in sessions erased 7 days after they end; lab output 24 hours; run records 12 months | as long as the application exists; after non-payment 90 days archived, then erased |
| Location | Canada (OVHcloud, Beauharnois); uploaded files in the United States (Virginia); mail in Canada; backups in the European Union | Canada (OVHcloud, Beauharnois); labs in the United States (OVHcloud, Oregon); backups in the European Union | United States (OVHcloud, Oregon); backups in the European Union |
Annex 2: Security measures in place
| Area | Measure |
|---|---|
| Location | servers in Canada (OVHcloud, Beauharnois) and the United States (OVHcloud, Oregon; Virginia for uploaded files of SEADS AI); mail in Canada; encrypted off-host backups in the European Union (Germany) |
| Network | a firewall on every server; SSH only from two named machines, keys only, password login off |
| Access to production | only the owner of SEADS and the infrastructure operator, each with a personal key; connections logged; developers and support staff have no access to the production database |
| Staff tools | staff sign-in requires two-step authentication and is limited to staff groups |
| Staff view of content | no screen or interface of SEADS AI shows an administrator or SEADS support the text of a member's conversation; staff support sessions are time-limited, need a stated reason, are recorded and never return message content. Platform operators could technically access stored data |
| Separation | SEADS AI: logical separation (one shared database, an organization identifier on every record, the organization resolved on the server from the person's membership, never from the request), with tests; no database-level row security. SEADS Academy: per-organization separation enforced in the database by forced row-level security, with an application role that cannot alter the schema, bypass that security, or change or delete work and the audit record (append-only tables); this is the code's design, effective when the production database is created. SEADS BUILD: each application isolated, with its own user store and resource limits |
| Encryption | in transit by TLS. Off-host backups encrypted (Borg), keys kept off the servers. Live databases are not encrypted at rest on disk (provider's local disks, no disk encryption) |
| Backups | SEADS AI and SEADS BUILD: daily, off the host; 30 daily, 12 monthly, 3 yearly; restores tested. SEADS Academy: encrypted off-host backups kept 35 days at most, set up with the restore drill before opening |
| Payments | card numbers never reach SEADS servers |
| Staging | holds no copy of production customer data |
| Incidents | a suspected breach is handled before anything else |
Annex 3: Subprocessors
| Subprocessor | Service | Based in | Product |
|---|---|---|---|
| OVH US LLC, doing business as OVHcloud (Delaware, United States) | hosting | Canada (Beauharnois); United States (Oregon; Virginia for uploaded files of SEADS AI) | SEADS AI, SEADS Academy, SEADS BUILD |
| Hetzner Online GmbH | encrypted backups | Germany | SEADS AI, SEADS Academy, SEADS BUILD |
| SEADS BUILD (a SEADS service) | running Academy labs, without name or email | SEADS, United States (OVHcloud, Oregon) | SEADS Academy |
| SEADS mail server | sending applications' sign-in codes | SEADS, Canada (OVHcloud) | SEADS BUILD |
| OpenAI | AI models; transcription of voice messages (when voice is turned on) | United States | SEADS AI |
| Anthropic | AI models | United States | SEADS AI |
| Google (Gemini) | AI models | United States | SEADS AI |
| Mistral | AI models | France | SEADS AI |
| Black Forest Labs | image models | Germany | SEADS AI |
| DeepSeek | AI models | China | SEADS AI |
| Moonshot | AI models | China | SEADS AI |
Model providers receive data only for the models the Customer enables; the order form may limit the list. For an organization in the European Union, the European Economic Area, the United Kingdom, or with no country set, models from providers based in China are off by default; for any other organization they are on by default and the Customer may exclude them. SEADS Academy sends no data to any AI model provider. Payment providers (Stripe, PayDunya) receive billing data as SEADS's own processors, not the Customer's content. Let's Encrypt receives application addresses only.
Annex 4: Product annexes
4-A. SEADS Academy (edu.seads.io)
- What it is: a hands-on learning platform: courses, saved work, SQL labs, organizations, account deletion.
- Who: the Organization's learners, trainers and administrators; adults aged 18 or over. Trainers see saved work and results; each read of a learner's code is logged (kept 12 months). Administrators see progress and results, not code.
- What the Organization sets: list labels (left empty if the Organization wants name-free exports), the programme end date (it triggers erasure 12 months later; with no end date, nothing is erased automatically), lab caps per organization.
- What there is not: no AI tutor (no model provider receives Academy data); no grade or certificate issued by Academy in this version.
- Results: passed or not, per question, with number of attempts; append-only records, stamped by the database clock, with a cryptographic seal per record; export for trainers by hashed member code, without names (the Organization keeps the mapping between code and person).
- Deletion: by the learner ("Delete my saved work", account deletion) or, at the Organization's written request, by SEADS within 5 business days.
- Terms of use: Academy's learner terms and privacy notice (v1.7), accepted online by each learner.
- Use: labs run only code meant for the exercise (lab rules).
4-B. SEADS AI (ai.seads.io)
- What it is: an AI assistant: conversations, knowledge (the Organization's documents), images, assistants.
- Who: the Organization's members, adults aged 18 or over. The administrator manages members, allowed models, caps and retention; no screen or interface of SEADS AI shows an administrator or SEADS support the text of a member's conversation.
- What the Organization sets (order form): allowed models (choosing a list of models limits routing, fallback and targeted requests to those models); Knowledge on or off (the Knowledge feature indexes text with an OpenAI model whatever the model selection: turn it off if the Organization wants to limit providers); memory; usage cap per month per member; conversation retention: 30, 90, 180 or 365 days after the last message (180 by default).
- Training: SEADS does not use content to train models and does not sell it. Each model provider processes requests under its API terms; SEADS uses each provider's standard online terms.
- Export: no self-service export of conversations today; full copy on request to privacy@seads.io.
- Terms of use: SEADS AI's terms of use and privacy notice in force.
4-C. SEADS BUILD (seads.app)
- What it is: a platform to create and host applications from templates, at an address SEADS manages.
- Who: the Organization owns its applications and their content; the people who use those applications are its users, with no SEADS account; each application has its own user database, separate from the others and from SEADS's data; the Organization is responsible for the content and compliance of its applications toward its users.
- Plans and resources: Seed (14-day free trial), Sprout, Bloom, Harvest, Orchard (on request), as on the plans page; the plan and price are those of the order form. Archived for 90 days after non-payment, then erased; export possible during that time.
- Acceptable use: SEADS BUILD acceptable use rules; no special categories of data without written agreement.
- Terms of use: SEADS BUILD's terms of use in force.
Annex 5: Acceptable use
The Organization and its Members do not use the Products to: harm the security or operation of the Products or of third parties; access another organization's data without right; host or distribute unlawful content, phishing, malware, harassment or hate; mine cryptocurrency; send unsolicited bulk messages; get round caps; or for any use the law forbids or the Product's rules forbid (SEADS BUILD: SEADS BUILD acceptable use rules; SEADS Academy: lab rules; SEADS AI: terms of use). SEADS may suspend access for a serious breach.