Choosing a campaign platform involves more than the visitor experience. Here is a starting point for understanding how LeadSpark handles information.
LeadSpark handles account information, campaign settings, uploaded campaign assets and the details people submit through campaign forms.
Campaign records can also include consent choices, timestamps and integration delivery status. The fields collected depend on the campaign configuration.
Public campaign pages are designed for visitors to respond. Private account dashboards and lead lists require account access.
For deployment planning, discuss who needs access and what permissions your organization requires.
Customers can export records and configure supported integrations. A connected CRM, spreadsheet or webhook destination becomes part of that campaign’s data flow.
Confirm the destination, purpose and access arrangements before connecting a system.
A request for information and permission for unrelated marketing are different choices. Campaign terms and consent language should reflect what the organizer actually intends to do.
Customers are responsible for configuring suitable campaign terms and data destinations.
LeadSpark is an early-stage product and is not currently SOC 2 audited. Security readiness materials are maintained to support prospective customer discussions.
A readiness programme is not a certification. Discuss any contractual, security or procurement requirements before deployment.
For healthcare, pharmaceutical, government or other sensitive settings, begin with your intended use, information types and internal requirements.
Public information or event engagement does not imply suitability for clinical records or other sensitive data.
Start a requirements conversationThis overview is a practical introduction, not a replacement for the applicable product policy or an agreement about your deployment.
Read the LeadSpark privacy policyTell us who you want to reach and what you want them to do. We’ll help shape the right experience.