Not *exactly* what you asked for, but you could create a snapshot policy on the source side with a configuration that will retain a single copy of your daily snapshot, and then a vault policy and schedule on the destination side that has your desired retention.
That won't delete the local snapshot once the SnapVault relationship is updated though, it'll just ensure that only the most recent daily snapshot exists on the source volume while retaining x copies on the destination volume according to the policy. If you wanted to specifically delete the source snapshot as soon as the replication completes, a script/workflow of some sort would likely be required.