Chamko Docs

How it works

Architecture

The whole platform in one picture, then what happens when you use it.

Chamko at a glance

You and your customers

Website

Guides and free tools

Dashboard

Runs in your browser

Phone app

Same account

Review QR

Customers scan it

Encrypted HTTPS only

Chamko, running on Cloudflare

Secure API

Checks who you are and what is yours

Scheduled jobs

Prepare posts, watch for reviews

AI

Writes posts and replies from your business details

Encrypted connections

Where your data lives

Database

MongoDB Atlas. Google keys stored scrambled

Images

Cloudinary

Services we connect to

Google

Sign-in and your Business Profile

Razorpay

Takes your payment; we never see card details

Gmail

Sends sign-in codes and account emails

Everything you touch talks to one protected service. Nothing on your phone or browser reaches the database directly.

The three parts

What you use

The website, dashboard and phone app are just screens. They hold no business data of their own and ask the secure service for everything.

The secure service

Chamko's core runs on Cloudflare's global network. It decides who you are and what you may see, runs scheduled work and calls AI.

Storage and partners

Your data sits in a managed database with images stored separately. Connections to Google, Razorpay and email happen from the service, never from your device with our keys.

What happens on a single request

You open your reviews

  1. 1Your device connects securely

    The request travels over HTTPS to Cloudflare.

  2. 2The service checks it

    Is it from a Chamko site, and within limits?

  3. 3It confirms it is you

    Your signed session is verified and matched to your account.

  4. 4It fetches only your data

    The lookup is limited to your business, and the result goes back to you.

How the layers fit together

Walls around your data

1

Encrypted connection. All traffic is HTTPS. Browsers are told never to use anything else.

2

Traffic limits. Only our own sites may call the API, with limits on rate and size.

3

Proven sign-in. Google or a one-time email code. There is no password to steal.

4

Your account only. Every lookup is tied to your signed-in account and your business.

Your Google keys

Locked with AES-256-GCM encryption before they are saved

A request has to pass each wall in turn. Failing any one of them stops it.

How a review gets answered

From new review to reply

  1. 1A customer leaves a review

    Google tells Chamko, and a regular check catches anything missed.

  2. 2AI drafts a reply

    It follows the review's language and length, and your recent replies.

  3. 3The reply goes to Google

    If it fails, Chamko tries again. You can always edit a reply from the dashboard.