Different surfaces have different data paths.

Browser workspace

PDFs you choose, extracted text, organization notes, review selections, and exported preparation packs are processed locally in your browser and are not uploaded by the workspace. Search phrases and opportunity IDs are sent to public federal services to retrieve the records you request.

Free MCP tools

The discovery, preview, and standard complete-pack tools receive the opportunity ID and only the organization facts used by their published hard gates: entity type, state, optional country, optional requested amount, and optional cost-share capacity. They do not accept an organization name, EIN, UEI value, annual budget, project narrative, proposal document, or personal contact information.

To withstand a short Grants.gov outage, the service may retain a recent public-source response for up to six hours. Search text is not stored: the lookup key is a SHA-256 digest, and the cached value contains only the public federal response. Results label whether they came live, from a fresh cache, or from a stale fallback.

Aggregate MCP usage

Each valid MCP tool call increments one daily aggregate bucket containing only the distribution channel, tool name, success or error outcome, Korea calendar date (Asia/Seoul), and call count. The usage table does not store an IP address, user agent, caller identity, request ID, opportunity ID, organization profile, response, payer, or transaction. Distribution channel is derived from the registered endpoint path, not from fingerprinting the caller.

Aggregate workspace funnel

The site increments daily aggregate buckets for a closed set of steps such as opening the workspace, completing a search, loading an official source, exporting a pack, and reaching the start, halfway point, completion, or call to action of the product film. A 14-day source label can be set only by a published /from/… route. The table stores only Korea calendar date, a finite source label, a finite event label, success or error, and a count. It has no field for an IP address, user agent, referrer URL, search text, opportunity ID, profile, document, session identifier, playback time, or free text. Operator-authenticated release checks are kept in an INTERNAL bucket and excluded from external activation totals.

Website analytics

On grants.utilityhouse.xyz only, the public website loads Cloudflare Web Analytics to measure aggregate page traffic and site performance. It is not loaded on local or preview hosts. Cloudflare processes the network and browser data needed to provide that service under its own privacy terms; the Grant Evidence application does not copy those visitor-level analytics into its D1 product database.

Research review requests

If you voluntarily request a research review, we store only your email, professional role, one public opportunity reference, broad availability, time zone, whether you currently screen federal opportunities, whether you want contact about an access need, the consent version and time, and the closed acquisition channel. The form does not accept your name, employer, proposal, budget, credentials, organization identifiers, documents, or a free-text research answer.

The intake is used only to select and coordinate the September 2026 research round. Intake records are deleted after October 23, 2026. Recording is off by default and would require separate consent. To withdraw before deletion, email tytutueh15@gmail.com.

Complete-pack free beta

For a complete-pack call, the service stores the stable request ID, a one-way request hash, opportunity ID, snapshot hashes, result digest, UTC release day, and the released evidence pack. The pack contains the minimal organization category, state, country, requested amount, and cost-share response used by its gates. Released beta operation records expire after 30 days.

No payment service is contacted, no payment request is issued, and no blockchain settlement is created for a beta call.

Opt-in actual-profile proof beta

For opportunity 359701 only, a separate tool accepts structured non-personal organization, project, and readiness facts after the caller explicitly attests that they are current, confirms intent to apply to that opportunity, and consents to result storage. It rejects names, contact details, organization identifier values, narratives, documents, and credentials.

The service does not retain that raw profile. If every gate passes, it retains only the derived pointer-only pack and attestation receipt for 30 days. The receipt proves what a caller supplied, attested, and intended; it does not independently verify those facts.

Public sample and data status

The sample uses a fictional non-personal organization profile and public federal records. The live data-status endpoint exposes only aggregate snapshot metadata, content hashes, current access labels, and whether stored paid operations require reconciliation; it does not return requests, results, organization inputs, payer data, transaction data, addresses, or credentials.

The daily snapshot refresh records one row per run: a timestamp, a state, reason codes, and counts of listings selected, ready, failed and quarantined. It has no field for an opportunity, a recipient, an organization, a caller, an upstream response, or an error message. Run rows are removed after 45 days.

If you create a workspace account

An account is optional. If you create one, we store the email address and password hash, or the email returned by Google sign-in, plus a session cookie. We also store opportunities you choose to track and reminder-delivery records. Browser-local documents, notes, and review choices are not added to the account.

Emails and workspace payments

Deadline reminders and requested password-reset emails are delivered through Resend. Deadline Watch Pro payments are handled by Paddle as merchant of record; card details do not reach this tool. Purchase records retain the transaction ID, amount, and currency so an unlock can be restored.

Removing account data

Email hello@utilityhouse.xyz to request deletion of an account and its tracked opportunities. Payment records that must be retained are handled under applicable payment-provider terms and law.