Data categories
Website inquiries, demo requests, account information, and product usage data should be named plainly.
§ Legal - Privacy
Privacy policy.
How CORE handles website, demo, and product-related information across a regulated-credit workflow.
Privacy belongs in the diligence packet.
Privacy requests, data handling questions, security review, and contract documentation should all resolve to a clear owner and a reviewable record.
Website + product data handling§ Policy Scope
What privacy review should clarify.
Use and disclosure
Processing purposes, service providers, subprocessors, retention, and rights requests should be easy to locate.
Request path
Privacy and security requests should route to a responsible contact, not a generic inbox with no owner.
§ Fit
Privacy topics buyers ask about
The page should support procurement review without turning into a marketing argument.
01
Information collected
02
Processing purposes
03
Service providers and subprocessors
04
Retention and deletion
05
Privacy request contact
§ Path
Privacy request flow
Receive request
Route privacy or data-handling questions from the website, sales process, or customer review.
Match the context
Identify whether the request concerns website data, demo data, product data, or contract documentation.
Respond with records
Provide the applicable policy, DPA, security materials, or contract path for review.
§ Next Step
Need privacy or security materials?
Route the request to CORE and include the review context so the right materials can be provided.