Alishka Counterpart Lab

Privacy Policy

Last updated 3 October 2026

What this lab is

Alishka Counterpart Lab is a negotiation training lab at counterpart.infinet.services. You learn moves, practice them, rehearse a conversation, prepare for a real one, and keep a journal of what happened. This policy explains what the lab stores when you do that work. The lab trains you. It does not negotiate for you. It is not a security product, and it is not legal advice.

Accounts

When you create an account we store your name, your email address, and a hash of your password. We do not store the password itself. The account is what ties your drills, simulations, preparation sheets, journal, and progress together.

Google sign-in

If you choose Google sign-in, we ask Google for your name and email address. We only finish sign-in when Google reports that the email is verified. We use those details to open an existing lab account or to create one. We do not keep Google's access token after sign-in completes.

Email verification codes

If you register with email and a password, we send a 6 digit code to that address before the account is created. The code only checks that you control the inbox. It is kept until you use it or it expires, and it is not used for marketing.

Journal and training data

The lab stores the practice you do while signed in, including:

  • drill responses, scores, and feedback
  • simulation sessions, turns, notes, outcomes, and reviews
  • preparation sheets you write for an upcoming conversation
  • journal entries and the analysis the lab shows back to you
  • skill history used on your progress view

That record stays on your account so you can continue training. Other learners do not see it. We do not sell it, and we do not publish your private sessions as examples.

Optional Codex, Cursor, and Perplexity connections

You may connect Codex, Cursor, or Perplexity. These connections are optional and stored per user. The built-in practice lab works without them.

A Codex or Cursor connection keeps that provider's login session in a private folder for your account. A Perplexity connection stores an API key for your account only. The lab uses a connection only for a task you start. Disconnecting removes it from your account. One person's connection is not shared with another account.

Cookies and email

A signed-in browser keeps an httpOnly session cookie. A separate cookie remembers light or dark mode. Google sign-in uses a short-lived cookie so the return from Google matches the request you started. Verification codes and other account messages are sent to the email on your account through the lab's mail service.

How long we keep it

We keep your account, training data, journal, and optional connections while the account exists. A verification code is kept only until it is used or it expires. To ask a privacy question, or to ask for your account and its training data to be deleted, write through https://www.infinet.services/.