India · Prelaunch preview · Last updated [PUBLICATION DATE]
This Data Processing Addendum (“Addendum”) sets out the proposed terms on which Ardor Service LLC, doing business as TAP Agreements (“TAP”), processes personal data on behalf of the business customer identified in the accepted order (“Customer”). It becomes part of the India subscription agreement only when the applicable version and completed Schedules A to D are made available and accepted. An uncompleted preview does not authorise production document submission.
1 Scope applicable law and priority
“Customer Personal Data” means personal data contained in the documents, forms, participant details, responses, signatures, completed agreements and related evidence processed by TAP on the Customer’s behalf. “Processing” includes collection, storage, use, disclosure, return and deletion. A “Personal Data Breach” is an event compromising the confidentiality, integrity or availability of Customer Personal Data through unauthorised processing or accidental disclosure, acquisition, sharing, use, alteration, destruction or loss of access.
“Applicable Data Protection Law” means the laws and binding requirements governing the relevant processing, including applicable provisions of the Information Technology Act, 2000 and its rules and directions, and the Digital Personal Data Protection Act, 2023 (“DPDP Act”) and its rules to the extent the relevant provisions are in force and apply.
The DPDP framework has phased commencement. This Addendum does not state that every provision is already operative. Express contractual protections apply from this Addendum’s effective date even where a corresponding statutory duty has not yet commenced. When a binding requirement becomes applicable, each party must meet its own obligations and cooperate on necessary service changes.
This Addendum controls conflicting subscription provisions concerning processing on the Customer’s behalf. Mandatory legal protections prevail. It does not waive an individual’s rights, restrict a regulator’s powers or expand a liability limitation beyond what the law permits.
2 Roles and documented instructions
The Customer determines the purposes and content of its agreements, information requested, participants, permissions and lawful retention instructions. TAP processes Customer Personal Data to prepare and host forms, record signing, provide agreed delivery and storage, provide related support and carry out the operations in Schedule A. Where the DPDP Act applies, the parties’ actual activities determine their roles as Data Fiduciary and Data Processor; contractual labels do not change those activities.
TAP separately determines the purposes of processing needed for its own account administration, payments, fraud prevention, service security and legal duties. The India Privacy Policy explains that processing. A copy used for an independent lawful duty remains subject to appropriate purpose limits and safeguards; describing a function as security or administration does not authorise unrelated use of agreement contents.
The Customer’s instructions consist of this Addendum, its completed schedules, accepted service settings and documented requests accepted by TAP. TAP will process Customer Personal Data only for those purposes and instructions or as required by law. If TAP reasonably believes an instruction is unlawful, it will inform the Customer and may pause the affected processing while the issue is resolved. If law requires processing beyond the instructions, TAP will inform the Customer unless prohibited.
3 Customer responsibilities
The Customer must have authority to submit and use the data, give required notices, establish a lawful basis for processing and any overseas transfer, and obtain consent where required. It must provide information accurately, collect only what its transaction needs and keep user permissions appropriate. It must select a document and signing workflow suitable for the transaction and meet applicable execution and retention duties.
The Customer must not submit data requiring local hosting, professional secrecy, regulatory approval or safeguards the agreed service does not provide. The standard service is for ordinary business agreements. Clinical health records, biometric identification, children’s data and other restricted categories require a separately confirmed supported workflow and safeguards. An adult signing for a business does not establish authority to process another person’s data for an unrelated purpose.
These responsibilities do not relieve TAP of its own legal or contractual duties. Customer consent to this Addendum is not an individual’s blanket consent to every processing operation or overseas disclosure.
4 Purpose limits confidentiality and preparation
TAP will not sell Customer Personal Data, use agreement information for targeted advertising or marketing to signers, develop unrelated products from it or use it to train general-purpose models. TAP will require providers processing agreement information to observe the corresponding purpose restrictions. Signing does not subscribe a person to TAP marketing.
Preparation uses automated tools to extract content, identify fields and prepare signable forms. TAP does not routinely have a person read each agreement. Authorised TAP access is limited to what is needed for support, investigation, security or a legal duty. Under the proposed service, the TAP operator is located in the United States. Provider access is subject to the completed schedule and confidentiality obligations. A no-training restriction is separate from retention and does not promise zero provider access or immediate deletion of every provider record.
TAP will limit access to personnel and providers who need the information for an authorised function and who are bound by confidentiality. The Customer’s own authorised users and participants may access information as permitted by the selected workflow. TAP will not expand access merely because a document is available through a link.
5 Service providers and changes
Schedule B identifies the providers authorised to process Customer Personal Data, their functions, data categories and relevant processing locations. TAP will enter into binding arrangements requiring appropriate purpose limits, confidentiality, security, incident assistance and return or deletion. TAP remains responsible to the Customer for obligations it delegates under this Addendum.
TAP will give at least 30 days’ advance notice of a material new or replacement provider handling Customer Personal Data. The Customer may raise a reasonable data-protection objection within that notice period. The parties will seek a practical resolution. If no adequate resolution is available, the Customer may end the affected service before the change and receive a refund of attributable prepaid unused fees and unused purchased capacity TAP can no longer supply.
An urgent replacement needed to address a serious security issue, legal requirement or sudden provider failure may require shorter notice. TAP will notify the Customer as soon as reasonably practicable, explain the reason where permitted and preserve the objection and affected-service exit process. A provider change does not authorise a new processing purpose.
6 International processing
The standard service does not promise India-only storage or access. The agreed locations for hosting, backups, preparation, delivery and support are recorded in Schedule B. Hosting in one country does not establish that all provider support or onward processing occurs there.
Each party must meet the requirements applying to the transfers it initiates or authorises. TAP will apply this Addendum’s protections to authorised overseas processing. Where applicable sensitive-data rules require equivalent protection and a qualifying transfer basis, those requirements must be met. Any government restriction, binding localisation duty or sector rule that applies to particular data takes priority over the standard service description.
TAP will notify the Customer if it becomes aware of a legal restriction preventing agreed processing and will work on a lawful alternative or orderly termination of the affected service. Acceptance of this Addendum does not waive statutory protections or authorise every country named in a provider’s general global list.
7 Security
TAP will maintain documented safeguards appropriate to the information and service, including the agreed measures in Schedule C. They address authorised access, protection during transmission and storage, system monitoring, incident handling, recovery, provider oversight and secure disposal.
TAP will review the safeguards and will not materially reduce their overall protection during the agreed processing. A specific certification, data-residency commitment, identity-verification method or encryption architecture applies only if expressly identified in the completed schedule. This Addendum does not claim that TAP has an unlisted certification.
The parties will implement applicable Indian cyber-security requirements, including reporting, contact, time-synchronisation and log-retention requirements where they apply. Their arrangements must support statutory response times and must not rely on completion of a customer approval process before a legally required report.
8 Personal data breaches
TAP will notify the Customer’s designated security contact without undue delay after becoming aware of a Personal Data Breach affecting Customer Personal Data. It will not wait for a completed investigation before giving an initial notice where available information can be provided.
The initial notice and subsequent updates will include available information on the nature and timing of the event, affected data and individuals, likely consequences, containment and mitigation, and a contact for follow-up. TAP will take reasonable steps to contain, investigate and remediate the breach and preserve relevant evidence.
The parties will cooperate promptly on legally required reports and communications. Each remains responsible for obligations applying directly to it. Neither may delay its required report while waiting for the other’s approval. This clause does not replace a shorter legal deadline, including an applicable CERT-In deadline, or treat a later detailed-report deadline as permission to delay an initial notice.
9 Requests complaints and regulatory assistance
Taking account of the processing and information available, TAP will provide reasonable assistance with access, correction, erasure, consent-withdrawal, nomination and grievance requests to the extent those rights apply. TAP will promptly direct a request concerning the Customer’s agreement to the Customer where appropriate and will not make substantive decisions for the Customer unless authorised or legally required.
TAP may use proportionate verification to protect the requester and other people. It will not require unnecessary identity information or treat a request concerning one record as an automatic instruction to close the whole business account.
TAP will make reasonably necessary information about its compliance available and cooperate with lawful regulatory enquiries and required assessments. Where existing documentation is insufficient, reasonable verification arrangements will be agreed, protecting other customers’ data and system security. Confidentiality or audit conditions must not prevent a legally required inspection or disclosure.
10 Return retention and deletion
The Customer may retrieve available agreement records during the access periods in Schedule D and the Plans policy. On termination or an accepted deletion instruction, TAP will return or delete Customer Personal Data according to Schedule D, except to the extent a specific legal requirement or lawful preservation obligation requires continued retention.
TAP will identify the reason for retained exceptions where permitted, restrict use and access to that reason, review the continuing need and delete the information when that need ends. Backups and provider copies remain protected and expire under the completed schedule. Restoring a backup must not reverse a valid deletion instruction for ordinary use.
An optional customer archive is distinct from copies retained for law, security or evidence. The three-year archive is a service commitment subject to lawful earlier erasure; it is not a universal statutory retention period. Conversely, an account-deletion request cannot override a binding retention duty.
When the relevant DPDP retention provisions take effect and apply, the parties will implement the prescribed retention and erasure rules for covered personal data and logs. The normal service periods in Schedule D do not override those duties. Any resulting change to customer access or deletion arrangements will be explained before it applies where practicable and lawful.
11 Term and contact
This Addendum continues while TAP or an authorised provider retains Customer Personal Data under it. Ending a subscription does not end confidentiality, security, lawful retention or deletion obligations for data still held.
Privacy and Addendum contact: dpo@tapagreements.com. Support: support@tapagreements.com. Telephone: +1 626-630-0096.
Ardor Service LLC, doing business as TAP Agreements, 1034 N. Madison Ave., Pasadena, CA 91104, United States.
Schedule A Processing details
Customer: The legal entity or sole trader identified in the accepted order, with its authorised administrator and privacy/security contact. The acceptance record must identify that person or entity and the relevant contact details.
TAP: Ardor Service LLC, doing business as TAP Agreements, at the address above.
Duration: The agreed subscription and permitted record-storage period, followed by the applicable return, deletion, backup-expiry and lawful-preservation periods in Schedule D.
Purpose: Convert the Customer’s source paperwork into reusable forms; host forms and agreement instances; collect instructed participant information and signatures; produce completed records; deliver agreed notifications and copies; provide authorised retrieval, support, security and deletion.
Operations: Receiving, extracting, organising, formatting, storing, retrieving, displaying, transmitting, recording signing events, producing copies, restricting access, exporting and deleting.
People concerned: Customer staff, representatives, signers, witnesses where a supported process permits them, counterparties and other people lawfully identified in the Customer’s documents.
Data categories: Names, contact details, organisational roles, source-document content, form responses, transaction details, typed or drawn signatures, timestamps, IP addresses and other signing or technical events actually collected by the supported process. Passwords, payment credentials and unsupported restricted categories are outside the authorised document scope.
Customer instructions and contacts: [COMPLETE FROM ACCEPTED ORDER: legal customer name; administrator; privacy contact; security contact; service scope; additional authorised data categories, if any; applicable special restrictions.]
Schedule B Providers and locations
The following is the proposed provider schedule for completion before India processing begins. It must identify the actual contracted entities and relevant onward processing for the India service. A provider’s general worldwide operations do not establish where a particular TAP record is processed.
| Proposed provider | Function and data | Proposed location and completion needed |
|---|---|---|
| OVH US LLC trading as OVHcloud | Application, database and preparation workers; agreement, account and service records needed for those functions | United States, Virginia primary and Oregon standby. Confirm India deployment and applicable support access. |
| Amazon Web Services | Document storage, completed PDFs, signing evidence and backups as configured | Proposed document storage in Northern Virginia, United States. Complete contracted entity, backup destination and support/onward-access countries. |
| OpenAI OpCo LLC | Automated document preparation using necessary text, images, instructions and outputs | International processing. Complete actual service settings, retention and applicable processing/support locations; no India-only or US-only boundary is promised. |
| Twilio Inc and SendGrid service | Transactional email, recipient details, message content, titles, retrieval links and delivery records | Global email service. Complete contracted entity and service-specific processing/support countries. Standard copy messages use retrieval links. |
Other recipients of agreement data: [COMPLETE: any network delivery/security provider, monitoring provider, support service or other processor that actually receives agreement content or identifiable signing data; or record a verified conclusion that none is used.]
Payment and marketing-site services: Providers acting for TAP’s own payment, account or website purposes are described in the India Privacy Policy and the relevant purchase disclosures. They must also appear here if they process Customer Personal Data on the Customer’s behalf. No vendor is omitted merely because it is described as infrastructure.
Change notices: Send the notices required by section 5 to the Customer’s administrator or designated privacy contact. Provide sufficient details to assess the provider, function, location and safeguards.
Schedule C Security measures
The completed schedule must describe the measures actually implemented for the India service. The following are the contractual control areas to complete, not claims of a particular certification or unverified technical configuration.
Identity and access: [COMPLETE: individual staff access, available authentication controls, administrator privileges, least-privilege access, access review and removal, support/operator access logging and shared-workspace permissions.]
Transmission and storage: [COMPLETE: protection of client connections and service connections, stored documents and database records, backup protection, key management, and restrictions on retrieval links.]
Operations and resilience: [COMPLETE: vulnerability and patch management, monitoring, relevant logs and review, backup frequency, restoration checks, separation of customer records and incident-response responsibilities.]
Provider oversight: Verify confidentiality, processing-purpose limits, no general-purpose model training, incident cooperation, approved locations and retention/deletion controls against the actual contracts and settings.
India cyber-security arrangements: [COMPLETE: applicable CERT-In point of contact, reportable-event handling, required time synchronisation, the location and period for covered ICT logs, and monitoring capable of meeting applicable urgent deadlines.]
Deletion and evidence: [COMPLETE: deletion workflow, backup expiry, provider deletion, legal-hold authorisation and review, record-export format, available signing events and any integrity-verification evidence actually supported.]
Incident contacts: Customer contact from Schedule A. TAP operational contact: [COMPLETE MONITORED SECURITY CONTACT AND COVERAGE]. The public privacy mailbox remains dpo@tapagreements.com.
Schedule D Retention retrieval and exit
Completed agreements and signing evidence: Retain for the agreed active-account service and, where the Customer chooses the archive, three calendar years after paid service ends, subject to lawful earlier deletion and specific preservation needs. Authorised archive retrieval is available without a paid subscription or paid reactivation. The service-end confirmation identifies the archive start date.
Source originals: Normal service retention is up to 30 days after delivery of the prepared form for comparison and resolution of conversion issues. A specific unresolved issue or applicable law may require a restricted copy for longer. Source-original backups and provider copies follow the same service limit unless a stated legal requirement applies. Source originals do not automatically enter the three-year archive.
Templates and unfinished agreements: [COMPLETE: active-use period; treatment of abandoned, rejected and unsigned records; any post-service export period; deletion trigger and completion period. These records do not automatically receive the completed-agreement archive.]
Temporary conversion copies: [COMPLETE: purpose and maximum period for temporary text, images, intermediate output, queue files and provider processing copies; how this is reconciled with source-original retention and applicable law.]
Backups: [COMPLETE: backup cycle, expiry period and secure deletion/overwrite treatment for each record category. Identify any retained exception and ensure restoration cannot restore deleted information to ordinary use.]
Security and legally required logs: Retain covered records for the periods and locations legally required. Applicable CERT-In directions require 180 days of ICT logs within Indian jurisdiction. Applicable intermediary rules separately require specified 180-day preservation of removed information and related records, and registration information after cancellation. These duties are not a general instruction to archive every agreement indefinitely.
DPDP transition: When operative and applicable, the DPDP Rules’ security-record and processing-record requirements, including rules 6 and 8, govern covered categories. Rule 8, subrule (3), specifies a minimum one-year period for covered personal data, associated traffic data and processing logs, including processor-held data, followed by the prescribed erasure treatment. Complete the category mapping and reconcile it with continuing archive purposes before those provisions take effect. A short source-file policy must not promise erasure that the law then forbids.
Billing and account administration: Retention for TAP’s own tax, payment, fraud-prevention and legal purposes is addressed in the Privacy Policy and applicable record obligations. Keep it distinct from the Customer’s agreement archive and do not use it to retain unrelated document contents.
Legal holds: Identify the basis, affected records, authorised decision-maker and review date. Limit use and access and release the hold when the reason ends, subject to continuing applicable duties.
Retrieval and expiry notices: [COMPLETE: download/export methods, identity checks, assistance route, notice before an archive expires, and maximum deletion-completion period after a permitted deletion becomes due.]
Account deletion: The India service will not accept production documents until the account and document-deletion process, lawful-retention exceptions and provider handling have been implemented and reflected in this schedule. A published preview is not a substitute for that process.