Security & Data Protection

Security-First by Design

Tundar.AI connects customer conversations, scheduling, and follow-through into one operational system. Protecting the information that moves through those handoffs is part of delivering dependable service.

Purposeful Use
Deliberate Access
Clear Boundaries
Human Escalation
Information Stays Purposeful

Information is used to receive, respond to, schedule, follow up on, and improve the customer work your team has asked Tundar.AI to support.

Operational Access Is Deliberate

Access is limited according to the roles, accounts, and provider permissions used to operate and support the agreed workflow. Client administrators are responsible for maintaining appropriate user access on systems they control.

Automation Has Boundaries

AI and automations support defined tasks such as intake, routing, reminders, and follow-up. When a decision needs judgment, the workflow should route the next step to a person.

Our Current Operating Boundaries

This overview describes the security-minded practices Tundar.AI can truthfully state today. It is not a representation of certification or a promise that every client configuration uses identical providers or settings.

How responsibilities are handled

  • Access controls and permissions: access depends on the accounts, roles, and permissions configured for each workflow and provider.
  • Information handling: collect and use only the information needed to respond, route, book, update, support, and improve the agreed workflow.
  • Third-party providers: voice, messaging, scheduling, hosting, CRM, and other providers may process information when they are part of the approved implementation. Applicable providers are identified during setup.
  • Human escalation: workflows should route uncertainty, exceptions, sensitive judgment, and approved escalation events to a person.
  • Retention: retention depends on operational need, provider settings, client instructions, and applicable obligations; specific practices are documented for the implementation.
  • Incident reporting: suspected unauthorized access, disclosure, loss, or workflow misuse should be reported promptly through the Tundar.AI Contact page so it can be reviewed and escalated.
  • Client responsibilities: clients must maintain appropriate access, permissions, notices, consents, accurate instructions, and timely review of automated workflows.
How We Strengthen Responsible Operations

Improvement Is Part of the Operating Model.

01Map the Workflow

Understand where information moves and who needs it to deliver service.

02Set Boundaries

Define responsible access, automation roles, and escalation points.

03Document Decisions

Make the operating choices visible as systems evolve.

04Review and Improve

Strengthen practices as customer needs and operations mature.

See How Tundar Fits Your Workflow

See How Tundar Fits Your Workflow.

In a tailored demo, we’ll show how conversations, handoffs, and human oversight work together in the operational flow you want to improve.

Book a tailored demo →

This page is an operational trust statement, not a representation of certification or legal compliance. It will be updated as documented practices evolve.