Plainsong keeps the public site stack small.

Only what serves the leaf is named here.

Plainsong's public site is hosted on Cloudflare Pages. Cloudflare may process routine request metadata, such as IP address, user agent, request time, and security signals, to deliver and protect the site.

The current public site does not run account creation, payment checkout, hosted transcript storage, or cloud transcription. Core product positioning remains local-first desktop capture, transcription, review, and export.

If Plainsong later adds hosted accounts, payments, cloud transcription, sync, or team features, this disclosure should be updated before those services receive production traffic.

That is the same trust boundary described across the Plainsong launch pages. Public marketing can explain local-first transcription clearly without pretending that optional cloud features already exist or that hosted transcript storage is part of the current public site.

This disclosure should stay boring and specific. If a service only hosts the public website, say that. If a future service receives audio, transcripts, account records, support messages, payments, or analytics, name it before launch and explain what data it handles. That keeps the product story aligned with the privacy promise.

The current public site should therefore be read as a launch and trust surface, not as a hosted transcript platform. Cloudflare serves the pages, visitors read the product notes, and any future service that touches user-created audio or transcript content should be added here before it is part of the production workflow.

This page is also a promise about naming the boring parts of the stack. If Plainsong later depends on a storage provider, payment processor, support desk, analytics service, or hosted speech model, the disclosure should identify that service and the narrow purpose it serves.

For questions about subprocessors or data handling, use the Plainsong contact page.