Describes present public practices
Privacy and cookie notices must match implemented data flows and visitor controls.
Book a Demo Legal, privacy & trust center
Rules you can trace to the product and the contract.
Public notices, responsible-use rules, customer contracting frameworks, privacy controls, security boundaries, provider disclosures, and document history—kept separate so each one does the job it is meant to do.
Core documents
The four documents most visitors and customers need first.
These cover the public website, information handling, cookies, and the customer contracting framework. Supporting documents below add operational detail rather than overloading one policy.
PrivacyCurrent public notice
Privacy Policy
Controller and processor roles, collected information, sources, uses, disclosures, website tools, service data, communications, retention, security, transfers, and rights.
Read documentPrivacyCurrent public policy
Cookie Policy
A technology-level inventory covering consent storage, Google Analytics, Turnstile, session attribution, third-party features, duration, withdrawal, and Global Privacy Control.
Read documentWebsite usePublication draft
Website Terms of Use
Acceptance, eligibility, demos, accounts, permitted use, customer materials, AI limits, regulated uses, third parties, ownership, suspension, disclaimers, liability, and disputes.
Read documentCustomer termsExecution required
Service Agreement
Order Forms, implementation, customer duties, AI controls, communications consent, fees, data protection, security, confidentiality, ownership, warranties, indemnity, liability, and termination.
Read documentPrivacy
Notices and mechanisms for website visitors, prospects, end users, and individual rights.
PrivacyCurrent public process
Privacy Choices
How to change cookie preferences, opt out of optional analytics, request access or deletion, and raise a privacy concern.
Read documentPrivacyConditional supplement
Regional Notices
Supplemental disclosures for individuals whose local law grants additional privacy rights, without assuming a law applies solely because of residence.
Read documentWebsite use
Rules for public access, demonstrations, communications, AI features, and prohibited conduct.
Customer terms
Documents that allocate responsibilities for deployed services and require valid incorporation or execution.
Customer termsContracting framework
AI & Communications
Operational boundaries for AI-generated interactions, voice, SMS, email, recording, consent, human escalation, and customer-controlled communications.
Read documentCustomer termsExecution required
Data Processing Addendum
A controller–processor framework covering instructions, confidentiality, security, subprocessors, rights requests, incidents, transfers, deletion, and audit cooperation.
Read documentTrust
Fact-limited security, provider, and vulnerability disclosures without unsupported certification claims.
TrustPublic trust disclosure
Security Overview
A fact-limited explanation of LumiTalk’s security responsibilities, customer controls, incident cooperation, third-party dependencies, and assurance boundaries.
Read documentTrustDisclosure register
Subprocessors
A transparent distinction between verified website providers, customer-selected integrations, and production subprocessors that must be identified contractually.
Read documentTrustGood-faith research policy
Vulnerability Disclosure
Rules for good-faith security research, safe testing boundaries, responsible reporting, prohibited activity, and coordinated disclosure.
Read documentRecords
Version history and rules for determining which document applied at a particular time.
How to read the status labels
Not every legal page has the same legal effect.
Becomes binding through agreement
DPAs, service terms, liability allocation, SLAs, and regulated-use terms require the correct parties and valid acceptance.
Explains boundaries, not certification
Security and provider pages disclose responsibilities and known facts without claiming an audit or compliance status.
Requests and contracting
Need a signed document or customer-specific schedule?
Use the contact page to request the current execution set, identify the customer and use case, and confirm legal-entity, data, jurisdiction, security, and commercial details. Do not send credentials or private keys.
From the blogAll articles
AI ReceptionistWhat Is an AI Receptionist? A Plain-English Guide7 min read 
Real EstateSpeed to Lead: Why the First 5 Minutes Decide the Deal8 min read 
SubscriptionAI Customer Service for Subscription Ecommerce8 min read 
Property ManagementAI Assistant for Property Managers: A Buyer’s Guide8 min read 
Med SpaHow to Reduce Med Spa No-Shows Without Nagging Clients8 min read 
Estate PlanningAnswering Service for Estate Planning Attorneys8 min read