You can read Ptichi without an account. This website does not ask for microphone access, record your voice or accept audio uploads. Its audio player plays a clearly labelled demonstration file.
Product
Privacy, without the fog
What happens when you read Ptichi, play a demonstration or contact the project.
What the website does
The current site has no sign-up form, checkout or advertising tracker. Optional Google Analytics is managed through Google Tag Manager and stays off until you choose “Allow analytics”. Before that choice, the site sends no analytics request to Google. A denied or granted choice is stored in your browser so the site can respect it; no advertising profile is created. Fonts, illustrations and demo audio are served as site assets.
Opening a webpage still sends a network request. Hosting infrastructure receives information needed to deliver and protect the service, such as an IP address and request details. Ptichi uses Vercel; its privacy notice describes the provider's practices. This page does not promise that hosting logs are absent or assign them an unverified retention period.
Website, search engine, desktop app
These are different boundaries. Search engines can discover public page addresses through a sitemap or a URL submission. That does not require sending a reader's voice or exercise text.
The desktop product is being built with local recording and core acoustic analysis by default. That is a product design boundary, not a claim that every future integration will work offline. Any optional service that sends content elsewhere needs its own clear explanation and choice before use.
Contact and external links
Our current contact route is a public GitHub issue. Posting there shares the text and attachments with GitHub and the public. Please do not include recordings, client names, confidential work text or credentials. The contact page explains what is useful to send instead.
Following an external source takes you to another service with its own policies. A link is not an embedded tracker on this page.
Changes and questions
If a future feature needs accounts or feedback collection, this explanation must change with that feature. The review date records the version described here, not a permanent guarantee. For a general question, use the public contact route without personal details; we do not currently offer a private support upload channel.
Reviewed: