Skip to main content

Data Processing Agreement

Last updated: 2026-05-23

Beta notice. This DPA is a working draft pending legal review before the Service exits closed beta. Closed-beta participants are governed by a manual data processing schedule attached to the engagement agreement.

1. Parties and scope

This Data Processing Agreement ("DPA") forms part of the Terms of Service between Exit Advisory Group Pty Ltd ("Processor") and the organisation accepting the Terms ("Controller"). It governs the processing of personal information that Controller submits to or generates via the Service.

2. Processing details

  • Subject matter: processing of personal information to deliver the Service.
  • Duration: for as long as Controller maintains an active account, plus the retention period in the Privacy Policy.
  • Nature and purpose: AI-assisted generation of broker artefacts (valuations, IMs, add-back schedules) from financial and intake data.
  • Categories of personal information: account holder details, seller representatives' details, buyer recipients' emails, financial data sourced from connected accounting systems (Xero, QuickBooks Online, MYOB) and uploaded statements, CRM records imported from Controller's CRM, and call recordings and meeting transcripts where those features are used.
  • Categories of data subjects: Controller's personnel, sellers' principals and personnel, buyers receiving share links.

3. Processor obligations

  • Process personal information only on Controller's documented instructions, which include accepted Terms and configured features.
  • Ensure personnel authorised to access the data are bound by confidentiality.
  • Implement appropriate technical and organisational measures to secure the data (Section 5).
  • Engage sub-processors only as listed in Section 6 and notify Controller of additions at least 14 days in advance.
  • Assist Controller in responding to data subject requests, data breach notifications, and regulator inquiries.
  • On termination, return or delete personal information in line with the Privacy Policy unless retention is required by law.

4. Controller obligations

  • Have a lawful basis for the data submitted to the Service, including consent or authorisation from sellers whose financial information is connected.
  • Not submit special-category data (health, biometric, religious) through the Service.
  • Be responsible for data subject notices to sellers and buyers as required by the Privacy Act 1988 (Cth) and the Australian Privacy Principles.

5. Technical and organisational measures

  • Encryption in transit: all connections use TLS 1.2+.
  • Encryption at rest: credentials for all connected services encrypted with AES-256-GCM and never readable back through the application; Supabase storage and DB encrypted at rest.
  • Tenant isolation: Postgres row-level security enforced on every tenant-scoped table.
  • Access control: magic-link authentication; role-based access (owner / admin / member / viewer).
  • Audit logging: append-only audit_events table (UPDATE/DELETE blocked by database trigger).
  • Backups: Supabase point-in-time recovery retained per provider defaults.
  • Vulnerability management: dependency scanning and periodic internal security review.
  • Incident response: data breach notification within 72 hours of confirmation.

5.1 Support access by Processor personnel

Processor's personnel have no standing access to Controller's workspace. To resolve a support request, an authorised platform operator may open a support session into the workspace that is (a) limited to 60 minutes, (b) read-only, (c) opened only with a recorded reason and, where applicable, a ticket reference, and (d) logged in Controller's append-only audit trail for every request made. Controller's owners and administrators are notified when a session starts and when it ends, and may end it at any time. Financial statements, uploaded documents and data-room files are excluded from the scope of a support session.

6. Sub-processors

This list is generated from the same declaration the application uses, so it cannot fall behind the integrations actually in the product.

6.1 Platform

In the path for every customer.

VendorPurposeLocation
SupabaseDatabase, authentication and file storageSydney, Australia (ap-southeast-2)
VercelWeb hosting and edge networkSydney, Australia (syd1 region); pages pass through Vercel's global edge network on the way to you
InngestBackground job executionUnited States
UpstashRate limiting (Redis)Sydney, Australia
SentryError monitoring. Receives error reports tagged with your user and workspace ids only; request bodies, cookies, link tokens, emails, ABNs, TFNs and phone numbers are removed before sending, and there is no session replayUnited States
PostHogProduct analytics. Receives page views without query strings, masked button clicks and a short list of named product events, identified by user and workspace id only; no IP address is sent, no session recording, no form input, and Do Not Track is honoured. Public share, portal and signing pages are not trackedAs set for the project (EU or United States)

6.2 Engaged by us

Used only where the corresponding feature is used. Where Controller supplies their own API credential, the relationship is theirs and the vendor processes on their instructions rather than ours.

VendorPurposeLocation
AnthropicAI processing (Anthropic API) for drafting, analysis and reading documents, including client data, and public web lookupsUnited States
ResendTransactional and campaign email deliveryUnited States / European Union
TwilioOutbound calling and SMS, including call recordingsUnited States
FathomMeeting recording, transcription and summariesUnited States
DeepLMachine translation of listings, teasers, information memoranda and buyer emails, where switched onEuropean Union
PerplexityWeb research on businesses and marketsUnited States
DataForSEOSearch visibility and backlink data for market analysisUnited States
Bright DataPublic web and review data collectionUnited States / Israel
Google (Maps Platform)Business location and review lookupsUnited States
Google (Search Console)Search performance data for a connected domainUnited States
ElevenLabsSpeech synthesis for generated mediaUnited States
fal.aiImage and video generation for marketing artefactsUnited States
Google GeminiGrounded web search for IM market research (industry and region only)United States
FirecrawlReading public web pages to confirm market research figuresUnited States
StripeSubscription billing and payment processingUnited States / Australia
CreditorWatchCredit and ABN checks on businesses and directorsListed for transparency; not yet enabled, so no data is sent.Australia
FrankieOneIdentity verificationListed for transparency; not yet enabled, so no data is sent.Australia
BusinessesForSaleListing syndicationListed for transparency; not yet enabled, so no data is sent.United Kingdom

6.3 Connected by Controller

Controller's own systems, connected at their direction. Data moves principally from these systems into the application; they are listed because personal data crosses the boundary, not because we engage them.

VendorPurposeLocation
XeroAccounting data read from a connected organisationAustralia / New Zealand
QuickBooks Online (Intuit)Accounting data read from a connected company fileUnited States
MYOBAccounting data read from a connected company fileAustralia
PipedriveCRM records imported and kept in syncEuropean Union / United States
GoHighLevelLeads from the customer's outbound funnel imported as CRM contactsUnited States
Pinch PaymentsCard and direct-debit payment of the customer's invoices, through their own Pinch accountAustralia
Employment HeroStaff, pay, leave and roster data read from a seller's payroll, for a sale's due diligenceListed for transparency; not yet enabled, so no data is sent.Australia
DeputyStaff, rostered shifts and leave read from a seller's rostering system, for a sale's due diligenceListed for transparency; not yet enabled, so no data is sent.Australia
Tanda (Workforce.com)Staff, rosters, leave and payslip totals read from a seller's rostering system, for a sale's due diligenceListed for transparency; not yet enabled, so no data is sent.Australia
Google DriveDocuments imported into a deal at the user's directionUnited States
Mailchimp (Intuit)Name, email, organisation, state and buyer criteria of contacts with recorded marketing consent, sent to the customer's own audience at their directionUnited States
DropboxDocuments imported into a deal at the user's directionUnited States
Microsoft (SharePoint)Documents imported into a deal at the user's directionPer the customer's Microsoft 365 tenancy
Microsoft 365Mailbox, calendar and SharePoint access for connected users (one consent)Per the customer's Microsoft 365 tenancy
Google WorkspaceGmail and Google Calendar access for connected users: email synced against the CRM, send-from-app, meetings and booking links (one consent)Per the customer's Google Workspace configuration
BasiqBank activity a seller chooses to share through open banking (Consumer Data Right), to verify revenueAustralia

Cross-border transfers to the United States are subject to standard contractual protections in our agreements with each sub-processor.

7. Data breach

We will notify Controller without undue delay and at the latest within 72 hours of confirming a personal data breach. Notice will describe the nature of the breach, categories and approximate number of data subjects, likely consequences, and measures taken or proposed.

8. Termination

This DPA terminates when the Terms of Service terminate. On termination we will return or delete personal information per the retention provisions in the Privacy Policy.