Last updated: 19 November 2026
Privacy Policy
Kontroma Private Limited (“Reimbilly”, “we”, “us”) is committed to protecting your personal data. This policy explains what we collect, why, and how you can control it.
1. Who we are
Kontroma Private Limited, incorporated in India on 18 July 2026 (CIN U62011MH2026PTC473706), operates the Reimbilly platform at reimbilly.com and app.reimbilly.com (“the Service”). Grievance Officer: Sachin Zore — grievance@reimbilly.com.
Registered office:
Floor 7, Skyline Icon, Marol Chimatpada,
J.B. Nagar, Andheri East, Mumbai 400059,
Maharashtra, India
2. Data we collect
- Account data: Name, email address, phone number (optional), profile photo.
- Expense data: Receipt images, vendor names, amounts, dates, categories, notes, GST details.
- Organisation data: Company name, team memberships, roles, spending policies.
- Usage data: App events and feature usage (via PostHog, hosted in the EU), crash reports (via Sentry), device type, OS version.
- Accounting data: If your workspace connects QuickBooks or Xero, we read your chart of accounts and supplier list, and write approved expense lines. See §5a.
- Payment data: We do not store card numbers. Card payments in India are processed by Razorpay, and subscriptions are sold through Paddle, which acts as merchant of record; we store only payment references and status.
- Direct messages: Private to the two participants — no one else in the workspace, including admins, can read them in the Service. Encrypted in transit and at rest and stored in India. They are not end-to-end encrypted, so we could be compelled by law to produce them.
- Secret chats: End-to-end encrypted on the sender’s phone or browser. We store only ciphertext and cannot read what we store. You can compare a security code with the other person to check their key, and the app warns you if it changes; until you compare, the first key is the one our server handed out. A secret chat stays on the phone or browser it was used on.
- Channel messages: Encrypted in transit and at rest, but not end-to-end encrypted. Your workspace admins can read them, and so can we if compelled by law. Use a direct message for anything you would not put in a work channel.
2a. Forms on our website
You do not need an account to write to us. When you use a form on reimbilly.com we keep what you enter, together with your browser's user-agent string:
- Contact: your name, email address, company (optional), the topic you choose, your message and, if you choose, a phone number.
- Demo request: your name, email address, company, its size, how you reimburse expenses today, the problem you describe and, if you choose, a phone number.
- Careers and talent pool: your name, email address, the role (for the talent pool, the kind of work you would like instead), a link to your resume, your LinkedIn and portfolio links if you add them, your note and, if you choose, a phone number.
- Newsletter: your email address only.
To stop automated abuse, each form is checked by Cloudflare Turnstile, and your IP address is used to limit how many messages one connection can send in an hour. The IP address is not stored with your message.
The emails we send. A copy of your message goes to our own inbox so that a person can reply. For a contact, demo or careers message we also send one acknowledgement email to the address you gave: it carries a reference number and when to expect our reply (for the talent pool, how long we keep your details instead), with links to our FAQ and docs, and none of the words you wrote. We send at most one a day to the same address, and none if the form's automated checks did not pass. A newsletter sign-up gets neither email. These emails are sent through Postmark (see the sub-processors page).
Purpose and basis. We use these details only to answer you: to reply to your message, arrange the demo you asked for, or consider your application. The basis is your request — you gave us the details so that we would reply (under the GDPR, steps you asked us to take or our legitimate interest in answering messages sent to us; under the DPDP Act, the purpose for which you provided them voluntarily). A newsletter sign-up is used only to send you product news, on the basis of your consent: once the form's automated checks have passed, your email address (and nothing else) is added to our newsletter list at Brevo, which sends the newsletter. Every issue has an unsubscribe link; after you use it, Brevo keeps your address only as unsubscribed, so you are not added back. We do not add the address from a contact, demo or careers form to the newsletter.
The talent pool. While we are not hiring, the careers page offers a talent pool instead of job applications. We keep an entry only because you ticked the box agreeing to it, and only so that we can contact you if a role that fits opens. You can withdraw that consent at any time and we delete your entry. If you send us a CV by email instead, we ask before keeping it, and keep it only if you agree. Talent-pool entries and CVs are kept in our own Google Workspace, not shared with anyone, and not used for anything else.
Phone numbers. A phone number is optional. We keep it only if you tick the box allowing us to call or WhatsApp you about your request (in the talent pool, about a role), and we use it only for that: never for marketing, and it is not passed to our newsletter provider or any other marketing tool. It is kept with your message, in our own systems and Google Workspace, and deleted with it.
How long we keep it. Contact, demo and careers messages are deleted automatically 12 months after we answer them, or 12 months after they arrive if they were never marked answered. A talent-pool entry, with any CV you sent, is deleted 12 months after you join. Our own record of a newsletter sign-up is deleted automatically 24 months after you sign up; your place on the Brevo list lasts until you unsubscribe or ask us to remove you. The copy in our inbox is kept with our ordinary email correspondence. To stop the newsletter, use the unsubscribe link in any issue. To have your message, sign-up or that copy deleted sooner, write to hello@reimbilly.com or to our Grievance Officer (§1).
3. How we use your data
- Providing and improving the Service.
- Processing expense reports and approvals.
- Sending transactional emails (approval notifications, invitations).
- Analytics to improve features (aggregated, not sold to advertisers).
- Compliance with legal obligations.
4. Legal basis (DPDP Act 2023 / GDPR)
Under the GDPR, we process personal data on the following bases: (a) consent — for marketing; (b) contract — to provide the Service you signed up for; (c) legitimate interests — for security monitoring and fraud prevention; and (d) legal obligation — for tax and regulatory purposes.
Under India's DPDP Act 2023, we do not rely on legitimate interest. That basis is not available to private entities under the Act. For users in India we process personal data on the basis of your consent, or for the limited legitimate uses and legal obligations the Act itself recognises. You may withdraw your consent at any time in Settings → Privacy, and withdrawing it is as easy as giving it.
5. Data sharing
We share personal data with third parties that operate parts of the Service on our behalf — hosting, email, crash reporting, payments, and analytics. The complete, current list, including what each one receives and where it is located, is published at reimbilly.com/subprocessors and updated whenever it changes.
We do not sell your data. We do not use your data for advertising.
5a. Accounting integrations (QuickBooks and Xero)
If a workspace administrator connects an accounting system, Reimbilly exchanges data with that provider strictly to keep your books in step with your approved expenses. Connecting is optional, is initiated by your workspace, and can be undone at any time.
- What we send: lines from approved expense reports only — vendor name, amount, currency, date, description, and the expense category — and, as the bill's payee, the name and the email address the employee being reimbursed signs in with (the money is owed to them). Nothing is sent for draft, submitted, or rejected reports.
- What we read: your chart of accounts and supplier list, so each expense can be booked against the right account rather than guessed.
- What we never send: receipt images, chat messages, your Reimbilly password, or any expense that has not been approved.
- Authorisation: we never see your QuickBooks or Xero login. You sign in on the provider's own site and the resulting access token is stored encrypted on our servers — never on your device.
- Disconnecting: using Disconnect in Reimbilly revokes our access at the provider and deletes the stored tokens. Anything already written to your accounting system stays there — it is your record, and we do not delete your books.
Data sent to QuickBooks is processed by Intuit Inc. under its own privacy policy; data sent to Xero is processed by Xero Limited under its own. Your relationship with those providers is governed by your agreement with them.
5b. How Reimbilly uses AI
Reimbilly uses AI in one place: reading the receipts you upload. When you add a receipt, the image is passed to an optical character recognition (OCR) service that extracts the text, and we then pattern-match that text to guess the merchant, amount, date and payment reference. The current OCR provider is listed on our sub-processors page.
- Every extracted field is a suggestion you can edit. Nothing is submitted or approved on the strength of an extraction alone.
- No automated decisions are made about people. Expense approvals, rejections and reimbursements are decided by a human approver in your organisation, never by a model.
- We do not generate synthetic content. Reimbilly does not produce AI-written text, images, audio, video or avatars for you to read or publish, so there is no AI-generated output to label.
- We do not train models on your data. Your receipts and expense records are not used to train or fine-tune any model, by us or on our behalf.
- You are never talking to a bot. Team chat and support replies are from people.
If we ever add a feature that generates content or interacts with you conversationally, we will say so clearly in the product and update this section before it ships.
6. International transfers
Your data may be processed in countries other than your own. The primary data store is in India (Supabase, ap-south-1); product analytics are hosted in the European Union (PostHog); and some processors operate from the United States. Which processor sits where is listed on our sub-processors page.
Where we transfer personal data out of the EEA or the UK, we rely on the Standard Contractual Clauses approved by the European Commission, together with the UK International Data Transfer Addendum where the UK GDPR applies.
Under India's DPDP Act 2023, transfers abroad are permitted except to territories the Central Government has restricted by notification. We monitor those notifications and will move or replace a processor if one of ours becomes restricted.
7. Data retention
- While your account is open, we keep your data until you delete it. Your plan never changes how long we keep anything: it changes how much of your history the app opens, and nothing is deleted because a plan ended.
- When you delete your account, it happens at once, not after a waiting period. Your name, email, phone number and photo are removed and you are signed out everywhere. Your receipt images, your expense notes and the text of the chat messages you sent are deleted. Expenses, receipts and reports you kept for yourself, outside any workspace, are deleted too.
- Expenses and reports you filed in a workspace are your company's records, which it must keep by law. They stay with the workspace without your name (shown as "Deleted User") while the workspace is open, and for 8 years after it closes (see "Closed workspaces" below). The record of the consents you gave and of your deletion request is also kept without your name, because the law asks us to be able to show them.
- Deleting your account is final. Deleted data cannot be recovered, including from backups: we never restore a backup to bring back one person's data, even if they ask.
- Backups exist only to restore the whole service after a disaster. They are kept for at most 30 days and then expire, so any copy of a deleted account in them is gone within those 30 days.
- So that restoring a backup after a disaster can never bring a deleted account back, we keep a short record of each deletion request outside our main database for 60 days: the request number, a one-way code derived from the account id, and the dates. It holds no name, email or other contact details, and is used only to delete that account again from a restored copy.
- Signing up again with the same email creates a new, empty account.
- Closed workspaces: when a workspace's owner closes it, everyone in it is told and has 30 days to export their data (someone who joins during those days is told when they join). Closing deletes nothing: the workspace's records (expenses, receipts, reports, approvals and payments) are kept for 8 years after it closes, because they are the company's books, and are then deleted. Meanwhile each person can still read and export their own expenses and reports. Direct messages are not part of the workspace and are not deleted with it.
- Messages sent through the forms on our website (no account needed): 12 months after we answer them. Talent-pool entries and CVs: 12 months after you join. Newsletter sign-ups: our record 24 months; the newsletter list at Brevo until you unsubscribe. See §2a.
8. Your rights
Under the DPDP Act 2023 and GDPR, you have the right to:
- Access and export your personal data (Settings → Data Export).
- Correct inaccurate data.
- Delete your account and data.
- Restrict processing in certain circumstances, and object to it.
- Withdraw consent for marketing.
- Nominate someone (India, DPDP Act 2023 §14). You may appoint another individual to exercise your rights on your behalf in the event of your death or incapacity. Write to our Grievance Officer to register a nominee.
- Lodge a complaint with a supervisory authority, or with the Data Protection Board of India.
To exercise your rights, email privacy@reimbilly.com. We respond within 30 days.
9. Children's privacy
Reimbilly is an expense-management tool for working professionals. It is not directed to children, and we do not market it to them.
Under India's DPDP Act 2023, which defines a child as anyone under 18, the Service is intended only for users aged 18 and over, and we do not knowingly process a child's personal data without verifiable consent from a parent or lawful guardian. A self-declaration checkbox is not treated as verifiable consent. Under the United States' COPPA, we do not knowingly collect personal data from children under 13.
If we learn that we hold a child's personal data without the consent the law requires, we delete it promptly. If you believe a child has given us data, contact our Grievance Officer at grievance@reimbilly.com.
11. Security
See our Security page for a full description of our technical and organisational measures.
12. Changes to this policy
We will notify you by email and in-app notification at least 14 days before material changes take effect. Continued use of the Service constitutes acceptance.
13. Contact and data controller
The data controller is Kontroma Private Limited (CIN U62011MH2026PTC473706), Floor 7, Skyline Icon, Marol Chimatpada, J.B. Nagar, Andheri East, Mumbai 400059, Maharashtra, India.
Privacy and data-rights requests: privacy@reimbilly.com
General support: support@reimbilly.com
Grievance Officer (India, DPDP Act 2023): Sachin Zore, Director — grievance@reimbilly.com. We acknowledge grievances on receipt and respond within 30 days, as the Act requires. You also have the right to complain to the Data Protection Board of India.