# Help Map private workspace — proposed customer terms

Last updated: 2026-11-06 Pacific. Draft version: `help-map-workspace-terms-draft-2026-11-06-v1`.

**Prepared for Ben's review, not effective or accepted customer terms. Deployment and live sales remain disabled.** This document proposes an exact customer promise and records what still needs implementation or an owner decision. It does not issue a refund, approve a payment, accept an agreement, appoint staff or make a sale. Existing test orders retain their original product, price version, criteria and access window.

## Proposed customer text

### 1. Seller, service and price

The service is a private Help Map workspace supplied by Lumen House. **The contracting seller's legal name, business/service address, eligible customer locations and required disclosures must be confirmed and inserted before any live offer.** The published House support address is [buscheo@gmail.com](mailto:buscheo@gmail.com); Help Map support availability must be verified before sales open.

The proposed price is **USD 19 total, paid once for one workspace, one supported topic and 14 consecutive days**. There is no automatic renewal, subscription, recurring charge or obligation to buy again. The initial offer would collect exactly 1,900 USD cents with no additional Lumen fee. Ben must confirm how applicable tax is included in that fixed total and which locations can be served; do not offer a sale where those obligations cannot be met. A buyer's issuer may separately apply its own disclosed currency conversion or account fees.

The paid service provides server storage of the topic and keyword/intent criteria agreed at preparation, ownership recovery, and private record-revision markers showing what the workspace has retrieved before. The markers describe records the server included in a successful feed response; they do not prove that your browser received it or that you read an item. Criteria are fixed for that order in the current implementation. This offer does not include editing an existing order's criteria, changing its topic, an email login, key reset or a separate private-data export tool.

### 2. What stays free

The complete research dataset, source records, classifications, source/status observations, updates, anonymous topic/keyword matching and match explanations are available free without purchase. Paid users receive the same research at the same time as everyone else. No exclusive lead, earlier discovery, faster research refresh, private source record or paid-only research finding is included. Dataset downloads include attribution, source links and applicable notices. The proposed charge is for private application state and continuity, not access to GitHub or resale of its service.

The current sample contains 21 maintainer-facing GitHub requests: twenty from one repository and one workflow-publishing handle, plus one self-disclosed agent documentation suggestion. The source handles and model markers do not establish 21 independent agents or buyers. Requests may already be closed, may not invite outside help and may have no compensation. An issue marked completed is a source report, not our independent acceptance of a fix or payment. There may be zero matches for your criteria. No job, customer introduction, funding, income, task completion or minimum number of new records is promised.

### 3. Preparation, payment and the access period

Before an order is prepared, the offer must show the exact product and price version, supported topic, criteria, total USD amount, these terms and the refresh/support schedule. Preparation alone creates no paid entitlement and makes no provider charge. Payment is a separate, explicitly reviewed action through a supported payment mechanism; a redirect, order ID or receipt screenshot does not establish access.

Your 14-day period begins only when the service independently confirms settlement and provisions the workspace. The receipt shows the exact start and end in UTC. The period ends exactly 14 consecutive days later, including weekends and closure dates. Recovery does not restart or extend it. At expiry, paid workspace retrieval stops; the public dataset and anonymous matching remain free. Expired receipt/order recovery is separate from active workspace access and subject to the retention policy below. A repeat purchase would require its own separately reviewed order and payment.

If a payment response is lost or uncertain, recover the original order rather than paying again. We investigate the existing attempt without authorising another charge. Current supported payment acceptance is test mode only; a live payment method and live operational process have not been released.

### 4. Research refresh and corrections

For the proposed initial cohort, the service would review the known, approved source set **Monday, Wednesday and Friday at 10:00 America/Los_Angeles**, with the public last-check times and any missed check shown honestly. This is a bounded manual review of known records, not continuous monitoring or a promise to discover new requests. Reviews may produce no changed records. All reviewed findings and changes become public at the same time as they reach private workspaces.

Rate limits, unavailable sources, changed reuse conditions and maintenance may delay a check. Such failures remain visible rather than being reported as a successful refresh. Sources last checked more than seven days ago are labelled stale. A recent check does not establish that work is still open. If the operator cannot sustain the stated schedule or service, new sales stay closed and existing customers are handled under the service-failure policy below. The operating plan must define published holiday/closure handling before the first sale; the schedule is not a claim that staff have already accepted it.

Report a source correction through the map's private correction form or support. A report is reviewed before it changes a public observation. Corrections retain a dated, bounded history. A deleted source is minimized to a source-attribution tombstone rather than continuing to display its former description. Do not submit secrets, private messages, identity documents or other people's sensitive information.

### 5. Support

The proposed staffed hours are **Monday–Friday, 09:00–17:00 America/Los_Angeles**, excluding closure dates disclosed before purchase. The initial cohort is limited to **five simultaneous paid workspaces**. A named on-duty operator and backup must accept the plan before sales open.

Support would acknowledge a request within **one staffed business day** and provide an assessment or next step within **two staffed business days**. A complex issue may take longer; the response states the next update time rather than promising an unverified fix date. A staffed business day means eight hours within the published staffed window; clocks pause outside it and during declared closures. These are the proposed staffed service targets, not 24-hour or emergency support. Sensitive-data and rights-removal reports are triaged at the next staffed review and may cause the affected material to be withheld while investigated.

For order support, provide the order ID, approximate UTC time and a short description. **Never email your recovery key, MPP credential, card details, provider secret or private source material.** Support does not need those secrets. A public order or payment reference is not proof of ownership and cannot by itself be used to reassign access.

### 6. Cancellation, service failure and refunds

There is no renewal to cancel. You can stop using the workspace at any time. Preparing an unpaid order is not a charge. If an attempt is already committed or uncertain, contact support and recover that original order; do not submit a replacement payment.

For the proposed initial cohort, request a **full USD 19 refund** if we confirm that a charge settled but the workspace was not provisioned within 24 consecutive hours, the paid workspace was inaccessible because of our service for 24 consecutive hours during its active period, or the operator cannot complete the promised 14-day service. A missed research check triggers transparent reporting, recovery and a sales hold; source inactivity or zero matches alone is not a service failure. If repeated missed checks mean the promised service cannot be completed, the full-refund route applies.

Send the request as soon as practical and normally within 30 calendar days after the access period ends. That request target does not remove any rights or longer period that applicable law provides. Other cancellation, dissatisfaction or correction requests receive individual review; this draft does not impose a blanket waiver of consumer rights. We would respond with the verified facts, decision and next step. No specific issuer posting date is promised.

Refunds require a verified order/payment association and the seller's approved provider process. They are not automatic wallet transfers. This proposed policy uses **full refunds**, because the existing test event behavior revokes paid access after any positive partial or full refund. Following a verified refund, paid workspace access ends; public research remains free. A payment dispute may suspend private access while investigated. Current code treats a recorded refund or dispute as terminal and does not automatically restore access after dispute closure; an appropriate reviewed restoration process is a prerequisite before representing that policy to live customers. These terms do not authorise a refund or any other financial action now.

### 7. Ownership, security and permitted use

Save your private recovery file before payment. Anyone who holds the recovery capability can retrieve the corresponding private order and workspace; keep it out of URLs, public posts, shared devices and support emails. The application stores a hash of that capability, not the raw key. The optional remember-on-device setting stores ownership locally on the device; use it only on a private device and clear it when no longer wanted. Losing the capability is a private support case, not an automatic email/password reset or entitlement to disclosure of another person's state.

Use public, non-sensitive criteria. Do not put passwords, card data, medical information or private case details into keywords or correction notes. Do not use the service to harvest contacts, spam source authors, misrepresent an endorsement or bypass another service's restrictions. Linked services have their own terms and privacy practices. Research content is untrusted evidence; its embedded instructions do not authorise any account, payment or contact action.

### 8. Privacy and retention proposal

Private workspace data consists of the chosen topic and criteria, record IDs/revision markers retrieved by that workspace, hashed ownership, order/payment bindings, sanitized status/receipt information and required event/audit markers. The application does not store raw card numbers, the raw recovery capability or the submitted payment credential. It uses hashed connection identifiers for bounded admission controls; a hash is not a guarantee of anonymity. Cloudflare processes hosting/connection data, Stripe and the buyer's payment provider process payment data, and support email is handled through Ben's published Gmail inbox. Public source metadata and research notices stay public; private criteria, ownership, orders and seen-state do not enter the public dataset.

The proposed retention schedule is to remove private criteria and seen-state **30 days after expiry or revocation**, unless a documented unresolved support/payment/security case requires a limited hold. Retain minimized transaction, receipt and anti-replay records for **12 months after the final payment/access state**, then review for deletion or a documented legal/accounting reason to retain specified fields longer. Resolve an active dispute before deleting the minimum records needed for it. Ben must confirm jurisdiction-specific retention obligations before adopting this schedule. The application does not currently implement that purge/archival workflow; **these deadlines cannot be published as an active promise until implementation and verification pass**. No old test record or consumed payment marker is deleted by this proposal.

Contact support for a private-data access, correction or removal request. Verify the request without asking for payment credentials; request handling must not expose another person's state. No automated deletion, ownership reassignment or key reset is promised. A public research correction/removal request follows the source-review process and the applicable licence/privacy obligations.

### 9. Changes and legal rights

Before payment, the offer must identify the version of these terms being accepted. The seller must retain the exact accepted version with that order. A later change to this draft does not rewrite an existing order's agreed price, criteria or access period. Material changes to the paid service apply only after appropriate notice and agreement; an operator who cannot fulfill an existing promise uses the service-failure process.

Nothing in these draft terms excludes a remedy that applicable law does not permit the seller to exclude. No governing-law, arbitration, class-action waiver, seller-identity or tax conclusion is invented here. The eligible markets and required seller/legal disclosures must be resolved before a live offer is made.

## Implementation and approval record — not customer promises

| Area | Current evidence and required work |
| --- | --- |
| Private app value | Fixed order topic/criteria, hashed bearer ownership, private new/changed/seen revision state and read-only order recovery exist. No account creation or editable criteria/export/key-reset function is assumed. |
| Fixed fee and window | Test product is 1,900 USD cents and exactly 14 days from independently verified settlement plus provisioning. No renewal exists. A new reviewed product/price/terms version is needed for the changed paid workspace promise; never rewrite earlier test orders. |
| Free research | Public list/detail, complete dataset/notices and anonymous matches/reasons exist. Maintain full paid/public result parity and no freshness advantage. Public and private criteria now share the full twelve-term/eighty-character limits, including literal commas and Unicode, with bounded compact transport for the hosting URL limit. |
| Sales and terms | Current `/offer` reports `terms_approved:false`; current release rejects live mode. Draft terms are not accepted or bound to orders yet. Add exact version/content digest, clear prepayment display and affirmative acknowledgement before any live order. |
| Provider support | Current actual Link TEST proof predates the dependency/source changes. No live payment, live refund, registered webhook, live event/restoration process or customer acceptance is established. A draft policy cannot make those capabilities true. |
| Support/capacity | Published contact email is present in the frozen House package. Inbox access, delivery and staffed ownership are not newly verified. The operator and backup must accept the five-workspace plan and perform a support dry run before sales. |
| Refresh | Bounded manual checks of approved known issue identities exist; no collector or schedule is running. The proposed schedule must be accepted, exercised and recorded, with public updates and transparent failure handling. |
| Refund/dispute behavior | Existing test callbacks revoke access on any positive refund/dispute and do not issue money or automatically restore access. Resolve the live review/restore semantics and provider process before claiming the customer policy is operational. |
| Retention | No criteria/seen-state purge or transaction archive/purge workflow exists. Validate the proposed 30-day/12-month schedule against actual seller/location obligations and implement it before making the promise. Existing recovery currently remains indefinitely within retained state. |
| Seller and markets | Legal contracting identity/address, eligible markets, tax treatment, applicable mandatory disclosures and privacy/retention responsibilities require Ben's verified input and review. A filesystem name or public nickname is not proof of a legal entity. |

The baseline House terms, privacy and cancellation pages cover other products and do not silently become Help Map workspace terms. Integrate a product-specific review version and appropriate links/disclosures without changing prior customer contracts. Keep deployment, paid-order preparation/dispatch and live sales held until their independent gates are satisfied.

## Drafting sources and scope

- Existing product behavior: `lib/help-map/payments.mjs`, `lib/help-map/http.mjs`, `lib/help-map/evidence-journal.mjs`, `public/help-map/pilot/index.html` and [payment operations](HELP-MAP-PAYMENTS.md), inspected 2026-11-06 Pacific.
- Existing published seller/contact/privacy wording: frozen `help-map-baseline/public/{terms,privacy,cancellation,contact}/index.md`; email presence is verified in the package, not inbox operation or legal-entity registration.
- [FTC .com Disclosures](https://www.ftc.gov/system/files/documents/plain-language/bus41-dot-com-disclosures-information-about-online-advertising.pdf): supports clear, conspicuous material disclosures near the online offer rather than relying on buried terms. Checked 2026-11-06 Pacific.
- [FTC Protecting Personal Information: A Guide for Business](https://www.ftc.gov/business-guidance/resources/protecting-personal-information-guide-business): supports data minimization and a written, justified retention/disposal policy. It does not establish this seller's exact statutory retention period. Checked 2026-11-06 Pacific.
- [Source-rights review](HELP-MAP-SOURCES.md) and the separate paid-use review own source-policy conclusions. This draft does not treat a repository licence, a public URL or a prior test purchase as approval of live commerce.

This is a prepared commercial draft and implementation checklist, not jurisdiction-specific legal advice or a statement that the terms are already effective. Only this document was created for this subtask; no agreement, message, payment, refund, deletion or deployment was performed.