The public linkifact.com/artifacts/… page contains platform UI only, never uploaded bytes.
Untrusted HTML.
Very little trust.
An artifact is an untrusted document from someone else. Linkifact treats it that way: separate origin, script-free browser sandbox, no outbound network, and no access to account state.
Defense in depth
The artifact gets a tiny browser-shaped box.
No single header carries the whole security model. Independent origin, iframe policy, response policy, and publication-time validation reinforce one another.
User HTML is displayed with an opaque origin under pages.linkifact.com, which never receives or sets cookies.
Scripts, network, frames, forms, workers, and plugins are disabled; the document cannot navigate its parent page.
HTML policy and secret checks reject unsupported or high-risk content before storage.
V1 browser policy
Self-contained does not mean executable.
The release-safe profile supports responsive HTML, inline CSS, same-document fragment links, native controls such as details, and embedded media. All JavaScript is rejected at publication, while runtime CSP still enforces script-src 'none' inside a sandbox with no permission tokens.
ALLOWED
- Inline HTML and CSS
- Semantic and responsive layouts
- Same-document fragment links
- Data images
- Data fonts and media
- Native HTML controls
BLOCKED
- Scripts & event handlers
- Network requests
- Forms & password inputs
- Popups & downloads
- External or active URLs
- Frames & objects
- Service workers
Retention boundaryGone from the web first.
Gone from the web first.
Cleaned from storage next.
Shared content stops
The cookie-free renderer inside the fixed branded wrapper immediately returns 410 Gone. The noindex wrapper remains a 200 shell so it can display that tombstone; user content is no longer publicly available.
Object cleanup
A deletion queue and R2 lifecycle policy remove payload objects. Reconciliation catches partial failures.
Metadata tombstone
Minimal non-content metadata can remain for abuse controls, audit, and deletion reconciliation.
Database history
Cloudflare D1 Time Travel may retain recoverable database history according to the platform's service window.
Important boundaries
What “unlisted” means.
Artifact URLs are bearer links, not access-controlled private documents. Anyone who receives a share URL can view it.
Artifact, collection, error, and expiry responses carry X-Robots-Tag: noindex, nofollow, noarchive, nosnippet, noimageindex. They are not included in Linkifact sitemaps or crawlable marketing links. A robots directive is a request to compliant crawlers, not a confidentiality mechanism.
Do not publish credentials, personal data, confidential source code, or anything whose disclosure would cause harm. Linkifact scans for common secrets, but no scanner is perfect.
Session bundles are also unlisted bearer links and carry the same noindex response policy. Export recognizes and redacts common credential and absolute-path patterns. Structured adapters omit recognized tool turns by default, while opaque Markdown can contain tool or terminal output. The publisher must review the entire bundle because unknown sensitive content can remain.
Imported sessions are injection-warned continuation context, never trusted instructions or restored authorization. Linkifact does not write native harness session stores or claim exact resume behavior.
Responsible disclosure
Found a way through the box?
The monitored security mailbox is still being activated. For shared-content concerns, use the Report action on the affected Linkifact page. Until a verified security address appears here, do not send vulnerability details to a guessed address and do not access other people’s data or disrupt the service.
SECURITY CONTACTDedicated mailbox pendingOnly verified contact details will be published here.
Publish with clear boundaries
Make the artifact. Keep the permissions small.
Create a free account to publish sandboxed artifacts, organize collections, and share reviewed session context.