Privacy Policy

1. This policy is about the Nusa website, Nusa Node (the program a host runs on their machine) and the emails Nusa sends. They are run by Nusa (the operator). The Terms say what the service is.

1. Your account: the email address it goes by (one proved by a sign-in provider, or confirmed from a message we sent) and the ways of signing in attached to it. There is no password. Linking a second way to sign in doesn’t record that way’s email address.
2. Signing in: when you continue with a provider such as Google or GitHub, the provider gives Nusa an identifier for you and, for the way that created your account, a verified email address. When you sign in by email, Nusa sends a message with a link and a code to the address you enter.
3. Renting: the machine and model you rented, how long for, what it cost, how it ended, the quotes and payments behind it, and the Connect key issued for the rental. When you top up, your card details go to the payment provider (Stripe); Nusa keeps the outcome in your transaction history, not the card.
4. What you send to a model: during a rental, your prompts go to the host’s machine, which runs the model through Nusa’s engine, and the answers come back the same way. Nusa relays them without keeping them. Your Playground conversation is kept in your own browser only. In the trial on Overview, Nusa doesn’t keep what you type or the answers either; it records how much of your allowance a message used.
5. Hosting: Nusa Node sends what Nusa needs to list and run the machine: its hardware (GPU, memory, disk), its benchmark results, whether it is online, which models are installed and how their downloads go, and each rental’s activity. Its location is detected from where it connects, and renters see only the country. It also sends hashes of its hardware identifiers, never the identifiers themselves (see below).
6. Support: the topic, the email address and the message you send; we reply by email. The Windows waitlist: the email address you leave.
7. Invitations: the code you arrived with, and which account’s link you joined through. The account that invited you sees only how many joined through its link and how many of those rented, never who.
8. Emails: Nusa emails you about your account and your rentals: as a rental nears its end or ends early, when one of your machines goes offline, the result of a review, and before the rules for hosts change.

1. To run the service: your account, rentals, payments, listings, earnings and refunds.
2. To settle what happens when a rental is interrupted, and to review it when a host asks or Nusa decides to.
3. To keep Nusa safe for everyone: recognising the same physical machine, ending a rental that breaks the terms, putting an account under review.
4. To reach you about your account and, with your permission, to see how the site is used (Analytics, below).

1. With your permission, Nusa uses PostHog (hosted in the United States) to see how the site is used and where it can be better: the pages you open and what you click. Once you sign in, that activity is linked to your account, including its email address. Nothing is sent until you accept, we never send what you type to a model, sign-in links or payment details, and declining clears what was stored.
2. Nothing is loaded or stored for analytics until you accept, in the bar at the bottom of the page or here. Declining stops it at once and removes what PostHog kept in this browser. Your choice is kept in this browser, and you can change it here at any time.
3. Parts of an address that could identify you or what you typed are masked before an event leaves your browser: a sign-in token, the code a sign-in provider returns, the text you searched for, a payment attempt and an invitation code.

1. Nusa sets no cookies of its own. What it needs between pages is kept in this browser’s own storage, under the names below, and leaves it only as part of what you do on Nusa. Clearing the site’s data removes all of it.
2. Signing in: compute-poc-jwt (your sign-in token), nusa.lastSignIn (which way you last signed in), nusa.emailSignIn.browserSecret and nusa.emailSignIn.returnTo (an email sign-in started in this browser), nusa.tokenRotating.… (a token being renewed) and, for as long as a sign-in or a link is in progress, nusa.socialSignInInProgress, nusa.oauthState, nusa.linkInProgress, nusa.linkOutcome, nusa.signInOutcome, nusa.authCallbackNext, nusa.authCallbackOutcome, nusa.pendingIntent and nusa.reauthReturn.
3. Your choices: nusa-theme (light or dark), nusa.analyticsConsent (your analytics choice; once allowed, PostHog keeps its own entries, whose names start with ph_), nusa.modelsFilters (the Models page’s filters) and nusa.marquee.reviewClosed (a notice you closed).
4. Where you were: nusa-workspace-memory and nusa-workspace-memory-owner (the last page on each side), nusa.providerSetup.… and nusa.providerActivated.… (where your hosting setup got to).
5. Renting: nusa-transcript-… (a rental’s Playground conversation, one per job), nusa-lease-flow-… (where a job’s setup got to), nusa.pendingTopup, nusa.rentResume and nusa.rentToppedUp (a top-up started from checkout), nusa.trial.draft (a trial message typed but not sent) and nusa.trial.usedUp (that the trial is used up).
6. Invitations: nusa.invite, the code you arrived with, kept for 30 days or until your account claims it.
7. The demo version of the site keeps its sample data under names starting with nusa-mock- and compute-poc-mock-, and in nusa.mockStubs; none of it is sent anywhere.

To stop a machine’s reliability score being laundered by pairing it again on the same account, we keep hashes of the hardware identifiers of every machine paired to Nusa, never the identifiers themselves. We keep them permanently, including after a machine is removed and after an account is deleted, and use them only to recognise the same physical machine for its reliability record.

1. Your account, its rentals, earnings and transaction history are kept while your account exists, so that each balance and its history stay complete.
2. What you send to a model and its answers are not kept by Nusa at all, in a rental or in the trial. A rental’s conversation lives in your browser only, and goes when you clear the site’s data.
3. Hashes of a machine’s hardware identifiers are kept permanently, including after the machine is removed and after the account is deleted, for the one purpose below.
4. An invitation code waits in your browser for 30 days. A waitlist entry is kept so that Nusa can tell you when support expands.
5. Analytics data is kept by PostHog under Nusa’s project; declining removes what was kept in your browser.

1. Hosts and renters see little of each other. A host sees that their machine is rented, which model is in use, how long it has run and what it earned, but not who the renter is, where they are, or what they send. A renter sees the machine: its hardware, its country, its reliability and its price, not who hosts it.
2. Nusa shares data with the services it runs on, for what they do: Stripe for payments, PostHog for analytics once you allow it, the provider you sign in with for the sign-in itself, and the service that delivers Nusa’s emails.

1. You can change your analytics choice at any time, above. Everything the site keeps in your browser is yours to clear.
2. To ask what Nusa holds about you, to have it corrected, or to have your account deleted, contact support. We reply by email.
3. This draft is written from the product spec. When the official text is ready, it replaces this page.