SwiftSoft Labs

CodeRunner Account Deletion and Data Erasure

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

Account Deletion and Data Erasure

1. Who this policy is from

This policy is from SwiftSoft Labs LLC ("we", "us"). It explains how you ask us to delete personal data we hold about you.

Jurisdiction: Wyoming, United States (us-wy)

2. What you can ask us to delete

You can ask us to delete the personal data described in our Privacy Policy, including the data tied to your account.

You can also ask us to tell you what we hold and to correct it. Those requests use the same contact.

3. How to ask

Write to legal@swiftsoftlabs.com. Tell us the email address on the account and what you want deleted, so we can find it.

We may need to confirm who you are before we delete anything. We will tell you if we need more information.

4. What we delete and what we keep

Retention: Account, profile, runs, prompts, code, replays and sign-in logs are kept until your account is deleted. There is no self-service deletion yet: email legal@swiftsoftlabs.com and we delete your account and its runs, prompts, code and replays, including from leaderboards and replay pages, within 30 days. Billing records are kept as tax and accounting law requires.

When that period ends we delete the data or make it anonymous. We keep a record where the law requires us to, and we tell you if we refuse a request for that reason.

5. Providers who hold data for us

We will ask these providers to delete the personal data they hold for us when we delete it:

  • Google Sign-In
  • InsForge
  • OpenRouter
  • PostHog
  • Sentry
  • Vercel

Kelviq sells the service as merchant of record and keeps its own purchase records under its own privacy policy. Ask it directly to delete them: https://www.kelviq.com/buyer-privacy/

6. How long a request takes

We delete your account and its runs, prompts, code and replays within 30 days of confirming the request, and we tell you when it is done. We answer other requests within one month.

7. Changes and contact

We may update this policy. Questions go to legal@swiftsoftlabs.com. Our address is 312 W 2nd St, PO Box 5309, Casper, WY 82601.

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:15:54 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 880f40955bbc9359e05f7f92fae103caa052d46a9d1278d61415a555509d42eb -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/coderunner?version=1.0.0' | jq -j .signature.manifest > manifest.json
curl -s 'https://synlex.vercel.app/api/public/v1/swiftsoftlabs/coderunner?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