YOUR DATA & YOUR CHOICES
Privacy policy
Updated October 12, 2026
AudioScript is developed by Amit Cohen Raab for turning screenplays into directed audio. This policy covers the desktop production application, AudioScript Reader, and their pages at amitcohenraab.com/audioscript. The desktop application verifies your Google Drive account during initial setup. After setup, connection problems or reconnect requests do not block local reading or production. Synchronization, cloud backup and the Reader require a working Google connection.
Data the application uses
AudioScript stores the screenplays you import, extracted text, project and draft information, performance direction, voice selections, generated audio, playback timing, production progress, and recovery history on your computer. It uses this data to provide the production and playback features you choose.
Connecting Google Drive
You connect your own Google account through Google's authorization screen. The desktop application requests the https://www.googleapis.com/auth/drive.file permission, which covers files the app creates and files you explicitly authorize it to use. The desktop application does not request unrestricted access to the contents of your Drive.
The connection lets AudioScript find or create an AudioAppDB folder, organize project folders, upload and download project files and snapshots, and provide optional synchronization and backups. Those files may contain your imported scripts, direction, audio, and associated project metadata. Once you connect, the app exchanges project versions while it is open, uploading only files that changed. Drive keeps each version for 180 days and then one a month; older versions are moved to your Drive trash. A separate option can upload ZIP backups of completed productions.
AudioScript also reads your Google account's display name and email address through Drive to label the connected account in the app. It stores that label with the authorization on your computer. It never receives your Google password.
Where data is stored
The separate web/mobile Reader requests the same limited permission, https://www.googleapis.com/auth/drive.file, for AudioScript files: AudioAppDB, synchronized project versions, screenplays, completed audio, listening positions, marks and notes. It cannot see unrelated Drive files. The Reader saves positions, marks and notes and performs no audiobook speech generation.
The Reader loads project data and audiobook audio directly from Google Drive into your browser. Device storage keeps library snapshots, opened screenplays for offline reading, account labels, favorites and reading/playback positions. The service worker caches the application interface and audio that you explicitly save for offline listening. Notes and original recording chunks use separate account-bound storage. Remove offline copies clears disposable caches; sign-out hides private library data while preserving pending notes and marks under their original account.
Local project files and recovery copies remain in the application's data folders. Google access and refresh tokens are stored in your operating system's credential store, such as Windows Credential Manager or macOS Keychain, separately for each installation. Desktop production provider API keys are also stored in the operating system credential store.
If you enable Google Drive features, copies are stored in your chosen Google account and may be downloaded to other AudioScript installations that you connect to that account. The Reader's sign-in service exchanges Google authorization codes and refreshes access tokens on the site's Cloudflare server. It encrypts the refresh credential into a Secure, HttpOnly cookie bound to this website; browser JavaScript cannot read that cookie. A Reader sign-in lasts 90 days from sign-in, and Google may expire or revoke authorization sooner. The encryption key and OAuth client secret are Cloudflare secrets. Short-lived access tokens remain in browser memory. Ordinary project reading and audiobook playback transfer directly between Drive and your browser. Notes use the separate server storage described below. No separate website password is required. AudioScript does not automatically make Drive files public or change their sharing permissions.
Notes and recordings
When you record a note, AudioScript stores its original audio, timestamps, screenplay position and transcription. Manual text edits keep previous revisions. Notes synchronize through an account-bound service hosted on Cloudflare to the notes folder inside your existing AudioAppDB folder in Google Drive. Drive stores recordings, note events, original provider receipts and generated documents. Cloudflare retains account-bound job metadata and temporary transfer data until the Drive copy is verified, allowing accepted work to continue when your desktop is closed. No Notes files are stored in Cloudflare R2. Groq credentials and ChatGPT authorization are encrypted on the server with a separate secret key; provider credentials are not stored in browser local storage. A Google grant used for pending Drive synchronization is also encrypted on the server.
Recordings are sent to Groq for transcription. Only when you choose Send to AI are the selected notes, their positions, your additional prompt and the full original screenplay sent to OpenAI through your connected ChatGPT account. The selected model and output language are recorded with the result. Original notes and recordings remain separate from edited documents. These providers process data under their own account settings and policies. Connecting ChatGPT alone does not generate a document.
Notes, recordings, revisions, generated files and unfinished jobs have no automatic expiry or deletion policy. Clearing offline caches, signing out, changing accounts or restoring a production snapshot does not delete them. Pending device work stays associated with the original account for continuation or recovery download. Removing browser or operating-system storage outside AudioScript can remove local copies. Use Delete beside a note to remove its recording and revisions, or beside an AI result to remove that request's saved input and result. More → Clear all removes the open draft's notes and AI work. These removals synchronize with the Notes service, Drive and connected devices; offline devices apply them when they reconnect. Pending remote deletion remains visible until cleanup finishes. Content-free deletion records prevent an older offline copy from restoring deleted material. Files you have separately downloaded or shared remain in their chosen destinations.
AI and speech services
When you request analysis or speech generation, AudioScript sends the relevant script text and directing information to the supported provider you selected and connected. Depending on your configuration, this may use Codex (OpenAI), Claude Code (Anthropic), Antigravity (Google), Grok (xAI), and Speechify for speech. Codex and Grok run only after you allow them in the app. These services process requests under their own account settings and policies. Connecting Drive alone does not start analysis or speech generation.
AudioScript uses Google data only to provide the features you request. It does not sell Google user data, use it for advertising, or use it to develop, improve, or train generalized AI or machine-learning models. Transfers to a selected production provider are limited to the data needed for the analysis or audio feature you request.
We follow the Google API Services User Data Policy, including its Limited Use requirements.
Retention, Trash, and deletion
AudioScript's Trash offers a 30-day restoration window for deleted projects, screenplays, drafts, direction and audio. After those 30 days the files are removed from your computer and are no longer synchronized. Local recovery copies keep the newest 30 versions of each project and one a day for 30 days; older copies, and productions replaced by newer ones (the current one and the two newest are kept), are removed automatically. In Google Drive, versions older than 180 days are moved to your Drive trash, except one a month. Exported ZIP backups stay until you delete them.
To erase all copies, pause synchronization on your connected computers and remove the corresponding project data, recovery copies, exports, and Drive copies you no longer want. Google's own Trash and retention rules also apply to files removed through Google Drive. The developer cannot delete files in your account or on your devices on your behalf.
Disconnecting and revoking access
In the Reader, Sign out of this device hides private local library data, preserves pending account-bound notes and marks, then ends the device connection and revokes the Reader's Google authorization; when offline, revocation happens as soon as the device is online again. It does not disconnect the desktop app or other devices. Reconnect the original account to continue pending synchronization. Disconnecting Groq or ChatGPT removes the service's saved provider connection without deleting original notes or previously received results.
Disconnect Drive in AudioScript removes that installation's saved Google authorization and pauses its synchronization and automatic backups. It does not delete your local or Drive files, and it does not disconnect your other installations. You can revoke Google's authorization for AudioScript from your Google Account connections. Reconnecting requires your consent again.
This website and support
The information pages do not include advertising, analytics scripts, or a Google sign-in form. Cloudflare hosts the pages and processes ordinary connection information, such as IP addresses and request details, to deliver and protect the website.
For privacy questions, use the user support email displayed in AudioScript's Google authorization screen, or the developer contact through which you received the desktop app. Please do not send passwords, authorization tokens, or private screenplays in a support request. If you contact the developer, the information you choose to send is used to address your request.
Changes
Updates to these practices will be reflected on this page with a revised effective date. Material changes to Google data access or use will be disclosed before the changed feature is enabled and will request consent where required.