Privacy notice

Who operates this app

AI Campaign Studio is operated by Bissolux L.L.C.. This notice covers the AI Campaign Studio website and its mobile apps. Other Bissolux products have their own notices. Privacy requests can be sent to info@bissolux.com.

The operational descriptions below reflect this application’s current features. Necessary account and creation processing supports your requested service; required payment records support accounting obligations, while optional analytics requires consent.

Before publication, the operator must confirm the applicable legal bases, international-transfer safeguards, processor arrangements and retention schedule for the actual deployment.

Account, creative and payment information

• Account details: email address, optional display name, account identifiers, creation time and protected session records. Passwords are processed for sign-in and stored as salted password hashes, not plaintext passwords.
• Your workspace: briefs and prompts, uploaded image/video references, generated outputs, brand kits, storyboards, selected models and settings, job status and recovery records.
• Billing: plan, store and transaction identifiers, verified purchase state, credit allowance, reservations, usage, refunds and disputes. Web card details are entered with Stripe; mobile purchase credentials are handled by Apple or Google. The app backend does not store full card numbers or card security codes.
• Support and safety reports: information you choose to send, including the selected job reference, reason and optional description. Reports do not automatically copy your prompt, media or signed download links.

This information is used to operate your private account, carry out your explicit creation requests, deliver files, verify purchases and investigate errors, abuse or billing disputes. Account security, essential hosting and payment records are separate from optional analytics consent.

What is sent to AI providers

When you explicitly generate an image, frame, video or Product set, the chosen provider receives the prompt and compatible inputs needed for that request. These may include your product photos, start/end frames, reference video and brand context. A router can pass the request to the model’s underlying provider. Providers may process this data in other countries and apply their own retention, safety and service terms.

The selected model/provider is shown before generation. Merely editing a brief or choosing media does not start a generation. Uploads are first stored by the studio; live generation sends the relevant inputs onwards. Bundled sample previews do not call a generation provider. Do not submit confidential, personal or sensitive material unless you are authorized to share it with that provider. AI Campaign Studio does not promise that third parties never retain data or never use it for training.

• OpenRouter privacy information
• fal privacy information

The operator must confirm the provider list and terms for each enabled route before publishing this notice. Operator-hosted workflows also need their own documented processing arrangements.

Payments and other recipients

Stripe processes website checkout and billing-portal requests. Apple App Store or Google Play processes native purchases. RevenueCat helps validate native purchase and entitlement events using app account, product and transaction identifiers. Necessary hosting and optional private object storage hold workspace files and operational records. Bissolux personnel with authorized support or operational access may inspect relevant records when needed.

• Stripe privacy notice
• RevenueCat privacy policy
• Apple privacy information
• Google privacy policy

Optional analytics and device storage

Optional analytics starts only after consent. It uses random visitor/session identifiers and bounded event categories such as known page, tool, language, broad browser/operating-system/device class and approved acquisition channel. It excludes prompts, uploaded media, account details, complete URLs, raw user-agent strings and provider secrets. It does not join web and native visitors into a verified person or prove an installation, completed download or ad sale.

You can decline or withdraw through Privacy & analytics without losing app features. Withdrawal clears active identifiers and queued events and requests deletion of associated optional analytics. A minimal deletion proof may remain only until the gateway confirms deletion so an interrupted request can be retried. The collector’s configured retention is displayed in analytics details; contact the privacy address above if you need help finding the current period.

Essential storage also includes sign-in cookies, your app preferences and local draft/recovery information. The native app keeps its expiring account session in device-protected Keychain/Keystore storage so reopening it does not require another login. Signing out disables restoration and removes that saved login; expired or revoked sessions require authentication again. Passwords are not saved by the app. Account deletion recovery uses a random request ID and a private receipt token on the device, not a saved password. Technical network requests can expose an IP address and protocol details to hosting, payment or AI providers; the optional analytics exclusions do not mean all infrastructure logs exclude technical metadata.

Retention, deletion and your choices

Workspace content stays with your account until you delete it through the supported account-deletion flow or it is removed for an operational or legal reason. Account deletion revokes access and schedules deletion of the profile, private creative records, report descriptions, uploads, generated files and configured private object-storage copies. Processing may wait for running jobs or retry unavailable storage; the deletion receipt shows whether erasure is complete.

A reduced, pseudonymous payment record may remain for accounting, refunds, fraud prevention, disputes and legally required records. External payment and AI providers keep their own records under their terms. Deleting an account does not remove files you downloaded or copies you shared elsewhere. Backup copies and legally retained records follow the operator’s retention schedule; contact the privacy address for the applicable periods. Instant erasure from every third party or backup is not promised.

You may ask for access, correction, a copy, deletion, restriction or other rights available under applicable law by contacting the privacy address above. Identity verification may be needed. You can also contact the appropriate data-protection authority where applicable. See the deletion guide for the app’s direct process.

Sign in with Apple

When enabled in the iOS app, you can choose Apple instead of an app password. Apple supplies a verified account identifier, your selected email or private relay address, and optionally your name. Our server validates the authorization with Apple and stores the account association and an encrypted refresh token needed to revoke authorization on deletion. The native app can retain the Apple user identifier alongside its protected, expiring account session, then restore it only to check credential revocation. This identifier is not an account authentication proof.

Apple sign-in does not purchase a plan or grant credits. Deleting an Apple account queues authorization revocation separately from private-content cleanup; an Apple outage can delay revocation. Existing email accounts are not automatically merged. Apple processes authentication under its privacy policy.