SwiftSoft Labs

SafeBuilds 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 prompts and AI output (form drafts, compliance explanations, audit summaries)
  • Account credentials (password hash, 2FA, passkeys, verification and reset codes)
  • Audit ledger entries (actor email and role, action, target)
  • Billing customer and subscription IDs
  • Form submissions, as each customer defines them
  • Form templates (field definitions)
  • Google account ID (sign in with Google)
  • IP address and browser details in hosting logs and error reports
  • Name (optional)
  • Organization name, industry and workspace role
  • Sign-in event log (account, action, time)
  • Usage analytics (anonymous page views on public pages)
  • Work email address
  • 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, 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: Account and workspace data are kept while the account is active and for 90 days after it is closed. A customer can ask us to delete its form templates, form submissions and audit entries by writing to legal@swiftsoftlabs.com, and we delete them within 30 days. There is no self-service account deletion yet. 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

The builder's prompt and industry, form templates with their compliance findings, and audit ledger entries are sent through the InsForge AI gateway to OpenRouter, which routes them to OpenAI GPT-4o mini (form drafts) or Google Gemini 2.5 Flash-Lite (compliance explanations and audit summaries). Audit ledger entries include team members' email addresses and roles.

Artificial intelligence providers: OpenRouter

AI output can be wrong. The compliance advisor's explanations are not legal advice, and an AI-drafted form is a starting point for you to check. We make no automated decision with legal or similarly significant effect about you. Never put protected health information into an AI feature.

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:11:47 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 b32e1b478fcede2a3dfb8374af74f2c098bdefd6dcaa1ade8db54d30adfd1ad9 -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/safebuilds?version=1.0.0' | jq -j .signature.manifest > manifest.json
curl -s 'https://synlex.swiftsoftlabs.com/api/public/v1/swiftsoftlabs/safebuilds?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