You should not attempt to cache responses locally for two reasons:
It violates the terms of service of SecData
The SecData database changes quickly and your cache will not be up to date
We should also point out that SecData includes anti-scraping technology. If our servers detect that a user is extracting large amounts of data (randomly/in sequence) then SecData will simply return negative responses (not a hacker IP / fraud phone number) for all queries not already answered at least once.