Data controls

Pressay uses your microphone, and when you confirm delivery it writes text into the app you are working in. This page states the boundary precisely: what Pressay can see, what it cannot, where your data is used, and where it goes afterwards. In one line: Pressay sees nothing until you start it, and does nothing until you confirm.

The current Pressay boundary: when it reads, and what

By default Pressay writes text only when you confirm; it reads from the target app in exactly the three ways below and in no other:

• Dictation context.When you start dictation, desktop can read the current app, window, available page information and text; mobile reads only the current keyboard field and its surrounding text, for this dictation’s cloud text refinement. Availability depends on the system and app. No screenshots or keystroke logs are taken, and context is not added to history or the dictionary. iOS hands it over in a protected temporary run file, removed through run consumption and cleanup.
• The selection is used for this command. Pressay reads the original selection when you tap and checks it again before insertion. History can keep the original selection, spoken instruction, and result on this device, subject to how long you choose to keep history and your deletion settings.
• After insertion it briefly watches your edits, to learn words. After text is written into your app, Pressay keeps an eye on the edits you make to that text — until 15 seconds pass without further edits, you move elsewhere, clear the field, or press Enter — to learn your own names and words. During that window the text in that field and the app you are using are sent to the cloud, processed in real time, and discarded as soon as the result returns; nothing is stored, logged, or used for training. All that remains is the learned word: every one of them sits on the dictionary page, where you can delete it at any time.

There is exactly one explicit path on the write side: tapping the shortcut again confirms direct insert. Dictation Mode and Command Mode both insert text and neither sends it for you; a rewrite replaces only the selection frozen when you tapped, re-reads the selection before writing and compares it word for word, and if it no longer matches it writes nothing and the result goes to the clipboard and history instead. Esc only aborts the active Dictation or Command session and writes nothing. Cloud processing for this request uses the audio, selection, and instruction you give Pressay, together with the dictation context described above. When the desktop app uses the system accessibility APIs (AX/UIA) to insert, it reads only the metadata delivery requires — whether a focused target exists, whether it is editable, whether it is a secure field — plus the selected text at the moment you tapped; during the observation window after insertion it additionally reads that one field’s text and the context around the cursor, released as soon as the window ends and never written to disk or logs.

Context capabilities in the future

As an AI composer, Pressay may support questions and tasks in the future, but “understanding more context” will never be implemented as silent background reading. Any new context must become an input that is visible in the interface, reversible, and bound to a specific task; the current candidate has no such reading path.

When the microphone is on

By default the microphone runs only during voice input that the interface visibly shows. The sole exception is iOS Always Ready, which you enable explicitly: the main app keeps the microphone channel open for up to 12 hours, the system microphone indicator and the Live Activity stay visible, and standby audio is discarded on the device immediately — never saved, never transcribed, never sent over the network. Tapping enters visible continuous dictation until you tap again or press stop. The capsule appears only while a dictation is running; clicking it only finishes or aborts that one and never starts recording. Any brief pre-roll audio used to cut first-word latency stays in private memory and enters real processing only after you confirm with a tap.

Ownership and how long data is kept

Your content never enters Pressay’s database

Live audio goes directly to the speech-recognition provider. Confirmed local recordings remain available locally for playback and recovery after text is inserted, copied, or recovered. Recordings follow your Keep history setting: Forever keeps them without automatic expiry, and Never immediately deletes existing recordings and stops saving new ones. You can also delete them earlier. Expired recordings are removed while the app is running, or when it next opens. When file recovery is enabled, you can send a complete recording of up to 9 minutes directly to the audio-processing provider to obtain the full transcript, without audio passing through Pressay application servers. Recognition results are saved locally first; provider data processing is governed by its service terms. Transcripts and refined results are never written to Pressay’s content database and exist only for as long as the current request requires. The cloud persists necessary billing and subscription records, your email address, account and preferences, login sessions and email-verification records, content-free usage, limited product events, file-recovery task metadata, stop latency diagnostics, onboarding survey answers, daily user activity and anonymous monthly activity and registration-week retention counts, dictionary entries, dictation channel tickets (holding only a ticket hash and expiry, at most 10 minutes), administrative audit records, and a request digest used to prevent duplicate processing — that digest holds only a request id, a request hash, and a processing state, and no audio or text. Production logs record no audio, no transcripts, no verification codes, no sessions, and no model prompts; server access logs do record access metadata such as IP address and browser identification, for security and troubleshooting.

Never used for training

Pressay does not train models on your voice or text. The speech-recognition and text-processing services we use commit in their terms of service not to use request content for model training; a link to each provider’s privacy policy is listed in the app’s speech-service settings.

No selling, no tracking

We do not sell user data, run advertising, or track you across apps. This website uses no advertising or personalization cookies. Website analytics follows regional defaults and your choices, as described in our Cookie Policy. Pressay’s future revenue will come from software services, not from user information — that is not merely a promise; it follows from the business model itself.

Where processing happens

In the current version both speech recognition and text refinement run in the cloud, so a network connection is required. That is a property of the current implementation, not a comparative claim about on-device processing; we publish when data is sent, how it is processed temporarily, and where it is deleted, and both input and insertion remain triggered by you.

Data on your device

History and dictionary

History stays on your own device. It is not uploaded, and it is not synced to your other devices. The history list shows the final result. Command details also keep the original selection and spoken instruction; all expire or are deleted together. History does not keep intermediate dictation versions. Desktop also keeps failed or cancelled recordings for recovery, for as long as you choose to keep history and separate recovery and deletion controls. Expired recordings are removed while the app is running, or when it next opens. Recovered raw text is saved locally first to prevent another loss. If refinement fails, any recoverable text is kept so you can retrieve it. Dictionary entries do sync across your devices: the cloud holds only the word form, the misheard forms, the source, usage counts, and deletion markers — never any text. You decide how long history is kept; setting Keep history to Never deletes existing entries, recordings, and recovered text permanently and immediately, and stops saving new recordings. Whether uninstalling also removes local data depends on the operating system, so uninstalling is not a reliable way to delete data.

Where dictionary entries come from

The dictionary supports manual additions and automatic learning: you can add terms on the dictionary page, and Pressay learns from your corrections to inserted text. That judgement happens in the cloud: only the text of that insertion, the contents of that field before and after, and the app you are using are uploaded, processed in real time and discarded as soon as the result returns; every learned entry sits on the dictionary page and can be deleted at any time. Pressay does not infer entries from your rewrite instructions or from your history. Entries are created on your device and sync to your other devices with your account; a deleted entry never appears in any later request.

Login credentials

Login credentials are written to the private application-data directory of the current system user. Inside the app, only the main process can read them; the interface layer cannot.

Deleting your account

Deleting your account immediately ends service and future billing without an automatic refund. Financial records lose their login association and remain restricted where legally required. Deleting your account clears the server-side account, login sessions, verification codes, usage, product events, onboarding survey answers; necessary Admin audit records are kept with the email address anonymized. Only after the server confirms success does the app clear local login state, history, and dictionary. If that cleanup fails, we keep your local data and tell you plainly rather than pretending it succeeded.

Third parties

Pressay uses third-party speech-recognition and large-language-model services to perform recognition and refinement. We send them only the audio and text you deliberately handed to Pressay, those services commit in their terms of service not to use request content for model training. Providers change as the service evolves; material changes are published on this page.

Contact us

If you have any question about how we handle data, write to support@deepflywheel.com.