Clavis Transaction Login

Clavis Transaction Login is a secure, field‑ready mobile app for recording employee check‑ins and check‑outs with clear UX, optional location stamping, and robust offline queuing. It pairs quick QR‑based setup with device‑derived UID mapping to your organization’s backend, ensuring accurate, auditable records with minimal friction. - Purpose - Streamlines on‑site access control, attendance tracking, and compliance logging - Designed for operational reliability: clear actions, resilient offline behavior, and informative error handling - Key Features - QR Setup: Scan a QR to configure the server API URL in seconds; or enter it manually - Clear Action Button: Always shows the next action (“Check In” vs “Check Out”) with matching color and icon - Secure Access: Uses Face ID/Touch ID when available; verification occurs on device and no biometric data is stored or transmitted - Location Stamp (Optional): Captures foreground location at the moment of check‑in/out to verify proximity; no background tracking - Offline Queue: If the network is unavailable, actions are queued and automatically sent when connectivity returns - Access Status: If the device isn’t authorized, an “Access Restricted” screen offers “Copy UID” and a controlled “Retry” (2‑minute cooldown) - Quick Recovery: From error screens you can “Change API” to reconfigure the server URL instantly - Reliability & UX - Haptics and smooth animations provide immediate feedback on actions - Cooldowns prevent accidental rapid repeats (5 minutes after a check‑in/out; 2 minutes on access retry) - Informative text clarifies status, last successful action time, and what happens next - Data & Privacy - Device UID: Derived via cryptographic hashing to avoid storing raw device identifiers on the server - Attendance Records: Direction (in/out), timestamp, and optional latitude/longitude (if permission granted at action time) - No Background Tracking: Location is foreground‑only for the specific transaction; continuous tracking is not used - Minimal Use of Permissions: Camera solely for QR setup; biometrics purely for local app access; location only at the moment of the action - Logs: Operational server logs may be retained for a limited period to troubleshoot and ensure security - Error Handling & Settings - “Connection Error” and “Access Restricted” screens provide actionable paths: “Settings”, “Change API”, “Copy UID”, “Retry” - Settings modal displays the current API URL and device UID; supports “Copy UID” and “Change API” for quick reconfiguration - Intended Use - For authorized employees/contractors to log entry/exit in facilities, sites, and workplaces - Integrates with your organization’s backend; requires an API URL to be configured - Notes - If location permission is denied, actions still complete without location - Production deployments should use HTTPS and follow your organization’s privacy and security policies