Here a couple of links to the manual:
www.limesurvey.org/manual/Survey_participants
And more specifically attributes:
www.limesurvey.org/manual/Survey_participants#Manage_attributes
www.limesurvey.org/manual/Expression_Manager
And more specifically
www.limesurvey.org/manual/Expression_Manager#Tailoring.2FPiping
So basically you run survey 1. Let's assume you ask for the gender of this person. For the next survey you don't want to ask that anymore, but rather just ask them to confirm if the data you have is correct.
So for survey 2 you create a token table with a custom attribute for the gender. let's assume this attribute is attribute_1.
Then you can access the data stored in this custom token attribute with something like {TOKEN:attribute_1}. (I haven't checked if this is the exact syntax, you will need to read about this in the manual and test it, it is just an example of how it works)
So you could for example as in a question:
"In our records with have the information that you are male. Is this correct? (yes/no).
But of course you could even just pass this information into a hidden question, etc. There are a lot of possibilities.
However, you will need to create the new token table for survey 2 with the information collected in survey 1 manually.
As Tpartner suggested, if you want to automate this, you could also make an Ajax call. You still will need to create a token table, but you don't need to create custom attributes and fill the these with the information collected from survey 1. But creating this token table from the data collected in survey 1 is not that much work either. If you run this only once, it is probably the same as creating the ajax script.