Authentication and session security
Authenticated areas are protected with Laravel-backed auth, secure session handling, and verified access paths for sensitive product actions.
This page describes the platform security posture, implemented controls, operational practices, and the direct contact path for responsible disclosure or privacy-related security questions.
Trust posture
Implemented, in progress, planned
No fake certifications, no invented uptime numbers, and no claims beyond what the product and operations can actually support today.
Fahrnex ist für Fahrzeugbetrieb, Abrechnungsklarheit und Datenschutzanforderungen in Deutschland ausgelegt.
Öffentliche Vertrauenselemente, Rechtstexte und Einwilligungssteuerung sind mit DSGVO-orientierter Transparenz formuliert.
Wir kommunizieren ehrlich, was schon live ist, was verbessert wird und was operativ noch weiter ausgebaut werden muss.
Dokumente, Erinnerungen, Ausgaben und Servicehistorie bleiben in einem strukturierten Arbeitsbereich statt in verstreuten Postfächern und Ordnern.
Authenticated areas are protected with Laravel-backed auth, secure session handling, and verified access paths for sensitive product actions.
Vehicle documents use private access flows, and selected connection credentials are stored with encrypted model casts.
Administrative changes and operational actions are recorded so support, finance, and system changes can be reviewed later.
Backups and recovery procedures are treated as an operational responsibility, but public customer-facing recovery documentation is still being expanded.
The platform already monitors operational health, while public status communication and reliability reporting remain on the roadmap.
Security and privacy questions can already be routed through direct contact channels while a fuller disclosure workflow is prepared.
Legal, privacy, and consent pages are part of the public product surface instead of hidden after sign-up.
Billing, admin, and stored documents are routed through authenticated and user-scoped endpoints.
Audit logs and operational history help make support and admin actions more accountable.
Public status visibility and customer-facing recovery communication are being expanded carefully rather than improvised.