SwiftSoft Labs

Smartfluence 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

  • Creators (account holders who build an AI likeness)
  • Fans (account holders who send requests to creators)

3. The personal data we collect

We collect the following categories of personal data:

  • AI-generated photos
  • Account credentials (password hash, verification and reset codes)
  • Content credentials (C2PA) provenance records
  • Content reports and blocked users
  • Crash logs and error stack traces (device and app details)
  • Email address
  • Face photos and the Identity Kit built from them (biometric likeness)
  • Fan requests: prompt, requester email, price, status and delivery
  • Google or Apple account ID linked at sign-in
  • Name, display name, handle, bio and avatar
  • Prompts and other content you write
  • Purchase history: plan, credits, subscription status and Kelviq IDs
  • Trigger word and physical descriptors
  • Wardrobe and garment photos
  • ip address (through Sentry)

4. Sensitive personal data

We collect the following sensitive personal data:

  • Biometric likeness: face photos used to build an Identity Kit

A creator who builds an Identity Kit uploads at least 15 approved photos of their own face. Before the kit is built, the app shows a face and identity photo notice and asks you to tick a box to consent to SwiftSoft Labs processing and keeping your face photos. We send the photos, your trigger word and your physical descriptors through OpenRouter to Google Gemini models, which check each photo, build your Identity Kit and generate images of you. We do not use your face photos to identify or verify you, and we do not sell them.

Identity Kit photos are kept in private storage until you delete your Identity Kit (Delete Identity Kit on the Training Data screen) or your account. Photos you upload that are not used in the kit are deleted after 30 days. Images already generated from your kit stay until you delete them or your account.

We use it only for the purposes in this policy.

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

  • 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
  • Data received: Google ID token, email address, name
  • Location: United States
  • Data processing agreement: https://business.safety.google/processorterms/

InsForge

  • Service: Hosting and infrastructure
  • Purpose: Database, file storage, sign-in service, realtime updates and transactional email
  • Data received: Account and profile data, password hash, sessions, face and wardrobe photos, generated images, fan requests and prompts, email address
  • Location: United States
  • Data processing agreement: https://insforge.dev/dpa

OpenRouter

  • Service: Artificial intelligence
  • Purpose: Routes AI requests to Google Gemini models for prompt help, prompt safety checks, photo checks and image generation
  • Data received: Prompts, trigger word and physical descriptors, face and wardrobe photos, generated images
  • Location: United States
  • Data processing agreement: https://openrouter.ai/data-processing-agreement

Sentry

  • Service: Monitoring and error reporting
  • Purpose: Crash and error reports from the mobile app and the billing API
  • Data received: Device and app details, error messages and stack traces, IP address, request URL
  • Location: United States
  • Data processing agreement: https://sentry.io/legal/dpa/

Vercel

  • Service: Hosting and infrastructure
  • Purpose: Hosts the app's API and the checkout return page
  • Data received: API requests from the app, IP address, 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/

**What other users see.** When a creator turns on public fan requests and has an active Creator Pro plan, signed-in fans can see the creator's display name, handle, avatar, bio and request price. When a fan sends a request, the creator sees the fan's prompt, email address and any garment photo the fan attached. The fan sees the images the creator approves in the app, and we also email the fan a private link to them that expires after 7 days.

**Services that act under their own policies.** We have no data processing agreement with the services below. They are not our processors, and each acts under its own privacy policy, not on our behalf.

  • **Apple (Sign in with Apple).** If you sign in with Apple, Apple confirms who you are and gives us an identity token, plus your email address and name if you choose to share them. Apple's privacy policy: https://www.apple.com/legal/privacy/en-ww/
  • **Unsplash.** Location thumbnails in the Studio screen load from Unsplash's image servers, which receive your device's IP address and app details when the images load. 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.
  • Sentry: United States. 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

The app does not use cookies, advertising identifiers or tracking pixels. It keeps a few items on your device:

  • In the device's secure storage (the Keychain on iOS, Keystore-backed storage on Android): your sign-in tokens (`smartfluence_access_token`, `smartfluence_refresh_token`) and a copy of your basic account details (`smartfluence_user`). Signing out removes them.
  • In the app's local storage: whether you finished onboarding (`@smartfluence/onboarded`) and short-lived checkout flags (`sf_checkout_open`, `sf_checkout_needs_abandon`, `sf_checkout_activating`), which are cleared when a checkout finishes.

These items stay on your device. Deleting the app removes them. Checkout and the billing portal open in your browser on Kelviq's pages, which may set their own cookies under Kelviq's policy.

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: Account data is kept until you delete your account in the app. Face photos and the Identity Kit stay until you delete the Identity Kit or your account; uploads not used in the kit are deleted after 30 days. Requests you sent to a creator stay with that creator's request, without a link to your account. Billing 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. You can also delete your account yourself in the app, as our Account Deletion and Data Erasure policy describes.

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. OpenRouter passes each request to one of Google's Gemini models.

  • **Identity Kit (creators).** Your face photos, trigger word and physical descriptors go to Gemini to check each photo, build your Identity Kit and compare test images with your photos.
  • **Image generation.** Your prompt, your Identity Kit reference photos and any garment photo go to a Gemini image model (Gemini 3.1 Flash-Lite Image, Gemini 3.1 Flash Image or Gemini 3 Pro Image, depending on the quality tier) to generate images of you. Fan requests a creator accepts are generated the same way.
  • **Prompt help and safety checks.** Prompts go to Gemini 2.5 Flash-Lite to suggest wording. Every fan request prompt is checked by it before the creator sees the request, and a prompt that fails the check, or that the check cannot read, is rejected.

When you use a feature that relies on one of them, the content you send to that feature is passed to the provider so that it can return a result. Do not put personal data into such a feature unless you need to.

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 14:55:08 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 e11dd956b00319bee147391b94960167769e92b436e606ce19c00a3fe866136a -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.swiftsoftlabs.com/api/public/v1/swiftsoftlabs/smartfluence?version=1.0.0' | jq -j .signature.manifest > manifest.json
curl -s 'https://synlex.swiftsoftlabs.com/api/public/v1/swiftsoftlabs/smartfluence?version=1.0.0' | jq -r .signature.value | base64 -d > manifest.sig
curl -s 'https://synlex.swiftsoftlabs.com/.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