SwiftSoft Labs

UxRay 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

  • Account holders
  • Invited team members (email address only)
  • People who use the contact form
  • Viewers of shared report links

3. The personal data we collect

We collect the following categories of personal data:

  • Account credentials (password, 2FA, passkeys)
  • Billing customer ID and subscription status
  • Contact form messages
  • Email address
  • Name
  • Profile picture or avatar
  • Scanned website addresses, scan results and AI summaries
  • Screenshots of scanned pages (optional, Growth plan)
  • Shared report links
  • Sign-in IP address and browser details (security log)
  • Team membership and invited email addresses
  • Usage analytics
  • ip address (through Sentry)
  • request bodies (through Sentry)
  • request url path and query string (through Sentry)

We do not collect these categories, even though a tool we use can:

  • payment card details: Only the unused stripe package names it; Stripe is not used, and Kelviq, the merchant of record, takes payments.

4. Sensitive personal data

We do not ask for sensitive personal data, such as data about health, ethnic origin, political opinions, religion, sexual orientation, or biometric identity, and the service is not designed to collect it. Please do not send it to us.

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. Anonymous page-view analytics on public marketing pages (session storage only, no advertising cookies)
  • 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.

Google Sign-In

  • Service: Sign-in and identity
  • Purpose: Sign in with a Google account
  • Data received: Google account id, email address, name, profile picture
  • Location: United States
  • Data processing agreement: https://business.safety.google/processorterms/

InsForge

  • Service: Hosting and infrastructure
  • Purpose: Database, private file storage, authentication emails and AI gateway
  • Data received: Account data (email, name, avatar, credentials), team and invitee emails, scanned URLs, results and AI summaries, optional screenshots, share links, contact messages, billing customer id and status
  • Location: United States
  • Data processing agreement: https://insforge.dev/dpa

OpenRouter

  • Service: Artificial intelligence
  • Purpose: AI model routing (Google Gemini 2.5 Flash-Lite, reached through the InsForge AI gateway) for AI summaries, issues, persona analysis and optional screenshot vision
  • Data received: Scanned page content and URLs, optional screenshots of scanned pages
  • Location: United States
  • Data processing agreement: https://openrouter.ai/data-processing-agreement

PostHog

  • Service: Analytics
  • Purpose: Anonymous marketing page-view analytics
  • Data received: Usage analytics (page views, anonymous session id, browser details)
  • Location: United States
  • Data processing agreement: https://posthog.com/dpa

Resend

  • Service: Email and messaging
  • Purpose: Sending transactional email (team invitations, notifications)
  • Data received: Recipient email addresses, names, email content
  • Location: United States
  • Data processing agreement: https://resend.com/legal/dpa

Sentry

  • Service: Monitoring and error reporting
  • Purpose: Error and performance monitoring
  • Data received: IP address, browser details, request URL path and query string, request bodies, error stack traces
  • Location: United States
  • Data processing agreement: https://sentry.io/legal/dpa/

Vercel

  • Service: Hosting and infrastructure
  • Purpose: Hosting the web app and serving requests
  • Data received: Request logs (IP address, browser details, requested URLs)
  • 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/

**Independent services.** Browserless runs the headless browser we use to scan pages. When you ask us to scan a page, our server sends Browserless the page's address, and Browserless loads the page and returns the rendered page and screenshots. Browserless acts under its own privacy policy, not on our behalf: https://www.browserless.io/privacy-policy

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.

  • Google Sign-In: United States. Transfer mechanism: Standard contractual clauses.
  • InsForge: United States. Transfer mechanism: Standard contractual clauses.
  • OpenRouter: United States. Transfer mechanism: Standard contractual clauses.
  • PostHog: United States. Transfer mechanism: Standard contractual clauses.
  • Resend: United States. Transfer mechanism: Standard contractual clauses.
  • Sentry: United States. 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.

10. Cookies and similar technologies

UxRay sets four HttpOnly cookies on its own domain that keep you signed in and keep sign-in secure: `ux_access`, `ux_refresh`, `ux_oauth_state` and `ux_mfa_pending`. Your browser also keeps your theme (`uxray-theme`) and the team you last chose (`defaultTeamId`, `dashboardTeamId`) in local storage, and flags for a checkout you started in session storage.

On our public pages, PostHog counts page views with a random ID (`ssl-marketing-distinct-id`) kept in your browser's session storage, which is cleared when you close the tab. We set no advertising cookies.

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: Account data and scan data (projects, scans, results, teams and uploads) are kept until you delete your account in Account settings, which removes them from our database and storage. Shared report links are kept until you revoke them or they expire. Billing records are kept as tax and accounting law requires.

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.

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.

Not established. The model providers (InsForge, OpenRouter and Google) act under their own terms.

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 11:27:20 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 2c4b7fdf8559ef3875f7b162280cf80fa18e1ca71aca2596595d8c9e9dc3f6bd -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/uxray?version=1.0.0' | jq -j .signature.manifest > manifest.json
curl -s 'https://synlex.vercel.app/api/public/v1/swiftsoftlabs/uxray?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