1. Parties
This Data Processing Agreement ("DPA") is entered into between:
The Customer named in the order form or account ("Controller"); and
Algobain Technologies Opc Pvt Ltd, trading as Tenyq, Sreepally, Kathal Tala, Road No. 7, Siliguri, Darjiling, West Bengal 734005, India ("Processor").
It forms part of the Terms of Service or other agreement under which the Processor provides the Tenyq platform (the "Agreement"). Where this DPA conflicts with the Agreement on the processing of personal data, this DPA prevails. Where the Standard Contractual Clauses apply and conflict with this DPA, the Standard Contractual Clauses prevail.
2. Subject matter and duration
The Processor processes personal data on behalf of the Controller to provide the platform under the Agreement. This DPA applies for as long as the Processor processes personal data on the Controller's behalf, and ends when that processing ends under Section 12.
3. Nature and purpose of processing
Hosting, storage, retrieval, organisation, analysis (including AI-assisted analysis the Controller's users request), transmission (including email the Controller's users send through the platform), and deletion of personal data, solely to provide, secure and support the platform for the Controller, and only on the Controller's documented instructions. The Agreement, this DPA and the Controller's use of the platform's features are the Controller's instructions.
4. Categories of data subjects and personal data
Data subjects: the Controller's users (partners, analysts, controllers and other staff); limited partners and their representatives; founders, employees and officers of portfolio and prospective companies; other contacts the Controller records.
Personal data: names, business contact details, job titles and affiliations; account and authentication data; investment, commitment and capital-account data relating to individuals; content of notes, documents and communications the Controller uploads or sends; technical data such as IP addresses and device information.
Special categories: none are intended. The Controller will not upload special-category data unless both parties have agreed in writing to additional safeguards.
5. Processor obligations
The Processor will:
- process personal data only on the Controller’s documented instructions, including for international transfers, unless required otherwise by law (in which case it will inform the Controller first, unless the law prohibits it);
- tell the Controller promptly if, in its opinion, an instruction infringes applicable data protection law;
- ensure that everyone authorised to process the personal data is bound by confidentiality;
- implement the technical and organisational measures in Annex II;
- engage subprocessors only as set out in Section 6;
- assist the Controller, taking into account the nature of the processing, in responding to data subject requests;
- assist the Controller with its obligations on security, breach notification, data protection impact assessments and prior consultation, taking into account the information available to the Processor;
- make available the information needed to demonstrate compliance with Article 28 GDPR, and allow for audits as set out in Section 10.
6. Subprocessors
The Controller gives general written authorisation for the Processor to engage the subprocessors listed at tenyq.com/legal/subprocessors.
The Processor will update that list, and notify the Controller by email to its account owner, at least 30 days before a new subprocessor begins processing personal data. Where a replacement is urgently needed to keep the platform secure or available, the Processor may give shorter notice and will explain why. The Controller may object on reasonable data protection grounds within the notice period. If the parties cannot resolve the objection, the Controller may terminate the affected service and receive a pro-rata refund of prepaid fees for the unused period.
The Processor will impose on each subprocessor, by contract, data protection obligations no less protective than those in this DPA, and remains liable to the Controller for each subprocessor's performance of those obligations.
Integrations the Controller itself enables with its own accounts (listed separately on the subprocessors page) are not subprocessors of the Processor.
7. Security
The Processor will implement and maintain appropriate technical and organisational measures to protect personal data, including those in Annex II. The Processor may update those measures, provided the overall level of protection is not reduced.
8. International transfers
The Processor is located in India, and some subprocessors are located outside the EEA, the UK and Switzerland (see the subprocessors page for locations).
EEA: to the extent a transfer of personal data under this DPA is a restricted transfer from the EEA, the Standard Contractual Clauses adopted by Commission Implementing Decision (EU) 2021/914 (the "SCCs") are incorporated into this DPA by reference. Module Two (controller to processor) applies where the Customer is a controller, and Module Three (processor to processor) applies where the Customer is itself a processor. For each Module: Clause 7 (docking clause) applies; Clause 9 Option 2 (general written authorisation) applies, with the notice period set out in Section 6; the optional language in Clause 11 does not apply; the competent supervisory authority under Clause 13 is determined under Clause 13(a) by reference to the Controller; Clause 17 Option 1 applies, and the SCCs are governed by the law of Ireland; and under Clause 18(b) disputes are resolved by the courts of Ireland. Annex I of the SCCs is completed by Sections 1 to 4 of this DPA, Annex II by Annex II below, and Annex III by the subprocessors page.
UK: to the extent a transfer is a restricted transfer from the United Kingdom, the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses issued by the UK Information Commissioner, version B1.0, in force 21 March 2022 (the "Addendum"), is incorporated into this DPA by reference. Table 1 of the Addendum is completed by Section 1 of this DPA; Table 2 by the Module and Clause selections above; Table 3 by Sections 1 to 4, Annex II and the subprocessors page; and for Table 4, neither party may end the Addendum under its Section 19.
Switzerland: to the extent a transfer is a restricted transfer from Switzerland, the SCCs apply as set out above with these changes: the competent supervisory authority is the Swiss Federal Data Protection and Information Commissioner (FDPIC); references to the GDPR are read as references to the Swiss Federal Act on Data Protection (FADP); the law governing the SCCs under Clause 17 remains the law of Ireland; and the term "Member State" in Clause 18(c) does not prevent data subjects in Switzerland from bringing proceedings where they habitually reside.
Onward transfers to subprocessors are made under Module Three of the Standard Contractual Clauses or another transfer mechanism recognised under applicable law.
9. Personal data breach notification
The Processor will notify the Controller by email to its account owner without undue delay, and in any event within 48 hours, after becoming aware of a personal data breach affecting the Controller's personal data. The notice will describe, as far as then known, the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences, and the measures taken or proposed. The Processor will provide further information as it becomes available and will take reasonable steps to contain and remediate the breach.
10. Audit rights
On request, the Processor will provide the information reasonably necessary to demonstrate compliance with this DPA, including written answers to security questionnaires.
Where that information is not sufficient, the Controller (or an independent auditor bound by confidentiality) may audit the Processor's compliance on at least 30 days' written notice, no more than once in any 12 months unless required by a supervisory authority or following a personal data breach, during business hours and without unreasonably disrupting operations. Each party bears its own costs.
The Processor is preparing for SOC 2 and does not hold a SOC 2 report today. Once a report is issued, the Processor may provide it in satisfaction of information requests it covers.
11. CCPA
To the extent the California Consumer Privacy Act applies, the Processor acts as a service provider: it will not sell or share the personal data, will not retain, use or disclose it for any purpose other than providing the platform under the Agreement, and will not combine it with personal data it receives from other sources except as permitted by the CCPA.
12. Deletion and return
On termination of the Agreement, the Controller may request an export of its data by email to privacy@tenyq.com within 30 days, and the Processor will provide it. The Processor will then delete the Controller's personal data from production systems within 30 days, unless applicable law requires it to be stored, and will confirm deletion in writing on request. Copies in backups age out on their own backup cycle and are not restored to active use in the meantime.
Annex II — Technical and organisational measures
The measures the platform implements today:
- Encryption in transit: the platform is served only over HTTPS (TLS).
- Encryption at rest: the primary database encrypts its storage at rest.
- Field-level encryption: stored connection credentials (OAuth tokens, API keys, SMTP passwords, SSO secrets) are encrypted with AES-256-GCM before they are written, under a key held outside the database.
- Tenant isolation: every query is checked on the server against the caller’s workspace, not only in the interface.
- Role-based access control within each workspace, with separate surfaces for fund staff, LPs and founders.
- Audit log: record changes, exports and LP document views are recorded with the acting user, time and, where available, IP address. Entries cannot be edited or deleted through the API.
- Authentication: accounts are locked for ten minutes after five consecutive failed sign-ins; session tokens expire; SAML single sign-on is available on every plan.
- Rate limiting on sign-in, sign-up and public endpoints.
- Uploaded files are stored under randomised, non-enumerable URLs.
- Subprocessor control: every outside system the platform connects to is declared in one register, and the build fails if a platform-operated vendor is missing from the published subprocessor list.
- A published channel for security reports: security@tenyq.com.
Annex III — Subprocessors
The current list, with each subprocessor’s purpose and location, is maintained at tenyq.com/legal/subprocessors.