SwiftSoft Labs

Deepfluence Refund Policy

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

Refund Policy

1. Who this policy is from

This policy is from SwiftSoft Labs LLC ("we", "us"). It explains when you can get your money back for what you buy from us.

Jurisdiction: Wyoming, United States (us-wy)

Purchases are made from Kelviq, which sells the service to you as merchant of record and handles payment, sales tax or VAT, invoices, and refunds under its own buyer terms. This policy adds to those terms. It takes away no refund they give you.

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

2. Our refund rule

Refund: no refund.

We offer no refund beyond those that Kelviq's buyer terms or the law give you.

3. How to ask for a refund

Write to legal@swiftsoftlabs.com. Tell us the email address on your account and what you bought, so we can find the purchase.

You can also ask Kelviq directly, as its buyer terms describe.

We will confirm that we received your request and tell you our decision.

4. How a refund is paid

Kelviq pays a refund back to the payment method you used. How long it takes to appear depends on Kelviq and your bank.

Nothing in this policy limits a right the law gives you that cannot be waived.

6. Changes and contact

We may update this policy. A change applies to purchases made after it is published. Questions go to 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 12:16:57 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 5834e72f2c472bfa0c25631a0387ca1b7a10b1839cd32bb2fb1b9b73b4baae9f -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/deepfluence?version=1.0.0' | jq -j .signature.manifest > manifest.json
curl -s 'https://synlex.swiftsoftlabs.com/api/public/v1/swiftsoftlabs/deepfluence?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