Is Terminal (Padre) Custodial? Private Keys, Export and Import (2026)

Three questions about Terminal wallets have been asked on Reddit at least six separate times since July 2025, across four different subreddits. Almost none of them got a real answer. Here they are in the users' own words.

"I tried clicking on import wallet and selected Phantom wallet then it wants me to enter my private key. Why does it need my private key for?" (r/solana, 29 April 2026)

"Does this mean Terminal has access to all my funds and can drain it?" (r/CryptoMarkets, 29 April 2026)

"Every time I set It up it just says 'unable to import private key'." (r/CryptoCurrency, 9 July 2026)

The last post got exactly one reply, from a scammer offering to help in DMs. That is the state of public support for this product, and it is why this page exists.

The short answer

Terminal is the Padre trading terminal, renamed after pump.fun acquired it in October 2025. If that sentence is news to you, start with our guide to what changed in the rebrand and come back.

Custody was inherited unchanged from Padre, and the model is this:

• Keys are managed through Turnkey, key infrastructure built by Coinbase's custody team, in an air-gapped design.
• Your private keys are encrypted with a password that Padre's documentation said the platform never stores.
• The documented claim was direct: "Padre never stores or has access to your password." The same page went on to say your assets stay safe even from Padre itself.

That is the company's own account, and companies say flattering things about themselves. So here is the corroboration that does not depend on trusting them: the site's content security policy whitelists export.turnkey.com and import.turnkey.com. A CSP is a browser-enforced allowlist of what the page is permitted to load. Terminal has no reason to allow Turnkey's export and import origins unless the key export and import flows actually run inside Turnkey rather than inside Terminal's own code. It is a small detail and it is the strongest independent signal available.

Generated wallets versus imported wallets

Almost every version of this question traces back to one design decision that Terminal never explains in the interface. There are two different ways to get a wallet into the app, and they ask for very different amounts of trust.

When you open the app and let it create a trading wallet, no private key prompt appears, ever. The key is generated inside Turnkey and encrypted with your password. That is the normal path and it is the one most people should use.

The private key prompt only appears when you deliberately choose to import a wallet you already own. At that point the app cannot magically obtain a key it does not have. It has to be given one. That is not a red flag by itself, and it is also not nothing.

Be honest about importing

Pasting your Phantom private key into any trading terminal is a real decision, and the correct instinct is to hesitate. The redditor who asked whether Terminal can drain their funds was not being paranoid. They were doing the right kind of thinking with no one available to answer.

What is actually true:

The key goes into Turnkey, so the design intent is that Terminal's servers never hold a readable copy. That is meaningfully better than the Telegram trading bots that store keys in an ordinary database. But you are still typing a secret into a web page you did not write, served from a domain you do not control, running 4.5 MB of JavaScript you have not read. Any browser extension with page access, any compromise of the front end, and any future change to how that page behaves sits inside your trust boundary the moment you paste.

Worth adding: importing does have legitimate uses. If you already have a position sitting in Phantom and want to manage it with real order types instead of a swap button, importing is the only way to do it. Just do it knowingly.

There is no seed phrase, and that is why your search failed

Terminal issues per-wallet private keys, not a mnemonic. There is no 12 word phrase, no 24 word phrase, no master recovery seed, and no wallet-level derivation path you can reconstruct.

People search for "Padre seed phrase" and "Terminal recovery phrase" constantly and find nothing, then assume the documentation is hiding it. It is not hiding. The thing does not exist.

Two consequences that actually matter:

Every wallet you create is a separate secret. If you run five wallets in a group, backing up your account means exporting five keys, not one phrase. There is no single string that recovers the set.

And your password is not a recovery mechanism. It is the encryption key over your stored private keys. Those are different jobs, and conflating them is how people end up with nothing.

Exporting your keys, and why you do it before you deposit

Padre's own documentation gave this advice in the context of forgotten passwords, and it is the single most useful operational instruction in the entire archive:

"I forgot my password, what now? Unfortunately, there is no way to recover a forgotten password. Since all private keys to your wallet are encrypted with this password, we strongly recommend exporting your private keys and securely storing them offline."

Read that ordering carefully. Exporting after you have a problem is not possible, because the problem is that you cannot get in. The export is only available to a session that already has your password. So the export has to happen while everything is fine, which in practice means before you fund the wallet with anything you care about.

There is precedent beyond the password case. In February 2025, a roughly 15 minute Turnkey outage blocked transaction signing across the app. Padre's advice at the time was, in their words, to always export your private keys. A key you hold offline is a key you can import into Phantom and use during an outage. A key that only exists inside a service that is currently down is not available to you at all.

The other reason to keep an exported key handy is mundane: stuck withdrawals. The canonical Reddit case is a user who deposited USDT instead of SOL, hit an "insufficient balance to cover total tx cost" error, and could not withdraw because the app requires SOL for the transaction. The app's own strings confirm the constraint (Min. 0.01 SOL required to withdraw and Low SOL balance. Swap USDC to SOL). The fix that worked came from another redditor, not from support: export the private key, import it into Phantom, and move the funds from there. If you already exported, that is a five minute annoyance. If you did not, it is a bad afternoon.

"Unable to import private key"

This error is not in Terminal's documented error catalog. We pulled every error string out of the live bundle for our Terminal error messages guide, and this one is not among them, which suggests it comes from the import component or from Turnkey rather than the trading engine. No official cause has ever been published.

Things worth checking before you conclude the app is broken:

• Key format matching the chain. A Solana key is base58 and an EVM key is hex, often with a 0x prefix. Selecting the wrong wallet type and pasting a perfectly valid key produces a failure that looks like corruption.
• Invisible characters. Copying from a screenshot OCR, a PDF, or a chat client frequently drags in whitespace or a line break. Paste into a plain text editor first and look at what you actually have.
• Pasting a phrase instead of a key. If you are copying out of a wallet that uses a mnemonic, the 12 words are not the private key. You need the wallet's exported private key specifically.
• Bulk import instead of single. The app supports CSV wallet import, which is a different path with different formatting rules.

About that "2FA"

Padre's marketing mentioned 2FA, and reviewers repeated it, so people go looking for an authenticator app setting and cannot find one. There is no authenticator app.

What "2FA" refers to here is the password encryption layer sitting over your Turnkey keys. Login itself is social, through Telegram, Google or X, handled by Firebase. So the two factors, loosely, are your social account and your encryption password.

The practical implication, and this is our reading rather than a documented guarantee: someone who compromises your Google or Telegram account gets into the interface but still cannot sign transactions, because signing needs the password that decrypts your keys and the platform does not hold that password. That is a genuinely decent property. It also means your social account is the front door, and pump.fun's own track record on social accounts is the weakest part of its security history. Its X account was compromised in February 2025 and its Instagram in April 2026. Neither touched user funds, but the pattern is clear enough: put a hardware key or an authenticator on whichever account you sign in with, because Terminal is not going to do it for you.

Padre did support passkeys once and then removed them, saying that while "passkeys provide a robust layer of protection, we found that they introduced too much friction." Reasonable people can disagree with that call. It is the reason there is no stronger login option today.

What custody protects you from, and what it does not

Custody is the question everyone asks, and it is not the question that costs people money on this platform.

The default slippage setting is 20%, and for small trades that is a direct, repeatable loss. One user watched $40 become $30 and posted that they had "bought $16 worth and sold it all for $2," then diagnosed it themselves a day later and told everyone to change the setting. Nobody from support ever appeared. We wrote that up in full at why small trades lose money on Terminal, and if you read one other page here, read that one.

Beyond that, the 1% trading fee interacts with pump.fun's separate 1.25% bonding curve fee in ways worth understanding before you size a position, which our fees guide breaks down with sources. And your cashback rate is fixed at signup by whether a referral code was stored, which is covered on our referral page.

If your worry is broader than custody, the domain-level question of which Terminal addresses are real and why security scanners disagree about them is handled separately in is padre.gg safe.

The bottom line

Terminal is non-custodial, the keys sit in Turnkey, and the app never asks for a private key unless you tell it to import one. The prompt that alarmed everyone on Reddit is an import screen with no explanation attached to it, which is a documentation failure rather than a custody failure.

If you want the short operating procedure: use a wallet Terminal generates rather than importing your main one, fund it with money you can afford to lose, export the key the day you create it, store it somewhere offline, and put real protection on the social account you log in with. Do those and the custody question is settled well enough to stop thinking about it.