How to Track Customer Consent or Legal Basis in Sparkforge
Display your privacy policy at the point of collection and capture consent on forms, surveys, web chat, calendars, and order forms. When consent isn't explicit, tag the contact with the legal basis you're relying on.
This article is informational, not legal advice. Talk to your own counsel about consent and lawful basis for your business.
What counts as personal data
Any information that relates to an identified or identifiable natural person — name, email, phone, IP, location, etc.
Where you collect personal data in Sparkforge
- Funnels and websites
- Forms (standalone or embedded)
- Surveys (standalone or embedded)
- Web chat
- Calendars (standalone or embedded)
- Order forms (standalone or embedded)
Pre-requisites at the point of collection
- Show the privacy policy. A link must be visible at every surface where you collect personal data.
- Capture consent or document a legal basis. Either get explicit consent or be ready to record what other lawful basis you're relying on.
How to capture consent
Use a Terms & Conditions element or a checkbox on each surface — forms, surveys, web chat, calendars, and order forms — linked to your privacy policy. The submission record then ties the contact to a clear opt-in event.
How to track legal basis when consent isn't explicit
Create a tag (for example, legal-basis:contract or legal-basis:legitimate-interest) and apply it to the contact — manually or through a workflow. The tag becomes your documented record of why you're processing that person's data.
Frequently Asked Questions
What's the difference between consent and legal basis?
Do I need a checkbox on every form?
How do I see which contacts have which legal basis?
Can I automate consent tagging?
Was this article helpful?
Thanks for the feedback.