SwiftSoft Labs

Deepfluence Privacy Policy

Version 1.0.0, effective 20 November 2026. Signature verified with key synlex-1.

Privacy Policy

1. Who we are

SwiftSoft Labs LLC ("we", "us") decides how the personal data described in this policy is used.

  • Legal name: SwiftSoft Labs LLC
  • Legal form: Registered company (LLC, corporation or similar)
  • Jurisdiction: Wyoming, United States (us-wy)
  • Contact email: legal@swiftsoftlabs.com
  • Address: 312 W 2nd St, PO Box 5309, Casper, WY 82601
  • Data protection contact: legal@swiftsoftlabs.com

2. Whose data this covers

  • Brand users (business accounts)
  • Creators (influencers)
  • Prospects named in brands' recipient lists
  • Website visitors

3. The personal data we collect

We collect the following categories of personal data:

  • AI-generated videos
  • Account credentials (password, 2FA, passkeys)
  • Account role (brand or creator) and organization name
  • Anonymous page views on public pages
  • Billing and royalty references (Kelviq customer and subscription IDs)
  • Campaign scripts and creative briefs
  • Creator approval and veto decisions
  • Creator profile (name, bio, avatar, tags, royalty rate)
  • Creator reference photos (face likeness)
  • Email address
  • Google account ID and profile (Google sign-in)
  • Identity verification status (ID and selfie held by Sumsub)
  • Name
  • Recipient rows from brands (first name, company and other fields)
  • Sign-in and account activity logs
  • ip address (through Sentry)
  • request bodies (through Sentry)
  • request url path and query string (through Sentry)

4. Sensitive personal data

We collect the following sensitive personal data:

  • Biometric likeness (face photos)
  • Government ID (via Sumsub)

Biometric likeness means the reference photos creators upload of their own face. We use them only to make AI videos for brands that book the creator. A creator ticks a consent box before uploading a photo, we record when they did, and a photo is used only after the creator approves it. Creators can withdraw at any time by writing to legal@swiftsoftlabs.com.

Government ID: our verification provider, Sumsub, collects a creator's ID document and selfie and keeps them. We keep only the result of the check.

We use this data only for the purposes in this policy. Where the law requires your explicit consent to use it, we ask for that consent first.

5. Children

Minimum age: 18

The service is for people who are 18 or older. We do not knowingly collect personal data from anyone younger.

If you believe a person younger than 18 has given us personal data, write to legal@swiftsoftlabs.com and we will delete it.

6. Why we use personal data

  • Understanding how the service is used (behavioral). Legal basis: Legitimate interests. Identity checks on creators before booking and payout, security and error monitoring, and anonymous page-view counts on public pages
  • Operating and providing the service (operational). Legal basis: Contract.

7. Marketing email

We do not send marketing email.

8. Who we share personal data with

We use the service providers below. Each one processes personal data on our behalf and under a data processing agreement where one is listed. They may use the data only to provide their service to us.

Google Sign-In

  • Service: Sign-in and identity
  • Purpose: Sign in with a Google account (OAuth)
  • Data received: Google account ID, email address, name, profile picture
  • Location: United States
  • Data processing agreement: https://business.safety.google/processorterms/

InsForge

  • Service: Hosting and infrastructure
  • Purpose: Database, file storage for reference photos and videos, and sign-in emails
  • Data received: Account and profile data, creator reference photos, scripts and recipient rows, AI-generated videos, activity logs, billing and royalty references, sign-in emails
  • Location: United States
  • Data processing agreement: https://insforge.dev/dpa

OpenRouter

  • Service: Artificial intelligence
  • Purpose: AI gateway: routes video generation to Alibaba HappyHorse 1.1 or Google Veo, and the brand-safety check to Google Gemini 2.5 Flash-Lite
  • Data received: Creator reference photo (signed link), campaign script filled in from the recipient's row (for example first name and company), creative brief and tone; script templates for the brand-safety check
  • Location: United States
  • Data processing agreement: https://openrouter.ai/data-processing-agreement

PostHog

  • Service: Analytics
  • Purpose: Anonymous page-view counts on public pages
  • Data received: Random session ID kept in session storage, page URL and host, browser details
  • Location: United States
  • Data processing agreement: https://posthog.com/dpa

Sentry

  • Service: Monitoring and error reporting
  • Purpose: Error and performance monitoring
  • Data received: IP address, browser details, request URL path and query string, request bodies, error stack traces
  • Location: United States
  • Data processing agreement: https://sentry.io/legal/dpa/

Sumsub

  • Service: Sign-in and identity
  • Purpose: Identity verification of creators (ID document, selfie and liveness check)
  • Data received: Creator's ID document, selfie and liveness check, Deepfluence user ID; Deepfluence keeps only the applicant ID and the verification result
  • Location: Not provided
  • Data processing agreement: https://sumsub.com/files/data_processing_agreement.pdf

Vercel

  • Service: Hosting and infrastructure
  • Purpose: Hosting and serving the website and app
  • Data received: IP address, browser details, request URLs and request logs
  • Location: United States
  • Data processing agreement: https://vercel.com/legal/dpa

Purchases are made from Kelviq, which sells the service to you as merchant of record. The payment details you give at checkout go to Kelviq. It uses them as an independent controller, not on our behalf, under its own privacy policy.

Kelviq's privacy policy: https://www.kelviq.com/buyer-privacy/

**Independent services your browser loads.** Some of our pages load files from three services that act on their own account, under their own privacy policies, and not on our behalf. When a page loads them, each receives your IP address and browser details:

  • Google Fonts serves the Inter typeface on every page. Google's privacy policy: https://policies.google.com/privacy
  • Tailwind Labs serves the Tailwind CSS script from its CDN (cdn.tailwindcss.com) on every page. We found no privacy policy that Tailwind Labs publishes for this CDN.
  • Unsplash serves placeholder photos on the creator marketplace and the creator sign-in page. Unsplash's privacy policy: https://unsplash.com/privacy

9. Transfers outside your country

Some providers handle personal data outside the country where you live. Where the law requires a safeguard for that transfer, we rely on the mechanism listed here.

  • Google Sign-In: United States. Transfer mechanism: Standard contractual clauses.
  • InsForge: United States. Transfer mechanism: Standard contractual clauses.
  • OpenRouter: United States. Transfer mechanism: Standard contractual clauses.
  • PostHog: United States. Transfer mechanism: Standard contractual clauses.
  • Sentry: United States. Transfer mechanism: Standard contractual clauses.
  • Sumsub: Not provided. Transfer mechanism: Standard contractual clauses.
  • Vercel: United States. Transfer mechanism: Standard contractual clauses.

The safeguards we rely on:

  • Standard contractual clauses: the standard contractual clauses approved by the European Commission.

10. Cookies and similar technologies

We set four first-party cookies, all HttpOnly: `df_access` and `df_refresh` keep you signed in, `df_mfa_pending` holds a two-step sign-in while you finish it, and `df_oauth_state` protects a Google sign-in for 10 minutes. During checkout your browser's session storage keeps `df_checkout_open`, `df_checkout_needs_abandon` and `df_checkout_activating`, which are cleared when you close the tab.

We do not set analytics or advertising cookies. PostHog counts page views on our public pages using a random ID kept in your browser's session storage (`ssl-marketing-distinct-id`), which is cleared when you close the tab. Sentry error reports use no cookies.

Our Cookie Policy has the details.

11. How long we keep personal data

We keep personal data only for as long as it is needed for the purposes in section 6, or as the law requires. When it is no longer needed we delete it or make it anonymous.

Retention: Reference photos are kept while the creator is active and deleted within 30 days of withdrawal. Account data is kept while the account is active plus 90 days. To delete your account, write to legal@swiftsoftlabs.com. Billing and royalty records are kept as tax and accounting law requires.

12. Your rights

You can ask us to tell you what personal data we hold about you, to give you a copy, to correct it, and to delete it. Write to legal@swiftsoftlabs.com. We may need to confirm who you are before we act, and we answer within one month.

If you are in the European Economic Area, the United Kingdom or Switzerland, you also have the right to restrict our use of your data, to object to it (including use based on legitimate interests), to receive your data in a portable format, and to withdraw consent at any time without affecting earlier use. You can complain to the data protection authority where you live or work.

If you live in a US state with a privacy law, such as California, you have similar rights to know, correct and delete your data, and we will not treat you differently for using them. We do not sell personal data or share it for targeted advertising.

13. Security

We use technical and organisational measures that fit the risk to protect personal data against loss, misuse, and unauthorised access. These include controlling who can reach the data and limiting access to the people and providers who need it.

No system is completely secure. If a breach puts your rights at risk, we will tell you and the authorities where the law requires it.

14. Artificial intelligence providers

We use these artificial intelligence providers: OpenRouter, which routes our requests to the models below.

  • Video: to make a video, the creator's approved reference photo and the campaign script, filled in from the recipient's row (for example a first name or company), go through OpenRouter to the video model, Alibaba HappyHorse 1.1 by default, or Google Veo.
  • Brand safety: before videos are made, the campaign's script template and creative brief go through OpenRouter to Google Gemini 2.5 Flash-Lite for a brand-safety check.

The videos are AI-generated. Brands should put into recipient rows only the details a video needs.

No agreement was recorded that says these providers refrain from keeping that content.

SwiftSoft Labs does not use your content to train AI models. Our AI gateway, OpenRouter, does not store your prompts or responses or use them for training under its default settings. The model provider that answers a request handles it under its own policy and may keep it for a limited time to prevent abuse.

15. Changes to this policy

We may update this policy. When we make a material change we will update it here and, where the law requires, tell you.

16. Contact us

To use a right or ask a question, write to legal@swiftsoftlabs.com or to our data protection contact at legal@swiftsoftlabs.com.

Check these documents

Checking the signature in your browser…

Your browser computes the SHA-256 of each document on this page and compares it with the hash in the signed release manifest.

DigiCert, Inc. timestamped the manifest hash at Fri, 20 Nov 2026 12:16:57 GMT. Synlex checked the authority's signature, the hash, and its certificate chain to DigiCert Trusted Root G4, a root pinned in Synlex. To check the token yourself, download it from the footer and run:

openssl ts -verify -in release-v1.0.0.tsr -digest 5834e72f2c472bfa0c25631a0387ca1b7a10b1839cd32bb2fb1b9b73b4baae9f -CAfile /etc/ssl/cert.pem
Check the signature yourself with OpenSSL 3

The JSON API publishes the signed manifest bytes and the signature; the keys file publishes synlex-1's public key and its window. Then check that the manifest's signedAt falls inside that window and that its document hashes match the documents.

curl -s 'https://synlex.vercel.app/api/public/v1/swiftsoftlabs/deepfluence?version=1.0.0' | jq -j .signature.manifest > manifest.json
curl -s 'https://synlex.vercel.app/api/public/v1/swiftsoftlabs/deepfluence?version=1.0.0' | jq -r .signature.value | base64 -d > manifest.sig
curl -s 'https://synlex.vercel.app/.well-known/synlex-keys.json' | jq -r '.keys[] | select(.id == "synlex-1") | .publicKey' | base64 -d > key.der
openssl pkeyutl -verify -pubin -keyform DER -inkey key.der -rawin -in manifest.json -sigfile manifest.sig