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. 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. Separately, the selection is read once, at the moment you tap the voice shortcut with a selection, only for that rewrite; and after insertion Pressay briefly watches the edits you make to the text it just wrote, to learn your own words, all of which you can delete on the dictionary page. For the technical detail of each processing step, see Data controls.

What we collect

Account information

Pressay supports one-time email codes, with Google and Apple sign-in also available on the website, desktop, and mobile apps. The selected provider handles its hosted sign-in; Pressay receives your verified email and provider account identifier and stores the account link and accepted terms and privacy versions, never Google or Apple tokens or passwords. Temporary authorization flows expire within 10 minutes; sign-in tickets and website handoff tickets expire within 60 seconds and are cleaned up after expiry. Account links and consent records are deleted with your account.

Billing

Stripe hosts payment details and processes payments, subscriptions, invoices, and refunds under its own privacy policy. Pressay does not store card numbers, CVCs, or Alipay credentials. We retain only necessary financial account links, transaction references, orders, subscription and service periods, amounts, tax details, legal acceptance versions, refunds, disputes, and processing records.

Deleting an account removes its login association and ends future billing; it does not delete legally required financial records. Restricted financial records are normally retained for seven years after the related transactions finish, and longer where legal obligations or holds require it. Completed operational tasks and minimal event records are retained for 90 days unless needed to support a financial decision. Anonymous cumulative monthly and annual paid-user counts are retained long term. These records are not used for marketing or to restore a deleted account.

Voice and text

The audio you deliberately record by tapping the shortcut; the selection you hand over by selecting text and then tapping; and the rewrite instruction you speak afterwards. 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 the current command. History can keep the original selection, instruction, and result on this device, subject to how long you choose to keep history and your deletion settings; the cloud does not keep them. A request carries the highest-ranked entries from your dictionary so that recognition and refinement use the spellings you specified; those entries are sent with the request to the selected speech-recognition and text-processing services; an entry carries only the word form itself, never the text you learned it from. Live audio goes directly to the speech-recognition provider under a short-lived, session-scoped grant, without passing through Pressay application servers. On macOS, Windows, iOS and Android, confirmed recordings are saved locally for playback and recovery, including after text is successfully 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. If the app is closed when they expire, they are removed 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. Mobile does not automatically resume after its process is interrupted; you can retry from the local recording. Pressay’s servers process the transcript only for as long as the current refinement requires and never write it to Pressay’s content database. 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.

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

To understand whether Pressay is reliable, we record first use, activity when starting input or bringing the main window to the foreground, and whether a voice task succeeded or failed when it ended. These records include the platform, client version, and elapsed time from stopping to delivery and the complete reply. We also keep stop latency diagnostics (task identifiers, processing times, character counts, model identifiers, token counts, and fixed error codes) for 60 days, deleting them with your account. These contain no audio, transcripts, field contents, application titles, or screen content. They go only to Pressay’s service, with no third-party analytics.

Onboarding survey

Before first-time setup finishes on desktop, Pressay asks how you heard about Pressay, your role, and your industry. Each question takes a single answer from a fixed list; if you choose “Other”, you can add a short note of up to 28 characters. The platform and interface language you answered in are recorded with it. The answers are stored with your account and deleted together with it.

Website access data

Visits to pressay.ai generate basic access logs without voice or dictation content, while optional website analytics follows regional defaults and your choices; see our Cookie Policy for details and settings.

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
• Understanding how you heard about Pressay, your role, and your industry, to improve and promote the product

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: audio does not pass through Pressay application servers, and audio and transcript content are not written to Pressay’s content database. Local recordings remain available 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. Audio files for recovery are sent directly to the audio-processing provider without being stored in AWS S3. Recognition results are saved locally before text refinement. Provider data processing is governed by its service terms.
• Account, usage, and onboarding survey answers: kept while your account exists and deleted together with it. Necessary Admin audit records are kept, but your email address is anonymized. Product analytics: ordinary event details are kept for 60 days, first-use records for the life of your account, and daily user activity for 13 months. These account-linked records are deleted when you delete your account. Historical monthly active-user counts and registration-week retention counts contain no account identifiers and are retained long term.
• History: stays only on your device, for as long as you choose to keep it.

Third-party services

Speech recognition: your voice and dictionary words go from your device directly to Soniox (US). If you choose Alibaba Cloud Model Studio in Settings, that dictation is processed by Alibaba Cloud in Beijing, China.

Text refinement: the recognized text, dictionary words, the context read when you dictate (on desktop, the text available in the current app and window; on mobile, the text before and after the cursor in the current field), and any text you select to rewrite are sent to Amazon Web Services (Amazon Bedrock, US) and processed by models from OpenAI or xAI.

Login code emails are sent through Resend, which receives only your email address and the code.

Each of these services receives only the data needed for the corresponding request. On mobile, Pressay lists these recipients before you first use voice and sends nothing until you agree.

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.