Privacy

We cannot sell what we do not collect.

Effective July 20, 2026

Browser-only workspaces

The free request generator, paid command center, and Professional Client Share Kit assemble and save working data on your device. GeezerKeeper does not receive the names, contact details, provider list, request text, statuses, dates, or practice-branding fields you enter there. The paid workspaces use your browser's local storage so they can survive a refresh. Their clear controls remove the saved workspace or branding from the current browser.

Your device and exports

Anyone who can use the same browser profile may be able to view locally saved data. Do not use the tools on a shared device, and protect downloaded ledger, calendar, and handout files as you would other records. Clearing browser data may erase a workspace; GeezerKeeper cannot restore it.

Payments

Stripe processes checkout and payment information under its own privacy terms. GeezerKeeper receives ordinary transaction records such as purchaser email, amount, payment status, and transaction identifiers. We do not receive full card numbers. We use payment records to provide access, prevent fraud, handle refunds or disputes, and keep required business records.

Aggregate product telemetry

GeezerKeeper records a small set of first-party event categories so we can tell whether the public site is being found and whether the free tool or checkout is used. These records contain the event type, a page category, a coarse source category, the UTC day, and an anonymous request identifier. They do not contain form entries, names, contact details, request text, full referring URLs, cookies, advertising identifiers, or paid-workspace activity. Global Privacy Control and browser Do Not Track signals disable this telemetry. Raw event records are automatically removed after 90 days.

Embeddable caller checker

A publisher may place GeezerKeeper's free checker on another website. Loading its self-contained script creates one ordinary technical request to our hosting provider, but checking a phone number produces no request to GeezerKeeper: the comparison happens locally against the evidence bundled into the script. The embed does not put that number in a URL, request body, analytics call, cookie, or browser storage. A publisher's own page may have separate analytics or privacy practices that GeezerKeeper does not control.

Hosting and support

Our hosting provider may process ordinary technical request data, such as IP address, user agent, requested page, and timestamps, for delivery, security, and reliability. If you email us, we receive the address and content you choose to send. Do not email medical records, government identifiers, financial details, passwords, or identity documents.

No sale or referral use

We do not sell personal information, sell senior-care leads, earn facility referral commissions, or use workspace information to recommend a care provider.

Retention

Browser-workspace data remains under your control on your device. Payment and support records are kept only as reasonably needed for business, accounting, security, dispute, and legal purposes, then deleted or de-identified when practical.

Contact

For privacy questions or requests about information GeezerKeeper actually holds, email privacy@geezerkeeper.com. We may need to verify your identity before acting on a request.