Privacy policy
This policy explains what information Ledgeree collects when you install and use the app, why, who it is shared with, and how to exercise your rights over it. Last updated 18 October 2026.
Who this policy covers
Ledgeree is operated by Bytefacts Software Solutions, Tamil Nadu, India (“Ledgeree,” “we,” “us”). This policy applies to the Ledgeree Shopify app, Ledgeree Books, the ledgeree.com website, and the Ledgeree Agent used to connect to Tally Prime.
Information we collect
We collect only what the configured workflow needs to post correct, GST-compliant vouchers:
- From your Shopify store, via webhooks and the Admin API: fulfillment and order identifiers, line items (SKU, title, quantity, price, discount), shipping province and country, payment gateway name, tracking carrier, and -- only where you configure a GSTIN source -- a B2B buyer’s GSTIN from an order note, metafield, or Shopify B2B company record. For ordinary consumer orders, Ledgeree does not require the buyer’s name, email, phone number or full street address for its accounting records. The exception is B2B accounting: where required for GST reporting, we retain the buyer’s GSTIN and business name from the configured Shopify source.
- Configuration you enter directly: product-to-ERP mappings (SKU, HSN code, GST rate), ledger names, warehouse/state mappings, LUT number and financial year, voucher numbering rules, and (for Zoho Books) OAuth authorization.
- From your connected accounting system: ledger and Stock Item names read back from Tally Prime (via your local Ledgeree Agent) or Zoho Books, used to validate mappings, along with voucher and invoice figures, ledger movements and item quantities read for accounting reconciliation.
- Operational data: sync status, retry counts, error messages, and relay-agent heartbeat/connectivity logs, used to show you what succeeded, failed, or is pending.
- Support correspondence: anything you send us directly, e.g. via the contact form or email.
We do not collect payment card details. Subscription billing runs entirely through Shopify’s own Billing API -- Ledgeree never receives or stores your card number.
How we use this information
- To capture shipped/fulfilled orders and generate GST-correct accounting vouchers in your chosen ERP.
- To validate configuration before posting (e.g. blocking a push when a GST rate or ledger mapping is missing) rather than guessing.
- To show you sync status, retry failed pushes, and alert you to configuration gaps (e.g. an expiring LUT).
- To provide support when you contact us, and to secure the service against abuse.
- To meet our own legal, tax, and accounting obligations as a business.
We do not sell personal information, and we do not use order or customer data for advertising.
Who we share information with
Information is shared only with the service providers needed to run Ledgeree, and only to the extent each one needs:
- Shopify Inc. -- the platform Ledgeree is installed on; all order/fulfillment data originates from Shopify’s own APIs.
- Supabase (database, authentication, and edge functions) -- hosts the application database and the serverless functions that process webhooks and run daily aggregation.
- Cloudflare -- hosts the embedded app and the marketing website, and provides the network edge in front of both.
- Zoho Corporation -- only if you connect Zoho Books; order data is sent to your own Zoho Books organization via Zoho’s API under your own OAuth authorization.
- Web3Forms -- only processes messages submitted through the ledgeree.com contact form (name, email, message); it never receives order or accounting data.
We disclose information beyond this list only where required by law, regulation, or a valid legal process, or to protect the rights, property, or safety of Ledgeree, our users, or the public.
The Ledgeree Agent talks to Tally over your local network without requiring a publicly exposed Tally port. Ledgeree processes Shopify-derived accounting in the cloud and exchanges posting requests, results and the ERP readback data needed for mapping and reconciliation through the agent. Your Tally installation remains on your own machine or network.
International data transfer
Our infrastructure providers (Supabase, Cloudflare) may process and store data outside India as part of their global infrastructure. Where this occurs, we rely on those providers’ own contractual and technical safeguards for cross-border transfer.
Data retention and deletion
- If you uninstall the app, sync halts immediately and your session credentials are deleted.
- If your store goes more than 20% over the shipment limit of its plan, syncing to your accounting software pauses until you upgrade. After two months of that pause we stop capturing new orders, and after three months we cancel the subscription. We email you before each step, weekly and then daily in the final days, so you can upgrade first. These service emails go to the contact email you gave us or, if you have not set one, to your Shopify store’s contact or owner email.
- If your subscription is cancelled while the app stays installed, syncing and order capture stop, and we delete your store’s data two months after the cancellation. We email you from the first month (weekly, then daily during the final three days) so you can resubscribe or export what you need first. Orders placed while capture is stopped can be recovered from Shopify for up to 60 days after they were placed. Records already posted to your own accounting software are not affected. If you open the app again after the deletion you start as a new install.
- If you install the app but do not choose a plan or finish setup, we email you a few reminders during the first month (around days 3, 7, 14 and 30). These reminders do not pause or delete anything.
- When Shopify sends a
customers/redactorshop/redactrequest (per Shopify’s mandatory privacy webhooks), we process the relevant customer or shop erasure. Customer erasure clears identifying fields across source and derived accounting records and operational copies, including queued Tally payloads and results. Shop erasure removes the shop data and stored credentials covered by the request. - Customer and shop data subject to a valid Shopify deletion request is erased or irreversibly de-identified. Accounting figures may be retained only where Bytefacts Software Solutions has an independent legal obligation or the merchant has expressly instructed a lawful archival service; unnecessary customer identifiers are removed.
- Customer data-access exports are compiled when Shopify sends a valid
customers/data_requestwebhook. We notify the merchant by email and provide the export through an authenticated in-app download. The email does not contain the export. Export packages expire after 30 days.
| Record type | Retention |
|---|---|
| Completed or failed sync queue entries, closed errors and resolved incidents | Generally 30 days after completion or closure. Open and pending work follows its own resolution rules. |
| Specified operational audit logs | 90 days for accounting repair, historical repost/return and development-store audit logs, and for records of sync retries you request. |
| Short-lived technical records | Resolved order-reconciliation holds and development-store approval emails (which include the requester's email address and stated reason): 30 days. Queued notes that an order changed in Shopify (order identifiers only), if never processed: 60 days. Pairing-attempt records (IP address) and unfinished accounting-connection attempts: 1 day. |
| Customer-data export packages | 30 days from creation. |
| Erasure evidence | Three years: shop domain, request type, affected-record count and time, separately from the erased customer payloads. |
| Record that an erased shop existed | Three years after the shop's data is erased: the shop domain, when it installed and finished setup, its last plan, the status it ended in, when it was erased, and a one-way hash of its contact email (not the address itself). It contains no orders, mappings, credentials or other store data. |
| Books, mappings and stored reconciliation results | Not deleted by routine diagnostic cleanup. Cancellation, uninstall and valid deletion requests follow the separate rules above. |
Other security logs are retained for up to 12 months, support correspondence for 2 years, and privacy/grievance records for 3 years. Bytefacts Software Solutions’ own GST records are retained for 72 months from the applicable annual-return due date, and corporate books for up to eight financial years only where that rule applies.
Security measures
Zoho Books refresh credentials are encrypted at rest using AES-256-GCM before storage. All traffic runs over TLS. The Ledgeree Agent means your Tally instance is never exposed on a public port -- the agent polls out to our servers rather than accepting inbound connections. Access to production infrastructure is limited to the people operating the service.
Cookies and tracking
The ledgeree.com marketing site uses Google Analytics to measure aggregate site traffic, which sets analytics cookies in your browser. It does not use advertising cookies. The embedded Shopify app uses only the session mechanism Shopify itself requires for embedded apps to function.
Your rights
You may request access to, correction of, or deletion of your personal information, or object to a particular use of it, by emailing grievance@ledgeree.com. We may need to verify your identity and authority (e.g. store ownership) before acting on a request. Deleting data required for your own statutory accounting records may not be possible while you remain subject to those requirements.
Children’s privacy
Ledgeree is a B2B accounting tool for merchants and is not directed at, or knowingly used by, children.
Grievance officer
Grievances and questions about personal-data processing may be addressed to the Grievance and Privacy Contact, Bytefacts Software Solutions, Tamil Nadu, India, at grievance@ledgeree.com. We aim to acknowledge a grievance within 72 hours and provide a substantive response within 30 days.
Governing law
This policy is governed by the laws of India. Subject to any mandatory statutory forum, disputes are subject to the jurisdiction of the competent courts in Tamil Nadu.
Changes to this policy
We’ll update the “last updated” date above when this policy changes, and post material changes on this page before they take effect.
Contact
Questions about this policy: grievance@ledgeree.com.