Privacy information.

What is stored

Suggestion, correction and advertising-interest forms store the message, optional website, optional email (required for advertising interest), submission time, review state, and receipt reference. Facility-operator update forms separately store the representative name, role, business email, optional official website, factual corrections, selected feature and availability claims, optional structured price observation, public evidence URL, note, review state and receipt in local SQLite. A separate confirmation record stores a narrow manual representative-verification state, date and review note; it does not certify prices or other facts. They are not emailed, sent to facilities, sold, or enrolled in a mailing list.

Measurement

First-party events record page views, facility views, website clicks, phone-link clicks and submissions. Each event contains the site, event type, controlled page path, optional facility ID, time and automation-check flags. For storage comparisons, events can also contain a controlled category, unit-size intent, size group, climate preference, selected offering ID, location and price interaction or price band. The needs matcher adds controlled vehicle, enclosure, feature requirements, length band and counts of strong or possible results, plus matcher interaction actions. These counts are not people or verified leads. No entered budget amount or free-text search is recorded. A tab-local landing path and coarse source class help us understand which pages lead to facility activity. We distinguish Google/Bing search referrers, other search, direct or unknown sources, referrals, internal navigation and tagged campaigns. Campaign labels use only short letters, numbers, underscores and hyphens; do not include personal information in campaign tags. No raw referrer URL, visitor ID, fingerprint, IP address, raw user agent or search query text is saved in events. Search Console search-query data, when imported by the operator, is stored separately for search analysis. The request user agent is checked transiently for obvious automation.

Known automated checks and our own testing are excluded from reported visitor activity. A click is not a call, lead, booking or sale. There is no outcome-verification integration. A search referrer can also come from an advertisement and does not prove an organic visit. Search Console is the separate source for organic search clicks. Third-party analytics and ads are disabled.

Browser storage and security

Your comparison shortlist, selected storage-intent context, matcher selection and result facility IDs, and landing-source context use this tab’s session storage. Landing and storage-intent context expire after 30 minutes and contains no visitor identifier. We do not link your activity across tabs or devices. Administrator login uses an essential HttpOnly session cookie with an eight-hour lifetime. Authentication is handled by Better Auth; password hashes and admin account/session data are stored locally. Admin IP and user-agent tracking are disabled. Form tokens and rate limits reduce simple replay, login attacks and automated spam. Known testing is excluded from visitor metrics.

Retention

Daily maintenance removes individual events older than 30 days. Daily aggregate counts, imported Search Console data and private recommendation history are kept for 400 days to support year-over-year comparisons. Resolved submissions and rejected or proposal-staged operator updates are removed after 90 days. Open submissions and operator updates awaiting review or proposal handling remain until handled. The dated operator-confirmation state remains separate from contact details until manually changed or revoked. Expired form tokens and rate windows are purged on requests. Admin session expiry is enforced by the auth component; the maintenance command removes expired database sessions. Production runs daily maintenance and creates database snapshots with 30-day local retention. Weekly provider server backups are retained for 28 days. Separate restricted-access recovery copies are also held and must be refreshed or removed when no longer needed. Backups are not publicly accessible. Minimal service logs may record time, response status, response size and duration; the access-log configuration removes request details, including addresses, URLs, headers and cookies. Service error logs are access-restricted and rotated.

Optional Google map

Opening the map loads Google Maps JavaScript directly from Google. Google receives technical request information, including your IP address, browser information and the site referrer, and may use cookies or other storage under its own policies. The map does not request your device location. We send our reviewed public facility coordinates to display markers; we do not send administrator credentials or form messages. The list and filters work without opening the map. See Google’s Privacy Policy and Google Maps terms.

Our first-party analytics count map opens, marker selections and map-to-profile actions with the selected storage intent and facility identity. These are interaction counts, not unique visitors, bookings or verified leads.

Links

Facility links take you to an independent operator’s website. Their privacy practices apply there. No provider is contacted merely because you submit this directory’s form.