Skip to main content
PRIVATE EARLY ACCESSBuilt for the tables that bring people together.Take the product tour
K Y A L O G E / TRUST & POLICIES

Data Processing & Security.

A transparent overview of how restaurant information is separated and handled.

Transparent by design Updated 13 Oct 2026
Clarity, at every step.How we think about trust
PurposeProtectionYour choicesServiceAccountability
THE BIG PICTURE

What's covered,
at a glance.

Follow the information map, then explore any section in detail. These notices explain how the service is designed and where final launch approvals still apply.

Data Processing & Security4 connected areas of responsibility

Explore a topic ↓ · Each item opens the detailed explanation below.

Pre-launch policy & review status

This policy describes KyaLoge's current design and intended operations. Verified legal entity and professional India-specific review must be completed before paid production launch. It is not an independent legal certification.

01 / 04

Roles and purpose

Each restaurant ordinarily decides its operational purposes for orders, final bills and permitted customer communication. KyaLoge provides technical processing tools under the corresponding business agreement.

Any formal data processing agreement, subprocessor list, international transfer assessment, lawful basis and retention schedule must be reviewed with the restaurant before live processing.

02 / 04

Security architecture

The platform uses restaurant-specific database tenancy controls, role-limited staff permissions, encryption for selected sensitive fields, protected provider settings, and operational audit logs. New owner access can require multi-factor authentication.

Technical safeguards reduce risk but do not remove it. Independent security assessment is part of the separate prelaunch approval process.

03 / 04

Processors and retention

Providers for infrastructure, transactional messages, optional AI suggestions and approved messaging are connected by the authorised operator. Credentials and recipient details are not intended for public exposure.

Data retention, deletion and breach-notification responsibilities should be finalised in signed agreements and published notices consistent with applicable law.

04 / 04

Requests and incidents

For security disclosures, privacy requests or suspected improper disclosure, contact the KyaLoge team through the contact page without sending private passwords or identity documents in the first message.

STILL HAVE QUESTIONS?

We're here to make it clearer.

Send a question about this policy, privacy, your restaurant account or how the product works.

Talk to KyaLoge