Security · Vulnerability disclosure

Vulnerability Disclosure Policy

Last updated: November 21, 2026

We welcome reports from security researchers. If you find a vulnerability in Maglis, tell us privately and give us a fair chance to fix it, and we will work with you in good faith.

01How to report

Email security@maglis.ai. Please include:

  • the affected URL, endpoint or feature;
  • clear steps to reproduce, with a proof of concept where possible;
  • the impact you believe it has;
  • how you would like to be credited, if at all.

You can write to us in English or Arabic.

02In scope

  • maglis.ai and www.maglis.ai, including the signed-in application
  • docs.maglis.ai and trust.maglis.ai
  • Maglis APIs, share links and the Maglis MCP server

03Out of scope

  • Reports from automated scanners without a demonstrated impact
  • Missing security headers or cookie flags with no exploitable effect
  • Email configuration reports (SPF, DKIM, DMARC) without a working spoof
  • Self-XSS, clickjacking on pages without sensitive actions, and logout CSRF
  • Rate limiting on non-sensitive endpoints
  • Vulnerabilities in third-party services we use; please report those to the provider

04Rules of engagement

  • Test only against accounts you own or have explicit permission to use.
  • Do not access, change or delete other people's data. If you reach real customer data, stop and report it at once.
  • No denial-of-service, spam, social engineering or physical attacks.
  • Keep the details confidential until we have fixed the issue and agreed a disclosure date with you.

05What you can expect from us

  • An acknowledgement within 3 business days.
  • An initial assessment within 10 business days, and regular updates until the issue is resolved.
  • Credit in our acknowledgements once the fix is live, if you would like it.

06Safe harbour

If you act in good faith and follow this policy, we will consider your research authorised, will not pursue or support legal action against you, and will work with you to understand and fix the issue quickly. We do not currently run a paid bug bounty.