Privacy notice

Who we are

Ridepro Learning Private Limited, 105 Shaalimaar Complex, 19/1 Manoromaganj, Indore 452001, India ("Tallycon", "we", "us") makes the Tallycon desktop app, runs this website and runs the Tallycon account service. This notice explains what personal data we process, why, and your rights under the Digital Personal Data Protection Act, 2023 (the "DPDP Act") and the rules made under it.

Questions or requests: contact@ridepro.in. Grievance officer: Anis Khan, Grievance Officer, Ridepro Learning Private Limited, contact@ridepro.in, 105 Shaalimaar Complex, 19/1 Manoromaganj, Indore 452001.

The short version

• The website keeps an access log of each request (including your IP address and browser details), only to count page views, for 90 days. It sets no tracking cookies.
• The website collects what you type into the demo form, and only to arrange a demo and reply to you. Your email address also goes to Plunk, our email service, for up to three follow-up emails. If you book a time, you do it on Cal.com, which gets what you type there.
• The desktop app reads your Tally books on your own network. It keeps what it makes on your own computers. To answer a question, it sends the data that question needs to our AI provider, Anthropic. We keep no copy of your books, questions or answers on our servers.
• If your firm uses Tallycon accounts, we keep what is needed to sign you in, count usage and bill the firm, and nothing from your books.

1. This website

The site is hosted on Amazon Web Services: its pages are stored in Amazon S3 in Mumbai and served through Amazon CloudFront, which delivers them from the edge location nearest you. To serve a page, CloudFront processes your IP address and the page you ask for.

CloudFront keeps an access log of each request in a fixed format. Each entry records: the date and time; the edge location that served it; your IP address and port, and any IP address your connection reports it was forwarded for (for example by a proxy); the method, site name, page and any query string (the part of the address after a ?); the response status, its content type and size, and the bytes sent and received; how long the request took and whether it was served from the edge's cache; the page that linked to it (the referrer); your browser's user agent (its name, version and operating system); the protocol, TLS version and cipher your connection used; and a request id. We read these logs only to count page views, see which sites refer visitors and tell crawlers from people. They are kept in a private Amazon S3 bucket in Mumbai, deleted automatically after 90 days, and not shared with anyone. Cookies are not recorded in them.

The site sets no analytics, advertising or tracking cookies and loads no third-party scripts; page counts come from these logs alone.

2. Demo requests

What we collect: your name, work email, phone number if you give it, firm or company, your role, the number of clients if you are a CA firm, which Tally you use, and anything you write in the question box.

Why: to arrange a demo with you and reply to your request, including up to three follow-up emails about the demo. Nothing else. We do not add you to a newsletter: no Plunk campaign or broadcast goes to your address beyond those three follow-up emails. We do not sell or share your details for marketing.

Legal basis: your consent, given by ticking the box on the form (section 6 of the DPDP Act).

How it is handled: the form sends your details to a small service of ours on Amazon Web Services, which emails them to our team through Amazon SES and keeps no copy of the request. The email stays in our team mailbox until the demo and its follow-up are over, and we then delete it unless you have become a customer. Amazon processes the message to deliver it, under its own terms.

Follow-up emails (Plunk): when your request is accepted, the service also sends your email address, and no other field from the form, to Plunk, an email service that processes it for us. Plunk sends you up to three emails about the demo: one straight away, one after 2 days and one after 7 days. We stop them when you reply, and they stop when you book a demo on Cal.com (below). Open tracking is turned off, so the emails carry no tracking pixel. Plunk keeps your address, under its own terms and on servers that may be outside India, until we delete it from Plunk, which we do when you withdraw consent.

Booking a time (Cal.com): the page you see after sending the form, and each follow-up email, link to our booking page on Cal.com, a scheduling service that processes bookings for us. Nothing from Cal.com is loaded on our website: the link opens Cal.com in a new tab, and our site sets no Cal.com cookie or script. If you book, Cal.com gets what you type there (your name and email address) and the time you pick, sends you the meeting link and tells our team. Booking stops the follow-up emails: your address is marked in Plunk as booked and unsubscribed. If you book on Cal.com without having sent the demo form, the email address you book with is added to Plunk only as an unsubscribed contact marked as booked, so no email is sent to it. Anyone you add to a booking as a guest is not passed to Plunk. Cal.com keeps the booking, under its own terms and on servers that may be outside India, until we delete it, which we do when you withdraw consent.

Withdrawing consent: write to contact@ridepro.in at any time. We will stop using your details, delete the request from our mailbox, remove your address from Plunk, delete any booking from Cal.com and stop any follow-up emails not yet sent, unless we must keep something by law. Withdrawing is as easy as giving consent and does not affect anything done before.

Please do not put figures or party names from your books in the question box.

3. The Tallycon desktop app

The app runs on your computer and reads Tally over your office network. It does not write to Tally.

On your computers, not ours: settings, Tally addresses, your Anthropic key if you use your own (encrypted with your operating system's keychain), conversations and the vouchers behind each answer, the question log, GSTR-2B files you load, a log of the questions asked, exports and statements made, and the exported files. They stay until you delete them; we cannot see them. The app has no telemetry or analytics.

Sent to Anthropic to answer a question: the question, the conversation so far, and the data from your books that the question needs. That data can include personal data about your clients, parties and employees, such as names, figures, narrations, GSTINs and PAN status. It is sent over an encrypted connection, either directly with your own key or through our metering proxy (section 4). Anthropic, PBC processes it under its commercial terms to produce the answer; it may be processed outside India, including in the United States. We have asked Anthropic for zero data retention on our account; until it is granted we make no statement about how long Anthropic keeps request data.

Remote access, if you turn it on: a laptop paired with your office asks through our relay. The relay forwards end-to-end encrypted frames that it cannot read. It logs connection details only: when an office or device connects and disconnects, a shortened office id, the number of frames, how the connection closed, and the device's network address, with the last part removed for IPv4 addresses (IPv6 addresses are currently logged in full). These logs are kept in Fly.io's log service for as long as Fly.io's log retention keeps them.

Updates (Windows installs): the app checks our release feed on GitHub for a new version. GitHub sees your IP address and the app version.

Your role: for the books you read with Tallycon, you (or your firm) decide what is processed and why. Where those books hold personal data, you remain responsible for it as Data Fiduciary, and we process it only to answer the questions you ask.

4. Tallycon accounts

If your firm signs in to Tallycon, we process:

• To sign you in: your email address, a one-time code, an installation id (a random number, not tied to your hardware), a name you give the computer, its public key, app version and platform. Google Workspace sign-in is planned; when a firm turns it on, we will also keep the Google account id and Workspace domain that Google returns, never your Google password or tokens.
• To manage your firm's account: your role, whether you are disabled, your seat, your devices, and which clients you may see. Clients are short numbers made from a key only your firm holds; we never receive client names.
• To count usage and enforce caps: for each question through our proxy, who asked (firm, user, seat, device), when, the model, token counts, cost, request sizes, status, Anthropic's request id and any error type, any refusal code, where Anthropic processed the request, the amount set aside against caps, and the client number. The proxy passes your question and the data from your books to Anthropic in memory and does not store it.
• To bill your firm (when online payment opens): the firm's legal name, GSTIN, state and billing email, and the plan, seats, amounts, tax and dates of each payment, with Razorpay's ids for them. Card and UPI details are entered only on Razorpay's pages and never reach us. Razorpay, our payment provider, keeps its own payment and invoice records under its own terms.
• To email you: sign-in codes, invitations, role changes, security notices, cap alerts and billing notices, sent through Postmark.

Legal basis: performing the contract with your firm, and legitimate uses permitted under section 7 of the DPDP Act where the firm has provided your details for your account. The service runs on Fly.io in Singapore.

How long we keep it:

• Your account, devices, seat, client assignments and usage: while your firm is a customer. If a paid firm's plan ends, we keep them for 12 months so the firm can come back, then delete them. A free trial that never becomes a paid plan is deleted 60 days after the trial ends.
• Sign-in codes: deleted when used or once they expire. Sign-in tokens: kept only as hashes, and deleted 30 days after they expire. Records used to limit sign-in attempts: one day.
• Cap alerts already sent: 13 months.
• Billing records: 8 years after the firm's last payment, as accounting and tax law requires, also after the firm's account is deleted. They name the firm, not a person; the billing email is not kept with them once a firm's account is deleted.
• Free trial sign-up: to stop a free trial being started twice from one email address, we keep a one-way code made from the address (not the address itself) for 2 years, also after the firm's account is deleted. With it we keep one-way codes made from the network address block you signed up from and from your email's domain (none for public email services such as Gmail), to limit trials per network and per company; these are cleared about a month after the sign-up.
• Sign-up codes asked for before a firm exists: a one-way code made from the address you typed, a hash of the code and the number of attempts, deleted when the code expires.

A partner in your firm can erase a person or a device at any time: their email address, device names, installation ids and keys are removed, and only anonymous ids stay so the firm's usage still adds up. A firm that leaves can ask us to delete its account.

5. Your rights

Under the DPDP Act you can:

• ask for a summary of the personal data we process about you and how we process it;
• ask us to correct, complete, update or erase it;
• withdraw consent where we rely on it;
• nominate another person to exercise these rights if you die or cannot act;
• have a grievance about our handling of your data addressed.

Write to contact@ridepro.in or our grievance officer above. We will reply as soon as we can, and within the time the DPDP Rules set. If you are not satisfied with our reply, you may complain to the Data Protection Board of India.

If your data is in a firm's Tally books, the firm is the right place to ask first; we will help it respond.

6. Security

Data sent off your network is encrypted: TLS to Anthropic and to our services, and remote access end to end. Tally itself is read over your office network without encryption, which is why Tallycon never exposes it beyond that network. Keys and sign-in data on your computer are sealed with your operating system's keychain. Our service stores sign-in tokens only as hashes. If a personal data breach affects you, we will tell you and the Data Protection Board as the DPDP Act and its rules require.

7. Children

Tallycon is for businesses and their advisers. It is not meant for anyone under 18, and we do not knowingly collect children's data through the website or demo form.

8. Changes

We will post any change here with a new date, and tell account holders by email when a change matters to them.