SwiftSoft Labs

StackedStage 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 (artists and venues)
  • Website visitors

3. The personal data we collect

We collect the following categories of personal data:

  • AI assistant chats and contract text sent for explanation
  • AI usage counts
  • Account credentials (password hash, verification and reset codes)
  • Artist profile (stage name, bio, genres, rate, radius, scores, track record)
  • Billing customer and subscription IDs
  • Cancellations and disputes
  • Email address
  • Gigs, bids and offers, with budgets and messages
  • Google or Spotify account ID (sign-in)
  • Inbox messages and notifications
  • Name
  • Reviews and ratings
  • Settlement records (attendance and agreed payout; ledger only)
  • Sign-in session records
  • Usage analytics
  • Venue profile (name, location as entered, capacity, preferences, tech rider)
  • ip address (through Sentry)
  • request bodies (through Sentry)
  • request url path and query string (through Sentry)

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 pages (session storage only, no advertising cookies) and error tracking to keep the service working
  • 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 Google (OAuth)
  • Data received: Google account ID, email address, name
  • Location: United States
  • Data processing agreement: https://business.safety.google/processorterms/

InsForge

  • Service: Hosting and infrastructure
  • Purpose: Database, transactional sign-in email and realtime updates
  • Data received: Account, profile, gig, offer, settlement, review, message, dispute, AI usage and billing ID data; email addresses and sign-in emails
  • Location: United States
  • Data processing agreement: https://insforge.dev/dpa

OpenRouter

  • Service: Artificial intelligence
  • Purpose: AI gateway to Google Gemini 2.5 Flash-Lite and Gemini 2.5 Flash for the assistant and AI writing tools
  • Data received: Chat messages, gig, application, offer and track-record context, venue location text, artist bios, contract text
  • Location: United States
  • Data processing agreement: https://openrouter.ai/data-processing-agreement

PostHog

  • Service: Analytics
  • Purpose: Anonymous page-view analytics on public pages (no cookies)
  • Data received: Page URL, a random per-session ID, IP address and browser details
  • Location: United States
  • Data processing agreement: https://posthog.com/dpa

Sentry

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

Vercel

  • Service: Hosting and infrastructure
  • Purpose: Hosting, serving requests and the daily score cron job
  • Data received: Request logs (IP address, browser details, URLs) and all data passing through the app
  • 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 and the public.** StackedStage connects venues and artists, so some of what you enter is shown to others. An artist's stage name, scores, badges, performance history and reviews, and a venue's name, location as entered, capacity and open gigs, appear on public pages that anyone can see. Bids, offers, inbox messages, settlement records and dispute details go to the other party to the gig.

**Independent services.** Two services act under their own privacy policies, not on our behalf:

  • **Spotify** runs Sign in with Spotify. When you choose it, you sign in on Spotify's own pages, and Spotify returns your profile to us. We keep your Spotify account ID, email address and display name. Spotify's privacy policy: https://www.spotify.com/us/legal/privacy-policy/
  • **Lorem Picsum** (picsum.photos) serves the placeholder background photo on our sign-in and sign-up pages. When those pages load it, Lorem Picsum receives your IP address and browser details; we send no referrer. Other placeholder photos are fetched by our host, Vercel, so your browser does not contact Lorem Picsum for them. Lorem Picsum publishes no separate privacy policy; its site is https://picsum.photos

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.
  • 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

The service uses cookies and browser session storage to run, to keep you signed in, and to keep the service secure. We set no advertising cookies and use no tracking pixels.

  • **Cookies:** `ss_access_token` (15 minutes) and `ss_refresh_token` (30 days) keep you signed in. `ss_oauth_state` protects sign-in with Google or Spotify and lasts 10 minutes. We set all three on our own domain, as HttpOnly cookies.
  • **Session storage:** the progress of a checkout (`stackedstage_checkout_open`, `stackedstage_checkout_user` and `stackedstage_checkout_activating`). Your browser clears session storage when you close the tab.
  • **Analytics:** our analytics provider, PostHog, counts page views on our public pages with a random ID (`ssl-marketing-distinct-id`) that our pages keep in session storage and send to PostHog. It sets no 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, profiles, gigs, offers, messages, reviews and records are kept until the account is deleted. There is no self-service deletion yet: email legal@swiftsoftlabs.com and we delete the account within 30 days. Sign-in codes expire after 15 minutes and sessions after 30 days. 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.

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 12:16:55 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 c84e2bb56db307bf7d90618583a964df5b19d9c5e831f7da74e2a1d47fa6fc86 -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/stackedstage?version=1.0.0' | jq -j .signature.manifest > manifest.json
curl -s 'https://synlex.swiftsoftlabs.com/api/public/v1/swiftsoftlabs/stackedstage?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