Rehearsal: Cue & Record privacy

Steelyard Ventures LLC · Updated October 13, 2026

This policy describes the current private beta 0.1.0, including ordinary SDK-unlinked and Consent Test versions. Production ad serving and public app release are not enabled. It must be reviewed again before those practices change.

Your library

Rehearsal stores scripts, prompt preferences, recordings, take labels, notes, dates and keeper choices in private storage on your device. There is no app account, cloud sync, speech-recognition or remote AI service. Scripts, recordings, labels and notes are not intentionally sent to Steelyard or included in ad requests. The advertising version places a banner only on Scripts/library, not the editor, Rehearse, recording, Takes, playback or export.

The library is excluded from automatic device backup. Export important videos and keep a separate copy of script text before deleting the app or changing devices. Video export is not a whole-library backup. Deleting a script deletes its takes after confirmation; failed cleanup can produce a warning. Interrupted recordings may leave a private file for recovery or explicit deletion. Steelyard cannot recover or delete device-only content remotely, and local deletion is not a secure-erasure guarantee.

Camera, sound and export

Camera permission is requested when you choose Start camera. Microphone permission allows sound; silent recording remains available when it is off. Scripts and prompts work without camera permission. Change permissions in iOS Settings. The app does not request location, contacts or entire photo-library access. Record people and material only with appropriate permission.

Export opens the system share sheet for your selected video; it does not attach the script or notes. The receiving app or service handles that copy under its own policies. Rehearsal cannot delete copies shared elsewhere.

Optional advertising and your choices

The ordinary app contains no Google advertising or consent SDK. The internal Consent Test version tests Google advertising and consent. Its banners are Google demonstration ads and earn no production revenue. Production banner serving is not enabled.

Advertising versions first offer “I’m 18 or older — continue”, “I’m under 18”, and “Keep ads off”. The age choice remains in memory for this app session; we do not ask for or store your birth date. This is self-confirmation, not independent age verification. Choosing under 18 or keeping ads off leaves the app free and ad-free.

Google’s consent service retains consent signals locally, and the app remembers whether an ad-privacy-options entry was previously required so you can revisit it after relaunch. This retained status is not advertising permission or a stored birth date. Choosing a required privacy-options control can contact Google to refresh and display your choices even while ads are off or before this session’s adult confirmation. Before this session’s adult confirmation, or while local ads are kept off, this withdrawal action does not enable banners or request tracking authorization. In an adult-enabled session, changed choices are reevaluated under the normal permission checks, including Apple tracking permission when needed.

After adult confirmation, Google’s consent service presents the applicable regional choices. Ads stay off unless required regional permissions are affirmatively satisfied. Unknown, missing or malformed permission state, refusal or a setup error does not enable ads. Only after this check does the app request Apple App Tracking Transparency permission when needed. The advertising SDK and banners are allowed only while Apple reports tracking is authorized and all other eligibility checks pass. Denied, restricted or unanswered tracking permission leaves the app free and ad-free. Core features do not require ads.

Required Google ad-privacy options remain available even when Apple tracking permission is denied. You can revisit available privacy controls in the app and change tracking permission in iOS Settings. Keeping ads off stops further banner requests and removes the displayed banner; it does not erase data already processed, and initialized or in-flight service activity may finish.

Google’s consent service runs before Apple’s tracking prompt. A later tracking refusal does not reverse consent-service processing already performed. The current publisher-consent test uses Steelyard’s Google application identity and a Google demonstration banner; it does not request production banners.

Information used by Google services

Google services can process IP address and approximate location, device/app identifiers, advertising and app interactions, and crash, performance or other diagnostic information. Google and its advertising partners use service data to deliver and measure advertising and operate or improve their services. Tracking-authorized advertising can link device identifiers to people or devices and use them for advertising measurement across other companies’ apps or services. The advertising disclosure therefore includes Device ID as collected, linked and used for tracking. Test ads do not eliminate service processing.

The app requests nonpersonalized ads and disables Google’s publisher first-party ID. These are additional limits, not promises of anonymity, no identifiers or no tracking. There is no mediation adapter, uploaded customer list or private app-content targeting in this implementation. See Google’s SDK data disclosure and Google’s privacy policy. We do not promise a fixed retention period or remote deletion of every Google or advertising-partner record.

Support and testing

Email help@steelyardventures.com for help or privacy requests. We receive your message, email address and attachments you choose to send, and use them to respond and investigate. Support correspondence is held separately from local app data and kept as needed to resolve the request and meet applicable business or legal requirements; no fixed automatic expiration is promised. You may request deletion at the same address. Removing the app does not delete correspondence already sent. Do not send passwords, payment details or identity documents; an initial report does not require private content.

When you use this beta through TestFlight, Apple and Steelyard automatically receive crash logs and usage data; TestFlight does not provide an opt-out from that beta-data collection. Written or visual feedback you submit is optional. Tester information, diagnostic data and screenshots can contain identifying information. This processing is separate from the app’s local storage and Google services and is used to investigate and improve the beta. Avoid confidential content in feedback. Stopping testing does not erase reports already submitted. See Apple’s TestFlight terms.

Changes

We update this policy when the app’s data practices change. The policy must match the version you use. Apple, Google and services you deliberately share with handle their own services under their policies.