Privacy Policy
Effective 18 September 2026
ZAMEER LLC, a Kentucky limited liability company, is the fractional operating practice of Zeeshan Bhatti. This policy covers two things: the zameer.io website, and the software we build and operate for clients, including any application that connects to a client's QuickBooks Online company. We have written it to be read rather than skimmed past.
The zameer.io site has no accounts and no login. If you write to us or book a call, we receive what you choose to send: your name, your email address, and whatever you tell us. We use it to reply and to carry out the work, and for nothing else.
Our website host records standard server request data, such as IP address, browser type and the pages requested, as almost every web host does. Pages on this site load a typeface from Google Fonts, which means your browser makes a request to Google's servers and Google receives your IP address as part of that request. We use no advertising trackers and no analytics cookies.
Links to the demonstration pages we send prospects, at addresses beginning zameer.io/d/, record the browser type and the referring page in a database ZAMEER LLC operates. That record is first-party, is used only to see whether a demonstration was opened, and is not shared with advertisers or anyone else. We do not delete it on a schedule: it is kept until we clear it. If you would like the record of your visit removed, write to zeeshan@zameer.io and we will remove it.
Where a client engages us to build software that connects to their QuickBooks Online company, that connection is authorised by the client and limited to reading financial records needed for reporting. In practice that is:
The software holds read-only access to QuickBooks. It has no capability to create, alter, void or delete a record there, no configuration or setting enables one, and it will not be given one without the client's written agreement. QuickBooks remains the system of record for every figure the software reads.
Where a client engages us to connect their Microsoft 365 mailbox, the software reads mail threads and contacts for the customers and vendors in the client's CRM, so that recent correspondence appears beside each record. It holds write permissions limited to creating draft emails in the client's own mailbox and adding or updating the client's own contacts. It cannot send mail, and it has no delete operation of any kind. Those threads and contacts include the personal data of the client's correspondents: names, email addresses and the contents of messages. That data is read into the client's own store, on the client's own systems, and is handled under the same commitments as the client's accounting data. The credentials for this connection are stored on the client's own systems in the same way.
It lives on the client's own systems: the computer the application runs on, and the client's own cloud storage, where the store is kept and mirrored. The application runs locally. The access credentials that authorise the connection are stored on those same systems, never with us. We operate no cloud service that receives, stores or processes a client's QuickBooks data, and none of it is transmitted to us in the ordinary course of the software running.
Because we build and support the software under a services agreement, we may see a client's data while doing that work, in the same way any professional adviser sees the records they are engaged to work on. We treat it as confidential, use it only for the engagement, and do not disclose it.
When you approve the connection, QuickBooks returns you to a page on this site with a short authorisation code in the address. That page is static: it reads the code in your browser and displays it. It stores nothing, transmits nothing and sets no cookies.
To be complete: because the code arrives as part of a web address, it may appear in our website host's ordinary request logs. The code is short lived, single use, and worthless without a client secret that never leaves the client's computer. We consider this the honest disclosure to make rather than the one to leave out.
Client accounting data is retained on the client's own systems for as long as the client keeps it. They control deletion directly. Correspondence and engagement records are kept for as long as needed for the engagement and for the period our professional and legal obligations require, then deleted.
Credentials are held on the client's own systems, in a folder kept out of cloud backup, and are never committed to source control or written into any published file. Every connection the software makes, to QuickBooks and to Microsoft 365, is made over HTTPS. Before every release, and on every commit, the published source repositories for our client software are swept for identifying content, meaning names, email addresses, tenant identifiers and local file paths, and credential files are kept out of the published tree by kind. No system is perfect, and we would rather describe our practices accurately than promise more than any practice can deliver.
You can disconnect the application from QuickBooks at any time, under Settings, then Apps, then Disconnect. Access stops at once. You may also ask us what we hold about you, ask for it to be corrected, or ask for it to be deleted, and we will do it. Write to zeeshan@zameer.io.
Our services are for businesses. They are not directed at children, and we do not knowingly collect information from anyone under 18.
If this policy changes we will update the effective date above. Where a change is material and affects an active client connection, we will tell that client directly rather than rely on them noticing.
ZAMEER LLC, a Kentucky limited liability company
Contact: Zeeshan Bhatti · zeeshan@zameer.io
Louisville, Kentucky, United States
QuickBooks and Intuit are trademarks of Intuit Inc. ZAMEER is not affiliated with, endorsed by, or sponsored by Intuit.