Privacy Policy
Software Ownership Disclosures, Legal Role Allocations, and Local-First Architecture
1. Software Ownership & Critical Identity Disclosures
This Privacy Policy governs the SmartCA Office Connect software product (hereinafter referred to as the "Software", "Application", or "SmartCA").
A. Nature of the Product, Current Status, and Intended Deployment Model
SmartCA is an independent software application developed, owned, and operated by its individual software developer (hereinafter referred to as the "Software Provider" or "Software Operator"). At present, the application architecture and features have been tested in a single-instance development environment on the developer’s local Windows computer in India.
The intended commercial model is to offer the software as an on-premises desktop automation companion to independent Chartered Accountancy firms, practitioners, and accounting professionals (each, a "Customer CA Firm"). When commercially distributed, each Customer CA Firm will independently deploy and operate its own local software instance to manage its respective accounting, GST reconciliation, tax filing, and client communication workflows. Commercial multi-firm deployment is an intended design model and has not yet been rolled out to external commercial customers.
Software Ownership & Operator Identity
The Software product is legally owned and operated by:
Software Developer / Legal Owner
MODI KRISH
Product / Brand: SmartCA
Operating Location
Surat, Gujarat, India
Software Support & Privacy Contact
2. Data Protection Roles & DPDP Act Framework
Under the Digital Personal Data Protection Act, 2023 (DPDP Act) and applicable data protection principles, legal responsibilities (such as those of a Data Fiduciary or Data Processor) are not determined by unilateral software labels. Instead, legal roles depend on the actual purposes, means of processing, technical control, and contractual agreements in place between the parties:
Tier A: Software Provider Level
Software OperationsApplies to: Software customer account administration, license validation, developer API configuration metadata (such as Meta Developer App sandbox credentials and Cloudflare edge hosting), and technical diagnostics submitted for software support.
Role Determination: The Software Provider determines the purpose and means for processing its own administrative, licensing, and support data.
Tier B: Customer CA Firm Level
Client WorkflowsApplies to: Client financial records, purchase invoices, sales ledgers, bank statements, tax return drafts, PAN/GSTIN identifiers, and direct client WhatsApp communications processed within an on-premises deployment.
Role Determination: When a Customer CA Firm collects, evaluates, and files tax records for its clients, it typically determines the purposes and means of that professional engagement. However, the precise division of data protection responsibilities between the CA firm, its clients, and software/platform vendors depends on the specific commercial agreements and technical configurations in place.
3. Categories of Information Processed
A. Software Administrative & Support Data (Collected by Software Provider)
- Customer Account Particulars: Contact name, business email, and administrative correspondence of software licensees or evaluation contacts.
- Technical Diagnostics: Error logs, application crash traces, and version telemetry submitted for technical troubleshooting (stripped of client financial ledgers).
B. Client Financial & Accounting Data (Processed within Local Deployments)
- Client Identifiers: Name, trade name, WhatsApp phone number, email address, PAN, and GSTIN of client representatives.
- Accounting Source Records: Purchase registers, sales bills, debit/credit notes, inventory sheets, and trial balances.
- Banking & Compliance Files: Bank statements, challan receipts, GSTR-2B data, and computation working papers.
C. Communication Telemetry
- WhatsApp message identifiers (wamid), timestamps, delivery status receipts (sent, delivered, read), and attachment metadata handled during messaging workflows.
4. Integration & Communication Processing Status
SmartCA Office Connect includes modular communication capabilities. To ensure strict factual accuracy, their verified implementation and deployment status are classified below:
Meta WhatsApp Cloud API
Developer Sandbox VerifiedWebhook ingestion, HMAC-SHA256 signature verification, and automated response messaging have been tested and verified exclusively within Meta’s Cloud API developer test environment (using developer sandbox credentials and test recipient numbers). Commercial production WhatsApp operation has not been verified or deployed. For commercial production deployment, each Customer CA Firm will be required to connect its own verified Meta Business account and commercial business phone number.
Email (Gmail / Google Workspace)
Configurable (Inactive)Underlying data models exist within the application architecture, but live Google Workspace / Gmail OAuth connections and mailbox syncing are currently inactive. No email data is transmitted or retrieved until explicitly configured by an authorized administrator.
Document Intake & OCR
Local Rule Engine (On-Premises)Document files (PDFs, images, Excel sheets) received via messaging or direct drop are organized into local folders on the host computer. Text classification and extraction execute locally using deterministic rules and local OCR libraries. All extracts remain in an "UNDER_REVIEW" status and are never finalized without manual verification. No unredacted client financial records are transmitted to public cloud OCR services.
5. Automated Systems & JARVIS AI Architecture
SmartCA incorporates internal automation routines (designated under the JARVIS / OpenJarvis practice assistant architecture) to facilitate routine accounting tasks:
A. Implemented & Verified Architecture (On-Premises Rules & Local Execution)
- Local Deterministic Rule Engine: Automated features currently active in the application operate via deterministic, rule-based algorithms executing locally on the host machine (e.g., verifying invoice tax math against GST rates, standardizing dates, detecting duplicate invoices).
- Local-First Intelligence: Natural language command routing is powered by local runtime engines (such as a local Ollama instance on the host machine or deterministic fallback logic).
- Zero Third-Party Model Training: Client books of accounts, banking transactions, and PAN details are never transmitted to or used for training public artificial intelligence models.
B. Future / Planned Cloud AI Integrations
External cloud LLM APIs (such as Google Gemini API or Anthropic API) are planned architectural extensions but are currently inactive in this deployment. If external cloud AI capabilities are subsequently activated:
- Data transmission will be strictly minimized to the specific text query required.
- Integration will be contracted solely under enterprise zero-data-retention commercial terms where vendors do not retain prompts or train foundational models.
- Users will be notified before confidential records are analyzed via external cloud models.
6. Local-First Storage Architecture & Access Boundaries
SmartCA is architected with privacy by design, avoiding centralized cloud multi-tenancy:
- On-Premises Host Storage: The software is designed to run locally on the user's Windows hardware. Accounting records, vouchers, and communications reside in a local-first SQLite database on the host machine (utilizing local filesystem storage with Write-Ahead Logging).
- Zero Centralized Cloud Database: The Software Provider does not host or operate a centralized multi-tenant cloud database storing client financial ledgers, audit evidence, or personal tax records.
- Local Access Controls: Data protection on the host relies on physical computer custody, Windows operating system Access Control Lists (ACLs), user account authentication, and disk encryption where enabled by the user.
- External Ingress Restriction: Ingress is restricted via a dedicated local reverse proxy gateway that strictly allowlists webhook endpoints while blocking internal administrative dashboards and databases from public access.
- Technical Support Boundaries: While the application does not automatically sync client data to the Software Provider, technical support sessions requested by a user (such as remote desktop assistance or manual log examination) may involve provider personnel viewing diagnostics under mutually agreed confidentiality terms.
- External Network Communications: While primary financial records are held strictly on-premises, external network communications occur exclusively when specific modular integrations (such as WhatsApp Cloud API messaging or public edge webhook tunnels) are activated, as detailed in Section 7 below.
7. Third-Party Service Providers & External Data Flows
SmartCA Office Connect is designed with a local-first architecture, meaning core client financial ledgers, GST calculations, and accounting books reside strictly on the local workstation. However, specific modular features require external network communications. To ensure complete transparency, all third-party services, transit pathways, and external data flows are documented below based on verified implementation behavior:
| Service & Provider | Status | Information Transmitted | Trigger & Direction | Client Personal Data Included? |
|---|---|---|---|---|
| WhatsApp Cloud API Meta Platforms, Inc. / WhatsApp LLC | Developer Sandbox Verified |
Message Metadata: WhatsApp Message IDs (wamid), sender/recipient phone numbers, sender display names, message timestamps, delivery status receipts (sent, delivered, read).Text Content: Freeform conversation text in incoming messages and outbound automated/manual reminders. Media IDs & Attachments: Inbound webhooks transmit Meta-generated media IDs and MIME types. When processing document intake, the backend makes an outbound GET request to Meta's Graph API to download the raw document binary (PDFs, images) into local workstation storage. |
Inbound: Automatic webhook from Meta edge servers. Outbound: User-triggered (staff manual message/reminder) or automated receipt acknowledgement. |
Yes: Client representative phone numbers, contact names, message text, and submitted compliance documents. |
| Quick Tunnel & Webhook Gateway Cloudflare, Inc. | Developer Sandbox Active |
Edge TLS Termination & Intermediary Processing: Inbound HTTPS connections terminate at Cloudflare's global edge network (*.trycloudflare.com). As a reverse proxy intermediary, Cloudflare decrypts the TLS session and processes the HTTP request (inspecting headers, IP metadata, and raw JSON payload) before forwarding it down the multiplexed tunnel connection to the local cloudflared daemon on the Windows workstation.Local Ingress Boundary: The local gateway (port 8088) strictly blocks all non-webhook requests (HTTP 403 Forbidden), ensuring internal dashboards, databases, and APIs are inaccessible from the tunnel. |
Inbound: Automatic daemon transit routing from Cloudflare edge down the tunnel to local port 8088. | Yes (In transit): Cloudflare edge has visibility into in-transit webhook payloads (sender phone numbers, timestamps, and message text). Cloudflare does not store or access local databases. |
| Public Legal Site Hosting Cloudflare, Inc. (Pages) | Planned / Not Yet Published |
Local Pre-Deployment Staging: Static legal documentation files (Privacy Policy and Data Deletion Instructions) have been authored and tested locally in the smartca-legal-site project directory. The website is not yet publicly published or deployed to Cloudflare Pages.Upon Future Deployment: Cloudflare edge servers will serve the static HTML/CSS assets and collect standard web visitor telemetry (visitor IP, User-Agent, referer header, timestamp, TLS cipher, Cloudflare Ray ID). No client accounting files or databases will be hosted or accessible. |
Planned: Static asset delivery will be automatic upon future public deployment. Currently zero external traffic. | No client data: Standard visitor web telemetry only. No financial ledgers or client tax records. |
| Gmail / Google Workspace OAuth Google LLC | Configurable (Inactive) | If activated: OAuth tokens, email message bodies, subject lines, sender/recipient addresses, attached financial documents (invoices, statements) if enabled. | Inactive: Requires explicit admin OAuth consent and user-triggered inbox sync. | Yes (if activated): Client email addresses, communications, attached invoices/records. |
| Google Gemini Cloud LLM API Google LLC | Planned / Inactive |
If activated: Text prompts, document classification queries, structured schemas. Current active intelligence runs 100% locally via deterministic rule engines or local Ollama without transmission. |
Inactive: Requires user to enter an API key; triggered only during accounting query execution. | Potentially (if activated): Prompt context. Currently zero data transmitted. |
| Technical Diagnostics & Logs Local Host / Software Provider | Local Only (No Telemetry) |
Application Logs (Backend): HTTP request lines, response codes, latency metrics. Statutory identification numbers (PAN, GSTIN), passwords, API keys, and bank accounts are intercepted and redacted in-memory via SensitiveDataFilter prior to emission.Reverse Proxy Gateway Logs: The standalone gateway logs request paths, response statuses, and masked signatures ( sha256=****...). It does not record request bodies, but operates independently of the backend filter.No Automated Uploads: Zero crash-reporting or cloud telemetry SDKs exist. |
Automatic locally; zero automated cloud upload. External transmission occurs only if manually shared by user during technical support. | Sanitized: Statutory IDs and credentials redacted. Contact names or error strings may appear in diagnostic traces. |
8. Statutory Record Retention Disclosures (Indian Legal Frameworks)
Under Indian law, certain entities and professionals are subject to statutory record preservation obligations. Retention duties depend on the legal form of the entity, the specific category of record, and whether official tax or corporate proceedings are active:
-
Indian Income-Tax Law:
Under Indian income-tax law (governed by the Income-tax Act, 2025, which replaced the Income-tax Act, 1961 with effect from 1 April 2026, alongside applicable transitional provisions and rules), specified assessees and business entities are required to maintain and retain books of accounts and supporting vouchers for prescribed periods. The exact statutory retention duration depends on the nature of the assessee, turnover thresholds, and whether reassessment or appellate proceedings are pending, and must be confirmed by a qualified tax professional. -
Central Goods and Services Tax (CGST) Act, 2017 (Section 36):
Applicable to registered persons under GST, requiring the maintenance of books of account and related records for a prescribed statutory duration (generally 72 months from the due date of furnishing the annual return for the year pertaining to such accounts), or longer if proceedings, audits, or appeals are ongoing. -
Companies Act, 2013 (Section 128(5)):
Applicable specifically to incorporated companies, requiring that books of account and related vouchers be preserved in good order for a period of not less than 8 financial years immediately preceding a financial year, subject to statutory orders. -
ICAI Professional Standards (SQC 1):
The Standard on Quality Control (SQC 1) issued by the Institute of Chartered Accountants of India provides professional standards for audit documentation retention (mandating retention for not less than 7 years from the date of the audit report) specifically for audit and assurance engagements.
9. User Rights & Data Deletion Paths
Data deletion requests follow separate procedural paths depending on the nature of the data:
- For Software Licensing & Support Data: Requests to delete software account information or developer support communications should be submitted directly to the Software Provider.
- For Client Accounting, Tax & Financial Records: Requests concerning accounting records, tax filings, or client contact details maintained by an independent CA firm should be submitted directly to that respective firm.
For complete step-by-step instructions, please review: 👉 User Data Deletion Instructions (/data-deletion)
10. Professional Legal Review Flags
⚖️ Mandatory Professional Legal Review Notice
The legal frameworks, operational descriptions, and contractual assumptions outlined in this policy must be submitted for formal review by qualified legal counsel and practicing Chartered Accountants prior to commercial software distribution:
- Indian Digital Personal Data Protection Act (DPDP Act, 2023) & Rules: Formal review of Data Fiduciary vs. Data Processor contractual boundaries, notice requirements, and data principal grievance workflows.
- Customer Agreement & Data Processing Agreement (DPA): Drafting of binding commercial terms governing on-premises licensing, technical support access boundaries, limitation of liability, and data confidentiality.
- Statutory Retention & Legal Holds: Verification by qualified Chartered Accountants of statutory preservation schedules under the Income-tax Act, 2025, CGST Act, and Companies Act against specific client engagement contracts.
- Third-Party Cloud Provider DPAs: Review of enterprise terms with Meta Platforms and Cloudflare.
- Professional Liability Disclaimer: Contractual reinforcement that the Software Provider does not provide accounting, audit, or tax advice, and disclaims liability for tax filings or computations generated by users.
11. Software Operator Contact Details
For inquiries regarding this Privacy Policy, software licensing, or technical data handling by the Software Provider, please contact:
SmartCA Software Operations
Software Product: SmartCA
Software Operator: MODI KRISH (Individual Software Developer / Owner)
Operating Location: Surat, Gujarat, India
Designated Privacy Email: gamingtr465@gmail.com
Support Email: gamingtr465@gmail.com
Note: Inquiries regarding specific client accounting, tax filings, or local office records must be directed to the respective independent Customer CA Firm.