Privacy Policy

General Principles & Zero Tracking

This application and its underlying infrastructure operate on a strict zero-tracking architecture. We do not require, create, or maintain user accounts or registration profiles. We do not deploy first-party or third-party cookies, web beacons, tracking pixels, session replay technology, or persistent fingerprinting mechanisms of any kind.

Profile

All professional identity profiles created, imported, uploaded, or parsed within the Profile interface (including text input, YAML, JSON, and Markdown-frontmatter files) are evaluated exclusively on your client device using in-browser JavaScript. Raw profile files and structured attributes are never uploaded to, transmitted across, or ingested by our servers during the import process. Validated profile data and recent audit URL history are persisted solely within your local web browser storage (localStorage). The site operator retains no custody, visibility, or administrative access to locally stored records. You may permanently eradicate all local profile and history data at any time by utilizing your browser’s standard site data deletion utilities.

Create

When generating structured markup via Create, submitted form parameters and active profile records are transmitted transiently over an encrypted transport layer (TLS) to stateless serverless functions strictly to execute schema compilation and JSON-LD graph serialization in accordance with schema.org specifications. All transmitted payloads, intermediate object representations, and compiled outputs are held in memory only for the duration of the request. No submitted data, compiled markup, or entity definitions are logged, cached, or persisted on server storage.

Check

When initiating a URL audit via Check, our infrastructure acts as an automated user agent to request the one page you name, following at most four redirects. It identifies itself as RealEstateSchemaBot and first reads the site’s robots.txt, honoring rules addressed to that name; see RealEstateSchemaBot. Outbound requests are designed to refuse internal, private, and other non-public network addresses, and ports other than 80 and 443. Neither retrieved external page markup nor generated audit diagnostics are archived, logged, or retained on our systems. When auditing via pasted code, submitted markup is analyzed ephemerally in volatile memory solely to return the conformance report and is not preserved.

Live DOM Check (Bookmarklet)

The optional RE Schema Inspector bookmarklet runs in your own browser, on whatever page you click it on. It reads that page’s JSON-LD and its full address, including any query string, and opens Check in a new tab with them in the address fragment (the part after #, which browsers do not send to servers). Check then sends the address and the JSON-LD to our server to produce the report, and our server requests that page once to compare it with its HTML source. None of it is stored on our servers; the address is added to the recent audit history in your browser. Because it reads whatever page it runs on, do not use it on signed-in or private pages such as email, banking, or dashboards.

Find on Wikidata

When you press “Find on Wikidata” next to a place field, your browser sends the place name you typed straight to Wikidata (run by the Wikimedia Foundation) to look up matching states, counties, cities and neighborhoods. Nothing else from your profile is sent, the request does not pass through our servers, and nothing is sent unless you press the button. Wikimedia’s own privacy policy applies to that request.

API

All programmatic endpoints under /api/v1 (including /api/v1/validate and /api/v1/recipes/*) operate under the identical stateless, non-logging, and ephemeral processing constraints established for the browser interfaces. Payloads are processed in memory and are never committed to persistent storage.

Infrastructure, Hosting & Webmaster Tools

This application is hosted and served through the edge network of Vercel Inc. (Vercel). Vercel may process and retain standard technical access logs (including originating IP address, request method, user agent, and timestamp) in accordance with Vercel’s privacy and security policies strictly for operational maintenance, traffic routing, security auditing, and DDoS defense.

This website utilizes Google Search Console, a webmaster diagnostic and administrative service provided by Google LLC, strictly for domain ownership verification, indexing management, crawl performance oversight, and search appearance diagnostics. Google Search Console does not collect end-user behavioral profiles, inject advertising cookies, or deploy client-tracking libraries on visitors to this application.

All typographic font assets are self-hosted, pre-bundled, and delivered statically at compile time. No runtime network queries are dispatched to external font repositories or third-party content delivery networks.

Disclaimer of Warranties & Updates

The services, validation reports, and code outputs generated by this platform are provided on an “as is” and “as available” basis without warranties of any kind, express or implied. The operator reserves the right to revise or update this privacy notice periodically to reflect operational, legal, or regulatory modifications, with revisions becoming effective immediately upon publication to this page.

Hold Harmless

By using this website, its tools, its API, or any markup, reports, or other output it generates, you agree to indemnify, defend, and hold harmless the operator and its owners, affiliates, contractors, and agents from and against any and all claims, liabilities, damages, losses, costs, and expenses, including reasonable attorneys’ fees, arising out of or relating to your use of the services; any content, data, or URLs you submit; your publication or deployment of generated output on any website; your use of the bookmarklet on any page; or your violation of any law or the rights of any third party. To the fullest extent permitted by law, the operator shall not be liable for any indirect, incidental, consequential, special, or punitive damages, or for any loss of rankings, traffic, revenue, or data, arising from your use of or reliance on the services.

Effective Date

Effective date: 11/07/2026. Changes are posted on this page.