SwiftSoft Labs

Vibemend 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

  • Clients who book debugging sessions
  • Experts who offer sessions
  • Website visitors

3. The personal data we collect

We collect the following categories of personal data:

  • AI session summaries and recaps
  • Account credentials (password hash, email verification and sign-in codes)
  • Billing customer ID
  • Call transcripts
  • Email address
  • Expert onboarding assessment answers and scores
  • Expert payout settings and payout ledger
  • Expert tax form details (legal name, address, tax status, birth date on W-8BEN)
  • Google or GitHub account ID (sign-in)
  • Issue descriptions, code snippets and error text
  • Live call audio, video and screen share (relayed, not recorded)
  • Name and display name
  • Profile details (avatar, bio, skills, hourly rate, availability, time zone)
  • Reviews, ratings and disputes
  • Session chat messages
  • Session cost, payment and refund records
  • Sign-in and session records (IP address, browser user agent)
  • ip address (through Sentry)

**Live calls.** A session is a live video call with screen sharing. It runs through our own media server. We do not record the audio or video. Our own speech-to-text software turns what is said into a transcript, which both people in the session can see and which we store with the session. The join screen tells you that the call may be transcribed before you join. The transcript and chat are used for the AI recap described in the section on artificial intelligence providers, and we may review them if a dispute is raised about the session.

4. Sensitive personal data

We collect the following sensitive personal data, from experts only:

  • Bank and payout account details (experts only)
  • Government ID document (experts only, via Sumsub)
  • Selfie for identity verification (experts only, via Sumsub)
  • Tax ID numbers: SSN, EIN or foreign tax ID (experts only)

We use it only for the purposes in this policy: to check an expert's identity before their profile is listed, to set up payouts, and to keep the tax forms the law requires. Sumsub collects the ID document and selfie in its own verification screen and keeps them; we keep only the result of the check. Full US tax ID numbers on W-9 forms are encrypted. We do not ask clients for any of this data.

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. Expert identity checks before listing, bot protection on sign-up, sign-in and booking, and error tracking to keep the service working and safe
  • 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.

Cloudflare Turnstile

  • Service: Hosting and infrastructure
  • Purpose: Bot protection on sign-up, sign-in and booking
  • Data received: IP address, browser and device signals
  • Location: United States
  • Data processing agreement: https://www.cloudflare.com/cloudflare-customer-dpa/

GitHub sign-in

  • Service: Sign-in and identity
  • Purpose: Sign in with GitHub (OAuth)
  • Data received: GitHub account ID, login, email, avatar, IP address, browser user agent
  • Location: United States
  • Data processing agreement: https://github.com/customer-terms/github-data-protection-agreement

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/

Hetzner

  • Service: Hosting and infrastructure
  • Purpose: Server for live calls (our own LiveKit media server) and our own speech-to-text transcription
  • Data received: Live call audio, video and screen share, transcript text, IP address
  • Location: United States
  • Data processing agreement: https://www.hetzner.com/AV/DPA_en.pdf

InsForge

  • Service: Hosting and infrastructure
  • Purpose: Database hosting, account and transactional email, scheduled tasks
  • Data received: All stored account, session, chat, transcript, payment, payout and tax form data; email addresses
  • Location: United States
  • Data processing agreement: https://insforge.dev/dpa

OpenRouter

  • Service: Artificial intelligence
  • Purpose: AI gateway to Google Gemini 2.5 Flash for issue summaries, session recaps and onboarding quiz questions
  • Data received: Issue descriptions and error text, call transcript excerpts, session chat (secrets, emails and phone numbers removed)
  • Location: United States
  • Data processing agreement: https://openrouter.ai/data-processing-agreement

Sentry

  • Service: Monitoring and error reporting
  • Purpose: Error and performance monitoring
  • Data received: Error details, page URLs, IP address, browser user agent
  • Location: United States
  • Data processing agreement: https://sentry.io/legal/dpa/

Sumsub

  • Service: Sign-in and identity
  • Purpose: Expert identity verification (ID document and selfie check)
  • Data received: Government ID document images, selfie, name, country, user ID (experts only)
  • Location: Not provided
  • Data processing agreement: https://sumsub.com/files/data_processing_agreement.pdf

Vercel

  • Service: Hosting and infrastructure
  • Purpose: Website and application hosting
  • Data received: All web traffic, IP address, 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/

**Other users.** The client and the expert in a session see each other's display name and avatar, the chat, the shared screen and the call transcript. Expert profiles (display name, avatar, bio, tagline, skills, hourly rate, rating, time zone and hours) and reviews are public on the marketplace.

**Independent services.** These services receive data directly and use it under their own privacy policies, not on our behalf:

  • Plaid: when a US expert connects a bank account for payouts, the bank sign-in happens in Plaid's own window. Plaid receives the bank account details and our ID for the expert. Privacy policy: https://plaid.com/legal/
  • Revolut Business: for experts outside the US, Revolut receives the expert's name, country, currency and the bank details entered in payout settings. Privacy policy: https://www.revolut.com/legal/privacy/
  • TaxBandits: after a US expert submits a W-9, it checks the legal name and tax ID number against IRS records. Privacy policy: https://www.taxbandits.com/privacy-policy/
  • Google Fonts: our icon font loads from Google's servers, which receive your IP address and browser details. Privacy policy: https://policies.google.com/privacy

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.

  • Cloudflare Turnstile: United States. Transfer mechanism: Standard contractual clauses.
  • GitHub sign-in: United States. Transfer mechanism: Standard contractual clauses.
  • Google Sign-In: United States. Transfer mechanism: Standard contractual clauses.
  • Hetzner: United States. Transfer mechanism: No transfer outside the region.
  • InsForge: United States. Transfer mechanism: Standard contractual clauses.
  • OpenRouter: United States. Transfer mechanism: Standard contractual clauses.
  • Sentry: United States. Transfer mechanism: Standard contractual clauses.
  • Sumsub: Not provided. 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.
  • No transfer outside the region: no safeguard, because the data stays inside the region.

10. Cookies and similar technologies

The service uses cookies and browser storage to run, to keep you signed in, and to keep the service secure. It sets no analytics or advertising cookies.

  • Cookies (first-party, HttpOnly): `vm_access_token` and `vm_refresh_token` keep you signed in. `vm_2fa_challenge` holds a sign-in code step for 10 minutes. `vm_oauth_state` and `vm_oauth_role` protect Google or GitHub sign-in for 10 minutes.
  • Session storage, cleared when you close the tab: `vibemend_issue_draft` (the issue you are booking help for), `vibemend_post_auth_path` and `vibemend_pending_role` (where to go after sign-in), `vm-session-join:<id>` and `vm-session-live:<id>` (call settings and live transcript for a session), and `vm:dismissed-incoming-sessions` (session requests an expert dismissed).
  • Local storage: `vibemend-session-noise-cancellation` remembers your noise-cancellation setting.

Cloudflare Turnstile and Sumsub may store data on your device in their own frames, under their own policies. Our Cookie Policy lists them and explains how to change your choices.

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: Kept until you delete your account in Settings. Deletion removes your profile, sign-in links and saved experts, deletes the chat and transcripts of your sessions, and signs you out. Session, payment, refund, payout and tax form records stay, linked to the anonymized account, as tax and accounting law requires. Sumsub keeps ID documents and selfies; we keep only the verification status.

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.

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, which sends our requests to Google Gemini 2.5 Flash.

  • Before a session, the client's issue description and error text are sent to write a short summary for the expert.
  • After a session, the call transcript, the chat, the issue description and the session's tools are sent to write a recap.
  • When an expert starts the onboarding quiz, their tools and skills are sent to write the questions. Our own code scores the answers.

Secrets, email addresses and phone numbers are removed from the text before it is sent.

When you use a feature that relies on one of them, the content you send to that feature is passed to the provider so that it can return a result. Do not put personal data into such a feature unless you need to.

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:02:14 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 660d059200702874f41fe0d34d6966494cb5e8ab18668e9ab1ee898103b0a2bd -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/vibemend?version=1.0.0' | jq -j .signature.manifest > manifest.json
curl -s 'https://synlex.vercel.app/api/public/v1/swiftsoftlabs/vibemend?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