Clear boundaries, traceable reporting and a secure production path.

Production sign-in stays on the EURtracker domain.

Normal account creation, sign-in and invitation flows are routed through the verified production application instead of generated preview hostnames.

• Authenticated workspaces are protected at the application session boundary.
• Redirect destinations are validated to reduce unsafe redirect paths.
• Preview environments are separated from the normal production sign-in flow.
• New-account passwords require a stronger minimum length than earlier preview builds.

Generated text remains connected to reviewed project memory.

EURtracker does not treat raw notes as formal reporting automatically. Quick Updates are reviewed through Progress before they become reporting material.

• Partner and Project Report packs are generated from reviewed/submitted reporting material.
• Exports preserve source traceability to the underlying project updates used in the report.
• Incomplete coverage is surfaced as preliminary rather than silently filled with assumptions.
• Report export metadata can be retained as a handoff history without storing duplicate Word-file bytes.

Modern browser protections are enabled in production.

The application sends a hardened browser security policy intended to reduce common classes of web attack and accidental data exposure.

• Content Security Policy and frame restrictions.
• Strict Transport Security and content-type sniffing protection.
• Restrictive permissions for camera, microphone, geolocation and similar browser capabilities.
• Referrer and cross-origin policies designed for a private authenticated application.

EURtracker prepares reporting; it does not replace the programme portal.

EURtracker supports project management and narrative reporting workflows. Formal programme submission, programme authority approval and formal financial reporting remain in the relevant external systems.