Vai al contenuto

Data Processing Agreement

Effective date: October 1, 2026

1. Parties and status

This Data Processing Agreement (the “Agreement”) is entered into between the customer that has accepted the Terms of Use (the “Customer”) and AIVIBE SOFTWARE SERVICES PRIVATE LIMITED, A501 Saraduez Olympus, Chennai, Tamil Nadu 600100, India (the “Company”), together with its subsidiary AIVEDHA INC, 169 Madison Avenue, 62146, New York, NY 10016-5101, United States, which serves the Americas and Europe under the parent's governance and jurisdiction.

It forms part of the Terms of Use and takes effect on the same date as them, for as long as the Company processes personal data on the Customer's behalf. No separate signature is required for it to apply. A Customer that requires a counter-signed copy may request one at support@aivibe.in, quoting the account.

Where this Agreement and the Terms of Use address the same subject, this Agreement governs as to the processing of personal data and the Terms govern as to everything else. This Agreement does not restate what is set out in the Privacy Policy; it refers to it.

2. Roles of the parties

  • The Customer is the controller of the personal data it submits to, or generates through, the Services — including the personal data of its own personnel who hold seats, and any personal data contained in the material it directs the Services to process.
  • The Company is the processor of that personal data, and processes it only on the Customer's documented instructions.
  • The Company is a controller in its own right in respect of a narrow set of data it must determine for itself: account and identity records required to operate a subscription, billing and tax records it is required by law to keep, security and audit logs, and the metering records that establish what was used. Those are described in the Privacy Policy and are not processed under this Agreement.

Personal data processed under this Agreement remains the Customer's. The Company acquires no right in it beyond what is necessary to perform the Services.

3. Subject matter, duration, nature and purpose

  • Subject matter. The provision of AicippY — the applications the Customer installs, the console, and the services they reach — under the Terms of Use.
  • Duration. From the date the Customer accepts the Terms of Use until the end of the Customer's last subscription period, followed by the deletion period set out in section 11.
  • Nature of the processing. Collection, recording, storage, structuring, retrieval, transmission to the destinations the Customer configures, erasure and destruction, performed by automated means.
  • Purpose. Performing the Services: authenticating the Customer's users, establishing and maintaining entitlement, operating seats and roles within a team, delivering model requests to the destination selected for them, metering use, producing billing documents, communicating about the account, and maintaining the security and integrity of the Services.
  • Instructions. The Terms of Use, this Agreement, the configuration the Customer sets in the product, and each use the Customer makes of the Services together constitute the Customer's documented instructions. The Company will inform the Customer where it considers an instruction to infringe applicable data protection law.

4. Categories of personal data and of data subjects

Data subjects. The Customer's personnel, contractors and other authorised users who hold a seat or sign in; the Customer's billing and administrative contacts; and any individual whose personal data happens to be contained in material the Customer directs the Services to process.

Categories of personal data. Account and contact data; authentication identifiers and session records; team, seat and role assignments; billing and transaction records; device and network data; usage and metering metadata; support correspondence; and the content the Customer submits to a model destination, to the extent it contains personal data. Each category is described, with what it is used for and who receives it, in the Privacy Policy.

Special categories. The Services are not designed for, and are not to be used for, the processing of special categories of personal data, of data relating to criminal convictions and offences, or of the personal data of children. The Customer is to refrain from submitting such data.

5. Obligations of the Company as processor

The Company:

  • processes personal data only on the Customer's documented instructions, including as to transfers, unless required to do otherwise by a law to which it is subject, in which case it informs the Customer of that requirement before processing, unless the law prohibits that information on important grounds of public interest;
  • does not sell personal data processed under this Agreement, does not use it for advertising, and does not use it to train a model of its own;
  • applies the technical and organisational measures described in section 7 and takes steps to see that a person acting under its authority who has access to personal data processes it only on the Customer's instructions;
  • restricts access to personal data to the personnel who require it to perform the Services, and removes that access when it is no longer required;
  • assists the Customer as set out in sections 9 and 10, taking into account the nature of the processing and the information available to the Company; and
  • makes available the information required to demonstrate compliance with this Agreement.

6. Confidentiality

Personnel of the Company authorised to process personal data under this Agreement are bound by a written obligation of confidentiality that survives the end of their engagement, or are under an appropriate statutory obligation of confidentiality. The same obligation is imposed on contractors engaged by the Company, under the written engagement described in the Modern Slavery Statement. Personal data processed under this Agreement is treated as the Customer's confidential information.

7. Security measures

The technical and organisational measures applied are set out in full on the Security page, which forms part of this Agreement. They include a multi-tenant PostgreSQL database with row-level security enforced by database policies, application scoping of records above it, encryption in transit, encryption at rest by the managed storage services under their own configurations, short-lived and cryptographically verified sign-in tokens, least-privilege roles, network isolation of the platform database, integrity verification of payment messages, boundary controls on the web surface, and logging of administrative and payment events.

That page describes controls that are applied. It states what is implemented, not the result of implementing it, and this Agreement incorporates it on that basis. The measures are reviewed and may be changed; a change does not reduce the overall level of the measures applied.

The control set is aligned to ISO/IEC 27001 and the schema and services are authored against it. That is an alignment, not a certification.

8. Sub-processing

The Customer gives the Company general authorisation to engage sub-processors for the performance of the Services. Where the Company engages a sub-processor, it does so under a written contract imposing data protection obligations no less onerous than those in this Agreement, and it remains liable to the Customer for that sub-processor's performance.

The current list of sub-processors — each named, with what it handles, the categories of data it receives, the region in which it operates, and a link to its own terms and privacy notice — is maintained in the subprocessor table of the Privacy Policy. That table is the list for the purposes of this Agreement, and it is kept current rather than duplicated here. By function, the sub-processors engaged are:

Function What it handles Where it operates
Cloud infrastructure and hosting Application compute, the platform database, object and key-value storage, the GraphQL and realtime API, the sign-in directory, transactional email, secret storage and content delivery United States and India regions
Edge network Serving the website and console at the edge, rate limiting and abuse mitigation Global edge network
Hosted model inference Model requests served through the Company's own model proxy United States region
Payment gateways Taking payment, operating the mandate, and returning amounts India; United States and the European Union for the non-Indian gateway
Telemetry and error reporting Edge and backend logs, traces and error records United States
Product and site analytics Aggregate usage of the website and console, subject to the cookie preferences set United States; global

The Company names its cloud infrastructure by function rather than by an undertaking to retain a particular vendor. A change of sub-processor is notified as set out immediately below.

Notice and objection. The Company gives notice of an intended addition or replacement of a sub-processor by updating the subprocessor table and notifying the Customer at the email address on the account. The Customer may object on reasonable data protection grounds within thirty (30) days of that notice, in writing to support@aivibe.in, stating the grounds. Where the objection cannot be resolved, the Customer may terminate the affected subscription in accordance with the Terms of Use, and the Refund and Cancellation Policy governs what happens to amounts already paid.

9. Destinations the Customer configures

A model provider, gateway or MCP server that the Customer configures with its own key or its own account is not a sub-processor of the Company. The product carries plugins for a long list of inference destinations. Where the Customer selects one and supplies its own credential, the request is addressed to that provider, on the Customer's key, because the Customer directed it. The Company does not stand between the Customer and that provider and does not receive the content of the exchange.

In respect of such a destination the Customer is the controller and that provider is the Customer's own processor or independent controller, as their arrangement provides. Concluding any data processing terms required with it is the Customer's responsibility, and that provider's terms and privacy notice govern the processing entirely. The same applies to an MCP server the Customer connects.

The one inference destination engaged by the Company, and therefore covered by section 8, is the hosted model service reached through the Company's own model proxy.

10. Assistance with data subject requests

Taking into account the nature of the processing, the Company assists the Customer by appropriate technical and organisational measures, so far as is possible, in fulfilling the Customer's obligation to respond to a request to exercise a data subject's rights of access, rectification, erasure, restriction, portability or objection.

Where a data subject addresses such a request directly to the Company in respect of personal data processed on the Customer's behalf, the Company does not respond to it itself. It refers the request to the Customer without undue delay and, where it has the contact details, tells the data subject that it has done so. The rights themselves, and how they are exercised, are set out in the Privacy Policy.

Requests are received at support@aivibe.in, or at support@aivedha.com where the matter concerns AIVEDHA INC.

11. Assistance with the Customer's other obligations

Taking into account the nature of the processing and the information available to it, the Company assists the Customer with:

  • the security of processing;
  • notification of a personal data breach to a supervisory authority and to affected data subjects;
  • data protection impact assessments; and
  • prior consultation with a supervisory authority.

The information required for those purposes is provided on written request to support@aivibe.in.

12. Personal data breach

On becoming aware of a personal data breach affecting personal data processed on the Customer's behalf, the Company notifies the Customer without undue delay, at the email address on the account. The notification describes, so far as the information is available at the time:

  • the nature of the breach, including the categories and approximate number of data subjects and records concerned;
  • the likely consequences;
  • the measures taken or proposed to address it, including to mitigate its possible adverse effects; and
  • a point of contact from whom further information may be obtained.

Where the information cannot be provided at once, it is provided in phases as it becomes available, without further undue delay. The Company records the facts of the breach, its effects and the remedial action taken.

Notification is made so that the Customer can meet its own obligations as controller. It is not an acknowledgement of fault, and the Company's liability is governed by the Terms of Use.

13. Return and deletion of data at the end

The Customer may export or retrieve the personal data held in the account at any time while the subscription or the account is live. A Customer requiring an export in a particular form may request one at support@aivibe.in before deleting the account.

On deletion of the account, personal data is deleted ninety (90) days afterwards. The ninety-day period, what happens during it and the narrow categories that continue to be held after it — records the Company is required by law to keep, such as billing and tax records, and records required for the establishment, exercise or defence of legal claims — are set out in the retention section of the Privacy Policy, and that position applies under this Agreement without alteration.

Data retained after the ninety-day period continues to be held under the measures described in section 7 and is processed for no purpose other than the one that requires it to be kept. The Company does not operate a second and longer retention position for personal data processed on a Customer's behalf.

Deletion of the platform user record cascades to the product records that reference it. Where deletion from backup media cannot be performed immediately, the data remains subject to section 7 until the backup cycle expires.

14. Audit and information rights

The Company makes available to the Customer the information necessary to demonstrate compliance with this Agreement. That information consists of this Agreement, the Security page, the Privacy Policy and its subprocessor table, and such further written description of the measures applied as the Customer reasonably requests in writing.

An audit is conducted on the following basis.

  • The Customer gives at least thirty (30) days' written notice.
  • An audit is conducted no more than once in any twelve-month period, except where required by a supervisory authority or following a personal data breach affecting the Customer.
  • It is conducted during business hours, without unreasonable disruption to the Company's operations, and in a manner that does not compromise the confidentiality or the security of another customer's data.
  • The auditor is the Customer or an independent auditor appointed by the Customer, who is not a competitor of the Company and who is bound by confidentiality.
  • The scope is the processing carried out for the Customer under this Agreement.
  • Each party bears its own costs; the Customer bears the auditor's costs.
  • Findings are the confidential information of both parties.

An audit does not extend to a sub-processor's own premises or systems. In respect of those, the Company makes available such audit material as its own contract with that sub-processor entitles it to obtain.

15. International transfers

Personal data processed under this Agreement is held on infrastructure operated by cloud infrastructure providers in the United States and India regions. Regions in Europe, Hong Kong, the United Arab Emirates, Japan, Singapore, Canada and Australia are maintained or planned, and processing may be performed in any of them as the Services are extended to those regions. Content is also delivered through a global edge network.

A transfer of personal data out of the jurisdiction in which it was collected is made only where a lawful transfer mechanism applies to it — the standard contractual clauses or an equivalent instrument where the law of the exporting jurisdiction requires one, an adequacy determination where one exists, or the data subject's own instruction where the transfer is made on it. Where the standard contractual clauses apply to a transfer from the European Economic Area, the United Kingdom or Switzerland, they are incorporated into this Agreement by reference, with the Customer as data exporter and the Company as data importer, module two where the Customer is a controller, and this Agreement supplying the appendices.

A transfer to a destination the Customer configures under section 9 is a transfer the Customer makes, to a recipient of the Customer's choosing, and the mechanism for it is the Customer's to put in place.

The Company's position on government and law-enforcement requests is set out in the Privacy Policy.

16. The Customer's obligations

The Customer:

  • warrants that it has a lawful basis for the processing it instructs, and that it has given every notice and obtained every consent its own law requires;
  • is responsible for the accuracy, quality and legality of the personal data it submits and for the means by which it acquired that data;
  • is responsible for the configuration it sets, including which model destination it selects and which MCP servers it connects;
  • is responsible for administering seats and roles within its team, and for removing access when a person leaves it; and
  • is to refrain from submitting special categories of personal data, data relating to criminal convictions and offences, and the personal data of children.

17. Liability

Liability under or in connection with this Agreement is governed by, and subject to, the limitations and exclusions in the Terms of Use and, as to amounts payable, the limit stated in the Refund and Cancellation Policy. Nothing in this Agreement excludes a liability that the applicable law does not permit to be excluded.

18. Order of precedence

Where there is a conflict, the following order applies: first, any standard contractual clauses incorporated under section 15; second, this Agreement; third, the Terms of Use; and fourth, any other document. The Privacy Policy is descriptive of the Company's processing and does not vary this Agreement.

19. Changes to this Agreement

This Agreement is reviewed and may be updated. A material change is notified at the email address on the account before it takes effect. A change that reduces the substance of the obligations the Company undertakes here is not made without notice. The version in force is the one published at this address.

20. Governing law and jurisdiction

This Agreement is governed by the laws of India. The courts at Chennai, Tamil Nadu, India have exclusive jurisdiction over every dispute arising out of or relating to it, wherever the party bringing it is situated and whatever the nature of the claim. This position applies equally to AIVEDHA INC, which operates under the parent's governance and jurisdiction. Where standard contractual clauses incorporated under section 15 stipulate a governing law and forum for a claim brought under those clauses by a data subject, that stipulation applies to that claim alone and the rest of this Agreement is unaffected.

21. Contact

AIVIBE SOFTWARE SERVICES PRIVATE LIMITED
A501 Saraduez Olympus, Chennai, Tamil Nadu 600100, India
Email: support@aivibe.in

AIVEDHA INC
169 Madison Avenue, 62146, New York, NY 10016-5101
Email: support@aivedha.com