Public-data products with minimal retained identity.
ActableSite processes public website and CMS records without collecting card details or creating a separate account system.
What the scan processes
When you submit a URL, the full readiness scan fetches the public homepage plus common public files such as robots.txt, sitemap.xml, and llms.txt. The live crawler check fetches robots.txt only. Public content is processed to create the response and is not deliberately stored in the product database.
Aggregate product telemetry
After a trusted pointer, touch, or keyboard interaction on a public acquisition route, the service records an anonymous engaged-visit count for the homepage, guide, or crawler tool. Passive loads and known automation are excluded, and a browser-session flag prevents the same tab from counting a route repeatedly; no cookie or server-side visitor identifier is created. For completed readiness scans, live crawler checks, and paid-report generation, the service records the event type, time, and a one-way digest of the hostname. Checkout-opening events have no hostname. This supports aggregate funnel measurement without retaining the submitted URL, page content, raw referrer, or a visitor profile.
Medicare revalidation assistant
The ChatGPT action sends the public NPIs entered for a lookup to ActableSite, which checks them against the current public CMS revalidation due-date list. ActableSite processes those NPIs to return the response and does not deliberately store the submitted NPIs, the response, or the ChatGPT conversation in the product database. It records an aggregate action-event time and a one-way digest derived from standard request information; it does not retain the raw caller address or a ChatGPT user identity. OpenAI governs information processed in the ChatGPT conversation. ActableSite’s policy governs the action request after it reaches this service.
Payments
Stripe hosts checkout and processes payment information. ActableSite does not receive or store full card numbers. Stripe’s own privacy terms govern data entered on its checkout surface.
Crawler Watch monitoring and email
Crawler Watch receives the public website and checkout email collected by Stripe. While the subscription is active, the service stores the domain, email, subscription status, check snapshots, alert state, and delivery timestamps in access-restricted operational storage. It fetches only public pages and common public discovery files. Resend processes the recipient address and message content to deliver activation, change, recovery, or configuration-error email. Operational records are removed or minimized after the subscription becomes inactive and any necessary support, refund, security, or accounting period ends.
Practice Radar source and access
Practice Radar processes public CMS NPPES records to create weekly samples and subscriber feeds. A Stripe checkout session ID is returned in a URL fragment, which browsers do not send in HTTP requests, stored in that browser’s local storage, and removed from the address bar. It is hashed locally to locate and decrypt a per-subscriber artifact. The public data repository contains only public samples, build receipts, and encrypted subscriber artifacts; it does not publish raw checkout session IDs. Active subscription status is checked with Stripe to create or remove access.
Pending Medicare edition access
The Pending Medicare product processes public CMS pending-enrollment files and public NPPES records. A one-time Stripe checkout session ID is returned in a URL fragment, stored in that browser’s local storage, and removed from the address bar. It is hashed locally to locate and decrypt the purchased edition. The public repository contains the free sample, source receipts, and encrypted customer artifacts; it does not publish raw checkout session IDs.
Medicare Revalidation Operations Dashboard access
Stripe returns a one-time dashboard buyer with a checkout session ID in the URL fragment. The browser stores it locally, removes it from the address bar, hashes it to locate the opaque encrypted artifact, and derives the decryption key locally. The downloaded dashboard sends only the NPIs submitted for a current public CMS lookup to ActableSite. Owners, internal status, next actions, and notes remain in the buyer’s browser storage when available and should never contain patient data, passwords, PECOS credentials, or private enrollment documents.
Infrastructure logs
Hosting, source-control, and security providers may temporarily process standard request information such as IP address, user agent, requested path, and error details to operate and protect the service. The one-time report access fragment is moved into tab-scoped session storage; Practice Radar, Pending Medicare, and Medicare dashboard access fragments are moved into browser local storage so the browser can retrieve purchased data later.
Your choices and contact
Use “Remove access from browser” on a data-product access panel to delete its stored access ID from that browser. Do not submit private, local-network, authenticated, or unauthorized URLs. Email support@actablesite.com with questions about public-data processing, anonymous funnel telemetry, or a purchase. Do not send passwords, access IDs, API keys, or private-page content.