Security Program
Kyntlo maintains a documented security posture covering account access, customer responsibilities, incident reporting, vendor usage, and data protection expectations.
Privacy, Security and Compliance
Kyntlo protects business workflows with a practical security program, privacy-first policies, customer controls, and transparent compliance status for subscribers and partners.
Current trust posture
This page summarizes the controls, policies, and operational practices that support Kyntlo. It is written for customers who need to understand how account access, privacy requests, data handling, and security responsibilities are managed.
Kyntlo maintains a documented security posture covering account access, customer responsibilities, incident reporting, vendor usage, and data protection expectations.
Privacy Policy, Terms of Use, Refund Policy, Cookie Policy, Accessibility, and Contact pages are available publicly from the website footer.
Website login actions point to the Kyntlo Hub, while demo requests are routed through the public demo form and sales email workflow.
Data handling
Kyntlo customers may need to understand where business and contact data is stored, processed, and transferred. Data location can depend on the connected platform, infrastructure providers, communications providers, payment providers, enabled integrations, and account configuration.
Customer data is stored and processed inside the platform and infrastructure provider environments used to operate each Kyntlo account. Hosting region and residency requirements should be confirmed before launch.
European customers can request available hosting-region details, subprocessors, data transfer safeguards, and contract terms before onboarding or during due diligence.
Kyntlo publishes privacy notices and provides request channels for access, correction, deletion, restriction, objection, portability, and consent withdrawal where applicable.
Kyntlo customers remain responsible for lawful lists, consent, messaging practices, opt-outs, and honoring applicable consumer privacy requests.
Messaging, calendar, payment, analytics, AI, and integration services may process limited data needed to deliver the selected feature or workflow.
Kyntlo should not be used for Protected Health Information unless a written agreement, provider support, and appropriate account configuration are in place.
Security pillars
The controls below define the standard Kyntlo security model. Final technical behavior may depend on the connected platform, hosting environment, payment provider, communications providers, and customer configuration.
Secure hosting, HTTPS transport, provider access controls, firewall protections, and vendor safeguards are expected for production services.
Customer accounts should use role-based permissions, strong authentication, limited user access, and careful workspace administration.
Support access, account changes, billing requests, and security issues should be handled through controlled support channels.
Customer-facing forms, automations, AI workflows, and integrations should be reviewed before launch to reduce abuse and data exposure.
Shared responsibility
Kyntlo can provide the workspace, controls, and support path, but each customer controls their users, contact lists, consent records, campaign content, workflow logic, and data handling practices.
For security questions, privacy concerns, customer due diligence, or account-risk reviews, contact Kyntlo with your company name, account email, request type, and any required deadline.
Contact contact@kyntlo.ai