Scriptus
RUEN

Document

Privacy policy

Three separate places: your Mac, the Scriptus server with its recognition and text processing providers, and account storage. Here is what goes into each.

Draft for legal review. The data controller, jurisdiction and legal entity details will be stated after review.

Updated:

1. What stays on your Mac

Dictation history, dictionary, settings and your own provider keys are stored locally in the app. Keys are stored encrypted in the macOS keychain. This data is never sent to Scriptus. You delete it yourself, in the app or by removing its data.

2. How dictation works with Scriptus access

This is the default path in app version 0.3.0 and later.

  • The app records the whole utterance and sends the audio to the Scriptus server (a Cloudflare Worker). The server forwards it to Groq for speech recognition (model whisper-large-v3-turbo).
  • The app sends the recognised text to the Scriptus server, which forwards it to Anthropic Claude (Haiku) via OpenRouter. The model only adds punctuation and capitalisation, fixes obvious misspellings and removes hesitations such as “uh” and “um”; it is not asked to reword the text.
  • The Scriptus server stores neither the audio nor the text: they pass through it only while the request is processed. Processing at Groq, OpenRouter and Anthropic follows those providers' terms.
  • File transcription on the website and in the app takes the same path: the audio goes in parts through the Scriptus server to Groq. The finished transcript is stored only in your browser (on the website) or in the app's notes on your Mac.

3. Older app versions

Versions before 0.3.0 stream audio directly to Deepgram using a short-lived token issued by the Scriptus server. In that case the recognised text does not reach the Scriptus server. We recommend updating.

4. Your own key

If you enter your own provider key in the settings (for example Deepgram, Groq or OpenAI), the app talks to that provider directly. Audio and text do not reach the Scriptus server, and processing follows that provider's terms and your agreement with it.

5. What Scriptus stores

Scriptus servers store only account and Scriptus access data:

  • Account: email address, user identifier, sign-in and account creation times.
  • Plan and invitations: which invite code was redeemed and when, the current plan and limit, including administrator overrides.
  • Access requests: when you sent one, your comment on it (if you wrote one) and the administrator's decision.
  • Usage metadata with Scriptus access: word count, audio duration, time, outcome (completed, cancelled, failed), app version and which provider account served the request. It is used for the weekly word limit, the stats on your account page and abuse prevention. Your account page shows your own dictation stats for the last 30 days, as counts only.
  • An administrator flag for accounts that manage invitations and limits.
  • Access change history: administrator and user identifiers, action, access state before and after, timestamp and the reason entered by the administrator.

6. What Scriptus does not store

  • Audio or audio fragments.
  • Recognised or cleaned-up dictation text, and clipboard contents.
  • Names of the apps and documents the text is pasted into.
  • Your own provider keys.

7. Email and sign-in

Sign-in emails with a link and code are sent by the authentication provider (Supabase Auth) on behalf of Scriptus. The address is used for sign-in and support correspondence. There are no newsletters.

8. Website, cookies and analytics

The website loads no third-party scripts, fonts or trackers and sets no tracking cookies; fonts are served from the website itself. Sign-in session data is stored in your browser and removed on sign-out.

The account page requests the latest app version number from the public GitHub API (api.github.com) without cookies. GitHub sees ordinary request data such as your IP address. App builds and updates are also hosted on GitHub.

9. Retention and deletion

Account data is kept while the account exists. Deleting the account from the account page removes the email address, plan, invite redemptions and usage metadata. The invitation's use counter remains as a number with no link to you. Local data on your Mac stays with you.

Access change history, including original identifiers and reasons, is not automatically removed with the account. Its retention period must be approved before public beta.

10. Your rights

You can request what data is stored, correct your email address or delete your account. Write to support from the account address, or delete the account from the account page.

Questions about data

Write to support@scriptus.online.