Consent data security for the evidence your team keeps
Consent records connect a person's contact details to a disclosure and captured action. ConsentVerified protects that evidence with encryption in transit and at rest, SHA-256 hashing, and access controls according to your plan. Your lead data stays yours. Review retention, team permissions, exports, and deletion as part of choosing how your organization handles consent evidence.
Protect records in transit and at rest
ConsentVerified encrypts consent data in transit and at rest. Encryption in transit protects information as it moves between your team, connected workflows, and the service. Encryption at rest protects stored records. These protections support the daily work of collecting evidence and retrieving it later, when the record may include disclosure text, phone details, timestamps, IP addresses, and user agent information.
Keep your own handling process aligned with the sensitivity of those records. Limit who can retrieve evidence and where exported files are stored. Encryption does not replace access review or protect a document after it is shared outside its intended audience. Include the systems that receive exports and API results in your internal data handling procedures.
- Consent data is encrypted during transfer and while stored.
- Access decisions remain part of your organization's evidence handling process.
- Exported files need appropriate protection in the destination where your team keeps them.
Use SHA-256 hashes to review record integrity
ConsentVerified hashes captured evidence with SHA-256 and connects it to a certificate ID and event timestamps. A hash acts as a fingerprint of the content used to produce it. Comparing the relevant content with its recorded hash helps check whether that content remains unchanged. The certificate reference connects that integrity information with the disclosure and interaction the system captures.
Hashing and encryption perform different jobs. A hash does not hide the underlying evidence and does not independently establish that a consumer owns a phone number or that an agreement satisfies the law. Timestamps record the system's capture timing rather than a legal conclusion. Follow the proof of consent workflow to see how these details support capture, verification, and evidence review.
- SHA-256 hashing supports integrity checks of captured content.
- Certificate IDs connect the evidence to the relevant submission record.
- Disclosure and session context remain necessary when reviewing what the record proves.
Match retention to your recordkeeping needs
The Evidence Vault retains evidence according to your subscription. Starter includes one year of retention, Growth includes three years, and Scale includes five years. Enterprise retains evidence for 7 years with legal hold. The right period depends on your obligations, contracts, dispute risks, and internal policies. A plan's retention period is a product allowance rather than a recommendation that the period satisfies every legal requirement.
Review your needs before selecting a plan and before allowing evidence to leave your retained records. Keep the certificate connected to the lead so authorized reviewers can retrieve the relevant evidence by phone number. Where your organization needs records in its own systems, export them within the applicable retention period and apply your own access and retention policy to those copies.
-
Starter includes one year of evidence retention.
-
Growth includes three years of evidence retention.
-
Scale includes five years of evidence retention.
-
Enterprise includes 7 years of retention and legal hold.
Preserve relevant evidence when a dispute requires it
Enterprise legal hold supports preservation of relevant records beyond routine retention while a hold applies. Use it when counsel or your compliance process identifies evidence that needs to remain available for a dispute or investigation. Keep the scope of the preservation request clear so the records involved can be identified and reviewed by the responsible people.
A hold affects preservation, not the legal strength of the underlying agreement. Your organization still needs to identify relevant records, coordinate with counsel, and preserve related information in other systems. When a hold ends, review how the applicable retention and deletion requirements apply before changing the record's status. Contact [email protected] when your team needs help with an account-specific preservation request.
- Legal hold is an Enterprise capability.
- Identify the relevant records and preservation scope with the responsible reviewers.
- Coordinate held evidence with contact histories and other records your organization maintains.
Assign access according to team responsibilities
Starter includes two team seats. Growth includes ten seats and roles. Scale includes twenty-five seats, roles, SAML SSO, and an audit log. Enterprise includes unlimited seats, SAML SSO, SCIM, custom roles, and an audit log. These controls let teams choose the access model appropriate for their work without implying that every plan includes the same identity and oversight capabilities.
Use roles to give staff access appropriate to their responsibilities. SAML SSO connects supported plans to your organization's identity process. The audit log provides a record of activity for review on Scale and Enterprise. Include API keys and connected workflows in access reviews, especially when an employee or vendor stops working with your organization. Keep account administration with the people responsible for evidence handling.
- Roles are included on Growth, Scale, and Enterprise.
- SAML SSO and audit logging are included on Scale and Enterprise.
- SCIM and custom roles are Enterprise features.
- Review human access and integration credentials as part of the same process.
Keep control of your records and their lifecycle
Your lead data stays yours. ConsentVerified provides evidence exports so your team can retrieve the records it needs for internal review, counsel, or an authorized campaign review. The evidence package includes a PDF for human review and JSON for structured handling. Exporting a record preserves access to the evidence in your own process without transferring the responsibility to protect the resulting files.
You can request deletion of your stored consent data through the account support process. Applicable preservation duties, an active legal hold, or other retention obligations can affect what is deleted and when. Review those conditions before requesting deletion, and keep any records your organization needs before ending access. Contact [email protected] for account-specific export or deletion assistance and share only the information needed to identify the request.
-
Export the relevant evidence package in PDF and JSON formats.
-
Limit access to files shared with internal or external reviewers.
-
Request deletion with applicable preservation and retention obligations in view.
-
Review retained copies in your own systems as part of the same lifecycle.
Choose security controls with capacity and retention
Plans start from $149 a month with Starter. Growth, Scale, and Enterprise provide different team controls and retention options alongside higher usage limits. Compare TCPA compliance software pricing before deciding which combination meets your organization's requirements. Enterprise also includes a security review and invoicing for organizations with formal procurement.
Review the consent verification features and SMS consent records to understand the information your workflows collect. Share these details with the people responsible for access, privacy, and records management in your organization. ConsentVerified is a compliance tool, not a law firm. Product controls support your process, and this information is not legal advice or a certification of your compliance.
Give consent evidence a clear handling process
Create your workspace and choose the capacity, retention, and access controls your team needs. Connect capture and verification to a recordkeeping process that covers retrieval, authorized sharing, preservation, and deletion. Your team keeps a usable evidence record with defined responsibilities throughout its lifecycle.