Frequently asked.

iPhone 8 and iPhone X, on iOS 15 or later, arm64, with a rootful Palera1n jailbreak. That is the supported set — not a suggestion. Other models and other jailbreaks are not supported.

No. MultiPerson ships on a device we provision — jailbreak, tweak, daemon and app, set up and tested before it reaches you. There is no public repo to add and no package to sideload. Get in touch to arrange a device.

Yes. A switch performs a userspace reboot, which restarts system daemons. The kernel is not rebooted and the jailbreak stays active.

One per Person, and that Apple ID is never shared with another Person. Each Person swaps in its own account state, so it signs in to its own iCloud and App Store.

Primary is the original device state — every app visible, no isolation, no identity spoofing. It cannot be deleted, and it is where the device falls back to if a licence lapses.

No. Third-party home directories are redirected per Person, and keychain reads and writes are transparently namespaced, so each Person gets its own partition of the device keychain. Safari and App Store data are physically swapped on disk at switch time — separate history, cookies, tabs, logins and downloads.

Most Apple system apps, plus Palera1n, Sileo and the MultiPerson app itself. Extra bundle IDs can be marked shared through the API if you want a tool such as a file manager visible everywhere.

For App Store transactions, yes. Each non-Primary Person is given its own per-unit identifiers — serial, UDID, ECID, die id, MLB — served only inside the App Store transaction daemons. The real model, board and chip are kept, so a Person reads as another unit of the same model rather than as different hardware. Primary is never spoofed and always reports the real device.

Because it does a userspace reboot rather than a quick respring, and that is a deliberate correctness trade.

Switching swaps the account on disk, but akd, secd, itunesstored and accountsd cache the previous account in memory. A respring restarts only SpringBoard, so the store keeps authorising the stale account and downloads fail with a verification error. Restarting every daemon is what makes the swapped account authoritative. We chose the slower path because the fast one produces a device that looks fine and quietly cannot download.

Yes. The store data is swapped and the account daemons are restarted, so each Person's App Store login persists across switches.

No. A key binds to the first device it activates on, permanently. A second device is refused. This is the main thing to get right before activating — see how activation works.

Activation. A 6-month key activated three weeks after purchase still runs a full 180 days from the day it was activated.

No. The licence keeps working offline for up to 14 days and never less than 7, depending on when the lease was last refreshed. It cannot outlast your expiry date.

The device switches back to Primary and refuses to switch to any other Person until you renew. Nothing is deleted — every Person's data stays on disk and comes back when a new key is activated. The rest of the API keeps working throughout.

In your dashboard at account.tsgotouch.com, with the bound device and expiry for each one. Keys are not sent by email — we only email to tell you they are ready.

Licence keys are digital goods paid for in crypto, and are sold final. There is one narrow exception, for a key that fails to activate because of a fault on our side. The Refund Policy sets out both.

No. Person names, Apple IDs, keychain contents and app data stay on the device. What our licence server receives is the key, a device identifier, a signed counter and the IP address the request came from. The Privacy Policy lists all of it.

No. It is a random identifier generated on the device the first time it is needed. It is not your serial number, IMEI, UDID or Apple ID, and it tells us nothing about the hardware.