SwiftSoft Labs

LiteAI 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:

  • Billing customer ID
  • Chat messages and chat history
  • Chat titles and last-used model
  • Credit wallet balance and transactions
  • Email address
  • Error diagnostics (stack traces, IP address)
  • Name
  • Preferences (theme, Ghost Mode)
  • Profile picture (Google sign-in)
  • Sign-in and session tokens
  • Sign-in audit log (IP address, browser)
  • Usage analytics
  • ip address
  • request bodies
  • request url path and query string

Processors:

  • GitHub OAuth (Sign-in and identity), United States, transfer: Standard contractual clauses, agreement: https://github.com/customer-terms/github-data-protection-agreement
  • Google AdSense and Google Ads (Advertising), United States, transfer: Standard contractual clauses, agreement: https://business.safety.google/processorterms/
  • 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 (US-East), 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
  • PostHog (Analytics), United States (PostHog US cloud), transfer: Standard contractual clauses, agreement: https://posthog.com/dpa
  • 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: Chats are kept until you delete them or delete your account. A Ghost Mode thread stays in your browser session only. Deleting your account removes your profile, sessions and chats; wallet records are kept anonymised. Billing records are kept as tax and accounting law requires.

Minimum age: 18

Sensitive data: Not recorded.

Purposes: behavioral (Legitimate interests); operational (Contract)

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

3. Models and automated decisions

Your chat messages, recent messages of the conversation and the system prompt are sent through OpenRouter to the AI model that answers: Google Gemini 2.5 Flash Lite by default, or the model you pick, which may be run by Google, Anthropic, OpenAI, xAI, DeepSeek, MiniMax or Alibaba (Qwen). Chat titles and search embeddings are produced the same way.

Artificial intelligence providers: OpenRouter

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

Not established. The model providers reached through OpenRouter act under their own terms.

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:32:01 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 a79469db31b5d1f01e2443e46b1a11ca7ac4a37352d66bca19d32a28c7630f84 -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/liteai?version=1.0.0' | jq -j .signature.manifest > manifest.json
curl -s 'https://synlex.swiftsoftlabs.com/api/public/v1/swiftsoftlabs/liteai?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