TAP Agreements is in development and is not yet open for business account registration or document submission. This page explains the proposed Australian Data Processing Addendum. The completed addendum and its schedules must be identified and affirmatively accepted before covered processing starts. Publishing this preview does not create that agreement.
What the addendum covers
The business using TAP decides the purpose of its agreements, what information to request and who may access the results. When the agreement service is available, TAP will handle that information to prepare, complete, deliver and store agreements, provide related support and protect the service. The addendum sets out those responsibilities while preserving each party’s own Australian privacy obligations.
Covered information includes uploaded documents, retained source originals, prepared forms, participant details, responses, signatures, completed agreements and related signing evidence. People concerned may include the business’s staff, signers, representatives and other people identified in its documents. Processing lasts for the agreed service and permitted archive period, subject to lawful earlier deletion and specific preservation requirements. The initial Australian service is for ordinary business forms. It is not offered as a clinical health-records system or for property transactions, wills, powers of attorney or other unsupported special workflows.
Our Australian Privacy Policy separately explains website, account and other personal information handling. The business must have lawful authority for its instructions, give appropriate collection notices and obtain any necessary consent, including for sensitive information. TAP retains its own obligations under applicable law; the business’s instructions cannot authorise unlawful processing.
Limits on use
We process agreement information only for the instructed service, its agreed storage and retrieval, related support, protection of the service and applicable legal duties. We do not sell personal information, use agreement information for advertising or marketing to signers, develop unrelated products from it, or use it to train general-purpose models. We do not permit providers to use agreement information for that training. Signing an agreement does not subscribe anyone to TAP marketing.
Preparation is automated. TAP does not routinely have a person read agreements. Within TAP, only our operator in the United States may access agreement contents when needed to respond to a support issue or investigate a failure, limited to the information needed for that issue. This does not remove legally required handling or the permitted access of the business, its authorised staff and agreement participants. Contracted providers may have authorised support, security or legally required access under appropriate confidentiality and data-protection obligations.
The no-training restriction is separate from retention. This page does not promise that every provider record is immediately deleted or that a provider can never have authorised human access.
Provider schedule
The following providers are selected for the planned Australian agreement service. This schedule describes their functions and established or configured hosting locations. It is not a statement that Australian document intake has opened.
| Provider | Function and information involved | Hosting or processing location |
|---|---|---|
| OVH US LLC, trading as OVHcloud | Application, database and preparation workers; agreement content, account and workspace records, and service records needed for those functions. | Virginia primary and Oregon standby, United States. Provider support and onward handling are described below. |
| Amazon Web Services (AWS) | Document storage, including retained originals, completed PDFs and signing evidence; database backups. | Document storage in Northern Virginia, United States. The backup destination and applicable onward-access arrangements will be confirmed in the completed schedule. |
| OpenAI OpCo, LLC | Automated document preparation using the text, images and instructions needed to prepare forms, and the resulting output. | International processing. The arrangement described here does not establish an Australia-only or US-only processing boundary. |
| Twilio Inc. / SendGrid | Transactional email: recipient details, message text, business or agreement titles, retrieval links and delivery records. The standard completed-copy message links to the agreement rather than attaching its PDF. | Global email endpoint; provider disclosures include United States infrastructure and possible processing beyond the United States as described below. |
This agreement-service schedule is separate from the website providers described in the Privacy Policy. Payment and other account-service providers will be identified with the relevant feature before they receive information.
Provider processing locations
TAP operates from the United States. Its application infrastructure and document storage are in the US locations above. AI preparation, email delivery and provider support can involve additional countries. The information below distinguishes established TAP hosting from provider-published possible processing arrangements, reviewed on 12 November 2026. It does not mean that every agreement is processed in every listed country.
OVHcloud. In addition to TAP’s US hosting, the OVH US data-processing agreement lists potential affiliate processing in Australia, Canada, France, Germany, India, Ireland, Italy, the Netherlands, Poland, Portugal, Singapore, Spain and the United Kingdom, and third-party processing in Finland, France and the United States. These are provider-listed possibilities; they do not establish that each location receives TAP agreement contents. Applicable support and onward access will be identified in the completed service schedule.
AWS. TAP document storage uses the Northern Virginia region. The AWS subprocessor list explains that relevant infrastructure depends on the selected service and region. It separately lists customer-requested support in Australia, Canada, Costa Rica, Egypt, France, Germany, Hong Kong, India, Ireland, Italy, Japan, South Africa, South Korea, Taiwan and the United States. AWS says customer data is shared with support subprocessors only with the customer’s agreement during support. Those support locations are not additional confirmed TAP storage locations.
OpenAI. Its API subprocessor list identifies cloud infrastructure in Australia, Belgium, Brazil, Canada, Denmark, Finland, France, Germany, India, Indonesia, Ireland, Italy, Japan, Malaysia, Mexico, the Netherlands, New Zealand, Norway, Poland, Singapore, South Africa, South Korea, Spain, Sweden, Switzerland, the United Arab Emirates, the United Kingdom and the United States. The Philippines is an additional listed location for conditional moderation and support. Customer-support processing depends on information explicitly shared in a support case. API network delivery can also follow Cloudflare’s global network routing. These are provider-published possibilities, not observed destinations for every TAP request; account settings and the features used affect applicable processing.
Twilio SendGrid. TAP uses SendGrid’s global email endpoint. The SendGrid-specific entries in Twilio’s subprocessor list describe infrastructure in the United States, North America and the European Union. That list does not identify every country applicable to TAP’s route. We are completing that service-specific mapping before Australian agreement processing opens. The regional descriptions are not a promise of US-only delivery or access.
Provider lists can change. We keep this schedule under review and will give appropriate notice of relevant changes. Before covered processing begins, the completed addendum will identify the applicable providers and countries and set out notice and a reasonable objection process for changes. Links to a provider’s wider list do not by themselves authorise unrestricted processing or a new purpose.
Overseas safeguards
Where Australian Privacy Principle 8 applies, we take reasonable steps before overseas disclosure to ensure the recipient does not breach the Australian Privacy Principles in relation to the information, unless a lawful exception applies. Those steps include assessing relevant arrangements and requiring appropriate restrictions on purpose, confidentiality, security, onward processing, retention and deletion, together with assistance for incidents and privacy requests. TAP remains accountable to the extent required by Australian law.
Acceptance of the service is not consent to waive Australian privacy protections. Provider locations and contractual safeguards are separate from a promise of Australian data residency, which the standard service does not offer.
Records and cooperation
Source originals. We keep them for up to 30 days after delivery of the prepared form, to compare what the business submitted with what TAP produced and resolve questions or conversion errors. Longer retention is limited to a specific unresolved issue for which the original is needed, or a legal requirement. The retained copy is restricted to that purpose, the need is reviewed and the copy is deleted when that need ends. An authorised administrator may request earlier deletion. The same limit and exceptions apply to source-original backup and provider copies. This is not a deadline for complaints or statutory rights. Source originals are not part of the three-year archive.
Completed agreements and signing evidence. The planned Australian service keeps these records while the business account is open and offers optional continued storage for three calendar years after cancellation takes effect at the end of paid service. The cancellation or subscription-ending refund confirmation identifies the date. This archive is a customer benefit for finding and retrieving completed records, not for TAP’s marketing or unrelated use.
Continued storage is optional. An authorised administrator can opt out of the archive or request earlier deletion through support@tapagreements.com, subject to applicable law, other people’s rights and specific lawful preservation needs. Individuals can also make privacy requests directly to TAP. We explain any lawful reason that prevents requested deletion and restrict information retained for that reason to the permitted purpose. Cancellation alone is not a deletion instruction, and turning off renewal does not start the archive period before paid service ends.
Authorised viewing, downloads and exports during the included archive period do not require an ongoing subscription or paid reactivation. Workspace permissions and reasonable verification apply. Signers have access only to records they are authorised or legally entitled to obtain. The Australian record schedule explains coverage and the remaining delivery details to be completed before intake.
Temporary processing copies are distinct from source originals kept for comparison. Drafts, unfinished agreements, unused templates, temporary uploads, logs, backups and provider copies have their own purposes and periods; the archive does not give every copy a three-year retention period. The completed schedule will specify deletion-completion and backup-expiry periods before Australian document intake begins, consistently with the source-original limit above. Backup information awaiting deletion stays protected and restricted from ordinary use, and restoration must not reverse a valid deletion instruction.
Australian launch will wait until account deletion and the associated data-deletion process are available. That process will remove the account and delete its associated agreement data, including source originals, templates, completed agreements and signing evidence, subject to specific lawful preservation requirements. Any information that must be retained is restricted to that purpose and the reason is explained.
When information is no longer needed for a permitted purpose, we take the steps required by applicable law to destroy or de-identify it, subject to applicable exceptions. The three-year archive is a service benefit, not a universal Australian statutory retention period or permission to disregard earlier deletion duties.
Security and incident cooperation
The service requires reasonable safeguards appropriate to the information, including access restrictions, protection in transmission and storage, incident handling and controlled deletion. The completed addendum will describe verified measures for the agreed service.
The addendum also covers access and correction requests, privacy complaints and reasonable information to assess compliance. TAP will notify an affected business without undue delay after becoming aware of a breach affecting its agreement information, provide available information and updates, and cooperate with containment, investigation and legally required notifications. TAP fulfils its own duties when coordinating with the sending business. Australian statutory assessment and notification requirements apply where relevant.
Before the addendum takes effect
Before accepting Australian agreement information, we will complete the provider and country details applicable to the service, the safeguards and security schedule, the record retrieval and deletion schedule, and the provider-change notice and objection process. The business will receive the completed addendum and schedules for affirmative acceptance. This preview supplies the current planned policy and available provider facts; it is not the completed processing contract.
Contact TAP
Ardor Service LLC doing business as TAP Agreements
1034 N. Madison Ave., Pasadena, CA 91104, United States
Privacy and addendum enquiries: dpo@tapagreements.com
General support: support@tapagreements.com
Telephone: +1 626-630-0096