Privacy and cookies
DealerAxis is operated by John Kuczer trading as Foundry83. Contact john@foundry83.co.uk about this application. Your dealership controls the business and staff records it enters. Contact your administrator about those records.
How information is used
Account details and permissions provide secure access. Dealership performance records and uploaded files provide the reporting functions your organisation requests. Security logs support fraud prevention and troubleshooting. Hosting is provided through OpenAI Sites with Cloudflare D1 and R2 storage. Records are not removed by clearing cookies. Retention depends on the organisation’s instructions and applicable business record requirements; contact your administrator for the schedule that applies to your data.
Your information rights
You can request access, correction, deletion, restriction or portability where applicable, and object to processing based on legitimate interests. Contact your administrator or John. You may complain to the Information Commissioner’s Office. We may need to verify your identity before acting.
Sign-in storage
DealerAxis uses Clerk to authenticate staff and a first-party __Host-dealership-session cookie to connect the verified sign-in to authorised dealership access. It contains a random session reference, is HttpOnly and Secure, and uses SameSite=Strict. It is created after successful sign-in and expires within seven days, or earlier if the Clerk session expires. Server access also expires after three days of inactivity. Sign-out revokes the application session.
The legacy __Host-dealership-signin cookie is cleared during sign-in and sign-out; the current application does not issue it. Clerk’s __session cookie is used in authentication. Additional Clerk cookies and their configured lifetimes require verification against the live authentication service; they are not controlled by this notice. See Clerk privacy information. Clerk optional SDK telemetry is disabled in the application’s browser and server configuration.
Authentication and fraud prevention are essential to the service staff request. Refusing optional technologies must not disable them. No application advertising pixels or optional audience analytics have been added. Operational records, uploaded documents and audit logs are stored on the server, separately from browser cookies.