Privacy Policy
Last updated: 6 November 2026
This Privacy Policy explains how 18th Digitech Private Limited (“18th Digitech”, “we”, “us”) collects, uses, stores and protects personal data in connection with MetryFlow (the “Service”), a platform that connects an organization’s marketing, e-commerce, accounting and ERP accounts to its own AI assistant. It is written to meet India’s Digital Personal Data Protection Act, 2023 (“DPDP Act”) and the rules made under it, and other applicable data-protection laws.
1. Who we are and our role
MetryFlow is operated by 18th Digitech Private Limited, a company incorporated in India. For any privacy question, request or complaint, contact us at support@metryflow.ai.
- For your own account data (for example your name, email and login details), we decide why and how it is processed, so we are the Data Fiduciary.
- For data inside the accounts your organization connects (for example orders in Shopify or contacts in Xero), your organization is the Data Fiduciary and we process that data only on its instructions, as its Data Processor. Our Data Processing Addendum covers this.
2. The personal data we process
- Account data. Your email address, name, and optionally phone number and time zone; a securely hashed password; two-factor authentication settings (stored encrypted); your organization and role.
- Business and billing details. Your organization’s legal name, address, tax and registration numbers (such as GSTIN or PAN), billing contact name, email and phone, invoice copy recipients, and invoices we issue.
- Access requests. If you ask for access through our website: your name, work email, company, role, team size and the use case you describe.
- Connection credentials and identity. When you connect a third-party account (for example Google Analytics 4, Google Ads, Google Search Console, Google Merchant Center, Google Business Profile, Meta Ads, Shopify, Magento, BigCommerce, Ahrefs, Microsoft Clarity, Prerender, Xero or MoEngage), we store its OAuth tokens or API credentials encrypted at rest, and the name or email of the account that was connected. We never display credentials back to you.
- Connection settings. Non-secret identifiers such as a property ID, ad-account ID, site URL, merchant ID or shop domain.
- Retrieved data (pass-through). When your AI assistant asks a question, the Service fetches the relevant data live from the connected account and returns it to your assistant. This data is not stored by us. Most answers are totals and trends. Where a connected account holds personal details of your customers, contacts or employees (for example the name, email, phone number or address on an order, a Xero contact or payroll record, or a reviewer’s name), those details are masked by default before they leave MetryFlow: names become a non-reversible label, emails and phone numbers are partly hidden, and street addresses, birth dates, bank and tax ids and free-text notes are removed. We show them in full only when your organization asks us to switch masking off. The only stored copies are small aggregated summaries for Google Merchant Center and Microsoft Clarity, which contain no personal data.
- Reports and dashboards you create. Their settings, the instructions you type, the email addresses you choose as report recipients, a summary of any reference file you upload, and delivery history. Report files themselves are emailed and not kept by us.
- Activity logs. For each request made through the Service: the tool, connector, connection, time, status, duration and number of rows returned, a short description of the request (for example the question or search terms typed), and any error message. Email addresses and phone numbers are removed from these before they are stored. We also log security-relevant actions such as sign-ins and administrative changes.
- Website. We use only an essential sign-in cookie and do not use advertising or analytics trackers. All fonts and files are served from our own servers, so your browser does not contact any third party when you visit.
3. Why we use it
- To provide the Service: create and secure your account, connect your sources, and return the data your AI assistant asks for.
- To run optional features you turn on, such as dashboards and scheduled reports.
- To keep the Service secure and reliable: enforce isolation between organizations, prevent abuse, investigate errors and incidents.
- To respond to access requests, onboard your organization, issue invoices and keep records required by law.
- To communicate with you about your account and material changes to the Service.
We process your data on the basis of the consent and information you provide when you request access, create an account or connect a source, and where the law otherwise permits. We do not sell personal data, do not use it for advertising, and do not use data from your connected accounts to train any AI model.
4. Google and Meta data
MetryFlow’s use and transfer of information received from Google APIs adhere to the Google API Services User Data Policy, including the Limited Use requirements. Specifically, data obtained from Google APIs is used only to provide or improve user-facing features that are prominent in the Service, is not transferred or sold for advertising or other purposes, is not used to train generalized artificial-intelligence or machine-learning models, and is only accessed by humans in the limited cases where you explicitly consent, where required for security or to comply with applicable law, or where the data is aggregated and anonymized.
Meta (Facebook) data. When you connect Meta Ads with Facebook Login, we request only the ads_read permission. We use it to list the ad accounts you can access and to read their performance insights (such as spend, impressions, clicks and conversions) when you view a dashboard or ask your AI assistant. We never create, edit or delete ads, we do not sell or share this data for advertising, and we use it only to provide the Service to you, in line with Meta’s Platform Terms.
5. AI processing
Your AI assistant. MetryFlow connects to the AI assistant your organization chooses (for example Anthropic’s Claude, OpenAI’s ChatGPT or Microsoft Copilot) through the Model Context Protocol. When you ask your assistant a question, your request and the retrieved data are exchanged with that assistant to produce the answer. Your use of the assistant is governed by your own agreement with that provider.
Our own AI features. Some features call Anthropic’s API (Claude) from our servers. Exactly what is sent:
- Choosing the right fields for a question: the text of your request and the names and descriptions of the available fields. No data values.
- Designing a dashboard or report: your instructions, the available field names and the current design. If you upload a reference file, its text or sample rows are sent so the design can match it.
- Written insights on a scheduled report, if you turn them on: the report’s computed tables, up to 15 rows each. If a report is broken down by a person (for example by customer or contact name), those names are masked first unless your organization has asked us to switch masking off.
Anthropic processes this data only to return the response and does not use it to train its models. This processing takes place outside India (see section 9).
6. Who we share it with
We share personal data only with the service providers below, each bound to protect it and use it only to provide their service to us:
| Provider | What they do |
|---|---|
| Cloud hosting provider (India) | Runs our servers, database and backups. |
| Anthropic, PBC (United States) | AI processing for the features in section 5. |
| Google LLC (Google Workspace) | Sends invitations, password resets, scheduled reports and invoices from support@metryflow.ai. |
The AI assistant you connect, and the platforms you connect (Google, Meta, Shopify, Xero and others), process data under your own agreements with them. We may also disclose data where required by law or a lawful order.
7. Security
We apply reasonable security safeguards, including: encryption in transit (TLS); encryption of stored credentials and secrets at rest (AES-256-GCM) with key rotation; database-level isolation (row-level security) so one organization can never read another’s data; role-based and per-member access controls; strong password hashing; optional two-factor authentication; immediate session revocation; brute-force rate limiting; activity and audit logging; regular backups; browser security headers; and read-only connectors that can retrieve but never change your connected accounts. No system is completely secure, but we work continuously to protect your data. If a breach affects your personal data, we will inform you and the authorities as the law requires.
8. How long we keep it, and deletion
| Data | How long we keep it |
|---|---|
| Account data | While your account is active. Deleted when your account or organization is deleted. |
| Connection credentials | Until you disconnect the source or your organization is deleted. |
| Retrieved data | Not stored. Passed to your AI assistant and discarded. |
| Activity log | Request descriptions and error text: 90 days. The rest of the log (tool, time, status, no personal data): 1 year, as the DPDP rules require. Daily totals are kept while your account is active. |
| Reports and dashboards | Until you delete them or your organization is deleted. Report delivery history: 1 year. |
| Access requests | 1 year, or earlier on request. We record when you agreed to this notice. |
| Privacy requests | 3 years after we close them, as a record that we responded. |
| Password-reset requests | 90 days. Expired one-time links are deleted within 7 days. |
| Server logs (including IP addresses) | 180 days, in India, for security and as the CERT-In rules require. |
| Business details and invoices | As long as Indian tax and accounting laws require. |
| Backups | A short rolling period (currently 7 days), then overwritten. |
How to delete your data
- Remove a connected login. Sign in to MetryFlow, open the connector (for example Meta Ads or Google Analytics 4), and click Delete next to the connected account. Choose to delete its connections too. We immediately delete the stored access token and those connections, and for Google we also revoke our access at Google.
- Remove MetryFlow from Facebook. In Facebook, go to Settings & privacy → Settings → Business integrations, select MetryFlow, and click Remove. This stops any further access from Meta’s side.
- Delete everything. Email support@metryflow.ai from your account’s email address and ask us to delete your account. We delete your account, organization, connections and stored tokens within 30 days and confirm by email. Copies in backups are overwritten within the backup period above.
9. Where your data is stored
MetryFlow is hosted in India: our servers and database are located in India. Some processing takes place outside India: by Anthropic in the United States for the AI features in section 5, by Google when it delivers our emails, and by the AI assistant provider your organization chooses. These transfers are made as permitted under section 16 of the DPDP Act and with appropriate safeguards.
10. Your rights
Under the DPDP Act and other applicable laws, you can:
- ask for a summary of the personal data we hold about you and who we have shared it with;
- ask us to correct, complete, update or delete your personal data;
- withdraw your consent at any time (this does not affect processing already done, and some features may stop working);
- nominate another person to exercise these rights for you in case of death or incapacity;
- raise a complaint with us about how your data is handled.
If you have an account, open your Profile page and go to Your privacy: you can download your personal data straight away and make any of these requests there. You can also email support@metryflow.ai from the email address linked to your account. We will respond within 30 days. If you are not satisfied with our response, you can complain to the Data Protection Board of India.
If your request concerns data inside an organization’s connected accounts (for example you are a customer of a store that uses MetryFlow), please contact that organization. If you contact us, we will pass your request to them and help them respond.
11. Children
The Service is meant for businesses and is not directed to anyone under 18. We do not knowingly collect account data from children.
12. Changes
We may update this Policy from time to time. Material changes will be reflected by the “Last updated” date above and, where appropriate, communicated to you by email.
13. Contact
18th Digitech Private Limited - support@metryflow.ai.