SwiftSoft Labs

PostDose 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:

  • Community posts, saved posts and reports you submit
  • Crash logs sent to Sentry
  • Email address
  • Google account ID, if you sign in with Google
  • Health info: GLP-1 medication, dose, injection dates, sites and notes
  • Health info: meal, water and recipe logs, allergies and diet preferences
  • Health info: nausea feedback, food-noise urges and water sips from toolkits
  • Health info: symptom check-ins (nausea, fatigue, food noise) and notes
  • Health info: weight, height, activity level, protein and water targets
  • Meal and menu photos sent for AI analysis, not stored
  • Monthly AI feature usage counts for plan limits
  • Name and display name
  • Password (stored as a bcrypt hash)
  • Performance and error diagnostics sent to Sentry
  • Purchase history: plan, status, renewal date and Kelviq customer ID
  • Sign-in audit log: IP address and user agent
  • Sign-in sessions and one-time verification codes
  • ip address

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
  • 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 your account is active. Deleting your account in the app erases your profile, health logs, meals, community posts and sign-in data at once. Subscription, billing and audit records are kept as tax and accounting law requires, with email, name and IP details removed. Signing out removes your sign-in tokens from the device; other app data on the device stays until you delete the app.

Minimum age: 18

Sensitive data: Health data: GLP-1 medication, dose and injection log, Health data: weight, height, symptoms, meals and allergies

Purposes: operational (Contract (legitimate interests for error monitoring))

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