Boldazzle.

Privacy Policy

Updated November 7, 2026

iPhone purchases and deletion

Apple processes iPhone in-app payments. Boldazzle receives signed purchase and refund records and uses a random purchase token to associate the transaction with the signed-in account. Card details stay with Apple. Purchase receipts, wallet entries and required financial records are retained for fulfillment, disputes and accounting. Clerk provides native authentication and stores session tokens through device secure storage. A deletion request can be initiated in the iPhone Account screen when enabled; the confirmation shows a target date and billing-retention notice. A random status receipt is saved securely on the device so deletion completion can be checked after identity removal. Account films, screenplay, media and workspace content are removed during processing; copies already exported outside Boldazzle and separately retained records held by providers are outside this process. Required billing reconciliation and external service cleanup can require operational review. Sandbox purchase credits are stored separately from live film-credit balances.

Who operates Boldazzle

Llewellyn Collymore operates Boldazzle from Queens, New York, United States. Contact hello@boldazzle.com with privacy questions, access requests or deletion requests.

Information processed

We process account identifiers, project briefs, uploaded text and audio, saved documents, scene plans, captions, video clips, assembled movies, workflow history, model settings, usage and cost records, and support messages you provide. Authentication and hosting services may process technical information such as IP addresses, browser information and security logs. Necessary session cookies and local browser storage support sign-in and workspace preferences.

Purposes and service providers

We use this information to authenticate users, save and run workflows, return requested outputs, track costs, prevent misuse and investigate failures. Clerk handles authentication; Vercel hosts the application and manages connector authorization; Neon stores workspace data. In direct text mode, OpenAI receives relevant briefs, reference text and saved documents for writing and research, without AI Gateway routing. Research queries use OpenAI web search. We set store=false for these Responses API requests; this is not a claim of zero data retention. OpenAI may retain abuse-monitoring logs for up to 30 days by default, with policy exceptions, and prompt caching may retain temporary application state. Its processing terms apply. Gateway mode, when separately enabled, routes model requests through Vercel AI Gateway. Enabled AI requests send relevant briefs, context and documents to the selected model providers. Gateway-mode research workflows use Exa web search through AI Gateway; direct text mode does not call Exa. Relevant search queries are sent to that service, and retrieved source material may be included in model context. Model zero-data-retention routing does not establish the retention policy of web-search services or delete saved workspace history. Their processing terms also apply. Do not submit sensitive information you are not authorized to share.

Runway video generation

When separately enabled and requested by you, Runway receives the selected shot prompt, model, duration and frame shape to generate a silent clip. Other saved documents and account profiles are not sent with that video request. We retain the task reference, credit reservation, reported cost and generated clip in your account workspace. Provider download links are temporary; saved workspace clips and downloaded copies have separate retention. Runway’s applicable terms, privacy policy and account settings govern its processing, retention, review and potential model-improvement use. We do not promise zero retention or that content cannot be used for model improvement. Do not include confidential or sensitive content you are not authorized to send to Runway. See https://runway.com/privacy-policy and https://runway.com/terms-of-use.

Movie audio and captions

Optional soundtrack uploads are processed in temporary files on our server to combine audio with a saved movie. The original uploaded audio file is not saved in your workspace; the resulting movie with audio and an input fingerprint used to recognize repeat uploads are saved. This soundtrack feature does not send the audio to an AI model. Written narration in scene plans supplies draft captions. When separately enabled and explicitly requested, spoken narration sends only the reviewed script, selected built-in voice, model and audio settings to OpenAI. Generated audio, a script fingerprint, voice selection and spending reservation are retained privately in your project. Narration is AI-generated, does not clone a person’s voice, and must be disclosed as synthetic when shared. This Speech API feature does not use the Responses API store=false setting; OpenAI’s applicable processing and retention terms govern it. It does not promise zero data retention. Attaching saved narration to a movie does not make another model request. Downloaded movies and editing packages remain wherever you save or share them.

Google Drive access

Connecting Drive is optional. Boldazzle requests drive.file access to specific files created or selected for use with the app. An export sends the approved document version to your Drive when you initiate it. We retain export metadata such as file identifiers and version receipts to prevent duplicate uploads and recover interrupted exports. Vercel Connect manages provider credentials on the server. The integration does not scan your entire Drive or change file-sharing permissions.

Google data use

Google API data is used only to provide the requested Drive connection and document-export features. We do not use this data for advertising or to train general-purpose AI models. Our use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. You can revoke access through your Google Account connections settings.

Retention and deletion

Saved workspace data remains while needed to provide your account and projects. Archiving hides a project; it does not delete it. Project-content deletion removes working content but may retain minimal accounting and deletion records. Backups, operational logs and provider-managed records may persist under their retention settings. External Drive exports remain in your Google account until you delete them there. Contact support to request account or data deletion; we will review the request and explain any records retained for security, accounting or legal obligations. No fixed deletion completion period is promised here.

Security and your choices

We use authenticated access and owner-scoped storage. No service can guarantee absolute security. You can edit saved work, download documents and choose whether to connect Drive. Service providers may process information in the United States or other countries where they operate. Contact support for access, correction or deletion requests.

Changes

We may update this policy as the service changes. The date below identifies this version. Material changes will be described through the service or an appropriate account notice.