SwiftSoft Labs

Slotfill Healthcare and Wellness Notice

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

Healthcare and Wellness Notice

1. Who this document is from

This document is from SwiftSoft Labs LLC ("we", "us"). Whether the plan records health, biometric, or wellness data. It does not decide that a health-privacy law applies.

Jurisdiction: Wyoming, United States (us-wy)

2. What the plan records

Data categories:

  • AI prompts and output
  • Account credentials (password, 2FA, passkeys, sign-in codes)
  • Billing customer ID and plan
  • Clinic team membership and role
  • Email address
  • Google account ID (sign-in)
  • Message templates and AI settings
  • Name
  • Patient appointment times and waitlist preferences
  • Patient insurance information
  • Patient name, phone number and email address
  • Patient reliability and urgency scores
  • Sign-in abuse-limit records (IP address)
  • Text and email messages with patients, including patient replies
  • Usage analytics

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/
  • Twilio (Email and messaging), United States, transfer: Standard contractual clauses, agreement: https://www.twilio.com/en-us/legal/data-protection-addendum
  • 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 and the patient records, appointments, waitlists and messages a clinic stores are kept until the clinician deletes the account in Settings > Security, which removes them. A clinic can ask legal@swiftsoftlabs.com to delete one patient's records, and we do so within 30 days. Billing and security audit records are kept as tax, accounting and security needs require.

Minimum age: 18

Sensitive data: Health data: patient status and appointments at a mental health practice

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

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

3. Health and wellness data

No health or wellness program. Clinics use SlotFill to offer cancelled appointment slots to their own patients. The service is not represented as HIPAA compliant, and no Business Associate Agreement is offered at launch.

Health or wellness data: Health data: patient status and appointments at a mental health practice

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 19:00:21 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 a02235963ca2978932be19c2961f21275a23092e5a76187cf53cd9446db0d6bb -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.vercel.app/api/public/v1/swiftsoftlabs/slotfill?version=1.0.0' | jq -j .signature.manifest > manifest.json
curl -s 'https://synlex.vercel.app/api/public/v1/swiftsoftlabs/slotfill?version=1.0.0' | jq -r .signature.value | base64 -d > manifest.sig
curl -s 'https://synlex.vercel.app/.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