01Introduction and scope
1.1This Privacy Policy explains how Vaylor Labs Private Limited (“Vaylor”, “we”, “us” or “our”), a company incorporated under the Companies Act, 2013 (India) (CIN U62011KA2026PTC227103) with its registered office at No 32/2, 34/1, 11th Floor, Innov8 Prestige Tech, Gunjur, Bangalore North, Bangalore 560087, Karnataka, India, collects, uses, discloses, retains and protects personal information.
1.2What this Privacy Policy covers. It covers: (a) “Website Data”, being personal information we collect through vaylorlabs.com and any other website, portal or web page that we operate (the “Sites”), and in our dealings with prospective customers, go-to-market partners, vendors and other business contacts; and (b) “Customer Data”, being personal information that we process for our business customers, including information that a customer’s authorised users or the third-party systems it connects send to us, when we build, host and operate software, AI systems, connectors, workflows and reports for them (the “Services”), including any application of ours that connects to a third-party platform such as Intuit QuickBooks Online. Section 2 explains our different roles for each.
1.3Customers. Our Services are made for businesses, not consumers. We contract with companies located in the United States, India or any other country (each a “Customer”). The written terms between us and a Customer, which may include a master services agreement, an order form, our End User Licence Agreement and, if both parties sign one, a data processing addendum, are the “Customer Agreement”. If a Customer Agreement contains specific terms about Customer Data, those terms prevail over this Privacy Policy for that Customer Data. This Privacy Policy does not replace the notices that a Customer must give to its own workforce, suppliers and customers (see Sections 2.3 and 12).
1.4Notice at collection. For Website Data, this Privacy Policy is also our notice at collection. Sections 3, 4, 7 and 9 set out the categories of personal information we collect, why we collect them, to whom we disclose them and how long we keep them, and Section 11 sets out your choices, including how to make a request and the rights of individuals in India.
1.5Our Sites and Services are intended for use in the United States, India and other countries where we make them available, by persons aged 18 or older acting for a business. Section 14 explains how we treat other users.
1.6By using the Sites you acknowledge that you have read this Privacy Policy. If you do not agree with it, please do not use the Sites.
1.7Where to find what applies to you. Sections 1 to 10 and 12 to 15 apply to everyone. To make a request about your personal information, see Section 11.2. If you are in India, your rights are in Section 11.3. If your information is held in a Customer’s system, please see Sections 2.3 and 11.1.
02Our roles: who decides what
2.1Our role depends on the kind of information, as set out below.
| Information | Our role | Who decides why and how it is used |
|---|---|---|
| Website Data (Sites, enquiries, business contacts, partner contacts) | Business / controller (Data Fiduciary under the DPDP Act, defined in Section 2.2) | Vaylor |
| Customer Data (data processed to build, run and support a Customer’s system) | Service provider / contractor / processor (Data Processor under the DPDP Act) | The Customer, through the Customer Agreement and its documented instructions |
| Account and Authorised User data (log-ins, roles, usage logs for a Customer’s system) | Business / controller for security and account administration; service provider for the rest | Vaylor for security, billing and account administration; the Customer otherwise |
2.2Customer Data. For Customer Data we act only on the Customer’s documented instructions, as a “service provider”, “contractor” or “processor” under applicable US state privacy laws (“US Privacy Laws”). As to individuals in India, we act as a “Data Processor” under India’s Digital Personal Data Protection Act, 2023 and its rules (the “DPDP Act”). In this Privacy Policy, “Privacy Laws” means US Privacy Laws, the DPDP Act and any other privacy or data protection law that applies. We do not decide why a Customer collects personal information, and the Customer remains responsible for the lawfulness of its collection and its instructions to us.
2.3Individuals whose data is in Customer Data. If you are an employee, contractor, supplier, customer or other individual whose information is held in a Customer’s system, or you use a Customer’s system as one of its Authorised Users (for example, on a shared tablet at work), that Customer is responsible for your information and for telling you how it is used. Please direct any request or question to the Customer. If you contact us, we will, where we can identify the relevant Customer, refer your request to it and will not respond to it ourselves except as the Customer Agreement or law requires. We hold the account and activity records of Authorised Users described in Section 3.2 to secure and administer the system.
2.4No joint control. Vaylor is not an employer, joint employer, payroll provider, accountant, tax adviser, bank or financial institution of any individual whose information is in Customer Data.
03Information we collect
3.1Partner data. Contact details, company details and referral information of our go-to-market partners and the prospects they introduce, and the commercial information we need to calculate and pay commission.
3.2Account and Authorised User data. Name, business email, role, log-in credentials (stored in hashed or tokenised form), activity records and support requests of the Authorised Users.
3.3Customer Data. The Customer decides what it sends us. Customer Data is the information that a Customer or its Authorised Users submit to the Services, or that the Services retrieve from the Customer’s own systems on its behalf. It may include personal information about the Customer’s personnel, customers, suppliers and other business contacts, such as identity and contact details, business, financial and workforce records, and documents and communications. We collect and use only what is reasonably necessary and proportionate to provide the Services the Customer has asked for (see Section 3.6).
3.4Website Data and business-contact data. Name, business email address, telephone number, job title, employer, the content of your message or form submission, meeting and call details, marketing preferences, and records of our correspondence. We receive this from you, from the Customer or partner that introduced you, and from public business sources.
3.5Technical data. IP address, device and browser type, pages viewed, date and time, and error and security logs collected automatically when you use the Sites or Services (see Section 13).
3.6Data minimisation. We collect, access and use personal information only to the extent reasonably necessary and proportionate to provide the Services the Customer has asked for, and for the purposes in Section 4. In practice: (a) we ask for the narrowest access scopes, fields, mailboxes, folders and date ranges that the Services need, and we do not ask for broad access when narrower access will do; (b) the Customer should configure its connections and send us only the personal information those Services need, and should leave out anything that is not needed; (c) we may restrict a connection to specific fields, and we may refuse, filter, quarantine or delete data that goes beyond the agreed scope or that the Customer Agreement tells the Customer not to send; (d) where we can do the work with de-identified, masked or truncated data we will do so; and (e) we keep Customer Data only for the periods in Section 9 and delete or return it when the Customer Agreement ends. A Customer may ask us to narrow its connections or scope at any time.
04How we use information
4.1We use it to respond to enquiries and provide proposals; to negotiate, perform and administer contracts; to operate and secure the Sites; to send business communications about our Services (you may opt out at any time, and each marketing email carries an unsubscribe link, in line with the CAN-SPAM Act); to calculate and pay partner commission; to keep records and comply with legal, tax, accounting and regulatory obligations; to establish, exercise or defend legal claims; and to improve our Sites and Services.
4.2We process Customer Data only to build, configure, host, operate, support, secure, back up and report on the Customer’s system and to perform the Customer Agreement, in each case on the Customer’s documented instructions. We may also process it to detect and prevent security incidents, fraud and abuse, to debug and repair errors, and to comply with law.
4.3We do not sell it. We do not share it for cross-context behavioural advertising. We do not retain, use or disclose it outside our direct business relationship with the Customer or for any purpose other than those in Section 4.2. We do not combine it with personal information from other sources except as the Customer instructs or Privacy Laws allow. We do not use it to train, fine-tune or improve any artificial intelligence or machine-learning model, including any large language model, except that a Customer’s own system may learn from or compare against that Customer’s own data, for that Customer only (see Section 5). We use Customer Data in aggregated, de-identified form to improve our platform across customers only if the Customer has agreed to that in writing.
4.4We may compile technical and operational metrics about the performance and use of the Services (for example, volumes, response times, error rates and feature use) that do not contain Customer Data content and do not identify any Customer or individual. We may use these metrics, and our general skills, know-how and experience, to operate and improve our platform and reusable components. We will not attempt to re-identify de-identified data.
4.5US law does not generally require a stated legal basis. Where the DPDP Act applies, we process personal information on your consent or for another legitimate use that the Act permits, such as where you voluntarily provide it for a stated purpose, to comply with law, or for employment purposes. Where a law of another jurisdiction applies, we rely on performance of a contract, our legitimate business interests (including security, fraud prevention and business development), compliance with legal obligations, and consent where required.
05Artificial intelligence and automated processing
5.1Our Services use AI to read documents, extract and classify data, match records, draft entries and generate reports. We may use third-party AI model providers, acting as our subprocessors.
5.2AI output can be incomplete or wrong. Our Services are designed to support, not replace, a Customer’s own review. Unless the Customer Agreement says otherwise, each Customer is responsible for reviewing AI-generated entries, records and reports before relying on them or posting them to its books, payroll or other systems.
5.3Our Services are not designed to make, and a Customer must not use them to make, solely automated decisions that produce legal or similarly significant effects on an individual (for example, hiring, firing, pay, discipline, credit or housing decisions) without meaningful human review by the Customer. Several US and other laws regulate automated decision-making and profiling, including California’s regulations on automated decision-making technology (which apply from 2027) and state laws on algorithmic discrimination that take effect in 2027. Where a Customer uses the Services in a way that engages those rules, the Customer is responsible for giving any required notices, offering any required opt-outs and access, and carrying out any required risk assessments, and we will give reasonable assistance under the Customer Agreement.
06Data from third-party platforms, including Intuit QuickBooks Online
6.1Our Services connect to platforms the Customer already uses, including not limited to, such as Intuit QuickBooks Online, SAP Business One, FileMaker, ADP, OLOID, Microsoft 365 and Google Workspace (each a “Third-Party Platform”). We connect only when the Customer (or a person with authority to bind it) authorises the connection, and we request only the access scopes needed for the Services the Customer has bought.
6.2How we connect. Where the platform supports it, we connect through its official authorisation flow (for example, OAuth 2.0 with Intuit). We do not ask for, collect or store a Customer’s own user name and password for a Third-Party Platform unless the Customer Agreement expressly provides for it. Access tokens and similar credentials are encrypted, stored separately from Customer Data content and used only to provide the Services.
6.3Intuit QuickBooks Online. Information we receive from QuickBooks Online (“QuickBooks Data”) is used only to provide and improve, for the Customer that connected it, the features of the Services that the Customer has requested. We will not: (a) sell, rent or license QuickBooks Data; (b) use it for advertising, marketing to third parties or profiling for any other purpose; (c) use it to train any AI or machine-learning model; (d) show it to, or allow it to be used by, anyone except the Customer and its Authorised Users, our personnel and subprocessors that need it to provide the Services (Section 7), or where law requires; or (e) use it in a way that breaches the Intuit Developer Terms or Intuit’s applicable policies.
6.4Disconnecting. A Customer may withdraw our access at any time through its Intuit account (by disconnecting the app) or by notifying us at the address in Section 15. On disconnection we stop accessing the platform and revoke our tokens, and we delete or de-identify the QuickBooks Data and other Customer Data already received as Section 9 provides, after any return period the Customer asks for. We are not responsible for how Intuit or any other platform provider processes information; their own privacy statements apply to that processing.
6.5Email. If a Customer connects a mailbox for supplier-invoice intake, we access only the mailbox, folders or labels and the scopes the Customer authorises, and we read and process messages only for the purposes of the Services. To the extent a Third-Party Platform provider publishes data-use requirements for its APIs (for example, the Google API Services User Data Policy, including its Limited Use requirements), our use of data received through those APIs follows them.
6.6Customer’s authority. The Customer is responsible for having the rights, consents and authority needed to connect each Third-Party Platform and permit us to access it. We rely on the Customer’s authorisation and do not verify it.
07How we disclose information
7.1We do not sell personal information, and we do not share it for cross-context behavioural advertising, and we have not done so since we began operating. We do not sell sensitive personal information or precise geolocation, and we are not a data broker.
7.2Subprocessors and service providers. We disclose personal information to vendors who help us run the Services and the business, under written contracts that require them to protect it, to use it only for our instructions and to meet equivalent privacy and security obligations. The categories are:
| Category | Purpose | Provider |
|---|---|---|
| Cloud hosting and storage | Hosting the platform and Customer Data in the United States | Google LLC (Google Cloud), United States; Hetzner Online GmbH (Hetzner Cloud), data centre in Ashburn, Virginia, United States |
| AI model providers | Document reading, extraction and classification | Google LLC (Vertex AI on Google Cloud), United States; OpenRouter, Inc., United States, which passes each request to a provider of the model we use: Anthropic PBC (Claude), Amazon Web Services, Inc. (Amazon Bedrock) or Google LLC (Vertex AI). Each provider handles the information under its own terms and may keep it for a limited period. |
| Email, communications and support tools | Service notices, support, and any Vaylor mailbox that a Customer uses to send invoices | Google LLC (Google Workspace) |
The table above is our current list of subprocessors. We will give Customers at least 30 days’ notice before we add or replace a subprocessor that processes Customer Data.
7.3Go-to-market partners. Our partners introduce prospective customers and, in some cases, hold the contract with the Customer. We may share with a partner the contact details of a prospect it introduced, the status of the engagement and the information needed to calculate commission. A partner receives Customer Data only where the Customer obtained the Services through that partner and asks for its help. Partners have no authority to bind Vaylor or to collect personal information on our behalf.
7.4Professional advisers and insurers. Lawyers, accountants, auditors, banks, payment processors, insurers and similar advisers, who are bound by duties of confidentiality.
7.5Legal process and protection. We may disclose information where we believe in good faith that disclosure is required by law, regulation, subpoena, court order or government request, or is needed to enforce our agreements, protect the rights, property or safety of Vaylor, our Customers or others, or investigate fraud or security incidents. Where the information is Customer Data and the law allows, we will give the Customer prompt notice so that it may seek protection, and will disclose only what is legally required.
7.6Business transfers. If we merge with, are acquired by, or sell all or part of our business or assets to another organisation, or transfer the Customer Agreement to an affiliate (including a future United States affiliate), personal information may be transferred as part of that transaction, subject to this Privacy Policy and the Customer Agreement.
7.7With your direction or consent. Including at the direction of a Customer for its own Customer Data.
7.8De-identified information. We may disclose aggregated or de-identified information that cannot reasonably be used to identify a person or Customer. We do not make Customer Data available in de-identified form to other customers or to third parties, or use it to improve our platform across customers, unless the Customer has agreed in writing (see Section 4.3).
08Where information is processed and cross-border access
8.1United States hosting. Customer Data is hosted in the United States, unless the Customer Agreement says otherwise.
8.2Access from India. Vaylor is based in India. Our personnel in India, and our subprocessors, may access Customer Data remotely where needed to build, support and secure the Services. That access is limited to authorised personnel with a need to know, made over encrypted connections, logged, and bound by written confidentiality obligations. By using the Services, Customers acknowledge and agree to this access and to the resulting transfer of personal information to India, which we make under the Customer Agreement.
8.3Restricted jurisdictions. We do not knowingly permit access to Customer Data by any person or entity that is a “covered person” or located in a “country of concern” under the US Department of Justice rule on access to bulk US sensitive personal data (28 CFR Part 202), and we do not sell or license Customer Data to any such person.
8.4Other jurisdictions. Our Sites and Services are intended for US businesses and for personal information about individuals in the United States, India and other countries that we approve. We do not intentionally offer them to individuals in the European Economic Area, the United Kingdom or Switzerland. A Customer must not submit personal information of those individuals without our prior written agreement and appropriate transfer terms.
09Retention, return and deletion
9.1How long we keep information. We keep each category of personal information for the period below, or for as long as needed for the purposes in Section 4, our legal, tax, accounting and dispute-resolution needs, and any period the Customer Agreement sets.
| Category | How long we keep it |
|---|---|
| Customer Data | For as long as the Customer Agreement is in force and as the Customer instructs. After the Customer Agreement ends, or a Customer disconnects a Third-Party Platform, we make an export available on Customer’s request, then delete or de-identify the data within 30 days. Copies in encrypted backups are overwritten in the ordinary course within 30 days. We keep the record of each entry that the Services write to a Customer’s accounting system, with its source reference and its reviewer, for 8 years as an audit trail, unless the Customer asks in writing for earlier deletion. |
| Website Data and partner data | Inactive prospect records are deleted two years after the last contact. Contract, commission and financial records are kept for the period the law requires, currently up to seven years. |
| Account and Authorised User data | While the account is active and for as long afterwards as needed for security, audit and legal purposes. |
| Security and access logs | For as long as needed for security, audit and legal purposes. |
9.2Legal requirements. We may keep Customer Data longer only where law requires, in which case we will protect it and use it only for that purpose. When we dispose of records that contain sensitive personal information, we destroy them by shredding, erasing or otherwise making the information unreadable or indecipherable.
9.3Legal holds. We may suspend deletion where needed to preserve information for a legal claim, investigation or regulatory request.
10Security and incident notification
10.1Safeguards. We maintain administrative, technical and physical safeguards that are appropriate to the nature of the information and the risks, including: encryption of data in transit and at rest; storage of access tokens in encrypted form, never written to logs; access to production systems restricted to named personnel and logged; and backups.
10.2Notification. If we confirm that Customer Data in our possession or control has been accessed, acquired, disclosed, lost or altered without authorisation (a “Security Incident”), we will notify the affected Customer without undue delay, and will give the information the Customer reasonably needs to meet its own legal notification duties. Customers, and not Vaylor, decide whether and how to notify individuals and regulators, unless law requires otherwise. Where the DPDP Act applies, the Customer, as the Data Fiduciary, is responsible for reporting a personal data breach to the Data Protection Board of India and to affected individuals, and we will give it the information it needs to do so.
10.3Limits. No system is completely secure. We cannot guarantee that information will never be accessed, disclosed, altered or destroyed by a breach of our safeguards, and a notified incident is not by itself an admission of fault or liability.
10.4Your role. Customers and Authorised Users must keep credentials confidential, use strong authentication, and tell us promptly at hello@vaylorlabs.com if they suspect unauthorised access.
11Your privacy rights
This Section explains how to make a request about your personal information (Section 11.2) and the rights of individuals in India (Section 11.3). For Customer Data, see Section 11.1.
11.1Customer Data. For Customer Data we are a service provider or processor. If your information is in a Customer’s system, please contact that Customer. We will help the Customer respond to your request as the Customer Agreement provides.
11.2How to make a request. Email hello@vaylorlabs.com or write to the address in Section 15, giving your name, business email address and what you are asking us to do. We may ask for more information to confirm who you are. We will respond within a reasonable time.
11.3Individuals in India. If you are in India and we hold your personal information as a Data Fiduciary, the DPDP Act gives you the right to access a summary of it, to ask us to correct, complete, update or erase it, to have your grievance redressed, and to nominate another person to exercise your rights if you die or become incapacitated. You may withdraw any consent you have given at any time, without affecting processing before the withdrawal. Please use the methods in Section 11.2, and contact our Grievance Officer in Section 15.5 first. If your grievance is not resolved, you may complain to the Data Protection Board of India. We will respond within the period that the DPDP Act and its rules require and, where none applies, as Section 15.5 describes. We ask for consent only for Website Data. For Customer Data, the Customer is the Data Fiduciary and is responsible for notice and consent, so please contact the Customer, as Section 11.1 explains.
12Workforce and other individuals’ data: what Customers must do
12.1Where a Customer sends us information about its own employees, contractors or applicants (“Workforce Data”), such as time-clock, attendance or payroll records, the Customer is the employer and the business or controller of that data, and we are its service provider or processor.
12.2Each Customer is solely responsible for: (a) giving its workforce every notice required by law, including notice at collection and any workplace-monitoring notice required by state law; (b) having a lawful basis to collect Workforce Data and to give it to us; (c) obtaining any consent required by law; (d) complying with wage-and-hour, record-keeping, payroll, tax and employment laws that apply to it (in the United States, India or elsewhere); (e) responding to access, correction and deletion requests from its workforce; and (f) all employment decisions made using the Services.
12.3Biometrics. Time-clock and access systems may use biometric identifiers. We do not collect, store or process biometric identifiers or information. The Customer must configure those systems so that only the resulting time-and-attendance record, and no biometric identifier, template or image, is sent to us. The Customer is solely responsible for compliance with the applicable biometric privacy law that applies to its own use of those systems, including giving notice and obtaining informed consent before any biometric identifier is captured, limiting its disclosure, protecting it with reasonable care, and destroying it within the time the law requires.
12.4Minimisation. Section 3.6 applies. In particular, the Customer should send only the Workforce Data needed for the agreed Services (for a time-and-attendance project, time and attendance records and the minimum identifiers needed to match them to a person) and, for any other individuals’ data, only what the agreed Services need. We may restrict our connection to specific fields and may refuse data that exceeds the agreed scope.
12.5Flags and reports. Where our Services compare, flag or report on time and attendance records (for example, a missing punch, a gap or a long day), those results are aids for the Customer’s review. They are not a determination of hours worked, pay due or compliance with any law, and the Customer decides what to do with them. We do not calculate or pay wages.
12.6Workforce questions. If you are a member of a Customer’s workforce, please contact your employer about your records. We are not your employer and do not make employment, pay or discipline decisions.
12.7Other individuals. The duties in Sections 12.1, 12.2 and 12.4 apply in the same way, with the necessary changes, to personal information about the Customer’s own customers, prospects, suppliers, vendors and other individuals. The Customer is the business or controller of that information, must give those individuals the notices and obtain the consents that the law requires, and must direct their requests to itself. If you are one of those individuals, please contact the Customer, as Section 2.3 explains.
13Cookies, analytics and similar technologies
13.1The website at vaylorlabs.com sets no cookies and runs no analytics or tracking scripts. Our applications use only the cookies needed to keep a signed-in Authorised User signed in, and do not use them for tracking. We do not use advertising or cross-site tracking cookies.
13.2You can block or delete cookies in your browser settings, but parts of the Sites may then not work. Because there is no common standard, we do not respond to “Do Not Track” signals.
13.3The Services themselves do not place advertising technologies on a Customer’s systems.
14Children, other jurisdictions and third-party links
14.1Children. The Sites and Services are for businesses and are not directed to anyone under 18. We do not knowingly collect personal information from anyone under 18. If you think a child has given us personal information, contact us and we will delete it.
14.2Individuals outside our service countries. See Section 8.4. If you access the Sites from a country where we do not offer them (see Sections 1.5 and 8.4), you do so on your own initiative and are responsible for compliance with local law.
14.3Third-party links. The Sites may link to other websites and platforms, including Intuit, ADP and our partners. We do not control them and are not responsible for their privacy practices. Please read their privacy statements.
15Changes, governing law, disputes and contact
15.1Changes. We may update this Privacy Policy from time to time. We will post the updated version at https://vaylorlabs.com/legal/privacy with a new effective date. For a material change that affects Customer Data, we will also notify Customers as the Customer Agreement provides. A change does not apply retroactively to reduce a protection we have promised for Customer Data already collected without the Customer’s consent.
15.2Governing law. This Privacy Policy, and any dispute or claim arising out of or in connection with it, is governed by the laws of India, without regard to conflict-of-laws principles. The United Nations Convention on Contracts for the International Sale of Goods does not apply.
15.3Disputes. If you are a Customer, the dispute resolution clause of your Customer Agreement governs any dispute with us arising out of or in connection with this Privacy Policy. For anyone else, before starting a claim, please contact us at the address in Section 15.5 and give us 15 Business Days to try to resolve it, and any claim that is not resolved shall be brought in the courts at Bengaluru, Karnataka, India, to whose jurisdiction you and we submit. “Business Day” means a day other than a Saturday, a Sunday or a public holiday in Texas, United States, or in Bengaluru, India.
15.4Non-waivable rights. Nothing in this Section limits any right that cannot lawfully be waived, including a right to complain to or cooperate with a regulator such as a state attorney general, or to bring a claim that applicable law requires be heard in court.
15.5Contact. Questions, requests and complaints about this Privacy Policy, and requests for this Privacy Policy in an alternative accessible format:
- Privacy contact: hello@vaylorlabs.com
- Grievance Officer (India): Grievance Officer, Vaylor Labs Private Limited, hello@vaylorlabs.com
- US privacy contact: hello@vaylorlabs.com
We will acknowledge a complaint within 7 days and aim to resolve it within 30 days.