Public website analytics
We use Ahrefs Web Analytics on public pages to understand visits, referral sources, approximate city or country, browser and device information, and common interactions such as link clicks and form-submission events. Ahrefs describes this service as cookie-free and says it discards raw IP addresses after processing. See how Ahrefs Web Analytics works.
This tracking is disabled for signed-in visitors, the private rehearsal app, and the feedback page. It is separate from the optional rehearsal measurement described below.
Early-access requests on this site
The early-access form on cueroom.studio stores your email address, consent text and version, and submission time in this site’s WordPress database. These requests are available to site administrators, who can review them for beta invitations and related testing emails. Submitting a request does not create an account, grant app access or send an automatic email.
The form uses short-lived rate-limit records derived from an IP address. The plugin does not retain the raw IP address; the hosting provider may keep separate request logs. Requests remain until removed following a verified request or an applicable account cleanup. Hosting backups may retain earlier copies. Contact the site owner below to ask for your request to be removed.
Feedback and bug reports
The feedback form stores your selected feedback type, message, optional reply email, optional device/browser description, and submission time privately in WordPress. Messages sent from the rehearsal app also include that source label and the app version. Site administrators can review submissions and track their review status.
Your email is optional and is used only to follow up about your feedback. The form does not automatically attach scripts, microphone audio, or recordings, and does not subscribe you to marketing emails. Short-lived hashed network identifiers help limit spam; raw IP addresses are not stored with feedback records. Feedback remains until removed following a verified request or an applicable account cleanup, and hosting backups may retain earlier copies. Send feedback, or use the contact below to request removal.
Earlier beta requests and scripts
Requests and scripts previously submitted on the original CueRoom beta service remain with that service and have not been transferred into this WordPress site. Contact the site owner below for questions about those earlier records.
Accounts, purchases and access
If you create or use a CueRoom account, we store your name if provided, email address, account identifiers, email-verification state, and the time and version of your terms acceptance. Account information supports sign-in, account management, access to services, and abuse prevention. Password setup and verification messages are sent to your email address. Sign-in uses authentication cookies. Short-lived hashed identifiers limit signup abuse; raw IP addresses are not stored in signup records.
The Android sample can be rehearsed without an account. Account information is needed when you choose account features, including an account trial, purchase verification, the online library, or Studio voices. Features and signup availability may differ during testing.
Google Play processes Android purchases made through Google Play. CueRoom receives purchase identifiers and tokens, product and purchase status, and account-linked access information to verify purchases, restore access, and prevent fraud. It does not receive your full card number or card security code from Google Play. Google’s handling of its payment and account records is described in the Google Privacy Policy.
Stripe processes website purchases and subscriptions. Checkout sends your account email and internal account/order identifiers to Stripe, which collects payment and billing details. CueRoom stores customer, purchase, subscription and invoice identifiers, payment/access status, and Studio character usage for each billing period. CueRoom does not receive or store full card numbers or card security codes. See Stripe’s privacy policy.
Android device registrations and account activity
To register devices, enforce account device limits, check trial or purchase access, and prevent abuse, the Android app sends CueRoom an app-and-site-specific hashed identifier derived from Android’s device identifier, plus the device manufacturer and model. This registration does not use an advertising ID, IMEI, serial number, or your personal device name. A hashed identifier linked to your account is still account data, not anonymous data.
Access checks can continue using a saved purchase-access receipt after you sign out. Signing out does not by itself remove the device registration or locally saved rehearsal access. You can manage registered devices through your account.
CueRoom records account-linked last-sign-in and recent-activity times for service administration and understanding account use. These records are separate from the optional web rehearsal measurement below. They do not contain microphone recordings or recognized speech.
Scripts, documents and images
Android can keep imported scripts and rehearsal settings on your device. Reading a file or recognizing text in a script photo locally does not, by itself, upload it to CueRoom. When you choose an online account feature, such as saving to your online library or claiming a saved trial excerpt, the relevant script data is sent to CueRoom.
Your online library can contain script titles and dialogue, roles, rehearsal position, bookmarks, reader preferences, and uploaded originals such as PDFs, text documents, and script photos. We use this information to import, save, synchronize and rehearse your scripts. Online scripts and originals are stored privately with your account, not in the public WordPress Media Library. Authorized site and hosting administrators can access stored data for administration and support.
Studio reader voices
When you audition or rehearse with Studio AI, or choose Best available and Studio is used, CueRoom sends the requested dialogue and voice settings through its server to ElevenLabs to generate reader audio. During rehearsal, it may prepare the next reader line in advance. This sends script text, not a recording of your microphone.
Generated audio is saved privately with your account. Purchased-account audio is retained within your account storage allowance; beta-only cached audio becomes eligible for cleanup after seven days. Replaying matching saved audio can avoid another generation. New generation and previews use your available character allowance.
ElevenLabs can retain generation history. Its retention and any permitted model-improvement use depend on its policies and the applicable service settings; this notice does not promise zero retention or that model training is disabled. See ElevenLabs’ Privacy Policy and its data-use explanation. CueRoom’s account-deletion process includes provider-side Studio generation records held on CueRoom’s behalf.
Device reader voices
Device voices use your Android or browser text-to-speech service. Depending on the selected voice and service, script text may be processed on your device or sent to that provider. Choosing Device voices avoids ElevenLabs, but is not a guarantee that every device voice works offline. The selected speech provider’s privacy policy and settings apply.
Microphone cues and Android speech recognition
Microphone cues are optional. The Android app explains their use before requesting microphone permission. Voice control starts off when the app reopens, and you can rehearse with the microphone off by tapping Next. When enabled, CueRoom listens during your turns to recognize when you finish a line, closes the microphone before the reader responds, and stops listening when the app goes into the background.
CueRoom first attempts on-device recognition when supported. If suitable on-device recognition is unavailable, it can use the default Android speech-recognition service, which may send your microphone audio to its provider’s servers. The provider can vary by device and settings; it may be Google or another installed service. CueRoom therefore does not promise that speech recognition always stays on your device.
CueRoom uses recognized words in memory to follow your cue. CueRoom does not save microphone recordings or recognition transcripts, and does not upload them to its own server or to ElevenLabs. This describes CueRoom’s handling only: the Android speech provider controls its own processing, retention, and any additional uses under its privacy policy and settings. We have not verified a single retention period covering every supported provider, and do not promise that all provider processing is temporary or that audio is always immediately deleted.
If your device uses Google’s speech service, consult the Google Privacy Policy and that service’s settings. For another provider, consult its corresponding policy and controls. Android documents that its speech-recognition service may stream audio to remote servers. Web microphone cues similarly use the browser’s speech-recognition service, which may process audio remotely.
You can turn Voice control off in CueRoom or revoke its microphone permission in Android Settings. Deleting a CueRoom account does not delete independent records held by your Android or browser speech provider; use that provider’s controls or contact it about those records.
Optional web rehearsal measurement
The WordPress app asks before sending optional usage events. If you allow measurement, it records app opens, imports, rehearsal starts and completions, general errors, and playback wait times. It associates events with your WordPress account ID and a random session ID. These events exclude script titles, dialogue, audio and microphone transcripts.
You can change your choice in Measurement preferences inside the app. Declining stops new optional events; it does not delete events already recorded. Administrator testing is excluded. Events become eligible for deletion after 90 days. Scheduled cleanup depends on WordPress site activity.
Who processes information and how it is protected
CueRoom uses its hosting provider to operate accounts and private storage, Google Play and Stripe for their respective purchases, and ElevenLabs when you choose Studio voices. Device speech services process text or microphone audio when you use those features. Public website analytics are described separately above. These services receive the information needed for the functions described here; their own policies also apply where they process information independently.
Connections between the CueRoom app and CueRoom’s servers use HTTPS encryption in transit. Private online scripts are protected by account access controls. This is not end-to-end encryption: CueRoom and its service providers can process information to deliver the service.
Storage, exports and deletion requests
Online scripts and originals remain until you remove them or they are removed through account cleanup. Account, purchase-access and service records remain as needed to operate your account, with the deletion and retention limits below. Retention periods for optional measurement and temporary caches are described in their respective sections.
To delete your CueRoom account and associated data, visit Delete your CueRoom account and data. Sign in, confirm your password and confirm deletion. Once verified, the request runs automatically; you do not need to keep the page open or ask us to process it manually. We complete verified requests from active CueRoom systems within 30 days. The deletion page explains how to check progress and what happens if cleanup needs attention.
Account deletion removes your account, online scripts and originals, generated reader audio, device registrations, trial and purchase-access records, and associated usage records, preferences, beta requests and feedback, subject to disclosed legal or security retention requirements. It includes provider records held on CueRoom’s behalf. It does not erase payment records that Google Play or Stripe must retain independently, request a refund, or erase independent speech-provider records.
To delete particular data while keeping your account, remove scripts through your online library or email support@cueroom.studio with the data you want removed. If you cannot sign in, use that address for help verifying ownership. Do not email passwords, payment-card details, or scripts.
Exports and copies already saved on your Android device, in your browser, in Downloads, or in your own backups are not erased remotely. Remove those copies separately if you also want them deleted. For subscription cancellation and purchase effects, follow the instructions on the deletion page.
Hosting backups and retained deletion records
Earlier copies may remain in hosting backups after active data is deleted. Our hosting provider has not confirmed a maximum backup-retention period, so we cannot give a verified expiry date. Restored backups must stay out of service until completed deletion requests have been reapplied. Hosting providers may also maintain separate security and request logs.
A deletion-status receipt remains available in the browser used for the request for up to 90 days. We retain a minimal recovery record containing an account number, a keyed identity check, request timing and cleanup status so an old backup cannot restore a deleted account. This record does not contain your email address, password, scripts or audio. It remains needed while a backup may contain the account; with the backup lifetime unconfirmed, it has no verified fixed expiry date.
If a particular record must be retained for a legal or security obligation, we will explain its type, reason and applicable retention period. Contact support@cueroom.studio with questions about this notice or your information.