pYro_65:
If you use AvrDude directly to upload (via ISP) it most likely will send the .eep file by default (never taken notice of EEPROM behavior via ISP) overwriting the EEPROM data. The IDE does not do this so the EEPROM data is persistent between uploads. You'd have to make sure you do not re-send the .eep file if you want to keep the data.Also there are commands in AvrDude to read the flash contents, I'd assume there is the same for the EEPROM.
AVRDude has a separate flag for writing the EEPROM file, it does not send it by default. When I was doing a project with ATtiny84s for school I had to modify the default Makefile that WinAVR gives you to have program-flash and program-eeprom targets using the following two flags:
AVRDUDE_WRITE_FLASH = -U flash:w:$(TARGET).hex
AVRDUDE_WRITE_EEPROM = -U eeprom:w:$(TARGET).eep
When I wanted to upload the firmware I did make program-flash command, and make program-eeprom uploaded the .eep file.