Security and data protection
Read-only, minimal, and in India.
Finance and IT ask the same questions before connecting anything. This page answers them: what Ayush Agro Foods can access, the exact permission scopes, what is stored and what is discarded, who can see it, and how it is deleted.
- Read-only access
- Data hosted in India
- Every access logged
- 10:42Priya Raman · Finance adminExported RCM working sheet, Nov 2026
- 10:31Ananya Iyer · Department headViewed Design tools
- 09:58Faisal Khan · ITConfirmed Framewell seat reassignment
- 09:30Ayush Agro Foods · SystemRead Google Workspace sign-ins (read-only)
- 09:12Rohit (CA) · Accountant, read-onlyViewed Invoice & GST, Nov 2026
Worked example, fictional company. Times in IST.
How Ayush Agro Foods handles your data
Eight commitments, before any connection.
Ayush Agro Foods needs to see the money and the sign-ins. It does not need to move money, read work or keep anything it cannot use.
- Read-only accessStatement uploads, read-only ledger access and read-only identity provider scopes. Messaging integrations post Ayush Agro Foods' own alerts and read only the replies.
- Data hosted in IndiaCustomer data is stored and processed in India.
- No full card numbersCard numbers are masked to the last four digits on upload. Statement data is reduced to recognised software charges after matching; other transactions are discarded.
- Minimal employee dataName, work email, department, seat assignments and last sign-in date per tool. Never emails, files or activity inside a tool.
- Encrypted in transit and at restTLS 1.2 or higher in transit; data encrypted at rest.
- Role-based accessDepartment heads see their own tools only. Finance admins see everything. Accountants get read-only access.
- Every access loggedEvery view, change and export is logged with the user and the time.
- Export on demand, deletion on exitExport your data at any time. When you leave, it is deleted.
Permission scopes
Every scope Ayush Agro Foods requests, per integration.
Anything not listed here is not requested. Each integration page explains the setup and what is never read.
| Integration | Scope or route | Why |
|---|---|---|
| Tally PrimeAccounting | Tally XML over HTTP: Export requests only | With Tally Prime set to act as a server on its configured port (9000 by default) on your network, the Ayush Agro Foods connector sends Export Data and Collection requests for the ledgers you selected. Import Data requests are never sent, so no voucher can be created, altered or deleted. |
ODBC read (alternative) | Where your IT team prefers ODBC, the connector reads the same ledger collections through Tally's ODBC interface with SELECT queries only. | |
File export (no live connection) | If you do not want any connection, export the ledger from Display More Reports as Excel or XML each month and upload it. Ayush Agro Foods reads the file the same way. | |
| Zoho BooksAccounting | ZohoBooks.bills.READ | Vendor bills for software, with tax lines, so foreign bills without GST and Indian bills with a wrong GSTIN can be flagged. |
ZohoBooks.expenses.READ | Expenses recorded directly against software accounts, often card payments. | |
ZohoBooks.contacts.READ | Vendor names, GSTIN and place of supply, to match vendors and check registration. | |
ZohoBooks.banking.READ | Bank and card transactions categorised to software, matched against uploaded statements so nothing is counted twice. | |
ZohoBooks.settings.READ | Organisation details and the chart of accounts, to pick the right organisation and suggest which accounts hold software. | |
| Zoho ExpenseAccounting | File export (no OAuth scope requested) | At launch Ayush Agro Foods reads the expense report export (CSV or Excel) that an admin downloads from Zoho Expense. No live connection to your Zoho Expense account is made. |
| Google WorkspaceIdentity and sign-in | https://www.googleapis.com/auth/admin.directory.user.readonly | The people list: names, work emails, departments, org units, suspended status and last login time. Suspension is one of the offboarding triggers. |
https://www.googleapis.com/auth/admin.reports.audit.readonly | Login and token audit events: when someone last signed in to a tool through Google, and which third-party apps hold a Google token. This is how shadow tools signed in with Google are found. | |
https://www.googleapis.com/auth/admin.reports.usage.readonly | Aggregate usage reports, including Workspace licence usage, to compare paid Workspace seats with active accounts. | |
| Microsoft 365 / Entra IDIdentity and sign-in | User.Read.All (Microsoft Graph, application) | The people list with departments and whether each account is enabled. A disabled account is one of the offboarding triggers. |
AuditLog.Read.All (Microsoft Graph, application) | Sign-in activity and sign-in logs: the last time each person signed in, overall and per enterprise application. | |
Directory.Read.All (Microsoft Graph, application) | Licence assignments, subscribed SKUs and the enterprise applications in your tenant, to count paid Microsoft seats and find tools set up with Microsoft sign-in. | |
| OktaIdentity and sign-in | okta.users.read | The people list and each person's status. Deactivation is an offboarding trigger. |
okta.apps.read | The apps configured in Okta and who is assigned to each, which is the paid-seat side for SSO tools. | |
okta.logs.read | System log sign-in events, to find the last time each person signed in to each app. | |
| SlackMessaging and alerts | chat:write | To post renewal alerts, seat checks and offboarding tasks as the Ayush Agro Foods app. |
im:write | To open a direct message with a tool owner, so the alert reaches the person who decides. | |
users:read | To list workspace members so owners can be matched to their Slack accounts. | |
users:read.email | To match each owner by work email to the person in your Google Workspace or Microsoft 365 directory. | |
commands | For the purchase request slash command, which opens a short form in Slack. | |
| Microsoft TeamsMessaging and alerts | Teams app with a bot, personal and team scope | Your Teams admin installs the Ayush Agro Foods app for the people who own tools and for a finance team. The bot can then send cards in a personal chat or a team channel. |
User.Read.All (Microsoft Graph, application), reused from the Microsoft 365 connection | To match tool owners to Teams users by work email. No extra Graph permission is requested for Teams. | |
| GmailInvoice mailbox | https://www.googleapis.com/auth/gmail.readonly | To search the connected finance mailbox for invoice emails. Ayush Agro Foods queries only with its sender and attachment filter, stores only matched invoice emails, and cannot send, delete or change mail. Use a dedicated billing mailbox, not a person's inbox. |
Forwarding (no scope) | Alternatively, set a filter in Gmail to forward invoice emails to your Ayush Agro Foods address. No Google permission is granted at all. | |
| OutlookInvoice mailbox | Mail.Read (Microsoft Graph, application) limited by an application access policy | To search one finance mailbox for invoice emails. Your Exchange Online admin applies an application access policy so Ayush Agro Foods can read only the mailbox you name, not every mailbox in the tenant. |
Forwarding (no permission) | Alternatively, an Outlook rule forwards invoice emails to your Ayush Agro Foods address. | |
| WhatsApp Business PlatformMessaging and alerts | Approved utility message templates | Business-initiated WhatsApp messages must use templates approved by Meta. Ayush Agro Foods' renewal, seat-check and escalation templates are utility messages about an account the recipient manages. |
Recipient opt-in | An owner opts in to WhatsApp alerts with their mobile number in Ayush Agro Foods. Without opt-in, alerts go by email, Slack or Teams. | |
Business Solution Provider | Messages are sent through a WhatsApp Business Solution Provider on the WhatsApp Business Platform, not from a personal phone or the WhatsApp Business app. | |
| Bank and card statement uploadStatements | PDF statements | Bank and card PDFs, including password-protected ones. You enter the statement password when asked; it is used to open the file and is not stored. |
CSV and Excel (XLS, XLSX) | Statement downloads from net banking and card portals. Column headers are mapped once per bank and remembered. | |
No bank credentials | Ayush Agro Foods never asks for net banking logins. A read-only Account Aggregator route is offered only once confirmed for your bank, through a regulated Account Aggregator. |
Ayush Agro Foods is not affiliated with the vendors named above. Names are used to describe compatibility.
Data inventory
What is stored, what is discarded, what is never read.
Retention periods are stated in your order form. Data that is not needed is discarded at matching time, not at the end of a retention period.
| Data | Source | Detail | Status |
|---|---|---|---|
| Statement lines that match software | Statement upload | Date, descriptor, amount, currency, INR debited, card or account last four digits | Kept |
| Statement lines that are not software | Statement upload | Travel, food, salaries and other transactions | Discarded after matching |
| Full card numbers | Statement upload | Masked on upload | Never stored |
| Ledger entries for software | Tally Prime, Zoho Books | Vendor, narration, amount, tax, GSTIN | Kept |
| Reimbursed software claims | Expense export | Claimant, merchant, amount, month | Kept; other claims discarded |
| Employee directory | Google Workspace, Microsoft 365, Okta | Name, work email, department, account status | Kept |
| Seat assignment and last sign-in date | Identity provider, vendor admin data | Per person per tool | Kept |
| Activity inside tools, email and files | None | Not requested | Never read |
| Invoices | Finance mailbox, forwarding | Matched invoice emails and their attachments | Kept; non-invoice emails not stored |
| Decisions and approvals | Ayush Agro Foods | Who decided, who approved, when, expected difference | Kept in the audit log |
DPDP Act, 2023
Your company decides. Ayush Agro Foods processes on its behalf.
Seat usage and offboarding involve employee personal data. The roles under the Digital Personal Data Protection Act, 2023 are clear, and so is the limit on what is collected.
Data fiduciary: the employer
Your company decides why and how employee sign-in data is processed: to manage software seats and remove access when people leave.
Processor: Ayush Agro Foods
Ayush Agro Foods processes that data on your behalf, under your instructions and the data processing agreement.
Employee data minimisation
Name, work email, department, seat assignments and last sign-in date per tool. Ayush Agro Foods stores the last sign-in date and seat assignment only, never activity inside a tool. That is a design commitment, not a legal claim.
General information, not legal advice. Processing of employee data for employment purposes is a listed legitimate use under Section 7 of the Act. The DPDP Rules were notified in November 2025 with phased commencement. Privacy questions: privacy@ayushagrofoods.com. Grievances: grievance officer.
Access control and logging
Each role sees what it needs. Every look is logged.
Role-based access keeps department heads to their own tools. Every access, change and export is logged with the user and the time, and the log can be exported for audits.
SAML single sign-on into Ayush Agro Foods is part of the Scale plan.
| Role | Can see and do |
|---|---|
| Finance admin | All tools, spend, renewals, GST view, exports, settings and connections |
| Department head | Their department's tools, seats, cost and renewals only |
| Tool owner | Their tools' seats and renewal decisions, mostly through alerts |
| IT | Seat usage, offboarding sweeps and connections; spend only where finance allows |
| Accountant or CA | Invoice & GST view and exports, read-only |
Export on demand. Deletion on exit.
Export the tool list, seat data, decisions, invoices and audit log at any time as Excel or CSV. When you leave, connections are revoked on our side, and your data is deleted. You can revoke each connection from your own admin consoles at any time too.
Certifications
No certification is claimed until it is held. When an audit is booked, this page will say so, and not before.
Responsible disclosure
Found a vulnerability? Write to security@ayushagrofoods.com with the steps to reproduce it. Our contact details are also published at /.well-known/security.txt.
We do not take legal action against good-faith research. Please do not access other customers' data or degrade the service while testing.
- Integrations, scopes listed
- 12
- Write scopes into your books
- 0
- Card digits ever stored
- 4
- Hosting country: India
- 1
Questions security reviewers ask
Can Ayush Agro Foods move money or change our records?
No. Access to banks and cards is read-only and works from statements at launch. Ledger and directory connections are read-only. Nothing is written into Tally, Zoho Books, Google Workspace, Microsoft 365 or Okta.
How long is our data kept?
Retention periods are stated in your order form. Statement lines that are not software are discarded after matching, whatever the retention period.
Do you hold SOC 2 or ISO 27001?
No certification is claimed until it is held. This page will say what is in progress only once an audit is actually booked.
Who at Ayush Agro Foods can see our data?
Only people who need to, for support you ask for or to run the service, and their access is logged like any other access.
Can we get a data processing agreement?
Yes. The DPA sets out Ayush Agro Foods' role as processor of employee data on your behalf. Ask at the address below or read the DPA page.
Bring your security questionnaire to the demo.
We will walk through the scopes, the data inventory and the audit log with your IT and finance teams.
- Read-only access
- Data hosted in India
- Priced in rupees
- 14-day trial on your data