Yes, as stated [on the heartbleed website:][1]

> Furthermore you might have **client side software** on your computer that
> could **expose the data from your computer** if you connect to compromised
> services.

In your case however, where you have a direct control over the OpenSSL client code (and I suppose this is the case based on your post), you have to ensure that your version of OpenSSL doesn't come with the Heartbeat option. 

To see which options were used to compile your version of OpenSSL, use:

    openssl version -o

And to compile OpenSSL without Heartbeat support, simply use this option when compiling :

    -DOPENSSL_NO_HEARTBEATS

If this is done, or if your version of OpenSSL didn't include it initially, then you are not vulnerable. 


  [1]: http://heartbleed.com/