SwiftSoft Labs

Nullify Privacy Policy

Version 2.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

  • Individuals named in customers' agent payloads (processed for the customer)
  • Website visitors
  • Workspace users (account holders)

When a workspace sends us the inputs and outputs of its own AI agents, the people named in that content are covered by that customer's own privacy notice. We process that content for the customer, on its instructions, only to run the service. If your data is in such content, contact the customer that uses Nullify, and we will help it answer you.

3. The personal data we collect

We collect the following categories of personal data:

  • AI agent records (name, provider, model, endpoint URL, quota)
  • Account credentials (password, 2FA, passkeys)
  • Agent input and output payloads supplied by the customer
  • Billing customer and subscription IDs
  • Email address
  • Google account ID (sign in with Google)
  • Name (optional)
  • Policies, decisions, alerts and notifications
  • Sign-in sessions and auth audit records
  • Usage analytics (marketing page views)
  • Workspace role
  • 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.

This includes the agent inputs and outputs a workspace sends for evaluation. They reach our AI providers without redaction, so do not include health information, payment card data or other regulated data in them.

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. Page-view counts on public marketing pages, error tracking and account security 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, sign-in emails (verification and reset codes) and the edge functions that run the AI gateway
  • Data received: Email address, name, password hash, 2FA and passkey data, sessions, workspace content (agents, policies, decisions, input and output payloads, alerts), billing references
  • Location: United States
  • Data processing agreement: https://insforge.dev/dpa

OpenRouter

  • Service: Artificial intelligence
  • Purpose: AI gateway that sends evaluation and policy-simulation requests to the selected model (default Google Gemini 2.5 Flash-Lite)
  • Data received: Agent name, decision type, agent input and output payloads, policy text, simulation prompts
  • Location: United States
  • Data processing agreement: https://openrouter.ai/data-processing-agreement

PostHog

  • Service: Analytics
  • Purpose: Counts page views on public marketing pages
  • Data received: Random session ID, page URL and host, IP address as received with the request
  • Location: United States
  • Data processing agreement: https://posthog.com/dpa

Sentry

  • Service: Monitoring and error reporting
  • Purpose: Error and performance monitoring for the website and app
  • Data received: IP address, browser and device details, page URL, error details and stack traces, request data attached to error reports
  • Location: United States
  • Data processing agreement: https://sentry.io/legal/dpa/

Vercel

  • Service: Hosting and infrastructure
  • Purpose: Hosts the website and app and runs its server code
  • Data received: IP address, browser user agent, request logs, 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/

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

Nullify sets four first-party, HttpOnly cookies that keep you signed in and protect your account: `ny_access`, `ny_refresh`, `ny_mfa_pending` and `ny_oauth_state`. During checkout, your browser's session storage keeps three short flags (`nullify_checkout_open`, `nullify_checkout_needs_abandon` and `nullify_checkout_activating`), which are cleared when you close the tab.

We do not set analytics or advertising cookies. PostHog counts page views on our public marketing pages using a random ID kept in your browser's session storage (`ssl-marketing-distinct-id`), and sets no cookies. 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 data and workspace content (agents, policies, decisions and their payloads) are kept while the account is active and for 90 days after it closes. There is no self-service deletion yet: email legal@swiftsoftlabs.com and we delete your data within 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, which routes each request to the model selected for it. The default model is Google Gemini 2.5 Flash-Lite.

When your workspace evaluates an agent decision or simulates a policy, we send the agent name, the decision type, the agent's input and output payloads and your policies through the InsForge AI gateway and OpenRouter to that model, so that it can return a risk score and an allow or block recommendation. We do not redact this content before we send it. Do not put personal data into it unless you need to, and never health information or payment card data.

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 13:00:40 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-v2.0.0.tsr -digest 488464e1e00edd6a5408fdec94795da1ac4745753f67f1cc89ae8639ab19e1f8 -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/nullify?version=2.0.0' | jq -j .signature.manifest > manifest.json
curl -s 'https://synlex.swiftsoftlabs.com/api/public/v1/swiftsoftlabs/nullify?version=2.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