Security at GreenKhata

GreenKhata is a cloud billing and business-operations platform operated by GreenKhata Technologies Pvt. Ltd.. We design security into our product architecture, operations, and vendor relationships so merchants can run invoicing, GST workflows, payments, and staff operations with appropriate technical and organisational safeguards.

This page describes our current security posture and control objectives. It is intended for customers, auditors, and procurement teams evaluating GreenKhata. Unless explicitly stated, references to alignment with international frameworks describe control objectives — not a claim of formal third-party certification for every workload.

Production workloads run on managed cloud infrastructure with environment isolation between development, staging, and production. Network boundaries, containerised services, and least-privilege service accounts reduce lateral movement risk.

Core application services are deployed with health checks, automated rollout pipelines, and monitored dependencies (databases, cache, message brokers). We use reputable infrastructure and platform providers; residual shared-responsibility risk remains inherent to any hosted SaaS model.

In transit: Customer-facing applications and APIs are served over HTTPS with modern TLS. Internal service communication is restricted to private networks within our deployment architecture.

At rest: Primary databases and object storage use provider-managed encryption appropriate to the storage tier. Application-layer secrets (tokens, passwords, API keys) are never stored in plaintext where hashing or encryption is required.

Cryptographic keys and secrets are managed through environment isolation and access controls; production secrets are not committed to source control.

GreenKhata supports multiple sign-in methods designed for both usability and security maturity:

• Email and password with strong password policies and secure hashing (bcrypt / Argon2id migration path).
• Phone OTP for passwordless and recovery flows, with rate limiting and abuse controls.
• Google sign-in (OAuth 2.0) for supported accounts.
• Passkeys (WebAuthn / FIDO2) for phishing-resistant authentication on supported devices and browsers.
• TOTP two-factor authentication (2FA) with one-time backup codes.

Passwords are checked against known breach corpora using the Have I Been Pwned k-anonymity range API at signup and password set/change — only a partial hash prefix is transmitted; the full password never leaves our systems.

Sessions use short-lived access tokens and revocable refresh tokens. Users can review active sessions and sign out of other devices. Staff access can be invited and removed by account owners; removing staff revokes associated sessions.

Enterprise SSO (SAML / OIDC with customer identity providers such as Okta or Azure AD) is on our enterprise roadmap and available on request for qualified deployments — contact security@greenkhata.ai.

Application access follows least-privilege and role-based patterns. Merchant staff roles (e.g. owner, manager, waiter) constrain billing, catalog, and operational actions within a tenant boundary.

Internal administrative access to production systems is restricted, logged, and granted on a need-to-know basis. Customer data is partitioned by tenant identifier in application logic and data-access middleware.

Service-to-service calls use internal authentication secrets; public APIs require valid user or scoped API credentials.

Sensitive actions — including invoice creation and updates, payments, customer changes, authentication events (login, passkey use, audit exports), and critical billing mutations — are recorded in an append-oriented audit trail with timestamps, actor context, entity references, and correlation identifiers for traceability.

Authorised account owners and managers can query audit timelines in the product and export activity logs as CSV (RFC 4180) or JSON over a defined date range for compliance reviews, dispute resolution, and internal controls. Export actions themselves are logged. Platform operators may additionally use immutable-friendly NDJSON exports for cross-tenant operational review under strict internal controls.

Audit retention is governed by configurable retention policy and legal-hold mechanisms for investigations. Application and infrastructure logs support incident diagnosis; we continue to expand metrics and alerting for production observability.

Our API layer uses GraphQL with authentication guards, input validation, query complexity limits, and sanitisation to mitigate common web risks aligned with OWASP guidance — including injection, broken access control, and excessive data exposure.

Rate limiting protects authentication, OTP, billing mutations, and audit export endpoints. Redis-backed limits apply in production with fail-closed behaviour where configured. Security headers (including HSTS and CSP-related controls) are applied at the application edge.

Dependencies are updated on a risk-prioritised basis. Security-relevant changes undergo code review before deployment.

Card and UPI payment processing is handled by licensed payment partners (e.g. Razorpay). Card data entry and storage for payment acceptance occur on partner infrastructure within their PCI-DSS scope. GreenKhata Technologies Pvt. Ltd. does not store full raw card numbers in application databases.

Webhook endpoints verify payment-provider signatures before updating subscription or invoice payment state.

Operational and audit data are retained for periods aligned with business, tax, and legal requirements. Merchants may request account and profile deletion subject to our Privacy Policy and applicable law; deletion workflows remove or anonymise personal data across linked systems where technically feasible.

Legal holds may suspend automatic expiry of audit records during active investigations or disputes.

We use vetted subprocessors to deliver the service. Categories and representative providers include:

• Cloud infrastructure & hosting — e.g. DigitalOcean (compute, databases, object storage).
• Frontend hosting & CDN — e.g. Vercel.
• Payments — Razorpay.
• Transactional email & SMS / WhatsApp — configured providers for OTP, notifications, and receipts (e.g. SMTP, Twilio, Meta Cloud API where enabled).
• Identity — Google (OAuth sign-in).
• Security intelligence — Have I Been Pwned (password breach range API, k-anonymity).

Subprocessors are subject to contractual confidentiality and security expectations proportionate to the data they process. A formal subprocessor list and Data Processing Agreement (DPA) are available to enterprise customers on request.

Databases and critical configuration are backed up on schedules appropriate to recovery objectives. We test restoration procedures periodically. No backup strategy eliminates all disaster risk; merchants should maintain their own exports for business-critical records where required by their auditors or regulators.

We maintain incident response procedures covering detection, containment, eradication, recovery, and post-incident review. Severity-based escalation ensures timely attention to issues affecting confidentiality, integrity, or availability of customer data.

Where required under applicable Indian data protection law (including the Digital Personal Data Protection Act and rules) or other mandatory regimes, we will notify affected parties and authorities within prescribed timelines with factual details available at the time of notification.

Report suspected security issues to security@greenkhata.ai.

We perform recurring vulnerability scanning, dependency review, and targeted manual testing proportional to release risk. Findings are triaged by severity with remediation or compensating controls tracked to resolution.

Independent penetration testing and bug-bounty programmes may be commissioned for major releases or enterprise engagements. Reports are available to qualified customers under NDA where applicable.

Our control objectives are informed by:

• India — DPDP Act & Rules (data fiduciary obligations, breach notification, grievance handling — see Privacy Policy).
• ISO/IEC 27001-aligned practices for information security management (risk assessment, access control, logging, vendor management).
• SOC 2-style trust principles (security, availability, processing integrity) as design goals for enterprise customers — formal SOC 2 Type II attestation is pursued when commercial and operational scale justify third-party audit cost.
• GST and financial record-keeping obligations relevant to Indian merchants using the platform.

Alignment statements describe our intended control environment; they do not by themselves constitute a certificate unless explicitly provided in a signed agreement or attestation letter.

AI-assisted features (voice parsing, suggestions, automation) process inputs necessary to deliver the requested function. AI usage terms are set out in our AI Terms of Use. We do not use customer invoice or customer PII to train public foundation models unless explicitly disclosed and consented for a specific feature.

We welcome responsible reports of potential vulnerabilities. Email security@greenkhata.ai with reproduction steps, affected URLs or APIs, and impact assessment. Please do not access data you are not authorised to view, perform destructive testing, or disclose issues publicly before we have had a reasonable opportunity to remediate.

Customers remain responsible for: strong account credentials, enabling 2FA or passkeys for privileged users, promptly removing staff who leave the organisation, classifying their own end-customer data lawfully, and maintaining offline backups or exports where their auditors require them.

GreenKhata provides the platform controls described on this page; each merchant implements policies appropriate to their industry and risk profile.

Security enquiries, audit export questions, DPA / subprocessor requests, and responsible disclosure: security@greenkhata.ai. Privacy: support@greenkhata.ai.

Enterprise customers may request security questionnaires, architecture summaries, and audit evidence packages subject to confidentiality. GreenKhata Technologies Pvt. Ltd.'s principal place of business is Bengaluru, Karnataka, India. See also our Privacy Policy and Terms & Conditions.