Skip to content

Security and responsible use

How Joinpane keeps a shared sign-in, who can see what inside it, and what we ask of every team that uses it.

Updated

  • Passwords are never storedTyped once into the website. Nobody can read one back, including us.
  • Sessions stay encryptedEncrypted at rest, decrypted only on the machine running the identity.
  • People handle the checksA person solves every human check. Codes come from your own phones.

How a shared sign-in is kept

An identity is one website login your team shares. It runs in one long-lived browser, in Joinpane's cloud or on a node of yours, with one IP address and one browser fingerprint for its whole life.

The owner signs in onceMei types the password into studio.example's own page, in the identity's browser.
Studio uploadsBrowser in Joinpane cloud, TokyoSession stored encrypted in TokyoDecrypted only on this machine
Everyone gets a windowThey see the page and send clicks and keys back. Cookies never leave the browser.
Control planeChecks who may open which identity and connects their window. It routes people, never page content.
  • We store the signed-in session, encrypted, in your workspace's home region. Northlight's, for example, is Asia Pacific, Tokyo.
  • It is only decrypted on the machine running that identity, when the identity wakes. It sleeps after 15 minutes with nobody inside.
  • Windows stream from that browser to each person. On strict office or hotel networks the stream goes through a relay, still encrypted.

Passwords

A password is typed once, by the person signing in, into the website's own page. It goes from their keyboard to the website.

  • Joinpane never stores it. The identity's browser doesn't save passwords, and we keep only the signed-in session.
  • Nobody can read one back, including your admins and Joinpane staff. There is nothing to reveal.
  • Teammates watching see dots. On phones, password fields are never echoed to anyone else.

Who sees what

Everyone inside an identity, person or agent, has their own window. Each window is private until its owner shares it.

  • Watchers are read-only. To click or type in a shared window they ask to take over, and the driver can say no.
  • Viewers can't copy out. They watch, and can't click, type, download or copy text to their own computer.
  • Admins can mark pages as admins only, like /settings/password or /billing. Members are stopped before those pages and told why.

Sign-in codes and phone owners

When a website wants to check it's really you, it texts or emails a code to the phone or inbox on the account. That phone belongs to someone on your team, never to Joinpane.

An admin names the phone owners for each identity: the people who hold that phone. When the website asks, we reach them in this order.

  1. A notification in the Joinpane app. They can type the code right into it.
  2. An email after 2 minutes without an answer. It links back to the same request.
  3. Telegram or a webhook, if you set one up. Each person chooses their own.

Anyone inside the identity can also type the code straight into the website's page. Codes usually last 10 minutes; if one runs out, ask the website for a new one. Joinpane never reads your texts. A code reaches the website only when a person types it.

Agents

Agents connect through MCP or the API with a key. Each gets its own window with a dashed frame and is always labelled as an agent, so everyone can tell who is acting.

  • They never get cookies or passwords. They see pages and press buttons; the session stays in the browser.
  • They ask a person before publishing, paying, changing settings or deleting, and wait for the answer.
  • They can't type into password fields unless an admin allows it. When a website signs one out, it waits for a person.
  • They pause when a person takes over and pick up again after the person hands back.

The record

The audit log records who opened, drove, downloaded and changed what, in which identity and from where. Agents appear under their own name and key. Nobody can edit an entry, admins included.

  • Ana Torres signed in with a code entered by Rin KatoAd account
  • Rin Kato took over from Mei Lin after she said yesStudio uploads
  • Uploader sent ep12_final_cut.mp4 from Drive to the websiteStudio uploads
  • Mei Lin downloaded uploads-report-oct.csv to DriveStudio uploads

Every paid plan keeps an audit log. Pro keeps it for a year and exports it as CSV.

Your own hardware

A node is a machine you run that hosts identities instead of Joinpane cloud. Use one when a website should see your office line, or when sessions must stay on your hardware. It starts with one Docker command.

  • Outbound HTTPS only. The node calls Joinpane and nothing calls in, so there is no port to open on your network.
  • The browser and its session live on your machine, and websites see your node's own address.
  • If a node goes offline, its identities wait for it. They never move to the cloud by themselves.

Data and deletion

Data lives in the home region you pick when you create a workspace. Here is what we keep, and for how long.

Passwords
Never stored.
Signed-in sessions
Until you remove the identity. We delete its session right away; the account at the website stays yours.
Drive files
Removed after 30 days by default. Admins can choose 90 days, or keep files until someone deletes them.
Audit log
1 year on Pro.
A deleted workspace
Can be restored for 14 days. Then it is gone, with its sessions, Drive and audit log.

Admins can export everything at any time: a zip of the audit log, the Drive file list and settings. Sessions and passwords are never exported.

Reporting a vulnerability

If you find a security problem in Joinpane, email us what you found and how to reproduce it. We confirm within 2 working days and keep you posted until it's fixed.

  • Test against a workspace of your own. The Free plan is enough.
  • Don't open other customers' data, slow the service down or publish details before we've fixed it.