Requirements, supported by evidence.

This website presents our services and provides a direct way to discuss a project. Vedetta is a product in development: its demonstration uses fictional information and does not perform real screening or accept client records.

For each commission, we agree on the users, deliverables and acceptance criteria before building. Reviews include normal use, mistakes and interrupted actions, so that a polished demonstration is not the only measure of readiness.

The Blaze website runs on Monaco Telecom infrastructure. Its enquiry messages use the existing Cloudflare email services and Google Workspace mailbox; the privacy notice explains how those enquiries are handled.

For a client application, hosting is one part of the operating plan. Access rights, document storage, service providers, backups and the people responsible for recovery must also be defined for that project.

Encryption protects information only when its keys, access rules and recovery process are handled together. A delivery plan should specify how important information is restored, who can perform that operation and how it is tested.

For systems holding sensitive records over long periods, we also assess changes in cryptographic standards and the ability to replace algorithms. Comprehensive protection against quantum threats remains a requirement under evaluation for Vedetta, not an achieved product claim.

This site loads its fonts locally and uses no advertising trackers, Google Analytics or tag manager. The contact form asks for consent to handle the enquiry and does not subscribe the visitor to a mailing list.

The information needed for a customer project is defined by its purpose. A public presentation, an enquiry and a confidential client workspace need different access and handling rules; we plan those boundaries as part of the service.

We design toward WCAG 2.2 level AA, with attention to readable text, keyboard navigation, focus, zoom and mobile controls. Automated page checks complement hands-on use; they do not replace a full accessibility audit.

Loading speed and layout stability are checked on representative pages and devices. Performance budgets help identify regressions during delivery, with results tied to the version and test conditions rather than a single score used as a universal promise.

Clear types, automated tests and versioned changes help keep software understandable as requirements evolve. The handover should explain how to operate the service, make a change and recover from a failed release.

When a tool supports due diligence, calculations and AI can help prepare an examination. The responsible professional keeps the decision, with the evidence, exceptions and reasons needed to explain it.

Your browser makes a HEAD request to this page. These values describe that response only: they establish neither data hosting nor the security of the entire service.

Reading response headers…

Content-Security-Policy

Defines permitted origins for certain resources, according to the received directives.

Strict-Transport-Security

Communicates an HTTPS access policy with a stated duration and scope.

X-Frame-Options

Indicates whether the page may be embedded in a frame.

X-Content-Type-Options

Asks the browser to respect the declared content type in the applicable cases.

Referrer-Policy

Controls address information sent during navigation or a request.

Permissions-Policy

Defines the browser capabilities the page may access.

• State the scope of the evidence

  Tie results to a version and test conditions, without turning a partial check into a general guarantee.

• Validate processing before real cases

  Document destinations, participants and required authorisations; a hosting choice is not sufficient on its own.

• Keep the decision human

  Due-diligence tools support examination. They confer no compliance status or approval by an authority.