Trust centre

Everything Xovris can fix, and every control you keep

Your data and AI trainingWhat each connection fixes

xovris.ai18 November 2026, 23:05:28 UTC
What this release hands you666 open-source packages, each named with its licenceBill of materials

Every check of xovris.ai is fine, read from outside

  1. Addressfine
  2. HTTPSfine
  3. Page from outsidefine
  4. Certificatefine
  5. Security headersfine
  6. Registrationfine
  7. DNSfine
  8. DNSSECfine
  9. Email protectionfine
  10. Certificate rulesfine
  11. Lookalike addressesfine

Reading Xovris’s own controls

xovris.ai, as it stood on 18 November at 23:05 UTC

Four facts to decide on before you connect anything. Each opens to say more.

xovris.ai, checked from outside And from your own browser, as you look

Whether xovris.ai is working right now, from outside and in your own browser.

Checked from outside and from your browser

Xovris checks xovris.ai from outside, the way a visitor reaches it. Last checked 18 November 2026 at 23:05 UTC.

The same checks, run by your browser against xovris.ai while you read this.

  • AddressFrom outside Fine104.21.72.44Your browser Checking
  • Secure connection (HTTPS)From outside FineYour browser Checking
  • Page from outsideFrom outside FineYour browser checked from outside only
  • CertificateFrom outside FineWE1Your browser checked from outside only
  • Security headersFrom outside FineA+Your browser checked from outside only
  • RegistrationFrom outside Fine2028-10-01Your browser Checking
  • Address book (DNS)From outside Fineben.ns.cloudflare.comYour browser Checking
  • Signed address book (DNSSEC)From outside FineYour browser Checking
  • Email protectionFrom outside FineMicrosoft 365Your browser Checking
  • Certificate rulesFrom outside Finecomodoca.comYour browser Checking
  • Lookalike addressesFrom outside Finexovis.aiYour browser checked from outside only

What this page asked of your browser

Measured as it opened.

Your browser, before it could draw this page

requests
–
KB transferred
–
third parties
–

The build, counting this page’s files

files
–
KB compressed
–
  • – page
  • – style sheets
  • – scripts
  • – fonts
  • – other files

Security headers on this response

  • strict-transport-security Checking
  • content-security-policy Checking
  • x-content-type-options Checking
  • referrer-policy Checking
  • permissions-policy Checking

What Xovris did on your systems

Every action is in your own account’s audit log. Nothing across customers is published.

Live

Every action Xovris takes on your systems – what it read, what it changed and how it can be undone – is in your own account, in its activity and audit log, for you and the people you choose. What Xovris does across its customers is never published.

Xovris right now

Each part of the service, read live.

Reading the live record…

Subscribe to updates

How deep Xovris goes and what it puts right in each

From the page your visitors see down to the networks and devices behind it. Each layer shows what Xovris fixes there and whether it is ready today.

  1. Websites and pages

    Pages that fail, slow down or go offline – found from outside, fixed and proven for every visitor.

    See it working
  2. Domains and DNS

    Changed or tampered records put back to their last verified version, with expiry and renewal watched.

    See it working
  3. Email and sender trust

    Who sends email as you, and the exact records that stop anyone else from doing it.

    See it working
  4. Apps and code

    Errors traced to the release that caused them, and the fix delivered as a change you review.

    See it working
  5. Security

    Certificates, DNSSEC and tampering caught early and put right.

    See it working
  6. Networks

    Office and home networks watched, and a fault traced to the device behind it.

    See it working
  7. Devices

    The laptops, phones and machines a business or a family relies on, kept healthy.

    See it working

Every repair is tested before and after – and guaranteed proved, or nothing is charged

Four steps, each proven before the next.

  1. Reproduced first Your own failing outcome is reproduced before anything changes.

  2. Fixed within what you allow Only the access you granted, with every step recorded.

  3. Proven after Re-run after the fix with the checks around it – the same test that failed must now pass.

  4. Paid when it passes You pay nothing for a fix until its after-test passes.

If an after-test fails, the change is put back exactly as it was and the next approach starts. The issue stays open and visibly progressing until a fix is proven.

The only limits: law, safety and consent

Xovris goes as deep as your systems go. These three are the only things that stop it, and each is named when it applies.

  • Law

    Xovris acts only on systems you own or are allowed to manage, and where the law says a person must decide, a person decides.

  • Safety

    A change that could harm people, data or money waits for a person – and anything that does not hold is put back.

  • Consent

    Nothing changes without the access you granted, and you can take that access back at any time.

Your data is never used to train our AI

No. Your data is never used to train AI – not Xovris’s own AI and not any AI company’s. Your systems, files, logs and settings stay yours, and nothing of yours ever reaches another customer.

  • Never used to train any AI

    Not Xovris’s own AI and not any AI company’s. There is no setting that turns it on, because it is never done.

  • Your memory serves only you

    Xovris remembers your setup only to help you. You can see everything it holds and correct anything it has wrong.

  • Pause it at any time

    While paused, Xovris remembers nothing new about your workspace. What it already knows is still used to help you.

  • Delete anything, with a receipt

    Delete a fact and Xovris removes it everywhere it could have been kept, checks each place again and gives you a signed receipt. Encrypted backups are gone within 35 days – Xovris reads every backup it holds and removes any that would keep the fact past the date on the receipt.

See and change it on your Memory page

What each connection lets Xovris fix before anyone connects

Each provider in turn: the fixes it unlocks first, then the exact access its own consent screen asks for and how to take it back – read access shown apart from change.

GitHubWhat Xovris can change in GitHub

What Xovris can read in GitHub

  • See repository names To let you pick the one repository the setup change goes into.
  • Read files in chosen repositories To read the package manifests and the files that start your app - nothing else.
  • Read check results on that pull request To tell you whether your own checks passed on the setup change.

What Xovris can change in GitHub

  • Commit to a setup branch in chosen repositories To commit the setup change to a new branch. Nothing is ever pushed to your default branch.
  • Open the setup pull request To open one pull request whose description lists every change.
  • Xovris keeps its key as an encrypted Actions secret in the chosen repository So your CI sends events with a key GitHub encrypts - it is never written in a file, and Xovris never reads it back.

To take it back: Uninstall the Xovris GitHub App from the repository; closing the pull request also deletes its branch.

VercelWhat Xovris can change in Vercel

What Xovris can read in Vercel

  • See your projects and deployments To map each deployment to its environment and release.

What Xovris can change in Vercel

  • Write environment variables To write the Xovris variables into the projects you choose, then read them back.
  • Manage the Xovris resource Vercel holds To keep the integration resource Vercel shows you in step with Xovris.

To take it back: Uninstall the integration in Vercel: Xovris deletes only the variables it added, revokes every key it issued and reads both back.

Cloudflare DNSWhat Xovris can change in Cloudflare DNS

What Xovris can read in Cloudflare DNS

  • See your zones and their settings To find the zone you chose and confirm its name servers.
  • Read DNS records To keep every verified version of your records, so a change can be explained and undone.

What Xovris can change in Cloudflare DNS

  • Change DNS records Only if you allow repairs: to put a changed record back to its last verified version under your standing policy.

To take it back: Do it yourself instead: revoke the Xovris grant in your Cloudflare profile; Xovris notices the revocation and stops offering repairs.

SlackWhat Xovris can change in Slack

What Xovris can read in Slack

  • See public channel names To let you pick a channel by name.
  • See private channels the app is in To let you pick a private channel the app was invited to.
  • See who people are, to mention the right person To mention the person who owns the alert.
  • Match members by email address To match your Xovris members to their Slack accounts.
  • Read messages in public channels the app is in To find an alert's own thread again after a restart, so an update is never posted twice or lost.
  • Read messages in private channels the app is in The same thread check, in a private channel you invited the app to.

What Xovris can change in Slack

  • Post alerts in channels the app is in To post alerts and their updates in the channel you choose.
  • Join public channels To join the public channel you picked, so you never have to invite the app yourself.

To take it back: Remove the Xovris app from your Slack workspace; Xovris reads the revocation and falls back to email.

Connections not listed here – the SDKs, OpenTelemetry and the coding-agent server – send data to Xovris and get no access to your systems at all.

Certifications each with its evidence

No third-party certificate is held yet - SOC 2 Type II, ISO/IEC 27001 and ISO/IEC 42001 each show here with their date once earned. These controls run today, each with its proof on this page.

Your data, and Xovris where it lives and who touches it

3 stores, each with where it is kept.

Where your data lives

Your data lives in the EU (Netherlands and Germany) site, chosen when you sign up.

  • Your account, checks, incidents and changes: the Netherlands
  • Error events and check results: the Netherlands
  • The history of each repair while it runs: Germany

Your data stays in the site you choose. Moving it later means exporting it and importing it into another site.

AI governance

  • What Xovris remembers about your setup is yours to see, correct, pause and delete.
  • A person approves every change unless you set a standing policy for that kind of change.
  • Anything written by Xovris is labelled as written by Xovris.
  • Nothing from one workspace is ever visible to another.

Sub-processors

Processing today

  • 4 AI companies – Understand and answer what a person asks Xovris, and write its explanations and proposed fixes (the United States and the providers’ own global networks; data from the UK and EU goes under the Data Privacy Framework or standard contractual clauses, as each provider’s terms set out, since 2 October 2026) None of them may train its models on anything Xovris sends – each provider’s own terms say so. Kept as long as each provider’s terms allow – at most 30 days where a period is stated.
  • Cloudflare, Inc. – Serves xovris.ai and keeps the sign-up list: your email address, the website you entered, when you agreed, and a one-way hash of your network address that limits repeat sign-ups (stored in Western Europe; pages served from the Cloudflare location nearest you, since 1 October 2026)
  • Google LLC (Chrome UX Report and PageSpeed Insights) – Measures the website address you give the speed test - the address only, nothing about you (Google’s global network, since 2 October 2026)
  • Google Cloud EMEA Limited – Runs the Xovris service, its workers and its database, including the answers the helper on xovris.ai gives (the Netherlands (europe-west4), since 2 October 2026)

Since accounts opened

  • 2 AI companies – Understand and answer what a person asks Xovris, and write its explanations and proposed fixes (the United States and the providers’ own global networks; data from the UK and EU goes under the Data Privacy Framework or standard contractual clauses, as each provider’s terms set out) None of them may train its models on anything Xovris sends – each provider’s own terms say so. Kept only as each provider’s terms allow.
  • Amazon Web Services EMEA SARL (Amazon SES) – Sends alert and account emails (the European Union (Ireland))
  • Stripe Payments Europe, Limited – Takes payments and keeps invoices (the European Union (Ireland))
  • ClickHouse, Inc. (ClickHouse Cloud) – Stores the events, logs and check results Xovris reads for you (the European Union)
  • Temporal Technologies, Inc. (Temporal Cloud) – Keeps the history of every step of each repair and investigation while it runs, so a run survives a restart and is never repeated (the European Union (Germany, Frankfurt))

Sent to each of them: the part of a problem a step needs - an error message, a few log lines, a setting before and after a change - with passwords, keys and card numbers removed and email addresses replaced; and the question a visitor types to the helper on xovris.ai.

The companies whose AI models answer for Xovris are listed by kind, with where they process, what is sent to them, the terms that forbid them to train on what they receive and how long they keep it. The data processing agreement’s annex names each one, and any new one is added there before it receives anything.

Report a vulnerability and how it is answered

Write to support@xovris.ai with “Security” in the subject. Please do not test against other customers' data or degrade the service.

What to send, and what happens next

If it is being exploited now, put “Exploited” in the subject as well. Those reports are handled first, and an actively exploited vulnerability in Xovris is reported to ENISA within 24 hours, with an update within 72 hours and a final report, as the Cyber Resilience Act requires.

  • What you found and where
  • How to reproduce it, each step in order
  • What an attacker could do with it

Accessibility

Xovris is built to WCAG 2.2 level AA.

Not yet independently audited; the result will be published here with its date.

Read the accessibility statement, with the European Accessibility Act

Documents for your review

Every document a security or procurement review asks for that Xovris publishes, in each form it comes in. Nothing is listed that Xovris does not hold.

For procurement

Statements machines read

This release

Start your security review

One message to Xovris’s security mailbox starts it: say who you are and what your review covers, and the reply sends what you need from the documents here, with answers to your questionnaire.

Questions a security review asks

Each answered in a sentence, with the way to the part of this page that proves it.

Does Xovris hold SOC 2 or ISO 27001?
Not yet. SOC 2 Type II, ISO/IEC 27001 and ISO/IEC 42001 are each listed with where they stand, and none is claimed before its independent audit. The proof
Is my data used to train AI?
No. Nothing you connect is ever used to train a model. The proof
Where is my data kept?
Places your data is kept: 3, each named with its country and what it keeps. The proof
Who else handles my data?
9 companies, each named with what it does, where and since when. The proof
What can Xovris read and change in my systems?
Only what each connection you make allows - what each one reads, what it may change, and how to take it back, written out one connection at a time. The proof
How do I report a vulnerability?
Xovris’s security mailbox takes the report and its reply says what happens next; what a report needs is set out, and security.txt gives the same to tools. The proof
How accessible is the site?
Not independently yet. The conformance report says where each criterion stands. The proof
Does the website track visitors?
No cookies, analytics or advertising - the cookies page has the details. The proof
Can I see, take or delete my data?
Yes, on the privacy page itself once you are signed in, or by writing to support. The proof

Every figure on this page is current – the status was last updated 18 November 2026 at 23:05 UTC, and your browser’s own figures were taken as you opened the page.

Words on this page, in plain English

Each technical word this page uses, said simply.

The open standard for app data (OpenTelemetry)
A free, widely used standard for collecting an app’s errors, timings and records and sending them to any monitoring service.

Ask Xovris

Open the full page