Privacy

PromptStage is designed to be privacy-conscious by default.

The product is built around low-friction utility use. That means keeping data handling narrow, avoiding unnecessary storage, and being direct about what the current product does and does not retain.

Current handling

What PromptStage processes right now.

Pasted HTML

When users paste HTML, the app processes that content to generate cleaned Markdown output. PromptStage does not present itself as a long-term storage system for pasted source material.

Public URL fetches

When users submit a public URL, the server fetches the page content to run the cleanup flow. Fetch safeguards are in place to reject private-network targets and unsupported protocols.

Generated output

Generated Markdown and related exports are returned to the user as part of the active session flow. PromptStage is not currently positioned as a saved-history product.

Analytics

Analytics are meant to describe product usage, not user content.

PromptStage currently uses lightweight first-party analytics events for product behavior such as conversion attempts, outcomes, copy actions, and export actions. These events are intended to support product QA and workflow understanding rather than to capture the body content users submit.

What analytics are for

Understanding whether core actions work, where users succeed, and where they encounter failures or friction.

What analytics should not include

Pasted HTML bodies, fetched page bodies, or generated Markdown content as part of ordinary product event tracking.

Future changes

If PromptStage changes its analytics or data handling approach materially, this page should be updated so the public description stays accurate.

Advertising and third parties

Future advertising disclosures will be added here before monetization goes live.

PromptStage's strategy calls for delayed, careful monetization. If Google AdSense or other advertising tools are introduced, this page should be updated to describe ad-related cookies, third-party behavior, and any required consent or region-specific disclosures before those placements are active.

Ads are not the current product focus

Monetization is planned to follow trust, usability, and content maturity, not to get ahead of them.

Questions or corrections

Use the contact page if you need to ask about data handling or want to flag something that should be clarified.