Hatzhold Designs · Updated November 10, 2026
Privacy
This notice explains what Hatzhold LLC ("Hatzhold", "we") collects through hatzhold.com, demo.hatzhold.com and the private Hatzhold Dashboard, and how we use it. Client websites that Hatzhold builds are run for their owners and follow their own privacy practices.
What we collect when you visit
Hatzhold's own pages don't use advertising or tracking cookies, and we don't sell or rent personal information. Some demo sites embed outside services, such as Google Maps or Google Fonts. Those services receive your IP address and may set their own cookies under their own privacy policies.
Cloudflare hosts the sites. Like most web servers, it records technical details of each request, such as your IP address, browser type, the page requested and the time. We use these records to keep the sites running, find errors, and block attacks and abuse.
The contact form
When you send the contact form, we collect your name, email address, business name and message. We save the message so we can reply, and send a copy to Hatzhold's inbox. We use it only to answer you and discuss possible work. We don't add you to a mailing list.
To stop spam, the form uses Cloudflare Turnstile to check that a person is sending it, and limits how many messages one IP address can send.
Client portal
Clients sign in to the client portal with a one-time code sent by email. Signing in sets one cookie that keeps you signed in, and the portal stores what's needed to run your account. Stripe processes payments, and Hatzhold does not store card or bank account numbers. A client's signed agreement also applies.
Who else handles your information
Cloudflare hosts the sites and sends Hatzhold's notification email. Stripe processes client payments. Google provides the Search Console data described below. We share information with others only when the law requires it, or to protect Hatzhold, our clients or the public from fraud, attacks or other harm.
Your choices
You can ask to see, correct or delete the information you sent us by emailing alex@hatzhold.com. We may keep some records when the law requires it or to resolve a dispute. Removing current records does not itself purge retained database backups.
Our sites are not meant for children under 13, and we don't knowingly collect their information.
Changes
We may update this notice by posting a new version on this page with a new date.
Hatzhold Dashboard: Search Console connection
This section describes Hatzhold LLC’s Google Search Console connection in its private dashboard.
What the connection reads
With an operator’s Google consent, the dashboard requests read-only Search Console access and reads the connected account’s property list to check access to the selected property. Other property entries are not stored. For explicitly selected website properties, it reads dated clicks, impressions, click-through rate, average position, top queries and pages, sitemap URLs and their submission, download, warning and error status. A one-time URL Inspection returns details such as the index verdict and last crawl time for a selected URL; that result is displayed in the dashboard and is not saved as a Search Console snapshot.
The connection does not read Gmail, contacts or Drive, or modify Google properties, sitemaps, indexing or DNS.
Use and storage
These observations support website visibility review by authorized Hatzhold dashboard operators. Google receives the authorized API requests. Tokens are encrypted in Hatzhold’s Cloudflare backend and are not returned to the browser. The latest successful property report and its fetch date are stored in the backend database. A fully successful refresh replaces it; a failed or partial read leaves the saved report available. This feature does not retain a series of every refresh.
Google account details and Search Console observations are not exposed through client portals. This integration has no advertising, resale, public export or AI-training feature. Google and Cloudflare provide the API and hosting infrastructure used by this connection.
Disconnecting and retained data
Disable stops reads for one property. Disconnect removes the locally stored shared Google token, stops all sites using that grant, and attempts Google revocation. The dashboard reports when Google revocation is unconfirmed. You can also remove the app through your Google account permissions.
Dated observations remain after disconnect; disconnect does not delete historical data. This integration has no automatic observation-deletion schedule. Consent state expires after ten minutes, and expired rows are cleaned up on a later Enable request. Client binding data is removed with its client record; Hatzhold’s own binding is separate. Removing current database records does not itself purge retained database backups.
For support or to request review of retained connection data, email alex@hatzhold.com. Disconnecting Google does not itself submit a deletion request.
Contact
Email alex@hatzhold.com with any privacy question or request. Read the terms, or contact Hatzhold.