Privacy.

Your privacy choices

This page is information. Manage privacy choices opens the same controls as Privacy in the menu. Reading this page or opening the controls does not change your saved choice.

When you send a message

The contact form asks for your name, email address, message, and an optional service category. These are stored in the site’s database with a submission reference, timestamps, and inbox status so the site owner can read and manage your inquiry.

Submitting the form does not send an automatic email. Replies may be handled separately through email. You do not need an account or acceptance of optional embeds to send a message.

Contact messages stay in the inbox or archive until the site owner deletes them. Messages moved to trash are scheduled for deletion after 30 days; physical database cleanup may happen later.

Backup copies may remain after a message is deleted from the live database. Deleting a live message does not erase copies in existing backups.

Choices saved in your browser

Privacy choices use a cookie and browser storage. Color-theme preferences also use a cookie and browser storage; the theme cookie is shared across stuerman.me subdomains. These preferences are separate from demo-access and sign-in cookies.

Accepting optional content is specific to each site and purpose. Reject or Withdraw attempts to save rejection on stuerman.me and admin.stuerman.me and reports any unconfirmed step. Other open tabs may need to resume or reload. Withdrawal does not sign you out, clear provider-hosted accounts, or remove information already received by another service.

Demo access and interactions

Entering a valid demo code creates an access session with an eight-hour limit. A random token is stored in a secure browser cookie; the database stores its digest, the demo reference, and expiry. Codes and demo content are managed by the site owner.

Some demo interactions, including photo uploads in the shop mockup, are saved in your browser. Shared menu-board settings are saved on the server and available to other authorized sessions for that demo. Use sample information in mockups.

Sign-in and other websites

Owner administration uses Clerk for authentication. Its sign-in features make requests to Clerk and use authentication cookies. Public pages and customer demo-code entry do not require a Clerk account.

External project previews stay unloaded until you accept optional content. Once loaded, the embedded website receives browser requests and may use its own cookies or services. Linked and embedded sites, including stuerman.art, have separate privacy choices and data practices.

Security and server records

Address-derived counters limit repeated contact submissions and demo-code guesses. Separately, web-server access and error logs can include IP addresses, requested URLs, times, response codes, referring pages, and browser details. Application logs are also kept for operation and troubleshooting.

The public app does not currently include a separate analytics SDK or tracking pixel. That does not mean requests are unlogged, or that an embedded site or authentication provider has the same data practices.

Questions about your information

Use the contact form to ask about information you have provided or to request a correction or deletion. Please describe the request without sending passwords, access codes, or other sensitive credentials.