Peg-in and peg-out are the two steps that connect the normal Litecoin chain to the MWEB extension block. They are also where most of MWEB's privacy limits come from.
Litecoin MWEB guides: overview · how to use MWEB · MWEB wallets · MWEB exchanges · peg-in and peg-out · is MWEB private? · MWEB balance · MWEB vs Monero and Zcash
Peg-in: from regular LTC into MWEB
According to LIP-0002, a user sends coins to a new kind of output (a witness-version output). Miners collect these outputs and spend them in a special "integrating transaction" that is part of each block. That transaction commits to the extension block, and the coins now exist on the MWEB side. A peg-in is publicly visible on the main chain, including its amount.
Peg-out: from MWEB back to regular LTC
A user creates a peg-out transaction on the extension block that commits to a regular Litecoin address, which destroys the coins on the MWEB side. The integrating transaction then pays the same amount to that address on the main chain. LIP-0002 says peg-out outputs must be locked for a number of blocks (the exact count isn't specified) so nothing can be built on them before a possible chain reorganisation.
What a peg-out reveals
LIP-0003 says peg-out kernels expose the amount, the fee and the recipient Litecoin address in plaintext, and that MimbleWimble fees are visible in kernels "by design". So the private part is what happens between the peg-in and the peg-out, not the entry and exit themselves.
Why timing and amounts matter
Because the entry and exit are public, a pattern such as a peg-in of 12.5 LTC followed shortly by a peg-out of about 12.5 LTC is easy to link. Waiting, splitting or mixing with other activity changes that, but nothing here guarantees privacy. See is MWEB private?.
What wallets add
Wallets set their own confirmation waits on top of the protocol. Cake Wallet documents six confirmations for peg-ins and peg-outs and none for MWEB-to-MWEB transfers. See how to use MWEB.