SwiftSoft Labs

Apptribute International Data Transfer Documentation

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

International Data Transfer Documentation

1. Who this document is from

This document is from SwiftSoft Labs LLC ("we", "us"). The provider locations and transfer mechanisms the plan names.

Jurisdiction: Wyoming, United States (us-wy)

2. What the plan records

Data categories:

  • Activity log of workspace actions
  • Bank account name, last four digits and transactions (Plaid or Finicity)
  • Billing email, Kelviq customer ID and subscription status
  • Email address
  • Error reports (IP address, browser details)
  • Google account ID, email and name (Google sign-in)
  • Ledger journal entries and imported bank or accounting file lines
  • Merchant, amount and date read from receipts
  • Name (optional)
  • Names and amounts of vendors, customers and contractors in ledger data
  • Payment events imported from a connected Kelviq account
  • Projects, expenses and allocations
  • Receipt images (read by AI, not stored)
  • Sign-in codes and session tokens
  • Usage analytics (anonymous page views)
  • Vendor bills, approvals, invoices and invoice PDFs
  • Workspace member roles
  • Workspace name, legal name, country and currency
  • ip address
  • request bodies
  • request url path and query string

Processors:

  • Google Gemini (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
  • 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: Posted ledger entries cannot be edited or deleted; they are kept for the legal and audit period, and corrections use reversing entries. Other account data is kept while the account is active and for 90 days after. There is no self-service deletion: email legal@swiftsoftlabs.com. Receipt images are not stored. Billing records are kept as tax law requires.

Minimum age: 18

Sensitive data: Business financial records

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

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

3. Transfers the plan names

Every provider named above has a transfer mechanism.

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