SwiftSoft Labs

Fortress Subprocessor List and Disclosure

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

Subprocessor List and Disclosure

1. Who this document is from

This document is from SwiftSoft Labs LLC ("we", "us"). The processors on the plan. A package the scan found is not, by itself, proof of a production subprocessor.

Jurisdiction: Wyoming, United States (us-wy)

2. What the plan records

Data categories:

  • AI prompts built from your entity, property and account data, and AI output
  • AI-generated documents (Operating Agreement addenda)
  • Account credentials (password hash, 2FA, passkeys)
  • Billing customer ID and subscription status
  • Email address
  • Entity names, types, jurisdictions and EINs
  • Investor class and investment preferences
  • Name and profile photo (Google sign-in)
  • Payment card brand, last four digits, expiry and cardholder name (simulated)
  • Property addresses, listing links and prices
  • Simulated bank account records and balances
  • Simulated filing jobs and compliance deadlines
  • Usage analytics (anonymous page views)
  • ip address
  • request bodies
  • request url path and query string

Processors:

  • Apify (Hosting and infrastructure), United States, transfer: Standard contractual clauses, agreement: https://docs.apify.com/legal/data-processing-addendum
  • Google (Artificial intelligence), 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, 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: While the account is active plus 90 days; deletion on request within 30 days. There is no self-service deletion or export: email legal@swiftsoftlabs.com to ask.

Minimum age: 18

Sensitive data: Financial and investment profile (investor class, EINs)

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

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

3. Subprocessors the plan names

No flow-down contract was recorded other than a vendor agreement link.

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:16: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 3ce12fe6c18841d9fbbeed759cd6e37c6922e24aaa9dc9e31d8c42844fa6442f -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/fortress?version=1.0.0' | jq -j .signature.manifest > manifest.json
curl -s 'https://synlex.swiftsoftlabs.com/api/public/v1/swiftsoftlabs/fortress?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