Does Duplicity modify atime when backing up?

My data resides on a SSD and — thanks to re-writes and Write Amplification — any modification of an atime will result in not only the inode being modified, but the whole block that it resides on being erased and rewritten. That is, obviously, undesirable as it would cause a large amount of unnecessary wear on the drive. When Duplicity backs up files, does it modify the **atime** attribute of the **source files** in the process? If it *does* modify the atime, does it do so on the initial (full) backup, the incremental backups, or both?