Frequently asked questions

Ordinary profiles separate cookies but share the same underlying device characteristics, so sites can tell they are the same machine. SessionPilot gives each profile its own consistent identity — user agent, platform, screen, hardware hints, fonts, canvas and WebGL behaviour — generated deterministically from a seed, so the profile looks the same every time you open it and different from your other profiles.

Two: a Chromium-based engine and a Firefox-based engine. Some sites behave differently across engines, and having both means you are not forced to present as Chrome when Firefox is a better fit.

Yes. A local automation API is exposed with an AdsPower-compatible surface, so Puppeteer, Playwright and Selenium attach without custom glue. A version-matched chromedriver is bundled.

Mobile device emulation is available on Pro and Team. Starter is desktop only. We are also explicit about the limit: emulated Android cannot pass hardware attestation, and we do not claim otherwise.

No. They are encrypted on your device before upload with a key derived from your passphrase, which we never receive. We hold ciphertext. See Security.

Your synced data cannot be recovered — by you, by us, or by anyone. There is no reset. This is a direct consequence of us not holding a key, and we would rather say it clearly now than at the moment you need it.

The workspace key is rotated and re-sealed to the remaining members. The removed person cannot decrypt anything published after their removal, even if they kept a copy of the data.

Yes. Membership and access changes are recorded in a hash-chained log, signed by the acting user, and exportable for offline verification against a server-signed anchor.

You can bring your own — HTTP or SOCKS5, with or without authentication — and bind one per profile. Timezone, locale and geolocation can follow the proxy’s exit IP automatically, so those signals agree with the network path instead of contradicting it.

Managed proxy service is in progress. Until it ships, bring your own; nothing about the product depends on buying them from us.

WebRTC is hardened on both engines so local and public addresses are not leaked around the proxy. You should still verify your setup — we publish how, rather than asking you to take it on faith.

Yes. Entitlements update on your next sync. Upgrades take effect immediately; downgrades apply from the next period.

Plan entitlements are withdrawn and the app stops granting the plan’s features. Data stored locally on your machine stays on your machine.

Yes — 14 days on a first purchase, and pro-rata where a failure on our side prevented you from using the service. Full detail in the Refund Policy.

Managing separate, isolated browser identities is ordinary business practice and lawful in itself. What matters is what you do with it. Fraud, unauthorised access and the other conduct listed in our Acceptable Use Policy are prohibited, and individual websites may set their own rules about multiple accounts that you are responsible for following. We are not able to give you legal advice about your specific situation.

We publish a Data Processing Addendum, keep a sub-processor list, and support data-subject requests. The architecture helps here: most of what you process never reaches us in a readable form.

We comply with valid legal process, and where we are permitted to tell you about a request, we will. What we can hand over is limited to what we actually hold — account records and ciphertext we cannot decrypt.