Dealpages

Changelog

What shipped, when

Short and honest. Entries map to real deploys.

2026-09-25

Reading data from shared offices · safer page passwords

  • Fixed: when several people at one company read their links from the same office network, reading time past about 600 beats an hour (roughly a committee of two reading for an hour) was silently dropped. Limits now apply per link and network, with a much higher ceiling per network that only stops floods. Comments work the same way.
  • Page passwords are now stored salted and slow-hashed. Pages protected before today keep working with the same password; setting a password again upgrades it.
  • Password guesses are capped at 10 per page per network per hour.
  • Hosted pages now tell the browser they can't register tools with a visiting AI browser agent, or ask a reader for camera, microphone, location or payment access.
  • Publishing now refuses pages shaped like credential phishing: password fields and redirects to another site. Forms that submit to another site are refused for accounts in their first 7 days and flagged after that. The error tells your AI what to change.
  • Page history is capped: each page keeps its first version, its latest 20, and any version a reader commented on. Older in-between versions are removed nightly (the privacy notice says so). Each account can also publish up to 50MB of pages a day.
  • Reported pages can now be taken down (reversibly) within minutes of a report, from a phone.
  • New: page playbooks served by Dealpages itself, so every connected AI builds pages the same careful way: a deal room, a proposal and a mutual action plan to start. Each tells the AI what to pull from your call, what to ask, what never to invent (prices, dates, people, customer claims) and how the page should look. Three new tools: get_skill, get_house_style, set_house_style (17 tools now).
  • New: house style. Your AI drafts your logo, colors, fonts, voice and approved proof points from your website, you approve them, and every page uses them. Pages only quote proof points from your house style. See it on your account page.
  • New: update_section and add_section. Your AI can change one section (say, pricing) or add one (say, security) without resending the whole page; get_page can return a single section too. Same links, new version, comments re-anchored (19 tools now).
  • Buyers' AI assistants can now read a page without a browser: every link has a text version (/text), the deal facts as data (/facts.json), and a way to ask the sender a question (/ask), which arrives as a comment labelled as sent by an AI assistant. The link is still the permission, and reads are recorded against it and shown to you honestly as an AI assistant's read.
  • Reliability fixes from the review: faster lookups on the busiest paths; the nightly jobs run independently so one failure can't skip the rest; retrying a publish with the same key at the same moment can't make two pages; simultaneous updates can't collide; republishing counts toward the page limit; image uploads and test notifications are rate-limited; cookieless visitor hashes are deleted after a day, as the privacy notice says.
  • More fixes from the review, on the buyer side: reading data and comments are checked for size and shape and only recorded for sections a page really has; a page that's offline takes no new reading data or comments; the text version and facts.json only ever show what the page itself shows; your Activity feed now credits a read to a person's link, not to the person; "opened for the first time" can't repeat; image copying and notification addresses get the same public-address checks. The privacy notice now also covers the owner cookie and what notification emails carry.
  • Security fixes from a full review: the console and sign-in screens can no longer be embedded in another page; text in confirm dialogs can't run as script; sign-in can't be triggered from another site; and a page taken down after a report stays down until the operator restores it.
  • Four more playbooks: post-call recap, champion kit, security and trust packet, and prospecting page. Your AI gets them automatically.
  • Logo and image upload: from the Style page, or your AI uploads from a URL or the file (upload_image) and gets a permanent address to use in pages. PNG, JPEG, GIF, WebP or SVG, 1MB each (26 tools).
  • New: notifications that wake your AI. Turn on email or give a web address (a scheduled AI task, an automation tool) and Dealpages sends one signed message when a stakeholder link is opened for the first time, someone new is likely reading, a comment or AI question arrives, a buyer's AI reads a page, or a page goes a week without readers. Off unless you turn it on; each event once; in Settings or via the notifications tool (25 tools).
  • Read-only API keys (tick the box when creating one): a CRM sync or reporting agent can read pages, engagement and comments but can't publish or change anything. New tools check_page (every publish check, nothing stored) and mint_links (links for a whole committee at once); 24 tools.
  • New tool what_changed: section-by-section changes between two versions of a page (22 tools).
  • New: deal facts. Your AI stores a deal's shared numbers and dates once (set_facts) and pages show them with a small tag; change the price once and every page that shows it updates, with no republish. Two new tools, 21 in all.
  • Your account has a new layout: Pages, Activity, Playbooks, Style, Connect and Settings in a sidebar. Activity is a plain feed of who opened what and how long they actually read, new-viewer signals and comments, in the same honest wording your AI gets. Still no charts.
  • New examples, built by an AI with the playbooks: a deal room, a proposal and a mutual action plan for one fictional deal. They're on the homepage and the Playbooks page (formerly Templates). The older examples are retired.
  • Publishing now warns while a page still has [[ placeholders ]] in it, so a half-finished page doesn't go out by accident.
  • Getting started is three steps on the homepage: add the connector, sign in, paste a transcript. When an AI connects to an account with no pages yet, Dealpages now tells it how to offer a first page, and every connected AI gets the same short guide to the workflow and the honest-signal wording.
  • The sign-in email's subject now reads "Sign in to Dealpages".

2026-09-16

Moved to dealpages.app · privacy notice and terms

  • Dealpages now lives at dealpages.app: this site at the apex, sign-in and the MCP endpoint at app.dealpages.app, published pages at pages.dealpages.app.
  • Every existing page link keeps working — the old pages.kylelegare.com addresses redirect to the same page, same token. MCP clients still pointed at app.kylelegare.com keep working too; update them when convenient.
  • New: a plain-language privacy notice and terms of service, linked from every page of this site. They describe exactly what the code does.
  • claude.ai can now connect with a sign-in instead of a key: add app.dealpages.app/mcp as a custom connector, sign in with your email, press Allow. Standard OAuth 2.1, so other clients that support MCP sign-in work too; API keys keep working exactly as before. Connected apps are listed on your account page with a Disconnect button.
  • Account page rebuilt for new users: three-step onboarding, a detail page per deal page with every stakeholder link and a copy button, reversible Unpublish and Kill-link buttons, key labels, and delete-my-account.
  • New MCP tool revoke_link (14 tools now); mint_link and list_links return a share block with a ready-to-paste line per person.
  • Your own visits no longer count: open a page's preview link once and that browser is yours — checking Sarah's link afterwards records nothing.
  • Every hosted page now has a Report this page link in its footer, next to the analytics disclosure, which now links to the privacy notice.
  • Abuse limits: sign-in links, beacons, comments and reports are capped per network; publishes are capped per account per hour; 100 live pages per account and 200 links per page. The limits are generous for real use and the errors say what to do.
  • Retention: fine-grained engagement events are now pruned after 180 days (raw request logs were already pruned at 90). Comments and page versions stay with the page.
  • Under the hood: the console session cookie is now host-locked so a published page can never interfere with it; page-password cookies no longer carry the password hash; an account can be disabled, which takes its pages offline and its keys out of service; deploys run from GitHub on every merge.

2026-07-15

Renamed to Dealpages · site rebuilt

  • Product renamed from the working title Salesroom to Dealpages — pages for deals.
  • Site rebuilt: sidebar docs navigation, quickstart, analytics reference, this changelog.
  • Template gallery expanded to six deal stages plus the living deal page, each with a live example.
  • MCP setup page with per-client config and the full tools table; new flagship demo built from a one-paragraph brief shown on the page itself.

2026-07-14

Self-serve sign-in

  • Magic-link email delivery went live — anyone can get a key without a human in the loop.
  • Scanner-safe redemption: corporate email scanners can't consume your sign-in link.

2026-07-13

First version live

  • Remote MCP server with 13 tools: publish, update-in-place with stable URLs, per-stakeholder links, engagement reports, buyer comments, page controls.
  • Engagement model: visible+focused+interacting time only, section-level dwell, scored forward detection, automated-traffic bucketing.
  • Buyer comment widget with anchors that survive page updates.