CASL consent timestamp not stored in Klaviyo per subscriber
CASL requires that a business be able to demonstrate, for any given subscriber, when consent was obtained, how it was obtained, and what the subscriber was told at the time of collection. This means a consent timestamp, consent source (signup form, checkout opt-in, loyalty enrolment), and consent method (express or implied) must be stored at the profile level in Klaviyo, not just in a separate CRM or as a platform-level default. Most Klaviyo integrations store a boolean opt-in field but do not capture the timestamp or source. If a CASL complaint is filed, the business must produce this data. An inability to produce it is treated as an inability to demonstrate consent, which shifts the burden of proof against the sender.