SwiftSoft Labs

SafeBuilds Privacy Policy

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

This is an earlier version. Read the current version, 2.0.0.

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

  • Customer team members (account holders)
  • Respondents to customer forms (we process their data for the customer)
  • Website visitors

When a customer stores form submissions in SafeBuilds, the customer decides what its forms collect and why. We process that data only to run the service for the customer and on its instructions. If you answered a customer's form, contact that customer to use your rights. We will help the customer respond.

3. The personal data we collect

We collect the following categories of personal data:

  • AI prompts and AI output (form drafts, compliance explanations, audit summaries)
  • Account credentials (password hash, 2FA, passkeys, verification and reset codes)
  • Audit ledger entries (actor email and role, action, target)
  • Billing customer and subscription IDs
  • Form submissions, as each customer defines them
  • Form templates (field definitions)
  • Google account ID (sign in with Google)
  • IP address and browser details in hosting logs and error reports
  • Name (optional)
  • Organization name, industry and workspace role
  • Sign-in event log (account, action, time)
  • Usage analytics (anonymous page views on public pages)
  • Work email address
  • 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. Please do not send it to us.

The form builder offers field types labelled for healthcare, real-estate escrow and legal matters. They are design aids only. Customers must not use SafeBuilds to collect or store protected health information, privileged legal material or other regulated data, as our Terms of Service say. We have no business associate agreement (BAA) under HIPAA with customers or with our providers.

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. Keep accounts secure, track errors, and count anonymous page views on public pages
  • Operating and providing the service (operational). Legal basis: Contract. Run customer accounts, the form builder, AI form drafting and billing

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, sign-in emails and the AI gateway function
  • Data received: Account and workspace data, form templates and submissions, audit ledger, email address for sign-in codes, AI requests
  • Location: United States
  • Data processing agreement: https://insforge.dev/dpa

OpenRouter

  • Service: Artificial intelligence
  • Purpose: AI gateway that routes requests to OpenAI GPT-4o mini and Google Gemini 2.5 Flash-Lite
  • Data received: Builder prompts and industry, form templates and compliance findings, audit ledger entries
  • Location: United States
  • Data processing agreement: https://openrouter.ai/data-processing-agreement

PostHog

  • Service: Analytics
  • Purpose: Anonymous page-view counts on public pages
  • Data received: Random session ID, page URL, 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 reports and traces: IP address, request URL and query string, request bodies, browser details
  • Location: United States
  • Data processing agreement: https://sentry.io/legal/dpa/

Vercel

  • Service: Hosting and infrastructure
  • Purpose: Hosting and serverless functions for the website and app
  • Data received: All data passing through the app; IP address, browser details and request logs
  • 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/

Services that act on their own

Our pages also load files from two outside services. They are not our sub-processors. Each one acts on its own, not on our behalf:

  • **Google Fonts.** Our pages load the Inter font from Google's servers (fonts.googleapis.com), so Google receives your IP address and browser details. Google handles them under its own privacy policy: https://policies.google.com/privacy
  • **Tailwind CSS CDN.** Our pages load their styling script from cdn.tailwindcss.com, run by Tailwind Labs, so Tailwind Labs receives your IP address and browser details. It handles them under its own terms.

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

SafeBuilds sets secure, HttpOnly cookies on its own domain to keep you signed in and protect your account: `sb_access`, `sb_refresh`, `sb_mfa_pending` (during a two-factor sign-in) and `sb_oauth_state` (during sign-in with Google). During checkout it keeps short flags in your browser's session storage (`sb_checkout_open`, `sb_checkout_needs_abandon`, `sb_checkout_activating`).

We do not set analytics or advertising cookies. PostHog counts page views on our public pages using a random ID kept in your browser's session storage (`ssl-marketing-distinct-id`), which is cleared when you close the tab. Sentry error reports use 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 and workspace data are kept while the account is active and for 90 days after it is closed. A customer can ask us to delete its form templates, form submissions and audit entries by writing to legal@swiftsoftlabs.com, and we delete them within 30 days. There is no self-service account deletion yet. 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. Our AI gateway function, which runs on InsForge, sends each request to OpenRouter, and OpenRouter passes it to the model that answers it:

  • OpenAI GPT-4o mini drafts a form from your prompt and the industry you chose.
  • Google Gemini 2.5 Flash-Lite explains the compliance findings on a form template, and summarises audit ledger entries, which include team members' email addresses and roles.

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, and never put protected health information into it.

AI output can be wrong, and it is not legal advice.

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:11:47 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 b32e1b478fcede2a3dfb8374af74f2c098bdefd6dcaa1ade8db54d30adfd1ad9 -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/safebuilds?version=1.0.0' | jq -j .signature.manifest > manifest.json
curl -s 'https://synlex.swiftsoftlabs.com/api/public/v1/swiftsoftlabs/safebuilds?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