HTMLvault Blog
Make AI-generated HTML worth reading, then see who reads it.
How to prompt for reports, dashboards and proposals that hold up, keep them current after they are sent, and put them to work in sales and marketing.
9 posts tagged Link expiry
How to Delete Claude Artifacts (and What Deletion Actually Removes)
How to delete a Claude artifact, its published link, and the conversation, in the right order — plus what deletion can't reach and how to make the next cleanup unnecessary.
Link Expiry Settings: Choosing a Window That Matches the Deal
Choose link expiry settings from the decision a link supports, extend on purpose when a deal slips, and set the account retention window that decides what's deleted after expiry.
Enterprise HTML Sharing Checklist for Teams
Use this enterprise HTML sharing checklist to evaluate a sharing tool as its approver: six criteria, the audit record, a real trial, and an approved path faster than the workaround.
Data Retention Window: Share Sensitive HTML Without Leaving a Trace
Some content shouldn't exist at rest—ever. HTMLvault's Data Retention window automatically purges your HTML from our servers once your retention window elapses, giving compliance teams one less thing to audit.
Secure AI Artifact Distribution That Holds Up
Where the reports and pages your AI tool makes should live, how to publish them from the tool itself, see who read them, and set expiry, password and retention defaults.
Password-Protected Links: How They Work and When to Use One
Password-protected links on HTMLvault hold your page on the server until the right password is typed. How to set one, what readers see, and when another control fits better.
Auto-Expiry: Time-Limited Links That Clean Up After Themselves
Auto-expiry takes an HTMLvault link offline after a window you pick: 24 hours to 30 days on Free, 1 hour to never on Pro and up. Extend it later and the same URL comes back.
How to Share an HTML File at Work: Send a Link You Can Track and Update
Send an HTML report or proposal as a link, not an attachment: it renders as built, shows who read it, and can be fixed after sending. One proposal is the worked example.
PII Detection and Redaction: Choosing What Stays in the Page
Finding personal data is half the job. How to choose between redacting, masking and restricting it, trim the export first, and check View Source so masked values are really gone.