Privacy controls and regulatory-support posture.

Website measurement is designed to start from denied consent for analytics and advertising storage. Visitors can accept, reject, or change choices through the cookie preferences control.

• Consent state is stored so the visitor can change choices later.
• Marketing events are blocked until analytics consent is granted.
• Customer deployments should still review their own notices, lawful basis, and regional consent requirements.

Public marketing analytics and form instrumentation are designed to avoid raw personal details. Operational product data should be limited to the agreed customer use case.

• No raw names, emails, phone numbers, company names, website URLs, or free-form messages in analytics payloads.
• Campaign attribution uses sanitized context rather than raw personal identifiers.
• Sensitive personal data should not be submitted through demo or contact forms.

LiveCart publishes contact paths for privacy requests and can support review of access, correction, deletion, portability, consent withdrawal, and objection requests where applicable.

• Applicability depends on the law, user location, customer contract, and LiveCart's role for the data.
• Identity verification may be required before a request is completed.
• Some data may need to be retained for security, fraud prevention, contractual, accounting, or legal reasons.

Service providers may be used for hosting, analytics, scheduling, communications, support, CRM, and infrastructure operations.

• Vendor review should consider the service role, data access, transfer path, and contractual protections.
• Customer-specific subprocessors and transfer terms should be confirmed during procurement or contracting.
• Public pages should not be read as a complete subprocessor list unless expressly labeled that way.

Procurement, security, and privacy review often requires documents that are more precise than public marketing copy.

• Signed agreements control service levels, data processing terms, confidentiality, retention, and liability.
• Public pages are informational and do not create a warranty or regulatory certification.
• Security questionnaires and legal review requests should go through the sales or support contact path.

The safer phrasing is that LiveCart provides GDPR, DPDP Act, and CCPA-aligned privacy controls where those laws apply, subject to customer configuration and legal review.

• Do not describe LiveCart as universally compliant with privacy laws on public pages.
• Do not imply legal advice, audit completion, certification, or regulator approval.
• Use customer-specific agreements and legal counsel for final compliance conclusions.