SwiftSoft Labs

Smartfluence Artificial Intelligence Use Notice

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

Artificial Intelligence Use Notice

1. Who this document is from

This document is from SwiftSoft Labs LLC ("we", "us"). The artificial-intelligence providers the plan names, and the uses it records.

Jurisdiction: Wyoming, United States (us-wy)

2. What the plan records

Data categories:

  • 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

Processors:

  • Google Sign-In (Sign-in and identity), United States, transfer: Standard contractual clauses, agreement: https://business.safety.google/processorterms/
  • InsForge (Hosting and infrastructure), United States, transfer: Standard contractual clauses, agreement: https://insforge.dev/dpa
  • OpenRouter (Artificial intelligence), United States, transfer: Standard contractual clauses, agreement: https://openrouter.ai/data-processing-agreement
  • Sentry (Monitoring and error reporting), United States, transfer: Standard contractual clauses, agreement: https://sentry.io/legal/dpa/
  • Vercel (Hosting and infrastructure), United States, transfer: Standard contractual clauses, agreement: https://vercel.com/legal/dpa

Merchant of record: Kelviq. It sells the service to buyers as an independent controller under its own terms, so it is not a processor or a subprocessor.

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.

Minimum age: 18

Sensitive data: Biometric likeness: face photos used to build an Identity Kit

Purposes: operational (Contract)

No certification was recorded. A detected dependency is not proof that a control runs in production.

3. Models and automated decisions

Creators' face photos, trigger word, physical descriptors, wardrobe photos and prompts, and fans' request prompts, go through OpenRouter to Google Gemini models (Gemini 2.5 Flash-Lite for text; Gemini 3.1 Flash-Lite Image, 3.1 Flash Image and 3 Pro Image for images) to check photos, screen and expand prompts, and generate images.

Artificial intelligence providers: OpenRouter

Generated images are AI output and can be wrong. The app records content credentials (C2PA) for them. The automated prompt check can reject a fan request before it reaches the creator, and a rejected request is not charged. Every request that passes the check is accepted or declined by the creator, not by AI. We make no automated decision with legal or similarly significant effect about you.

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.

4. Changes and contact

Questions go to legal@swiftsoftlabs.com. Our address is 312 W 2nd St, PO Box 5309, Casper, WY 82601.

We may update this document. A change does not by itself mean a control was deployed.

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