Privacy, in plain language.

Kiln Atlas is a portfolio concept with working data flows. This page describes what the current implementation stores and where care is required.

Sample reservations

The booking journey asks for an invented name, an address on example.com, example.org or example.net, material details, notes and a selected sample time. On confirmation, those details are stored as a sample reservation in Lovable Cloud. They are available to the authenticated Kiln Atlas owner inside the private workbench.

Do not enter a real name, personal email address, confidential note or information about another person. The form validates the example-domain restriction in the browser and again on the server.

Private status links

A completed journey creates a long, unguessable bearer link. The database stores a hash of its private token. Anyone who receives the complete link can view that sample reservation’s status and details, so treat it like a password and do not share it. The status page is marked for search engines not to index and uses a no-referrer policy, but those controls do not replace careful link handling.

Browser storage

An unfinished booking draft is kept in session storage in the current tab and removed after submission or when that tab session ends. Ember keeps a random session identifier, its visible conversation history of up to 20 turns, and a hint flag in session storage. The owner sign-in session is maintained by the authentication service in browser storage.

Ember and DeepSeek

Your browser may send a bounded recent chat transcript to the server so the interface can operate, but only the current visitor question is forwarded to DeepSeek with trusted safety instructions and owner-published answers. Earlier user and assistant turns are not forwarded to the model. If a limit or provider call fails, Ember uses the published answers without a paid model call.

Questions and replies are not intentionally saved as a server-side chat transcript. Please do not put personal or confidential information into Ember.

Rate limits and platform data

The booking and Ember services derive privacy-preserving rate keys from request metadata. Ember’s paid-call budget uses a hashed network identifier; booking safeguards may also hash a network address selected from trusted request headers. Rate-limit rows store the hash, bucket and timestamps rather than the raw question or reply.

Lovable’s Visitor analytics is enabled for a published version of this app, and AI app context is enabled in project settings. Platform infrastructure, preview tooling and error reporting may process technical logs or usage information under Lovable’s own practices. This site does not claim zero tracking, a fixed deletion schedule or compliance certification.

No email or payment

Kiln Atlas does not send reservation emails and does not collect payment details. The concept has no physical service, appointment, firing, pickup or shipment. For questions about this project, use the Noerong credit and project context supplied where you encountered it.