SwiftSoft Labs

AfterwordsAI Artificial Intelligence Use Notice

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

This is an earlier version. Read the current version, 2.0.0.

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 email drafts, extracted deal insights and draft feedback
  • Account credentials (password hash, 2FA secrets, passkeys)
  • Billing customer and subscription records
  • Email address
  • Email templates
  • IP address and browser details in sign-in logs
  • Job title and CRM type, instance URL or portal ID
  • Meeting records: prospect name, company, time, platform and duration
  • Meeting transcripts (speakers and spoken text), summaries and sentiment
  • Name
  • Profile photo link (Google sign-in)
  • Usage analytics (anonymous page views)
  • ip address
  • request bodies
  • request url path and query string

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 (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, 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: We keep your account, meetings, transcripts, drafts and templates while your account is active. There is no delete or export button in the app yet: email legal@swiftsoftlabs.com to have your account and its data deleted or to get a copy, and we act within one month. Sign-in codes expire after 15 minutes and sessions after 30 days. 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

When you ask for a follow-up email, the meeting transcript (speaker labels and text, up to 12,000 characters) and your chosen tone go to Google Gemini 2.5 Flash-Lite through OpenRouter. It returns a draft email, a summary, a sentiment rating and deal insights (buyer, pain point, timeline, competitors, budget). Transcripts can name prospects and other people.

Artificial intelligence providers: OpenRouter

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 12:10:50 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 812442f436fd1b8c3b6d70d2dc3f66166c0bcb3ac2465d3c998d13dcf8d6607e -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/afterwordsai?version=1.0.0' | jq -j .signature.manifest > manifest.json
curl -s 'https://synlex.swiftsoftlabs.com/api/public/v1/swiftsoftlabs/afterwordsai?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