Privacy policy

This policy explains how Pressay (“we”) collects, uses, and protects your information when you use the Pressay apps and the pressay.ai website. The governing rule is simple: Pressay processes only the audio and text you deliberately hand to it. The current Pressay candidate does not read existing field text, screen text, or selected text by default, and it does not monitor edits you make after insertion. For the technical detail of each processing step, see Data controls.

What we collect

Account information

Your email address. Pressay signs you in with a one-time email code instead of a password, so we hold no passwords at all.

Voice and text

The audio you deliberately record by tapping the shortcut, and the text you hand to the Pressay composer, whether dictated, pasted, or typed. We collect no context from the target application: we do not read the text in the app you are using, its screen content, or your selection. A request carries the highest-ranked entries from your dictionary so that recognition and refinement use the spellings you specified; those entries contain no history text, are not persisted on the server, and are discarded when the request ends. Raw audio travels from the client directly to the selected speech-recognition provider under a short-lived, session-scoped grant. It does not pass through Pressay’s servers and is not persisted on the client. Pressay’s servers process the transcript only for as long as the current refinement requires and never write it to Pressay’s content database.

Usage data

The word count, duration, and operation of each use. We use it to calculate your allowance and to show you your own statistics inside the app; it contains no voice or text content.

Limited product events and Pro notices

To confirm that the core experience is reliable, we record a limited set of content-free events, such as the composer opening, direct insert succeeding or failing, and the platform and client version. We do not record audio, transcripts, field contents, application titles, or screen content. Whether a direct insert succeeded and whether you reached an allowance limit are service events and are always recorded; the remaining improvement events can be switched off in the desktop app under About → Diagnostics → “Share usage events”. All events go only to Pressay’s own service, with no third-party analytics. When you register for the Pro launch notice, we store your email address, language, source, and the time you registered.

Website access data

Basic access logs generated when you visit pressay.ai. They contain no voice or dictation content.

How we use it

• Providing recognition, refinement, and translation
• Calculating and enforcing the usage allowance of your plan
• Sending login codes and essential service messages
• Diagnosing failures and improving product reliability

We do not use your content to train Pressay’s models, and we do not sell it to any third party.

How long we keep it

• Voice and text: raw audio never passes through Pressay’s servers; neither audio nor text is written to Pressay’s content database, and both are processed only for as long as the request requires.
• Account, usage, and product events: retained while your account exists and deleted together with it, including any Pro-notice registration under the same email address. Necessary Admin audit records are kept, but your email address is anonymized.
• History: stays only on your device, for as long as your own retention setting says.

Third-party services

We use third-party speech-recognition and large-language-model services to perform recognition and refinement, and a third-party email service to send login codes. Each of them receives only the data needed for the corresponding request.

Security

Network requests are encrypted in transit with TLS, and the server stores only an irreversible digest of each session token. Login credentials are kept in the private application-data directory of the current system user, where the interface layer cannot read them, and internal access is granted on a least-privilege basis.

Your rights

You can review your usage, delete your account, and clear local history inside the app. To request access to or correction of your account information, write to support@deepflywheel.com.

Changes to this policy

When this policy changes, we update the date shown at the top of this page; where the change is material, we also notify you separately.