Last updated: 2026-10-31

This privacy notice explains how Yieldwise Farmtech Private Limited ("we", "us", or "Hyperfiling") processes personal data when you use the Hyperfiling web application, marketing site, or any related service. Yieldwise Farmtech Private Limited is the Data Fiduciary, in the sense of section 2(i) of the Digital Personal Data Protection Act, 2023 (DPDPA), for the account, usage, billing and communications data described below. For personal data in the documents a firm uploads to a workspace, the firm is the Data Fiduciary and we process that data on its behalf as a Data Processor, as the Data Processing Addendum sets out.

1. Categories of personal data we collect

• Account data: name, work email, role (CA / CS / Firm Partner / Other), firm name, password hash.
• Usage data: pages viewed, queries submitted, documents uploaded, timestamps, IP address, user agent, audit log entries.
• Content data: notices, filings, drafts, and other documents that you or your firm choose to upload into a workspace.
• Billing data: business name, GSTIN, billing address, invoice history. Card numbers are processed and held by our payment processor. Hyperfiling does not store them.
• Communications: messages you send through forms, chat, or support channels.
• Records received from YieldWise: where a firm's client is a farmer producer organisation that uses the YieldWise platform, that platform can send the client's records to a Hyperfiling workspace held for that client, which it identifies by the workspace or by the client's PAN or CIN. The records are procurement batches, which name the farmer who supplied the produce and may include the farmer's phone number; grant expenses, which name the vendor paid; statutory due dates; and sales invoices, which may name the buyer and give the buyer's email address and GSTIN. The farmer's name, the vendor's name and the buyer's details are stored in the workspace as content data.

2. Purposes of processing

• Operate the service and answer your queries with cited sources.
• Show a client's records from the YieldWise platform in the workspace held for that client, where that platform sends them.
• Bill the subscription and issue GST-compliant tax invoices.
• Maintain audit logs of authenticated mutations for accountability.
• Detect fraud, abuse, and security incidents.
• Improve product quality through aggregate, de-identified analytics.

3. Lawful basis

Under section 4 of the DPDPA, personal data may be processed only for a lawful purpose for which the Data Principal has given consent, or for certain legitimate uses. Consent must meet the conditions in section 6, and the legitimate uses are those listed in section 7. The Act has no separate ground for performing a contract and no general legitimate-interest ground.

Sections 3 to 17 of the DPDPA, which hold these grounds, the obligations of a Data Fiduciary and the rights of a Data Principal, come into force eighteen months from the publication, in the Gazette of India of 13 November 2025, of the Central Government's commencement notification under section 1(2) of the Act (G.S.R. 843(E)). The one exception among them, section 6(9) on the registration of Consent Managers, comes into force one year from that publication. Section 44(2), which omits section 43A of the Information Technology Act, 2000, comes into force on the same eighteen-month date. The definitions in section 2 are in force now.

For the personal data for which we are the Data Fiduciary, we rely on:

• Your consent for marketing emails, such as our newsletter. You may withdraw it at any time by writing to privacy@hyperfiling.com.
• The legitimate use in section 7(a): processing for the specified purpose for which you have voluntarily provided personal data, such as creating an account, using the service, paying for a subscription or writing to us, unless you tell us that you do not consent to that use.
• The legitimate uses in section 7(d) and 7(e) where a law in force in India obliges us to disclose information to the State or any of its instrumentalities, or where we must comply with a judgment, decree or order.

For personal data in the documents a firm uploads to a workspace, the firm, as the Data Fiduciary, determines the ground on which it is processed.

4. Retention

Account and content data are retained for the life of the workspace. Deleting a workspace removes its records from the database immediately. Copies remain in our backups until those backups are deleted. As a rule, each nightly backup is deleted from our server within 16 days of being made, and the encrypted copy in AWS S3 expires 35 days after it is made and is removed permanently by S3 7 days after that. Copies made by hand before a software deployment, and copies kept for recovery from an incident, are not part of that schedule and may be retained longer. They are held on our server in Mumbai, and some of them also in AWS S3 in the Mumbai region (ap-south-1). We are separately building deletion of the underlying stored files, which is not yet complete, and we would rather say so than imply otherwise. Audit log entries are held in a table that cannot be altered or deleted through the application, so they persist for accountability. Billing records are retained as required by Indian tax law.

5. Recipients and sub-processors

We share personal data with the following recipients, only to the extent required to operate the service. We do not sell personal data.

• Hostinger hosts the server in Mumbai, India, that runs the application and holds the database, uploaded documents and the nightly backups. Hostinger also provides the hyperfiling.com mailboxes, so it receives and stores the email you send us, including privacy, grievance, billing and support requests.
• Amazon Web Services (AWS) provides AWS Bedrock, which generates text when our local model is unavailable, reads the text in uploaded images, and converts research questions and searches into embeddings (section 6), and AWS S3, which holds an encrypted copy of the nightly backups in the Mumbai region (ap-south-1).
• Resend delivers the emails the service sends.
• Razorpay processes subscription payments.
• Vercel hosts this website and serves the pages of the web application.
• Google Fonts supplies the typefaces of the web application. Your browser requests them from Google, which receives your IP address and browser details.
• Plausible Analytics receives details of visits to this website, such as the page viewed and the referring site, to produce aggregate visit statistics.
• The Government of India's open government data platform receives the company names and CINs the service looks up there, such as a name or CIN typed into company search, and returns the company's record.
• The DuckDuckGo and Bing search engines may receive a company name or CIN typed into company search when the government's company data does not find the company (section 6).

6. Where personal data is processed

The application server, the database, uploaded documents and the backups on our server are in Mumbai, India. The encrypted backup copy in AWS S3 is in the Mumbai region (ap-south-1).

Text the service generates with a language model, including research answers, drafts and the analysis of uploaded documents and notices, is generated first by a local language model, Gemma 4 (31B), which runs on computing hardware we operate in Karnataka, India. Our server reaches it over an encrypted SSH tunnel. If that model cannot be reached, times out, returns an error or no answer, or has just failed several times in a row, the request is sent instead to the Claude Sonnet 4.5 model on AWS Bedrock. That request enters AWS in the Mumbai region (ap-south-1), but it uses a global cross-region inference profile, so AWS may process it in another region, inside or outside India.

Text in uploaded images is read by the same model on AWS Bedrock, through the same global inference profile, so an image may be processed outside India. The local model is not used for images. Research questions and searches are converted into embeddings by AWS Bedrock in the Mumbai region (ap-south-1).

A company name or CIN typed into company search is looked up first in our copy of the government's MCA company master data and, if it is not found there, on the Government of India's open government data platform. If neither finds the company, the text typed may be sent to the DuckDuckGo search engine and, if that fails or finds nothing, to Bing, which may process it outside India. The text of a research question is not sent to any search engine.

Resend, Vercel, Google, Plausible Analytics and Hostinger's email service may process the data they receive outside India.

Section 16 of the Digital Personal Data Protection Act, 2023 empowers the Central Government to restrict, by notification, the transfer of personal data to a country or territory outside India that it notifies. Rule 15 of the Digital Personal Data Protection Rules, 2025 permits personal data to be transferred outside India, subject to any requirements the Central Government specifies, by general or special order, for making that data available to a foreign State or to a person or entity under the control of, or an agency of, such a State. Section 16 and rule 15 come into force eighteen months from the publication, in the Gazette of India of 13 November 2025, of the commencement notification (G.S.R. 843(E)) and of the Rules (G.S.R. 846(E)).

7. Your rights

The rights of a Data Principal under sections 11 to 14 of the Digital Personal Data Protection Act, 2023 come into force eighteen months from the publication, in the Gazette of India of 13 November 2025, of the Central Government's commencement notification under section 1(2) of the Act (G.S.R. 843(E)). We do not wait for that date. As a matter of contract, you may ask us today to:

• Access the personal data we hold about you.
• Correct or update inaccurate personal data.
• Erase your personal data, subject to legal retention obligations.
• Raise a grievance with our Grievance Officer (contact below).
• Nominate an individual to exercise these rights on your behalf in the event of your death or incapacity.

8. How to exercise your rights

Email privacy@hyperfiling.com from the email associated with your account. Identify the right you wish to exercise. We will respond within thirty days. We may need to verify your identity before acting on the request.

9. Grievance Officer

The Grievance Officer for Yieldwise Farmtech Private Limited is reachable at grievance@hyperfiling.com. Designation: Grievance Officer, Hyperfiling.

10. MCA Sync Companion browser extension

The MCA Sync Companion is an optional Chrome extension that copies company details from an MCA21 V3 page you are viewing into the Hyperfiling client workspace for that company. This section describes version 1.0.8. The extension reads only pages under mca.gov.in, where it adds a small "Sync with Hyperfiling" button to the corner of the page. It reads the page in front of you only when you click that button, which shows you what it read and sends nothing; when you open its popup; and when you press the popup's "Ingest company to Hyperfiling" or "Copy diagnostic report" button. While a Fetch everything from MCA that you started is running, it also reads each page that loads in the tab the fetch opened: when the page loads, each time it changes, and when you press "Sync this page now" on the panel it shows there, for as long as that page stays open. If an MCA tab was opened before the extension was installed or updated, the popup loads the extension's own page-reading script into that tab, and no other code.

• What it reads: from each page, the CIN or LLPIN of the company or LLP the records belong to, its name where the page gives one, and, apart from what the diagnostic report item describes, only the items below. A company or LLP name is sent only where it ends in Limited, Ltd or LLP. The company name in a row of a table is also read, to decide whose the row is, and the popup shows you the one in a filing's row when it asks you about that filing. Nothing is read from the extension's own button or from the panel it shows during a Fetch everything from MCA: neither is treated as part of the page. Application History and the Document Details list of View Public Documents, which the extension recognises by their address or the page's structure, each have a reader of their own. On the search and category pages of View Public Documents it reads nothing to send. Every other page under mca.gov.in is read by one general reader, written for Company or LLP Master Data, View Signatory Details, View Index of Charges and the SRN filing history of one company: it reads the items listed below for those four pages from any such page, wherever a table or field is labelled as they label it. To decide which company the page and each row of those tables belong to, as the item "When it sends, and where" describes, it also reads the CINs, LLPINs and other company identifiers in the page's text, whether shown or not, in the boxes on it and the text they show while empty, in the text shown in place of its images, and in quoted text its style sheets add; the company names and the words naming another entity in the text the page shows, in that quoted text and in text the page marks to be hidden from screen readers; and the labels of its fields; of these it sends only the page's own CIN or LLPIN and name and, for a filing whose row shows another company's CIN or LLPIN, that CIN or LLPIN and the name its rows give that company, where every row that gives one gives the same.
  • Company or LLP Master Data: the company or LLP name and its CIN or LLPIN and, where the page labels them, its date of incorporation, registered office address, status, class, category, ROC, and authorised and paid-up capital. On a company's master data page it also reads the date of its last annual general meeting, the date of its latest balance sheet and its e-mail address, where the page labels them, and the same values from an LLP's master data page where it labels them. A date, an amount or an e-mail address that the extension cannot read as one is left out, and an e-mail address is sent in lower case.
  • View Signatory Details: each signatory's DIN or DPIN, full name, designation and appointment date, and the cessation date, DIR-3 KYC status, whether a digital signature certificate (DSC) is registered and the DSC's expiry date where the page shows them. These are the names and identification numbers of the company's directors or the LLP's designated partners.
  • View Index of Charges: each charge's ID, charge holder, amount, creation, modification and satisfaction dates, and status.
  • The SRN filing history of one company: each filing's SRN, form, description, filing date and status, the CIN, LLPIN or other identification number and the company name where its row shows them, and the web address of a link in its row to a document or challan, where there is one. The extension does not open that link.
  • Application History: for the tab shown, each application's form, CIN or LLPIN, company or LLP name, SRN, status and Modification/Submission/Resubmission Date. It does not read the Filed by column or the Payment Status tab. It reads applications only from a table in the one shape the item "When it sends, and where" describes, with one column headed as the row's own identification number; from a table of applications in any other shape it sends none, and the popup says so when it reads no table on the page. An application that is not identified by a CIN or LLPIN, or that cannot be recorded as the page shows it (for example one not yet submitted, with no SRN), is listed in the popup and not sent. So is an application whose company is not clear: one whose identification cell shows its number beside a word such as holding, subsidiary, of or formerly, shows an identifier that does not stand on its own, or shows more than one identifier; and one whose other cells show a company identifier. A company is sent with the name its applications give only where every one of them that gives a name gives the same.
  • The Document Details list of View Public Documents: the company's CIN or LLPIN, from the one field the page shows that is labelled as its own CIN or LLPIN, as the item "When it sends, and where" describes for such fields, and otherwise the one MCA's page keeps in that browser tab's session; the company name in the page heading or, failing that, in that session; the document category you chose, kept in that session, for a row that does not show one, where you chose a single category; and, for each document listed, its name, form, file type and date of filing, and its category, year and SRN where the list shows them in a column that is shown. It does not read the list's hidden columns, and it reads the list only from a table in the one shape that item describes. The list is not sent when the page and the session give different CINs or LLPINs; when the fields the page labels as its CIN or LLPIN do not give exactly one; when the page shows any other company identifier, in its text, shown or not, in a box, or anywhere else the item "When it sends, and where" describes, within the limits set out there; when the heading, a field the page labels as the company name, or a company name in any text the page shows, other than a charge holder's name where that item allows one, names a company other than the one that session keeps; or when that session keeps no company name and the page names one in any of these, as that item describes company names. It reads the list, not the documents.
• When it sends, and where: only when you press a sync button in the popup, or during a Fetch everything from MCA that you started, as described below. The popup's sync buttons are "Ingest company to Hyperfiling" and, on a page that lists several companies such as Application History, the button that syncs the clients it matched. It then sends what it read from that page over HTTPS to the Hyperfiling API, naming the page as its reader identified it. The general reader names a page Company or LLP Master Data when it read a master data value there, otherwise after the kind of table it read there (signatories, charges or SRN filings), as a company page when it read more than one kind, and not at all when it read none; the other two readers name their own page; and a sync of several companies from any page other than Application History names no page. Hyperfiling records the named page with each signatory or charge it adds and, for the client, when each named page was last synced. On a page about one company, the records go to the client workspace you select, which must be recorded with that company's CIN or LLPIN or have none recorded, in which case the workspace takes the page's. On Application History, each company's applications go only to the workspace recorded with its CIN or LLPIN, and a company with no such workspace is handled as the item on clients added from Application History describes. The extension accepts one narrow shape of page and of table, set out below: it sends nothing about a company from a page that does not have that shape, and no row from a table that does not; the popup lists what it did not send, and why. It reads values only from what it takes your browser to show: nothing from an element that is marked hidden or hidden from screen readers, that has one of the class names pages use to hide an element or show it to screen readers only (hidden, hide, d-none, sr-only, visually-hidden, visuallyhidden or screen-reader-text), whether or not the page's styles hide it, or that is styled not to display, invisible, with an opacity of zero, with text of size zero, or clipped to nothing by a clip of no size or a clip-path inset of 50% or 100%, or inside such an element, and nothing from an element that has no box of any size on the page or whose box lies wholly above or to the left of the page, apart from what an element styled to show its content in place of a box of its own contains. It does not detect every way a page can keep text out of sight: text made transparent by its colour or a filter, clipped by any other clip-path or by an element around it that hides what overflows it, indented out of its box, or placed below or to the right of the page is read as shown. Text that is not shown is looked at only to refuse a page, a list or a table, for the company identifiers described next, for the words and company names described next where the page marks them to be hidden from screen readers in an element that is shown, and for whether a table hides text in a cell; to tell whether a table it does not read is one of signatories, charges, SRN filings, applications or documents, so as to list it as not read; and for the structure the diagnostic report item describes. On a page the general reader reads, the page's company is the one whose CIN or LLPIN is in the one field the page shows, which you cannot type in, that is labelled as its own CIN or LLPIN and holds that CIN or LLPIN alone, and only when all of the following also hold. The page shows no other company identifier in the text of its body, shown or not, also read with the text of elements shown in line run together; in a box on it or the text a box shows while empty; in the text shown in place of an image; or in quoted text its style sheets add before or after an element. The extension reads these only where it can reach them: it does not see text in a frame from another site, in a part of the page closed to other scripts (a closed shadow root) or placed outside the page's body, the label a list option shows in place of its text, or text a style sheet adds from an attribute, a counter or a list marker, and of each style rule it reads only the first quoted text, from the style sheets it is allowed to read. A value under a label or column heading that names a registration number counts as one, also where the number follows its label in the same element, except a labelled registration number of six digits that are the last six digits of the page's CIN; and a label or heading that names a registration number counts as one whatever is under it, unless the extension reads its value as a labelled field's or as the value of the box it labels. No text the page shows, whether a heading, caption, legend, card or panel header, title row, bold text, table heading, paragraph, list, label, link, the value a box shows or the option chosen in a list, no quoted text its style sheets add, and no text the page marks to be hidden from screen readers in an element that is shown, names another entity with one of the words and phrases the extension looks for, such as holding, subsidiary, associate, parent, group company, joint venture, amalgamation, transferor, transferee, formerly, previous name, foreign company, other company or related party (other wording, such as "another company", "merged with" or "sister concern", is not recognised), other than: "Subsidiary of Foreign Company" as the value of a field the page labels as the company's category, sub-category or class; the company's own name, as the field the page labels as its name gives it; the text of the rows the extension reads from a table of signatories, charges or SRN filings, apart from any heading, header cell or bold text in them and a row that shows text in one cell only; and the label "Previous firm/ company details" (or with ", if applicable"), which an LLP's master data shows, where the value beside it is blank or only dashes. And no such text names a company, as a name ending in Limited, Ltd, LLP, LLC, GmbH, Inc, Incorporated, Corporation, Corp, PLC, Bank, Pvt, Pte, Pty or Bhd does, or a firm, as a name ending in "& Co" or "and Company" does, other than the company's own name, as the field the page labels as its name gives it, or the charge holder's name in a cell of one line in the charge-holder column of a table of charges the extension reads. A name ending in any other word, such as AG, SA or BV, a name whose last word is followed by a number, as in a year, and a name with a comma before its last word are not recognised as a company's. The extension reads these words and names as they are written: it removes no invisible character, such as a soft hyphen, and does not read full-width or other compatibility forms as plain letters, so a word or a name written with one is not recognised. A field counts only where its label names the company's own CIN, LLPIN or identification number and nothing else: not where the label also names an FCRN, an FLLPIN, a foreign company, a registration number or another entity, as "CIN/FCRN/LLPIN/FLLPIN" and "Holding Company CIN" do, or has any other word; and not for a box or text you can type in, such as a search box, a field inside a table row of three, or more than four, cells, or of four cells under a row of column headings, or a field in a table with a cell that spans columns or rows. A CIN or LLPIN the page shows anywhere else is never the page's company. Where a field labelled as the page's holds two identifiers, an identifier with other words, or a number that is not a CIN or LLPIN, where two such fields differ, where two such fields give the same one, or where one value is labelled both as the page's and as another entity's, the page has no company of its own. Before it looks for an identifier, the extension removes the invisible characters it knows, such as zero-width spaces, joiners and soft hyphens (not every invisible character: tag characters, for example, are kept), reads compatibility forms of letters and digits, such as full-width ones, as those letters and digits, and ignores case. It does not read letters of other alphabets that look like Latin letters as Latin letters. It finds a CIN with spaces, hyphens, dashes, dots, slashes, underscores or bars between any of its characters, also where it runs into other letters or digits; an LLPIN, FLLPIN or FCRN with spaces, hyphens or dashes between any of its characters, where no letter or digit comes before it and no digit after it; and an LLPIN or FLLPIN written with a hyphen or dash also where other letters come before it, unless the word before the dash is a month. Three letters that are a month make a date, not an LLPIN. From a page with no company of its own nothing is sent but the filings whose rows show a company's CIN or LLPIN, as described below. The page's company is given the page's master data and its name, each read only from a field the page labels as such that is not a box you can type in, and never from a heading; and it is given the page's signatories and charges, except the rows described below. The rows of a table are read only where the table has one row of column headings, as its first row; no cell that spans columns or rows; no row of one cell, and no row under the headings without a number in it; no table inside it or around it; no hidden cell and no hidden text in a cell, apart from columns whose heading and every cell are hidden at the end of the table, and, in a table whose headings hide nothing, cells hidden in a row after every column the extension reads, as MCA's Document Details and Application History lists have; as many cells in every row as headings; and at most one column of company identifiers, headed only as the row's own CIN, LLPIN or identification number, with no heading that names another entity or a former identifier. A table whose only row under its headings is one cell across the table, with no number or identifier in it, is read as a table with no rows. From a table in any other shape no row is sent or offered, and the popup lists the table as not read where one of its rows is headed as a table of signatories, charges or SRN filings. An SRN filing is never attributed to a company by guesswork: it is given to a company only when its row shows that company's CIN or LLPIN alone in a column headed as the row's own CIN, LLPIN or identification number, with or without a label such as "CIN:", or, in a table with no such column, alone or in brackets after the name in the row's company-name column, and no other cell of its row shows a company identifier. A code of that form that is part of a name, such as "ZEN1947" in "ZEN1947 HERITAGE HOTELS LIMITED", is not the row's identifier. The page's company is given each filing whose row shows its CIN or LLPIN in this way. Another company is given a filing only when its row shows that company's CIN or LLPIN in this way, and the filing goes only to the workspace recorded with that CIN or LLPIN; with no such workspace, it is not sent. A filing whose row shows no company identifier at all is not sent on its own. Where the page has a company of its own and, on a page that lists several companies, that company has a client workspace, the popup says how many such filings the page shows, names the page's company, where the page gives its name, and its CIN or LLPIN, and asks whether to add them to the client workspace for that company, with a box that is not ticked. They are sent to that workspace only if you tick the box, and the sync's report then says how many were sent because you confirmed them. Otherwise, or if you leave the box unticked, the popup lists them as not sent. A filing identified by an FCRN or FLLPIN, the identifier of a foreign company or LLP, or by another number that is not a CIN or LLPIN, such as any other number in its identifier column, or a labelled number, a code of letters and digits or a number of five or more digits in brackets after the name, is listed as not identified by a CIN or LLPIN and is never offered or sent. A filing is also listed, with the reason, and never sent: where its identifier column shows its number beside a word such as holding, subsidiary, parent, of or formerly; where it shows a CIN, LLPIN, FCRN or FLLPIN, or a code of that form, other than alone as described above, for example as part of a name or with other words; and where its row shows more than one identifier, or a company identifier in any other cell, for example in a description. A signatory or charge row is not given to the page's company, and is listed in the popup as not sent, where the row shows another company's CIN or LLPIN, is listed for one of the reasons above for which a filing is listed, or names a company in a company-name column without showing a CIN or LLPIN. The extension refuses any server address that is not an https address on hyperfiling.com. Opening the popup also asks Hyperfiling for the list of your client workspaces; that request carries your sign-in and nothing from the MCA page.
• What a sync changes in Hyperfiling: it adds the records to the client's registers, or updates those already there. When it carries the company's name, Hyperfiling also fills in the client's legal name and, where the page gave them, its registered office address, date of incorporation, company status, authorised and paid-up capital, Registrar of Companies as MCA names it and e-mail address, where the field is empty, holds a placeholder, or has a value read from MCA or another register or worked out from the client's identifiers, except that an e-mail address removed from the client's profile by hand is not filled in again. Where the Registrar of Companies on the client's profile is the one the page names, and MCA's published list of Regional Directors and ROC offices gives it as exactly one office, Hyperfiling fills in that office's address, its Regional Director and its Regional Directorate from that list in the same way. When a sync carries the Registrar of Companies, Hyperfiling removes from the client's profile any office, Regional Director or Regional Directorate taken from that list that the list does not give for the Registrar of Companies the profile then records, and returns a note saying so. Any other value, such as one entered by hand, is kept, and where MCA shows something else, or an e-mail address removed by hand is not filled in again, Hyperfiling returns a note saying so. The date of the last annual general meeting is stored as the client's last AGM date only where no AGM date is recorded for the client, or the one recorded was stored by an earlier sync and has not been changed since, and the date falls between 1 April and 30 September; otherwise it is not written to the client's profile, and where it differs from the AGM date recorded, falls outside those months, or the AGM date was removed from the client's profile by hand, Hyperfiling returns a note giving MCA's date. The date of the latest balance sheet is not written to the client's profile. Either date, where it cannot be read as a date or is later than the day of the sync, and an e-mail address that is not one or is at a domain reserved for examples, are not stored; an amount of capital that is not a whole number of rupees is not written to the client's profile; and Hyperfiling returns a note for each. Hyperfiling's scheduled e-mails are not sent to an e-mail address only a sync recorded, until it is changed on the client's profile; e-mail that you or a colleague choose to send from Hyperfiling to the client, such as a compliance reminder, goes to the address on the client's profile, whatever its source. A client with no CIN or LLPIN recorded takes the page's, unless another client of your firm already has that CIN or LLPIN recorded: then nothing from the sync is written, and Hyperfiling says so without naming that client. Hyperfiling records, against each client field that a sync fills in from the page, including the last AGM date, that the value was read from MCA21 by the extension, with the page it was read from, where the extension named one, and the time of the sync, and against the ROC office, Regional Director and Regional Directorate that they were taken from MCA's published list, with the date that list was read. It records the same against a field that already holds the value the page or the list gives, unless that value is recorded as entered by hand, or is an e-mail address or a last AGM date with no recorded source, which stays recorded as it was entered. A client added from Application History, as the next item describes, also has recorded against its name, where the extension read one, and its CIN or LLPIN that they were read from Application History by the extension, with the time the extension added it; and against its type of entity, where its CIN or LLPIN indicates one, that it was worked out from the CIN or LLPIN. Each sync, except one of a View Public Documents list, also stores a copy of what it read, including the class, category, ROC and capital where the page gave them, and the date of the last annual general meeting, the date of the latest balance sheet and the e-mail address, apart from any of those three that is not stored as described above, and each sync adds an entry to the audit log with the CIN or LLPIN and the number of records synced.
• Clients added from Application History: when you press the sync button on Application History, the extension first sends Hyperfiling the CIN or LLPIN of each company on the page that matches none of your client workspaces, to ask which of them are already clients. A company that is already a client of your firm but is not assigned to you is not added again, and one that is already your client is synced to that client. Each of the others is added as a client in Hyperfiling with its CIN or LLPIN; with its name as the page shows it where the extension read one, and otherwise named by its CIN or LLPIN; with the type of entity its CIN or LLPIN indicates, where it indicates one; with the Companies Act as its regulatory category; and with a record that the extension added it from Application History, by whom and when. Its applications are then synced to it. A company that is not added is reported in the popup's summary, and its applications are not sent. The summary lists each client added with a Remove button, which asks Hyperfiling to remove that client; Hyperfiling does so only within 24 hours of the client being added, and only while it holds no document, task, invoice, notice or draft.
• Fetch everything from MCA: when you press this button in the popup, the extension asks Hyperfiling, with your sign-in and nothing from the MCA page, for your clients, and lists for you to choose from each client that you own or may edit, that has a CIN or LLPIN, that is not archived, closed, inactive or dormant, and for which no Company or LLP Master Data page has been synced and no director or signatory is recorded. The summary of clients just added from Application History has a button that starts the same fetch for them. When you start it, the extension opens MCA's Company or LLP Master Data page in a new tab, and then opens that page again in the same tab for each further client you chose, one after another; if that tab has been closed, it opens a new one. A panel on the page names the client and its CIN or LLPIN, with a button that copies the CIN or LLPIN to your clipboard. You sign in to MCA if it asks, and enter the CIN or LLPIN and MCA's captcha yourself. The panel itself, which shows the client's CIN or LLPIN, is never read as part of the page. When the page itself shows that client's CIN or LLPIN as the page's company, by the rule described above, together with its name or a table of signatories or charges, the extension sends what it read from the page for that client, as described above and named as the general reader identified it, to that client's workspace, and opens the page for the next client, if there is one. Of the page's SRN filings, it sends only those whose row shows the client's CIN or LLPIN. It never sends a filing whose row shows no company identifier, and does not ask about one; once the page is sent the fetch's message for that client says how many filings, signatory rows and charge rows were not sent, and why, and how many of the page's tables were not read. The panel's "Sync this page now" button sends the page at once, without waiting for its name or such a table, but only when the page shows the client's CIN or LLPIN as the page's company. A page that shows no CIN or LLPIN, or another company's, is not sent. If Hyperfiling refuses your sign-in, the fetch stops and asks you to sign in to Hyperfiling. You can skip a client or stop the fetch from the panel or the popup. The extension does not fill in or submit anything on MCA.
• Your Hyperfiling session: it reads one cookie, your Hyperfiling sign-in cookie on hyperfiling.com, and sends it only to the Hyperfiling API, so that you do not have to paste a token. It reads no cookie on any other site, and it creates, changes or deletes none.
• What it keeps on your computer: in the extension's own storage in your browser, the address of the Hyperfiling API it sends to and, if you entered one by hand, a sign-in token, once you save them under its Advanced settings; a record of the most recent failure, for the diagnostic report; and, while a Fetch everything from MCA runs and until you clear its summary or start another, a record of that fetch. The failure record holds the error code, the step at which the failure happened and, for an error returned by the Hyperfiling API, the HTTP status, the API's error code and the names of the fields it named. It holds no error message and no CIN, name or other value from the page. A later failure replaces it. A saved token that Hyperfiling refuses is deleted, whichever of the extension's requests it refused. The fetch record holds the list of clients it is fetching (each client's name, CIN or LLPIN and Hyperfiling workspace), the address of the Hyperfiling API, when the fetch started and ended, which tab it opened, and how far it has got: for each client, whether it is waiting, open in that tab, synced or skipped, and the last message the fetch showed about it. That message can include an error message from Hyperfiling, or the CIN or LLPIN of another company whose page was open in the fetch's tab. It can also say how many of the page's SRN filings, signatory rows and charge rows were not sent, and why, and how many of its tables were not read, without naming them. Beyond these records, the extension keeps no page content, no company data and no record of the pages you visit.
• What it does not do: it does not sign in to the MCA portal, fill in or submit its forms, enter or solve a captcha, make a payment, or open or download a document. Apart from opening MCA's Company or LLP Master Data page in a tab during a Fetch everything from MCA, as a link would, it sends no request of its own to the MCA portal. Any sign-in, captcha or payment that MCA asks for, you complete yourself.
• Diagnostic report: the popup's "Copy diagnostic report" button copies a report to your clipboard and shows it in the popup, for you to send to Hyperfiling support if you choose. The extension does not send it. To keep values out of the report, it reads the page as it does for a sync and also reads the company name, CIN or LLPIN, State and date of incorporation that View Public Documents keeps in that browser tab's session; none of these goes into the report. The report holds structure only: the extension version; the failure record described above; the page's address with numbers and identifiers removed; the hosts of its frames; the id and class names, headings, visibility, row counts and layout of its tables, the layout saying whether the extension reads rows from the table and, if not, which part of the one shape it lacks, and the labels of its fields, with every word that is not one of the portal's own label words replaced or left out; how many records the extension read, and the reasons it did not read some rows or tables, did not send some SRN filings, signatory rows or charge rows, or could not identify the company; and, if the page could not be read, the reason Chrome gave. It holds no CIN, LLPIN, name, amount, date or document name.

Records the extension syncs become content data in that workspace, and a client it adds from Application History is a client workspace like one you add yourself. They are retained, shared and deleted as described in sections 4 and 5, like anything else you add to the workspace. We do not use them for any other purpose, and we do not sell them.

11. Updates

We may update this notice. Material changes are announced in-product and on this page. The "last updated" date at the top reflects the most recent change.