--- title: "AI assurance and self-assessment · Avioverse" description: "Our self-assessment for your change process: Part-IS asset entry with CIA values and recovery targets, backup and restoration, IS risk assessment, EASA AI levels, EU AI Act and a supplier questionnaire." url: "https://avioverse.aero/ai-assurance" --- Avioverse Supplier self-assessment Edition 2026-10-23 v1.0 # Assess Avioverse before you rely on it. Our own assessment of Avioverse, ready for your change process: the Part-IS asset entry with CIA values and recovery targets, how backups work, an information-security risk assessment, the EASA AI level of each capability, our EU AI Act position and a supplier questionnaire. Every value is our recommendation for you to confirm. [Download assurance pack (.md)](https://avioverse.aero/ai-assurance/pack/avioverse-self-assessment-2026-10-23-v1.0.md) The downloadable assessment pack is in English. Both include the instructions for your AI assistant and all of our recommendations. Preview the complete assessment pack Complete assessment pack - Statement type Supplier self-assessment - CIA scale 1 to 5 - Risk method ICAO 5×5 matrix - Reviewed 2026-10-23 On this page ## How to use this assessment 1. ### 1. Choose your route Personal use, in your organisation, or full onboarding. Each route sets the values and steps that apply. 2. ### 2. Take our recommendations Copy the prompt or download the pack to prefill your asset register, risk register and change record. 3. ### 3. Confirm and accept Check each value against your own context and change any that don’t fit, with the reason. Your organisation records the decision. This is Avioverse’s own assessment, reviewed on 2026-10-23. It is not an EASA approval, and it cannot accept risk on your behalf: your organisation’s accountable people do that. ## Avioverse as a Part-IS asset Part-IS asks you to know which assets support your work, how much each one matters, and what could go wrong with it. You then rate each asset for confidentiality, integrity and availability, and assess its risks before you rely on it. A register holds many types of asset: information, software, **SaaS**, hardware, network and communications, people and facilities. Avioverse is one SaaS asset: you use it and we run it. ### Recommended register entry - Asset Avioverse with Metis: aviation workbench and AI assistant - Type SaaS (software as a service) - Supports The work you permit it for and the information used in it. Your organisation lists these. - Supplier AVIOVERSE LTD, Cyprus. Company registration number: HE 499684. Registered office: Agiou Efraim, 1A, Pera Chorio, 2572, Nicosia, Cyprus. Incorporated on 2026-10-12. - Data location Stored in the European Union. AI processing uses the providers and locations listed in our [privacy notice](https://avioverse.aero/legal/privacy). - Interfaces Web browser and email. Optional: browser extension, Telegram, calendar feed and scheduled reports. The extension can read and act on pages open in the user’s browser, including your own web systems, and always asks before it submits a form. - Owner Named by your organisation. - Review At each new edition of this assessment, and when one of your change triggers occurs. ### Recommended CIA values Rated from 1 (very low) to 5 (very high). If your scale differs, map these values to it. No value reaches 5, and each depends on how you use Avioverse. | Property | Personal use | In your organisation | Full onboarding | | --------------- | ------------ | -------------------- | --------------- | | Confidentiality | 2 Low | 3 Moderate | 4 High | | Integrity | 2 Low | 3 Moderate | 4 High | | Availability | 1 Very low | 2 Low | 3 Moderate | Safety relevance: indirect. Avioverse has no connection to aircraft or operational systems, and every effect on safety passes through a person’s decision. - Why: confidentiality Personal use covers public regulations and your own notes. In your organisation, internal material comes in, such as findings and draft assessments, so agree what may be uploaded. Full onboarding puts your records in Avioverse, including names in findings and reports. It stays below 5 because Avioverse is not meant for passenger, medical or security-classified information, and your upload rule keeps it out. - Why: integrity Personal outputs are working aids you check against the official source. In your organisation, an output enters your process only after a competent person checks it. Full onboarding makes Avioverse the record of what was found, decided and due, so its accuracy matters more. It stays below 5 because Avioverse has no connection to aircraft or operational systems: every effect passes through a person’s decision. - Why: availability With personal use and in your organisation, official sources and your existing systems remain the fallback, so an outage delays work but does not stop it. With full onboarding, the work waits until Avioverse is back. Our recovery targets below sit well inside the downtime you can tolerate, and your latest export keeps urgent work moving. What the values mean - 1 Very low: No noticeable effect on your work. - 2 Low: A minor inconvenience, easily put right. - 3 Moderate: A noticeable effect on your work, put right with some effort. - 4 High: A significant effect on a process or a compliance obligation. - 5 Very high: A direct, serious effect on safety or operations. Avioverse does not reach this level. ### Recovery targets Indicative values for your planning. They are targets, not a contractual service level. - RPO · Recovery point objective How much recent work could be lost About 5 minutes Records are backed up continuously. Uploaded files are backed up every hour, so up to about 1 hour of files. - RTO · Recovery time objective How soon Avioverse is back after a disaster 4 hours Recovery onto a clean server is rehearsed every month. Our latest rehearsal, in October 2026, restored the database and every file in under an hour. - MTD · Maximum tolerable downtime How long your work can do without Avioverse 72 + 72 hours Our suggestion for every way of using Avioverse: the occurrence-reporting deadlines. Our 4-hour recovery target sits well inside them. ## Backup and restoration Backups exist to bring the whole service back after a failure. This is how they work, in short. - Continuous and hourly Every change to your records is copied as it happens, with regular complete copies. Uploaded files and server settings are copied every hour. - Encrypted, in the EU, kept apart Backups are encrypted and stored in the European Union, apart from the working service. The keys to restore them are held away from the application servers. - Protected from deletion The working servers cannot delete or overwrite a backup, so a fault or an intruder on a server cannot remove them. - Fourteen days of history We can return the service to a chosen point within the last fourteen days. - Watched independently A separate monitor alerts us when a backup fails or stops reporting. - Rehearsed every month We restore the full service onto a clean server every month, and check records and files as a user sees them before we count it as passed. If the service needs recovery, an operator chooses the recovery point, restores records, files and settings together, and checks them before reopening the service. Backups recover the service; they are not your archive. Keep your own exports of records you must retain, using “Download my data”. [Read how backups and recovery work](https://avioverse.aero/docs/backups-and-recovery) ## IS risk assessment for adopting Avioverse A ready-made Part-IS information-security risk assessment for bringing Avioverse into your organisation (IS.I.OR.205 and .210, or IS.D.OR.205 and .210 under Regulation 2022/1645). Each risk is rated as it stands today, with what is already built into Avioverse. Take it into your risk register and adjust it to your operation. - Change assessed Introducing Avioverse for the work you name, in the way you choose to use it. - In scope Avioverse, the information you put into it, the outputs you rely on, your users’ accounts, and your web systems if you allow the browser extension. No risk is intolerable on either route. In your organisation: 8 acceptable, 3 tolerable. Full onboarding: 6 acceptable, 5 tolerable. In your organisation | Likelihood → | 5 | 4 | 3 | 2 | 1 | | -------------- | - | - | ------ | --------------------------- | - | | Catastrophic A | | | | | | | Hazardous B | | | | | | | Major C | | | | 2C: R2, R6, R10 | | | Minor D | | | | 2D: R1, R3, R4, R5, R7, R11 | | | Negligible E | | | 3E: R8 | 2E: R9 | | Full onboarding | Likelihood → | 5 | 4 | 3 | 2 | 1 | | -------------- | - | - | - | --------------------------- | - | | Catastrophic A | | | | | | | Hazardous B | | | | | | | Major C | | | | 2C: R2, R4, R6, R7, R10 | | | Minor D | | | | 2D: R1, R3, R5, R8, R9, R11 | | | Negligible E | | | | | | How the 5×5 matrix works - Rating: The risk as it stands with what is already in Avioverse and the checks your procedures already require. No further controls are planned, so each risk has one final value. - Severity: The worst credible effect on aviation safety. Every effect passes through a person’s decision, so no risk reaches catastrophic or hazardous. ### Likelihood - 5 Frequent: Likely to occur many times - 4 Occasional: Likely to occur sometimes - 3 Remote: Unlikely to occur, but possible - 2 Improbable: Very unlikely to occur - 1 Extremely improbable: Almost inconceivable that it will occur ### Severity - A Catastrophic: Aircraft or equipment destroyed; multiple deaths - B Hazardous: Large reduction in safety margins; serious injury; major equipment damage - C Major: Significant reduction in safety margins; serious incident; injury - D Minor: Nuisance; operating limitations; minor incident - E Negligible: Few consequences * Intolerable (5A, 5B, 5C, 4A, 4B, 3A): Not acceptable in the current circumstances. * Tolerable (all other cells): Acceptable once mitigated, with the decision recorded by the person who accepts it. * Acceptable (3E, 2D, 2E, 1B, 1C, 1D, 1E): Acceptable as it stands. ### Risk register 1. #### R1 · Confidential information leaves your control 2D In your organisation, acceptable 2D Full onboarding, acceptable Someone uploads internal material, such as findings, occurrence details or personal data, and it is then handled under Avioverse’s terms instead of your own contracts. Information is used in a way your policy does not allow. A leaked safety report can make people less willing to report. - Already in Avioverse Stored in the European Union. Your content is never used to train AI models. Every service provider is named in the privacy notice. Team content is visible only to Team members. - We recommend Agree what may be uploaded. Keep confidential occurrence reports and personal data out unless approved. Affects: Confidentiality · Owner: Information owner 2. #### R2 · A wrong answer is used in a decision 2C In your organisation, tolerable 2C Full onboarding, tolerable An answer, summary or extracted value is incomplete, out of date or wrong, and is used without a proper check. A wrong conclusion about applicability, a deadline or a finding enters your process. - Already in Avioverse Every answer shows its sources and is checked against them. The regulation library keeps each version with its dates, and ADs and SIBs are updated from EASA automatically. Every chat reminds users to check. - We recommend Name the outputs people may use and how each is checked. A competent person checks the official source before use. Affects: Integrity · Owner: Process owner 3. #### R3 · A document tries to steer the assistant 2D In your organisation, acceptable 2D Full onboarding, acceptable An uploaded file or web page contains hidden instructions meant to make the assistant do something else. An answer or a saved record departs from what the user asked. - Already in Avioverse Documents and web pages are read as content, never as instructions. Deleting, scheduling and submitting forms need the user’s approval. - We recommend Upload material from known sources, and read each approval request before accepting it. Affects: Integrity · Owner: Service owner 4. #### R4 · Someone gets into an account 2D In your organisation, acceptable 2C Full onboarding, tolerable A user’s email account is compromised, or someone keeps access they no longer need. Your information is read or changed without authority. - Already in Avioverse Sign-in is by one-time email code, Google or Microsoft, so there is no Avioverse password to steal. Every workspace request is checked on the server. Team owners and admins manage members and roles. - We recommend Use your organisation’s Google or Microsoft sign-in so your own security rules apply. Remove leavers on their last day. Affects: Confidentiality, integrity · Owner: Service owner 5. #### R5 · Information stays with people who leave 2D In your organisation, acceptable 2D Full onboarding, acceptable Organisation material sits in a personal workspace or in the assistant’s memory, and stays there when the person leaves. Your information remains outside your control. - Already in Avioverse Team content is kept apart from personal workspaces. The assistant’s memory belongs to each person and is never shared with the Team. - We recommend Keep organisation material in the Team workspace, and add Avioverse to your leaver steps. Affects: Confidentiality · Owner: Service owner 6. #### R6 · The browser extension reaches your other systems 2C In your organisation, tolerable 2C Full onboarding, tolerable The extension reads and works on pages open in the user’s browser, which can include your own web systems. Data from those systems reaches Avioverse, or an unintended entry is made in them. - Already in Avioverse The extension is optional and acts only when the user asks. Every form submission needs the user’s approval. - We recommend Decide whether the extension is allowed and, if it is, with which of your systems. Affects: Confidentiality, integrity · Owner: Service owner 7. #### R7 · A scheduled report is taken as full monitoring 2D In your organisation, acceptable 2C Full onboarding, tolerable A scheduled report fails, runs late or misses a change, and the silence is read as “nothing changed”. A new or revised requirement is not acted on in time. - Already in Avioverse Scheduled reports can only read and research. A run that cannot finish says so; it is never shown as checked. - We recommend Keep your official monitoring of ADs and regulatory changes, and treat reports as an extra pair of eyes. Affects: Integrity, availability · Owner: Process owner 8. #### R8 · Avioverse is unavailable when you need it 3E In your organisation, acceptable 2D Full onboarding, acceptable Avioverse is down or unreachable when the work needs it. Work is delayed. With full onboarding, a due item could wait until the service is back. - Already in Avioverse Continuous backups, a recovery rehearsal every month and a 4-hour recovery target. - We recommend Write down how urgent work continues without Avioverse, and keep a recent export where the fallback can reach it. Affects: Availability · Owner: Process owner 9. #### R9 · Records are lost or cannot be produced 2E In your organisation, acceptable 2D Full onboarding, acceptable Records kept in Avioverse are lost, deleted or cannot be produced when the authority asks, including after you stop using Avioverse. You cannot show what was found, decided or done. - Already in Avioverse Continuous, encrypted backups kept apart from the service. “Download my data” at any time. Account deletion waits 30 days in case you change your mind. - We recommend Decide which records are official, and export them to your records system on a schedule. Affects: Integrity, availability · Owner: Information owner 10. #### R10 · Checks become a formality 2C In your organisation, tolerable 2C Full onboarding, tolerable Under time pressure, or once people trust it, outputs are accepted without the agreed check. Outputs are relied on further than this assessment allows. - Already in Avioverse Sources are shown with every answer, and every chat reminds users to check. - We recommend Brief users on what Avioverse can and cannot do, and sample checked outputs at each review. Affects: Integrity · Owner: Process owner 11. #### R11 · A product change outdates this assessment 2D In your organisation, acceptable 2D Full onboarding, acceptable Avioverse changes a feature, AI provider or safeguard that this assessment relies on. The assessment no longer matches what you use. - Already in Avioverse Changes that affect this assessment are published as a new edition. - We recommend Name who watches for new editions, and reassess at each one. Affects: Confidentiality, integrity, availability · Owner: Service owner Personal use sits outside your organisation’s risk register; its checklist is in section 07. Add any risk specific to your own operation. ## EASA AI classification EASA’s AI levels describe who decides and who acts. We classify each capability by what Metis does and what the person keeps. | Capability | What Metis does | What the person does | Level | Why | | ----------------------------- | ---------------------------------------------------------------- | ------------------------------------------------------------------------------------ | -------- | ---------------------------------------------------------------------------------------- | | Ask and research | Finds, reads and summarises sources, and answers with citations. | Evaluates the answer and decides what to do with it. | 1A | It only gathers and analyses information. | | Assess and recommend | Compares requirements, drafts assessments and proposes options. | Chooses the option and makes the decision. | 1B | It assists the decision; the decision stays with the person. | | Save and update records | Creates or changes tasks, notes and records when asked. | Directs the change and can review or undo it. Deleting and scheduling need approval. | 2A | The person decides; Metis carries out the action under the person’s oversight. | | Scheduled watches and reports | Researches on a schedule and delivers a report. | Sets the watch and decides what to do with the report. | 1A or 1B | It runs unattended but can only read and research. 1B when the report recommends action. | | Browser actions | Reads and operates web pages in the user’s browser. | Gives the instruction and approves every form submission. | 2A | The person directs the task and approves each commitment; Metis performs the steps. | ### What the levels mean - 1A Human augmentation: The AI supports gathering and analysing information. - 1B Human cognitive assistance: The AI supports the person’s decision; the person decides. - 2A Human–AI cooperation: The AI carries out decisions and actions the person directs, under the person’s oversight. Levels 2B and 3 are not used: Metis never shares decision authority with the person or acts on its own authority. Avioverse is not a certified or approved aviation system. We use EASA’s levels because they are the recognised way to describe who decides and who acts. Concept Paper Issue 3 and NPA 2025-07 are proposals; we will revise this section when they are adopted. ## EU AI Act Metis is not a high-risk AI system under the EU AI Act. The Act’s Article 50 sets transparency duties for AI systems that talk to people or generate text: Avioverse is the provider of Metis, and your organisation is a deployer when it uses Metis. ### Article 50: what Avioverse does | Duty | What we do | Status | | ----------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------- | | 50(1) Tell people they are talking to an AI | A line under every chat box in the app and the browser extension, and once in the Telegram pairing message. | Done | | 50(1) Say it is an AI whenever asked | Metis answers truthfully today. An explicit instruction to Metis is still to be added. | Open | | 50(2) Machine-readable marks on AI text | Metis is built on AI models from specialist vendors, and we rely on their marking: an answer carries a vendor’s watermark where that vendor applies one. Every AI output is logged. | Position documented | | 50(2) Files Metis produces | Not marked. They are made on your instruction from your material, and their origin is recorded in Avioverse. | Position documented | | 50(4) AI summaries of ADs, SIBs and library documents | Each summary carries the Metis mark and the note “Summarised by AI.” | Done | | 50(4) Our articles and guides | A named author reviews each one and holds editorial responsibility. | Done | | 50(3) Emotion recognition or biometric categorisation | Not in the product. | Not applicable | | 50(5) Clear, at first interaction, accessible | Plain text, visible before the first message and read by screen readers. | Done | | Code of Practice on AI-generated content | Not signed. Our gap analysis against each of its required measures is in the next section. | Done | | Risk category | Not high-risk: Metis is not a safety component under Regulation (EU) 2018/1139 and not an Annex III use. | Position documented | ### What your organisation does - If you publish text Metis wrote on a matter of public interest, such as a safety notice to an open audience, without substantive human review, label it as AI-generated (50(4)). The Code of Practice’s EU “AI” icon, placed at the top of the text, is the recognised label. - The deepfake and emotion-recognition duties do not arise: Metis produces no images, audio or video, and does not recognise emotions. Code of Practice gap analysis The EU Code of Practice on transparency of AI-generated content (final, June 2026) sets out how to meet Article 50(2), (4) and (5). We have not signed it. The Commission expects non-signatories to show how they measure up, so here is our gap analysis against each of its required measures. ### Avioverse as provider of Metis (Section 1) | Code measure | Where we stand | Status | | -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- | | 1.1 Machine-readable marking of answers | Metis is built on AI models from specialist vendors, and we rely on their marking, as the Commission’s Article 50 guidelines allow. An answer carries a vendor’s watermark where that vendor applies one. | Via our model vendors | | 1.1 Very short text | AD and SIB summaries are 1–3 sentences, under the Code’s 200-token threshold, so no watermark is expected. | Not required | | 1.1 Files Metis produces | Files are made from your material: filled forms, tables, charts and format conversions only arrange or convert what you gave. Article 50(2) does not cover that (Article 50 guidelines, points 65 and 91–92). | Not required | | 1.2 Keep marks, offer no removal tools | Metis does not strip marks from your material, and we offer no tool that removes them. | Compliant | | 2 Detection | Each vendor that watermarks provides detection of its mark to authorities, researchers and media. Our records show which model wrote each answer. | Via our model vendors | | 3 Effective, reliable, robust, interoperable | Rests on each vendor’s marking and its testing, which a provider building on their models may rely on. | Via our model vendors | | 4 Compliance process | A documented compliance record, reviewed whenever models or features change. The operator is trained on Article 50, and we cooperate with market surveillance authorities. | Compliant | ### Avioverse as publisher of AI summaries and articles (Section 2) | Code measure | Where we stand | Status | | ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------- | | Scope | Section 2 covers deep fakes and text published to inform the public on matters of public interest. Metis makes no images, audio or video, and its answers reach only the person who asked. | Not applicable | | AI summaries in the library | Each AI summary of an AD, SIB or library document carries the Metis mark and the note “Summarised by AI.”, shown with the summary and read by screen readers. | Compliant | | 4 Human review of articles and guides | Each article and guide names its author, who reviews it and holds editorial responsibility. Name, role and contact are published. | Compliant | | 2 Internal process and corrections | Every place a label appears is recorded and checked when screens change. Report a missing or wrong label to privacy\@avioverse.aero and we fix it without delay. | Compliant | [How Avioverse uses AI](https://avioverse.aero/legal/ai-transparency) ## Management of change guide A step-by-step guide for each way of using Avioverse. Pick yours: each one starts from the CIA values and risk ratings above and lists what to put in place before use. ### Personal use You use Avioverse on your own account for your own work. No organisational change record is needed; this is your personal checklist. - CIA values Confidentiality 2 · Integrity 2 · Availability 1 - Risks R1, R2, R3 and R10 in section 04 apply to you as well. There is no organisational rating. #### Your checklist 1. Follow your employer’s policy on external software and AI tools. 2. Upload only material you are allowed to use. Ask before uploading your organisation’s documents. 3. Check each answer against the official source before you act on it. Metis shows the sources it used. 4. Treat outputs as your own working aids. They do not replace approved documents or your organisation’s procedures. - Sign-off: You. - Next route: Move to “In your organisation” when you upload your organisation’s material, when an output goes into your organisation’s process or records, or when colleagues join you in a Team workspace. ### In your organisation Your organisation uses Avioverse alongside its existing systems, which stay the official record. Typical uses: research, drafting, comparisons and working trackers. - CIA values Confidentiality 3 · Integrity 3 · Availability 2 - Risks R1–R11 in section 04, rated for “In your organisation”. #### Steps before use 1. Record the change: introduce Avioverse as a supporting tool for the work you name, and exclude official records and the only monitoring of ADs or regulatory changes. 2. Add the Avioverse asset entry to your register: Confidentiality 3, Integrity 3, Availability 2. 3. Name the service owner. 4. Take the recommendations from the risk assessment that fit your operation, give each an owner, and have the risks accepted. 5. Set the rule on what information may be uploaded. 6. Define who reviews outputs, the competence they need and the check they perform. 7. Brief users on what Avioverse is for, its limits and the upload rule. 8. Set up a Team workspace and assign roles. 9. Decide whether the browser extension is permitted, and for which of your systems. 10. Add Avioverse to your leaver steps: remove the person from the Team and ask them to remove organisation material from their personal account. 11. Set a review interval, such as twelve months or each new edition of this assessment. 12. If your exposition and procedures do not change, this is normally an internal change under your own change procedure. Confirm this against your exposition. - Sign-off: The person your change procedure names, normally the manager of the affected process. - Next route: Move to “Full onboarding” when Avioverse becomes the only place a record is kept, or when a procedure names it as the system to use. ### Full onboarding Avioverse takes over work you did in another system, such as a spreadsheet for findings, trackers or the audit programme. - CIA values Confidentiality 4 · Integrity 4 · Availability 3 - Risks R1–R11 in section 04, rated for “Full onboarding”. #### Steps before use 1. Complete every step for “In your organisation”, with the register entry at Confidentiality 4, Integrity 4, Availability 3. 2. Amend the procedures that name the old system, and check whether your approval’s change rules require the authority to be notified or to approve. 3. Decide which records in Avioverse are official. Export them to your records system on a schedule; our backups are for disaster recovery, not records retention. 4. Migrate the data, then reconcile it against the source: counts, open items and due dates. Sign off the reconciliation. 5. Run both systems in parallel for a set period and compare the results. 6. Set the downtime your work can tolerate, and write down how it continues meanwhile, using the latest export. 7. Confirm you can export everything you need in a usable format before you retire the old system. - Sign-off: The person your change procedure names for changes to procedures. ## Supplier self-assessment Our answers to the questions a supplier review normally asks. Contact us for anything not covered here. | Topic | Our answer | Status | | ---------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | | Company | AVIOVERSE LTD, Cyprus. Company registration number: HE 499684. Registered office: Agiou Efraim, 1A, Pera Chorio, 2572, Nicosia, Cyprus. Incorporated on 2026-10-12. | In place | | Hosting and storage | Servers, database, files and backups are in the European Union. | In place | | Service providers | Listed with their purpose, the data involved and their location in our [privacy notice](https://avioverse.aero/legal/privacy). | In place | | Training on your content | We do not use your content to train AI models. | In place | | Encryption in transit | All traffic to and from Avioverse uses HTTPS. | In place | | Sign-in | Email code, or Google or Microsoft sign-in. | In place | | Access control | Every workspace request is checked on the server. Team owners and admins manage members and roles. | In place | | Record history | Audits and forms keep a history of review decisions and changes, and forms and procedures record every change of who has access. Every AI generation is logged. | In place | | Backups | Records are backed up continuously and files every hour, encrypted and kept in the European Union apart from the service. Recovery is rehearsed every month. | In place | | Recovery targets | Indicative: about 5 minutes of records and 1 hour of files could be lost (RPO); service back within 4 hours (RTO). | In place | | Export | “Download my data” gives a machine-readable copy of your account at any time. | In place | | Deletion | Account deletion is self-serve, with 30 days to change your mind. Backup copies then expire on the schedule in our [privacy notice](https://avioverse.aero/legal/privacy). | In place | | Human approval and answer checks | Deleting, scheduling and submitting forms in the browser need your approval. Answers show their sources and are checked against them. | In place | | Security contact and breach notice | Report security issues to security\@avioverse.aero. We notify affected customers of personal-data breaches as the GDPR requires. | In place | | Security testing | Dependencies are checked for known vulnerabilities on every push. No external penetration test yet. | Partial | | Change notices | Changes that affect this assessment are published as new editions. | In place | | EU AI Act | We are the provider of Metis. See our EU AI Act position. | In place | ## Edition, sources and contact 1. ### 2026-10-23 · v1.0 Initial edition. Reassess when you change how you use Avioverse, when we publish a new edition, or after a relevant incident. Keep the edition you assessed with your change record; once Avioverse is in production, each new edition is listed here with what changed. Sources - [EASA Part-IS Easy Access Rules](https://www.easa.europa.eu/en/document-library/easy-access-rules/online-publications/easy-access-rules-information-security?erules-id=ERULES-1963177438-19915) · Regulations (EU) 2023/203 and 2022/1645 with AMC/GM - [EASA risk-management FAQs](https://www.easa.europa.eu/en/the-agency/faqs/risk-management) · Authority guidance - ICAO Doc 9859 Safety Management Manual, 4th edition · Source of the 5×5 risk matrix - [EASA AI Concept Paper, Issue 2](https://www.easa.europa.eu/en/document-library/general-publications/easa-artificial-intelligence-concept-paper-issue-2) · Published guidance, 2024 - [EASA AI Concept Paper, proposed Issue 3](https://www.easa.europa.eu/en/document-library/general-publications/easa-artificial-intelligence-concept-paper-proposed-issue-3) · Proposal, 2026 - [NPA 2025-07: AI trustworthiness](https://www.easa.europa.eu/en/document-library/notices-of-proposed-amendment/npa-2025-07) · Regulatory proposal - [EU Artificial Intelligence Act](https://eur-lex.europa.eu/eli/reg/2024/1689/oj) · Regulation (EU) 2024/1689 - [Commission guidelines on Article 50 transparency obligations](https://digital-strategy.ec.europa.eu/en/policies/guidelines-ai-transparency-obligations) · Adopted 2026 - [Code of Practice on transparency of AI-generated content](https://digital-strategy.ec.europa.eu/en/policies/code-practice-ai-generated-content) · Final, June 2026; not signed by Avioverse Need more evidence for your review? [Contact Avioverse](https://avioverse.aero/contact) [Explore what Metis can do](https://avioverse.aero/agent)