title: Filter out an attribute on Ruby object created from a Gem in Rails project
body: <p>I created a gem that acts as a wrapper for a 3rd party API. I now reference that gem in my main rails project. I have a standard pattern of:</p>
  <p><code>TheGem::Client.new(api_key: current_user.account.token)</code></p>
  <p>I can use <code>encrypts :token</code> when handling the sensitive token attribute on the <code>Account</code> model.</p>
  <p>However, the gem creates a client and a custom class:</p>
  <p><code>#&lt;TheGem::Client:0x0000000112505628 @adapter=:net_http, @api_key=&quot;197a.....7uw&quot;&gt;</code></p>
  <p>The same api_key here is listed as an attribute of this custom object created by the gem but I can't make use of built in ActiveRecord encryption (as far as I know) when creating the object. Feels like I'm negating the security effort of <code>encrypts :token</code> but I see this as a pretty common strategy across gems I use. Maybe I'm missing something obvious here.</p>
  <p>What is the strategy for handling and filtering out a sensitive attribute on a custom object created from a gem in the same way as <code>encrypts :token</code>?</p>