SwiftSoft Labs

Slotfill Privacy Policy

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

Privacy Policy

1. Who we are

SwiftSoft Labs LLC ("we", "us") decides how the personal data described in this policy is used.

  • Legal name: SwiftSoft Labs LLC
  • Legal form: Registered company (LLC, corporation or similar)
  • Jurisdiction: Wyoming, United States (us-wy)
  • Contact email: legal@swiftsoftlabs.com
  • Address: 312 W 2nd St, PO Box 5309, Casper, WY 82601
  • Data protection contact: legal@swiftsoftlabs.com

2. Whose data this covers

  • Clinicians and clinic staff (account holders)
  • Patients of our clinic customers (we process their data for the clinic)
  • Website visitors

**Patient data.** SlotFill is used by mental health practices. A clinic decides which patients it adds, and which patient details, appointments and messages it stores. For that data the clinic is the controller, and SwiftSoft Labs LLC processes it only on the clinic's instructions to run the service. A data processing agreement is available to clinics on request at legal@swiftsoftlabs.com. If you are a patient, send questions and requests about your data to your clinic first. We will help the clinic answer them.

3. The personal data we collect

We collect the following categories of personal data:

  • 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

We do not collect these categories, even though a tool we use can:

  • request bodies: Our Sentry setup removes request bodies, cookies and headers from every error report before it is sent.

4. Sensitive personal data

We collect the following sensitive personal data:

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

That a person is a patient of a mental health practice, and when their appointments are, is health data. Patient replies to our texts and emails are stored as the patient writes them, and may contain more. We process this data for the clinic, and we use it only for the purposes in this policy.

SlotFill is not represented as HIPAA compliant, and we do not sign Business Associate Agreements at launch. A clinic that is subject to HIPAA must decide whether it may use the service without one.

5. Children

Minimum age: 18

The service is for people who are 18 or older. We do not knowingly collect personal data from anyone younger.

If you believe a person younger than 18 has given us personal data, write to legal@swiftsoftlabs.com and we will delete it.

6. Why we use personal data

  • Understanding how the service is used (behavioral). Legal basis: Legitimate interests. Anonymous page views on public pages, sign-in abuse limits and error tracking to keep the service working
  • Operating and providing the service (operational). Legal basis: Contract.

7. Marketing email

We do not send marketing email.

8. Who we share personal data with

We use the service providers below. Each one processes personal data on our behalf and under a data processing agreement where one is listed. They may use the data only to provide their service to us.

Google Sign-In

  • Service: Sign-in and identity
  • Purpose: Sign in with Google (OAuth)
  • Data received: Google account ID, email, name, IP address, browser user agent
  • Location: United States
  • Data processing agreement: https://business.safety.google/processorterms/

InsForge

  • Service: Hosting and infrastructure
  • Purpose: Database and email delivery (sign-in codes and patient slot offers)
  • Data received: Account data, patient names, phones, emails, insurance info, appointment times and messages
  • Location: United States
  • Data processing agreement: https://insforge.dev/dpa

OpenRouter

  • Service: Artificial intelligence
  • Purpose: AI gateway to Google Gemini 2.5 Flash-Lite for picking waitlist candidates, drafting offers and reading replies
  • Data received: Patient display name, waitlist urgency and preferences, provider name, slot time, patient reply text
  • Location: United States
  • Data processing agreement: https://openrouter.ai/data-processing-agreement

PostHog

  • Service: Analytics
  • Purpose: Anonymous page-view counts on public marketing pages
  • Data received: Random session ID, page URL, IP address and browser user agent
  • Location: United States
  • Data processing agreement: https://posthog.com/dpa

Sentry

  • Service: Monitoring and error reporting
  • Purpose: Error monitoring
  • Data received: Opaque user ID, page URL without query string, error stack traces; cookies, headers and request bodies are removed before sending
  • Location: United States
  • Data processing agreement: https://sentry.io/legal/dpa/

Twilio

  • Service: Email and messaging
  • Purpose: Text messages to patients offering open slots, and their replies
  • Data received: Patient phone number, first name, slot time, message text and replies
  • Location: United States
  • Data processing agreement: https://www.twilio.com/en-us/legal/data-protection-addendum

Vercel

  • Service: Hosting and infrastructure
  • Purpose: Hosting the web app and running scheduled jobs
  • Data received: All request data, including IP address and browser user agent
  • Location: United States
  • Data processing agreement: https://vercel.com/legal/dpa

Purchases are made from Kelviq, which sells the service to you as merchant of record. The payment details you give at checkout go to Kelviq. It uses them as an independent controller, not on our behalf, under its own privacy policy.

Kelviq's privacy policy: https://www.kelviq.com/buyer-privacy/

**Services that act on their own.** Some pages load files directly from other services. Your browser then sends them your IP address and browser details. They act under their own privacy policies, not on our behalf:

  • Google Fonts and Google-hosted images: fonts and icons on every page, and some images on our home and onboarding pages. Google's privacy policy: https://policies.google.com/privacy
  • DiceBear: avatar pictures in the dashboard. It receives a person's initials or a short code made from their account ID, never an email address. DiceBear's privacy policy: https://www.dicebear.com/legal/privacy-policy

9. Transfers outside your country

Some providers handle personal data outside the country where you live. Where the law requires a safeguard for that transfer, we rely on the mechanism listed here.

  • Google Sign-In: United States. Transfer mechanism: Standard contractual clauses.
  • InsForge: United States. Transfer mechanism: Standard contractual clauses.
  • OpenRouter: United States. Transfer mechanism: Standard contractual clauses.
  • PostHog: United States. Transfer mechanism: Standard contractual clauses.
  • Sentry: United States. Transfer mechanism: Standard contractual clauses.
  • Twilio: United States. Transfer mechanism: Standard contractual clauses.
  • Vercel: United States. Transfer mechanism: Standard contractual clauses.

The safeguards we rely on:

  • Standard contractual clauses: the standard contractual clauses approved by the European Commission.

10. Cookies and similar technologies

We set secure, HttpOnly cookies on our own domain that keep you signed in and protect sign-in: `sl_access` and `sl_refresh` (your session), `sl_mfa_pending` (during a two-step sign-in), `sl_oauth_state` (during Google sign-in) and `sl_legal_consent` (records that you accepted our terms while you sign up with Google).

Your browser's session storage keeps `ssl-marketing-distinct-id`, a random ID PostHog uses to count page views on our public pages, and short-lived checkout flags (`sf_checkout_open`, `sf_checkout_needs_abandon`, `sf_checkout_activating`). Session storage is cleared when you close the tab.

We do not set analytics or advertising cookies. Our Cookie Policy has the details.

11. How long we keep personal data

We keep personal data only for as long as it is needed for the purposes in section 6, or as the law requires. When it is no longer needed we delete it or make it anonymous.

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.

12. Your rights

You can ask us to tell you what personal data we hold about you, to give you a copy, to correct it, and to delete it. Write to legal@swiftsoftlabs.com. We may need to confirm who you are before we act, and we answer within one month.

If you are in the European Economic Area, the United Kingdom or Switzerland, you also have the right to restrict our use of your data, to object to it (including use based on legitimate interests), to receive your data in a portable format, and to withdraw consent at any time without affecting earlier use. You can complain to the data protection authority where you live or work.

If you live in a US state with a privacy law, such as California, you have similar rights to know, correct and delete your data, and we will not treat you differently for using them. We do not sell personal data or share it for targeted advertising.

If you are a patient of one of our clinic customers, the clinic controls your data. Ask the clinic first; if you write to us, we will pass your request to the clinic and help it answer.

13. Security

We use technical and organisational measures that fit the risk to protect personal data against loss, misuse, and unauthorised access. These include controlling who can reach the data and limiting access to the people and providers who need it.

No system is completely secure. If a breach puts your rights at risk, we will tell you and the authorities where the law requires it.

14. Artificial intelligence providers

We use these artificial intelligence providers: OpenRouter.

Google Gemini 2.5 Flash-Lite, reached through OpenRouter, picks a waitlist candidate for an open slot, drafts the offer, and reads the patient's reply to decide whether to book. It receives the patient's display name, waitlist urgency and preferences, the provider's name, the slot time and the patient's reply text. Clinicians can also preview AI replies in the dashboard.

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.

15. Changes to this policy

We may update this policy. When we make a material change we will update it here and, where the law requires, tell you.

16. Contact us

To use a right or ask a question, write to legal@swiftsoftlabs.com or to our data protection contact at legal@swiftsoftlabs.com.

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