Using the Public Page Add-on

The Public Page Add-on lets you publish a Pulse record's verification details to a public URL. A client opens the link in any browser, sees the timestamp proof and the metadata you chose to share — without needing Pulse, an account, or a hash command line.

This guide covers the full lifecycle: publish, share, manage, expire, and delete.

Requirements

  • A Pro license, plus the Public Page Add-on subscription (or any bundle that includes it). See Plans and Pricing.

  • An internet connection at the moment of publish.

The Add-on is the only Pulse feature that talks to the network beyond OpenTimestamps. Publishing is always an opt-in action — Pulse never uploads anything you didn't explicitly publish.

What Gets Uploaded

A short, deliberate slice of your record:

  • Capture count, interval boundaries, and aggregate totals

  • The Bitcoin block height, block hash, Merkle root, and an Open in Block Explorer link for each anchored capture

  • The OpenTimestamps proof hash so a viewer can verify independently

  • A page theme (dark or light), language, and an optional creator name you provide at publish time

What is not uploaded:

  • Screenshots

  • Active app names

  • Mouse distance, click count, or keystroke count

  • Anything from your Work folder other than the public-safe metadata above

The implementation enforces this with an allowlist payload — there is no flag, no UI toggle, and no API path that ships those other fields. Adding screenshots or activity content to a public page would require rewriting the upload code.

Publishing a Work Page

  1. Open a Work on Pro with the Public Page Add-on active.

  2. Click Publish public page.

  3. Choose a TTL (time-to-live) — any whole number of days between 1 and 365. The default is 90.

  4. Pick a page theme (dark or light) and a language for the page.

  5. Optionally enter a creator name to show on the page (the page works fine without one).

  6. Click Publish.

Pulse uploads the page to verify.tsukulogic.com/v/<id> and shows you the URL. Copy it and share however you want.

Publishing a Project Page

You can publish at the Project level too: every Work in the Project gets its own page, plus an aggregate page that links them all together.

  1. Open a Project on Pro with the Add-on active.

  2. Click Publish project public page.

  3. Pick TTL, theme, language, and creator name as above.

  4. Click Publish.

Each child Work page has the same protections — no screenshots, no activity content. Only metadata.

TTL (Time-to-Live)

Every page has an expiry. The TTL is freely choosable per page, from 1 day to 365 days, with 90 days as the default. Pick what fits your delivery — short windows for one-shot deliveries, longer windows for engagements where the client may circle back. After it expires, the URL serves a "This page has expired" message and the underlying data is removed from the server.

You can re-publish any time after expiry — the new page gets a fresh URL and a fresh TTL clock.

Managing Your Public Pages

In the sidebar footer, click Public pages to open the management modal. From there you can:

  • See every active page (Work, Project, and aggregate) with TTL countdown

  • Copy a URL to clipboard

  • Delete a page early

The list is loaded from the server, scoped to your license. You won't see anyone else's pages.

Deleting a Page

Click Delete in the Public pages modal. The server immediately:

  1. Marks the page as deleted (the URL returns "This page is no longer available")

  2. Removes the underlying data

Deletion is permanent — the same URL cannot be re-used. If you need the page back, publish again to get a new URL.

What If My License Lapses?

You always keep the right to delete pages you published, even after your Public Page Add-on subscription lapses. Pulse uses a special, scope-limited authentication path for delete operations: it can list and delete your pages, but cannot publish new ones (that would require an active subscription).

This means lapsed subscribers do not get stuck with un-deletable pages. Renew when you want to publish again.

How Your License Key Is Handled

To prove that a page is yours (so the server lets you list and delete it), Pulse sends your license key to the Public Page server over HTTPS. The server validates it with Lemon Squeezy and uses the validated license id — not the raw key — as your stable owner identifier on subsequent requests. The raw key itself is hashed (SHA-256) and the hash is stored only as a short-lived anchor used to authorize the deletion of your own pages after a subscription lapse.

In practice:

  • The license key travels over HTTPS to Pulse's Worker at publish, list, and delete time.

  • The server side identifies you by ls_<license_id>, not by your email or name. There is no Pulse account, no profile page, and no way for the server to enumerate "all pages by this user" without a valid license key.

  • Page content (BTC anchors, capture counts, theme, language, creator name if you set one) is what's stored against that owner id.

If having your license key transit a Pulse-operated Worker isn't acceptable for your threat model, don't use the Public Page Add-on — every other Pulse feature stays local.

Limits

  • Each account can hold up to 100 active pages at a time. Delete or wait for old pages to expire before creating new ones beyond this limit.

  • TTL is capped at 365 days at the API level; the UI accepts any whole number of days from 1 to 365.

Related

  • Verifying Records — what a public page shows and how the underlying proof works

  • Plans and Pricing — Add-on pricing and how it relates to Pro

  • Activating Your License — applying your Add-on key

‹ Exports and Certificates

Pulse Plans and Pricing ›