Privacy Policy

1. Introduction

Dare is operated by Bounty Studio, Inc. (“Bounty Studio,” “Dare,” “we,” “our,” or “us”). For purposes of applicable privacy law, Bounty Studio is the data controller or business responsible for the personal information described in this Privacy Policy. This policy explains how we collect, use, disclose, safeguard, and retain your information when you use Dare — an AI image and video creation service that lets you generate images and videos from prompts and references, edit videos, swap characters into scenes, transfer motion, lipsync speech, relight media, and upscale your results.

By using Dare, you agree to the collection and use of information in accordance with this policy. If you do not agree with our policies and practices, please do not use our services.

2. Information We Collect

2.1 Account Information

When you create an account, we collect the information you provide directly:

• Name and email address (via Clerk, our authentication provider)
• Sign-in identity from Google or another supported sign-in method
• Purchase history and subscription status (payments are processed by Stripe or Apple, depending on the checkout you use; we do not store your full card number)

For App Store purchases, we send Apple a random account-linked identifier and use transaction identifiers, product details, and subscription status from Apple to verify purchases, grant credits, apply refund updates to your credit balance, and prevent duplicate credit grants.

2.2 Content You Provide and Create

When you use Dare’s creation and editing features, we collect:

• Images, videos, and audio you upload as inputs for generations, edits, character swaps, motion transfer, and lipsync; these may include your face or another person’s face with their permission (see Section 3, “Face Data”)
• The prompts, scripts, and instructions you write, and web links you attach as context
• Generated images and videos in your library, including edit history and generation settings

Your account library is personal to you. Dare does not publish your uploads or generations to a public Community feed. If you make a project public and share its link, others can view the shared project and its content; this does not give them permission to copy or remix it. If you export or share content outside Dare, the recipient or external service may process it under its own terms.

2.3 Automatically Collected Information

We automatically collect basic device and usage data so the service keeps working well:

• Browser type, device information, and operating system
• Crash logs and diagnostic information
• Feature usage tied to your account for generation history and credit accounting

We also use PostHog product analytics and Meta advertising tools as described in Section 5, “Analytics and Advertising.”

2.4 Connected AI Clients

You can connect your Dare account to an AI client such as ChatGPT or Codex. Clerk links the client to your account through OAuth, and the consent screen shows the permissions the client requests. The client sends Dare the prompts, scripts, tool inputs, and media references you choose to use. In response, Dare may return your primary email, credit balance, library and generation metadata, uploaded or generated media, and tool results needed to complete your request.

The connected client provider processes that information under its own terms and privacy policy. Some media URLs returned to a connected client can be opened by anyone who has the URL, so share them with care. You can disconnect the client or revoke its access through the available connection or account controls.

2.5 Support and Rights Reports

If you contact support or report suspected copyright or other rights infringement, we collect your contact details, the content or links you identify, and the statements and supporting evidence you provide. We use this information to review and respond to the report, enforce our Terms, and meet legal obligations. We may share the relevant allegation and evidence with the affected user so they can respond, without unnecessarily disclosing your contact details.

3. Face Data

3.1 What Face Data We Collect

“Face Data” means information in user content that depicts or relates to a person’s face or likeness. Dare collects Face Data only when you voluntarily provide or create content that includes a face. Face Data may include:

• Face images or video frames in photos and videos you upload for a generation, edit, character swap, motion transfer, lipsync, or similar feature
• Images or videos generated at your request that depict a face or likeness
• Limited validation results, such as whether an image is suitable for the feature you requested

Dare does not collect data from your device’s face-unlock system. We do not create or store faceprints, facial geometry or depth maps, or biometric identifiers used to identify or authenticate a person. A reference image is used only as a visual reference for content you request; it is not used for facial recognition or identity verification.

3.2 How We Use Face Data

We use Face Data only to:

• Check whether a submitted image or video is suitable for the feature you selected
• Perform the specific image or video operation you request, such as generation with a character reference, character swap, video editing, motion transfer, lipsync, relighting, or upscaling
• Store and display your inputs, outputs, edit history, and library so you can access, re-run, or continue editing them
• Investigate a support request you initiate, prevent misuse, protect the service, and comply with law

We do not use Face Data to identify or authenticate anyone, for surveillance, for advertising or marketing profiles, or to infer identity. We do not sell or rent Face Data, and we do not use Face Data to train our own AI models. We use business or API services and do not intentionally submit Face Data for provider model training.

4. How We Use Other Information

We use other information we collect to:

• Operate the service and show your generation history and library
• Grant credits, manage your subscription, and process purchases
• Fix bugs, apply safety decisions, prevent abuse, secure the service, and improve product performance
• Respond to support requests and meet legal obligations

We do not sell your personal information.

5. Analytics and Advertising

5.1 Product Analytics

On the web, we use PostHog as a product analytics and error-monitoring provider. PostHog may process your Dare account identifier and, when you are signed in, your name and email address; browser, device, page, and feature-interaction information; diagnostic and exception data; and operational events about generation outcomes, subscriptions, purchases, and credit grants. We use this information to understand product usage, troubleshoot errors, protect the Service, and improve performance. Our custom PostHog events are not designed to include prompt text, uploaded media, generated media, or Face Data.

5.2 Advertising

We advertise Dare on Meta platforms (such as Facebook and Instagram) and use Meta Business Tools to measure how our ads perform and improve how they are delivered. On the web, these include the Meta Pixel, which runs in your browser and sets cookies, and the Conversions API, which reports from our servers. In the iOS app, with your tracking permission, we use Meta’s SDK and App Events API to measure installs, app launches, and purchases. Through these tools we share with Meta:

• Activity events, such as viewing a page or an example, creating an account, starting a checkout, purchasing or renewing a subscription, buying a credit pack, and running a generation — along with details like the amount paid and the plan or pack involved
• Advertising identifiers: cookies set by the Meta Pixel, the ad-click identifier from the link that brought you to Dare, your IP address, and your browser information. With iOS tracking permission, we also share the device’s advertising identifier when available, Meta’s app-instance identifier, and app and device information used for attribution
• For signed-in website users, your email address, name, and account identifier — hashed before they are sent; Meta uses them only to match events to Meta accounts

We never share your prompts, uploads, generated media, or Face Data with Meta. Meta processes the shared data as described in its own Privacy Policy, including for ad measurement, attribution, and showing you more relevant ads. You can manage how Meta uses this data in your Meta account’s ad preferences, and clearing or blocking cookies limits collection in your browser.

On iOS, Dare asks for permission through Apple’s App Tracking Transparency framework before reporting activity from the native app to Meta for advertising measurement. If you decline, Dare does not send those advertising-measurement events from the native app to Meta, and all app features remain available. You can change this choice at any time in iOS Settings.

6. Third-Party AI Processing and Face Data Sharing

6.1 Service Providers

To provide a generation or editing feature, we send the selected provider the prompts, scripts, instructions, and specific uploaded media needed for that request. This may include Face Data. We do not share Face Data with third parties for advertising or their own independent commercial purposes. We disclose it to service providers when needed to provide the feature you request:

• Cloudflare: hosts our application, delivers media, and stores uploaded and generated media in Cloudflare R2
• PlanetScale: stores associated account, media, and feature records
• fal.ai: processes the images and videos needed for requested generations, edits, character swaps, motion transfer, relighting, and upscaling
• Atlas Cloud: processes the images and videos needed for requested video generations with Seedance models
• BytePlus: processes the images, videos, audio, and prompts needed for requested video generations with Seedance models
• LightSpeed Future: processes the images, videos, and audio needed for requested video generations with Seedance models
• Replicate: processes the images, videos, and audio needed for requested video generations with Seedance models
• sync.so: processes the videos needed for lip-synced video translations
• ElevenLabs: processes the videos and audio needed for requested video translations and dubbing
• OpenAI: processes the images needed for requested AI image generations and edits, and processes prompts or selected context for requested prompt-composition and content analysis features

A facial image or video is sent only to the provider needed for the feature you select, not to every provider listed above. We use business or API services and do not intentionally submit your content for provider model training. Each provider processes data under its applicable agreement, data-use settings, and privacy terms. Stripe, Apple, and Clerk do not receive Face Data from Dare for payment or authentication services.

6.2 Safety Processing and Decisions

The selected AI provider may use automated systems to evaluate a prompt, input media, or generated output against its safety policies. Dare receives the request status and may receive a reason for a rejection. When a provider declines a request for safety reasons, Dare’s server enforces that decision by stopping the run, marking the generation as failed, showing a user-facing failure state, and refunding the credits charged for that failed run. We may retain the generation status and limited failure information for support, security, abuse prevention, and legal compliance. Safety checks vary by provider, tool, and content.

6.3 Permission and Withdrawal

Before a generation is submitted, Dare explains that the prompt and media will be sent to third-party AI services. By choosing Generate after that notice, you authorize the transfer needed for that request. You may decline by not starting the generation, and you may withdraw permission for future AI-provider transfers at any time by not submitting additional requests. You may also delete content from your library or contact support@trydare.com to request account deletion. Withdrawal does not affect processing already completed, and a request already accepted by a provider may not be capable of recall. Section 7 explains deletion and retention.

6.4 Where Face Data Is Stored

Dare stores uploaded and generated face-containing media in Cloudflare R2 cloud object storage. Associated account links, media references, feature records, and related timestamps are stored in our PlanetScale database. AI providers receive a temporary copy of only the media needed to complete the requested operation. Face Data may be processed in the United States and in other countries where these providers operate.

We may also disclose Face Data if required by law, or when reasonably necessary to protect the rights, safety, and security of Dare, our users, or others.

7. Face Data Retention and Deletion

We retain Face Data as follows:

• Face-containing inputs, generated outputs, and edit history are retained while your account remains active so your library and edit history work. If you delete a generation, it is removed from your library.
• AI service providers retain processing copies under their API data retention terms and our applicable data-use settings; those periods can vary by provider. For example, OpenAI may retain limited abuse-monitoring data for up to 30 days. When responding to a valid deletion request, we delete data from Dare’s systems and take reasonable steps with service providers where applicable, subject to any security, legal, or compliance retention they are permitted to maintain.
• If you delete your account or ask us to delete it at support@trydare.com, we delete Face Data and other personal data associated with the account within 30 days, except for limited billing records and a minimal account-deletion record. We retain the account identifier and deletion timestamp to prevent delayed billing events from recreating the account. We retain purchase and subscription records and their account-linked identifiers after account deletion to verify purchases, prevent fraud and duplicate credit grants, and meet legal obligations. We do not retain Face Data with these records.

Deleted data may remain in access-restricted disaster-recovery backups until those backups are overwritten, for no more than 30 additional days. Backup copies are not used for any other purpose. If we must preserve specific Face Data to comply with law, we isolate it, do not use it for any other purpose, and delete it when the legal obligation ends. We do not retain Face Data indefinitely after deletion.

8. Security

We use reasonable technical and organizational measures to protect your information, including encryption in transit, access controls, and service providers selected to handle sensitive information. No method of transmission or storage is 100% secure, and we cannot guarantee absolute security.

9. Children’s Privacy

Dare is not directed at children under 13, and we do not knowingly collect their data. If you believe a child has provided us personal information, including Face Data, contact us and we will delete it.

10. Your Rights

Depending on where you live, you may have rights to access, correct, export, or delete your personal information, and to object to or restrict certain processing. You can delete individual generations and uploads from within the app. You can exercise other rights, including account access and deletion requests, by contacting us at support@trydare.com.

11. Changes to This Policy

We may update this Privacy Policy from time to time. Material changes will be announced in the app, and the “Last updated” date above will reflect the latest revision. Your continued use of Dare after changes take effect constitutes acceptance of the updated policy.

12. Contact Us

For any privacy question or request, including Face Data access and deletion requests, contact us at:

See also our Terms of Service.