The architecture, in one picture
Roy has exactly three parts, and only one of them ever touches your books:
| Part | Where it runs | What it does |
|---|---|---|
| Optriq Connector | Your Windows PC — the same machine that runs Tally | Reads from and writes to Tally Prime locally, using Tally’s own built-in HTTP-XML interface. The only component that can see your ledger. |
| Optriq Cloud | AWS Mumbai (ap-south-1) | Receives your chat message, works out what you’re asking, and sends the Connector a narrow, scoped request — “today’s sales total”, never “send the books”. |
| The chat | WhatsApp / Telegram on your phone | Where you talk to Roy and where you approve or reject every write. |
The Connector dials out: it opens a single outbound, TLS-encrypted connection to Optriq’s cloud. There are no inbound ports to open, no port forwarding, no static IP, no VPN, and no remote-desktop access of any kind. If you switch the Connector off, nothing can reach your Tally.
What stays on your PC — always
Your ledger lives on your PC and is never stored anywhere else. Vouchers, party masters, balances, stock, GST data — all of it is read from Tally on your machine, by software on your machine. We do not cache it, mirror it, sync it, or back it up to our cloud. This is not a policy we follow; it is how the product is built — there is no code path that uploads your books. When you ask Roy a question, only the specific figures that answer it transit — the next section spells out exactly what that means.
Alongside Tally’s own data, the Connector keeps a small local database (SQLite, in %AppData%\Optriq\) on your PC:
- Activity log — a record of everything Roy did: who asked what, what was posted, what was approved and when
- Settings — your preferences and approval rules
- License key — your subscription identifier
That database is yours too. It never leaves your computer.
What passes through our cloud, and why
Roy could not answer you if nothing ever left your PC — the answer itself has to reach your phone. Here is exactly what transits, and what happens to it:
| What | Why it transits | What happens after |
|---|---|---|
| Your chat messages | To understand what you’re asking for | Processed in memory, not stored |
| Voice notes | Transcribed to text | Audio discarded after transcription |
| Bill photos and PDFs you forward | Read into a draft voucher for your approval | Discarded after extraction |
| The specific figures a request needs (e.g. today’s sales total, one party’s outstanding) | To reason about your question and render the reply that reaches your phone | Held in memory for that conversation turn only, then gone — never written to a database, never stored |
What our cloud stores is deliberately boring: your license and pairing details, feature settings, and anonymised error logs. The full inventory, with retention periods, is in our Privacy Policy.
Trace one question end-to-end. You type “Mehta ji ka outstanding kitna hai?” The cloud works out this is an outstanding-balance query and asks your Connector for one party’s balance. The Connector queries Tally locally and returns that figure. The cloud composes the reply and sends it to your chat. Nothing from that exchange is persisted on our servers. Your ledger was never requested, never sent, never seen.
Every write needs your tap — cryptographically
Roy never posts anything on his own. Every voucher — sales, purchase, payment, receipt — is presented to you first as a draft card with the full breakdown: party, items, GST, total. You tap Approve, or you tap Reject.
The approval is not a soft convention — it is enforced by the software on your machine:
- When you tap Approve, our cloud issues a signed approval token (HMAC-SHA256) that is bound to the exact contents of that draft — the token embeds a SHA-256 fingerprint of the draft, down to the paisa.
- Your Connector independently verifies the signature and that the voucher it is about to post matches the fingerprint. If either check fails, nothing is posted.
- The check is fail-closed: a Connector that cannot verify an approval refuses all writes. There is no bypass, no “dev mode”, no fallback.
What you approve is what gets posted — and our record since launch stands: zero unapproved writes, ever. Every entry in every customer’s books came from a draft its owner tapped.
Reads are scoped the same way: the cloud can only ask the Connector the specific, narrow questions the product defines — it cannot ask for arbitrary data.
Your data trains nothing
We do not use your business data to train AI models — not ours, not anyone else’s. The AI providers we use process only what a specific request needs (your message, a voice note, a bill image, the figures needed to answer), under contracts and policies listed in our Privacy Policy. We do not sell your data, profile your business for advertising, or share your Tally data with third parties.
The software on your PC
- Two editions, one core. The flagship Connector runs on Windows 10 and newer; a Legacy edition covers Windows 7/8 machines still common on factory floors. Both are built from the same core code — a fix lands once and both editions get it.
- Signed updates. Every installer and every update is cryptographically signed. The Connector verifies the signature before applying an update — an unsigned or tampered build will not install.
- Outbound only. The Connector never listens for connections from the internet. It makes one outbound TLS connection to Optriq’s cloud, and it talks to Tally only on your machine.
Leaving is clean
If you stop using Roy, there is nothing to migrate and nothing held hostage — your books were in your Tally the whole time.
- Uninstall the Optriq Connector (Settings → Apps → Uninstall)
- Delete the
%AppData%\Optriq\folder if you want the local activity log gone too - Email support@optriqai.com — we delete your cloud data (license, pairing) within 7 working days and confirm by email
Your Tally, your data, and your books are exactly as they were. Roy only ever added the entries you approved.
Orionwave Private Limited • Your Tally data never leaves your computer.