Data Processing Agreement (GDPR)

Scope and acceptance

This Data Processing Agreement (DPA) is in force from 18 November 2026. It forms part of the Fintable Terms of Service and applies automatically, on every plan, to every customer established in the EU/EEA or whose use of Fintable is otherwise subject to the GDPR. Nothing needs to be signed; a countersigned copy is available on request at [email protected].

Fintable's privacy notice describes its own processing as a controller, and its subprocessor register lists the suppliers in Annex 3.

1. Parties, scope and roles

Fintable: Fintable LLC, Ukraine (ТОВ «ФІНТЕЙБЛ»), company registration number 45534002, Larysy Rudenko St, 6A, Suite 58, Office 1, Kyiv, 02141, Ukraine. Data-protection and incident contact: [email protected].

Customer: the person or legal entity that holds the Fintable account, as identified by its account and billing details. The Customer's account owner is its privacy and incident contact unless it designates another one to [email protected].

This agreement supplements the Fintable Terms of Service for the Customer's Primary Workspace and the Workspaces it owns or manages, including Workspaces created for the Customer's clients. "Customer Personal Data" means personal data Fintable processes on the Customer's behalf through that service, including relevant support, diagnostic and recovery copies. GDPR terms have their meanings in Regulation (EU) 2016/679.

Fintable acts as processor where the Customer determines the purposes and essential means of processing. Where the Customer processes on a client controller's instructions (for example, an accounting firm working for a client), Fintable acts as its subprocessor; the Customer must first obtain the controller's authorization and ensure that the instructions and obligations flow through the processing chain. Roles are recorded per activity in Annex 1; a Customer is not presumed to be a processor for every activity.

Fintable's separate controller activities for its business contacts, invoicing and independently determined security or legal obligations are described in its privacy notice. That distinction does not permit Fintable to repurpose client banking data or remove support processing performed on the Customer's behalf from this agreement.

2. Instructions and confidentiality

Fintable shall process Customer Personal Data only on documented instructions from the Customer, including instructions about transfers. Instructions comprise this agreement, its completed annexes, authorized service settings and subsequent written instructions from the designated contact. If EU or Member State law requires processing outside those instructions, Fintable shall inform the Customer beforehand unless that law prohibits notification for important public-interest reasons. Other legal demands are handled under section 7 and the applicable transfer instrument.

Fintable shall immediately inform the Customer if, in its opinion, an instruction infringes the GDPR or other EU or Member State data-protection law, and suspend the affected instruction pending clarification. It shall notify the Customer if it cannot comply with this agreement. The Customer shall provide lawful instructions, required notices and legal bases, and maintain authority to disclose the data; bank authorization alone does not establish every GDPR legal basis or international-transfer safeguard.

Fintable shall restrict access to authorized personnel who need it for the instructed service and are bound by contractual confidentiality or an appropriate statutory duty. These duties survive the end of their access. Fintable shall not sell Customer Personal Data, use it for advertising or unrelated product development, or permit general-purpose AI model training on it.

3. Security and assistance

Fintable shall implement and maintain measures appropriate to the risks under Article 32 GDPR, including confidentiality, integrity, availability, resilience, recovery and regular evaluation of safeguards. Annex 2 specifies the measures. Material reductions in the agreed protection require prior notice and an equivalent protective replacement.

Taking account of the nature of processing, Fintable shall assist the Customer through appropriate technical and organizational measures with data-subject requests. It shall promptly pass requests concerning Customer Personal Data to the Customer and shall not respond substantively except on instructions or as legally required. Requests concerning Fintable's own controller activities remain Fintable's responsibility.

Taking account of the nature of processing and information available to it, Fintable shall assist with security, breach notification, data-protection impact assessments and prior consultation under Articles 32–36 GDPR. Where the Customer is a processor, it shall pass relevant information and assistance to its client controller without delay.

4. Personal-data breaches

Fintable shall notify the Customer without undue delay after becoming aware of a personal-data breach affecting Customer Personal Data. It shall not wait for a completed investigation. The notice shall provide, as information becomes available, the nature of the breach, affected data and data-subject categories and approximate numbers, a contact, likely consequences, and measures taken or proposed to contain and remedy it. Missing information shall follow in stages without undue delay.

Fintable shall investigate, preserve relevant evidence, mitigate harm and cooperate with the Customer. The Customer or relevant controller decides on notifications to authorities and individuals, unless law independently requires Fintable to notify. Fintable shall keep the Customer informed of material developments and corrective action.

5. Subprocessors and AI

The Customer gives general written authorization for the subprocessors and activities listed in Annex 3. Fintable shall bind each subprocessor by a written contract imposing the same data-protection obligations as this agreement, insofar as applicable to the subcontracted processing, verify sufficient guarantees, and remain fully liable to the Customer for its subprocessor's performance of those obligations.

Fintable shall give at least 30 calendar days' prior written notice of a proposed addition or replacement, by email to the Customer's account owner and in the subprocessor register, including identity, purpose, data, countries and applicable safeguards. Where a replacement is urgently needed because a subprocessor fails or for security reasons, it may take effect sooner, with notice as soon as possible. The Customer may object on reasonable data-protection grounds during that period. Fintable shall work to resolve the objection or offer a suitable alternative. If no compliant alternative is agreed, the Customer may terminate the affected service and receives a prorated refund of prepaid fees for the remaining period; section 8 applies.

Fintable shall provide relevant subprocessing terms and compliance information on request, with proportionate redactions protecting unrelated confidential information, without withholding information necessary to demonstrate compliance.

AI position: the standard service does not provide an account-wide exclusion from Fintable's internal AI processing covering Workspaces, support, diagnostics, embeddings and engineering assistance. Avoiding optional AI features or disconnecting a customer-selected AI assistant does not establish such an exclusion. AI processing of Customer Personal Data is confined to the instructed purposes and the AI providers listed in Annex 3, under the terms identified there. Customers that require an AI-free arrangement should ask about the Enterprise plan.

6. Information and audits

Fintable shall provide the information necessary to demonstrate compliance with Article 28 and this agreement, including relevant processing records, locations, security evidence, subprocessor details, transfer assessments and deletion evidence. It shall allow and contribute to audits and inspections by the Customer, the relevant controller or an auditor mandated by them.

Audits shall use reasonable notice, confidentiality and security arrangements that protect other customers without preventing effective verification. Urgent incidents, credible noncompliance and regulator requirements permit expedited access. Existing independent reports may help an audit but do not replace statutory inspection rights. Fintable shall remedy substantiated deficiencies and provide evidence of remediation.

The standard service is not EU/EEA-only. Fintable's servers are hosted in Ukraine, and suppliers listed in Annex 3 process data in other countries, including the United States. Fintable shall permit a transfer or third-country remote access only on documented instructions and with a valid GDPR Chapter V mechanism covering the particular recipient and processing. Neither encryption alone, a provider's European headquarters nor bank consent substitutes for that mechanism.

Annex 4 applies the EU Standard Contractual Clauses for the transfer from the Customer to Fintable, with module selection determined by actual roles. For onward transfers to suppliers, Fintable relies on an applicable adequacy decision (including, for certified US recipients, the EU-US Data Privacy Framework) or the Standard Contractual Clauses in the supplier's data processing terms, as identified for each supplier in Annex 3. Fintable's transfer impact assessment is summarized in Annex 5.

Fintable shall assist with transfer-impact assessments and provide information about its own and onward processing. It shall promptly notify the Customer of an inability to comply, material changes affecting safeguards, and legally binding disclosure requests or direct public-authority access where permitted. It shall review legality, challenge unlawful or disproportionate demands where there are reasonable grounds, seek permission to notify where notice is prohibited, and disclose only what it is legally required to disclose, consistently with applicable SCC obligations.

Affected transfers shall be suspended if adequate safeguards cannot be ensured. The parties shall pursue corrective measures or terminate the affected processing and apply the SCC return and deletion requirements. The SCCs prevail over conflicting terms of this agreement or the Terms of Service.

8. Duration, return and deletion

This agreement continues while Fintable processes Customer Personal Data, including during return or deletion. At the end of the relevant service, or on a lawful instruction, Fintable shall, at the Customer's choice, return the data in an agreed usable format and delete remaining copies, or delete the data, unless EU or Member State law requires storage.

Annex 2 specifies the deadlines for active records, support and investigation copies, logs and backups. Retained copies shall remain protected, inaccessible for ordinary use and used only for the permitted retention or recovery purpose. Where a backup is restored, deletion instructions shall be reapplied before ordinary processing resumes. Fintable shall confirm completion on request and identify any lawful exception, its legal basis, safeguards and expiry. Routine account deletion or disconnection is not confirmation that all copies have been erased.

9. Precedence

For data-protection matters, the order of precedence is applicable mandatory law, the applicable SCCs, this agreement and its annexes, then the Terms of Service. Nothing limits statutory data-subject remedies, supervisory-authority powers, or SCC liability, jurisdiction or third-party beneficiary rights. The Terms' liability limitations and arbitration provisions cannot override those rights or the SCCs.

This agreement applies where the GDPR governs the Customer's processing of Customer Personal Data. It is governed by the law of the EU Member State in which the Customer is established or, if the Customer is not established in the EU/EEA, the law of Ireland, without restricting any mandatory forum or SCC rights. Where the Customer is not established in the EU/EEA, the supervisory authority is determined under Clause 13 of the SCCs. Changes to the standard DPA will be notified in advance; changes that reduce protection require the Customer's agreement or a right to terminate the affected processing.

Annex 1 — Processing description (SCC Annex I)

  • Exporter: the Customer identified in section 1. Importer: Fintable LLC, Ukraine, as in section 1.
  • Covered service: the Customer's Primary Workspace and the Workspaces it owns or manages. Where a Workspace is held for a client, the Customer keeps a record of the client controller and the scope of its instructions.
  • Roles: for activities where the Customer determines purposes and essential means, Customer = controller and Fintable = processor. For activities performed solely on a client controller's instructions, Customer = processor and Fintable = subprocessor.
  • Subject matter and purpose: obtaining bank data authorized by the account holder, maintaining Workspace-specific records, delivering those records to the destinations the Customer selects (spreadsheets, the Fintable API, connected AI assistants), and necessary support, security and recovery.
  • Operations: collection, transmission, storage, organization, retrieval, account and transaction normalization, customer-directed categorization, authorized API disclosure, troubleshooting, backup, restoration and deletion. AI assistance is limited by section 5 and Annex 3.
  • Data subjects: account holders and authorized representatives; employees, directors, sole traders, customers, suppliers, payees, payers and other identifiable persons appearing in bank records or support material; authorized Workspace users.
  • Data: names and business/contact details; account identifiers including IBANs where supplied; balances, dates, amounts, currencies, transaction descriptions, counterparties and categories; authorization and connection identifiers and service tokens; Workspace membership and access information; relevant support content, timestamps, device/network identifiers and diagnostics. For connections through open-banking providers, Fintable does not receive bank-login credentials: account holders authenticate on their bank's own pages. Some direct bank integrations (for example FinTS, or bank API tokens) require Fintable to store the account holder's bank login, PIN or token, encrypted.
  • Sensitive data: transaction descriptions or support attachments may incidentally reveal Article 9 or Article 10 data. Such data is not deliberately requested; the Customer is responsible for any additional legal basis it requires.
  • Frequency and duration: recurring collection and storage while connections and the service are active; retention and deletion under section 8 and Annex 2.
  • Supervisory authority: the authority of the EU Member State in which the Customer is established, subject to Clause 13 of the SCCs.

Annex 2 — Security measures and retention (SCC Annex II)

  1. Access and separation: authenticated users, Workspace roles and explicit API grants; staff access on a need-to-know basis under confidentiality duties; controlled privileged access, access review and revocation.
  2. Transmission and storage: encrypted connections to external services and protected integration secrets; encrypted production storage and backup media. Fintable must process readable data to deliver the service; this is not end-to-end encryption that prevents Fintable access.
  3. Operations: service and error monitoring, vulnerability management, security updates, change control and incident response, with minimized and access-restricted diagnostic data.
  4. Recovery: encrypted backups, regular restore verification and documented recovery procedures.
  5. Support and development: production copies can exist in investigation, development and recovery environments. These remain in scope of this agreement.
  6. Data-subject rights: a process to locate, export, correct, restrict and erase data and to pass instructions to subprocessors.

Retention and deletion:

Data / copy Retention Erased
Live Workspace and financial records While the service is used. On request before termination, an export in CSV or JSON. Within 30 days after termination or a deletion instruction.
Application, API, MCP and access logs (search index and raw archive) 90 days. Automatically after 90 days.
Detailed outbound-provider request logs 2 days. Automatically after 2 days.
Database backups Rolling copies for recovery. Within 60 days after the live records are erased.
Development, support and recovery copies Only while needed for development, investigation or recovery. Deleted when no longer needed.
Support correspondence and investigation records For the customer relationship and as long as needed to establish, exercise or defend legal claims. When no longer needed for those purposes.

Annex 3 — Subprocessors, locations and transfer safeguards

This list matches Fintable's subprocessor register. Changes follow section 5.

Supplier Processing Locations Terms and transfer safeguard
Cloudflare, Inc. Website delivery, security and traffic filtering; network identifiers, requests and responses Global network, including the United States Cloudflare DPA: EU-US Data Privacy Framework; SCCs (Modules 2/3)
BunnyWay d.o.o. (Bunny.net) Delivery of the Ukrainian website Slovenia (EU); global delivery network Bunny.net terms; established in the EU
DigitalOcean, LLC Storage of encrypted off-site database backups Frankfurt, Germany DigitalOcean DPA: EU-US Data Privacy Framework; SCCs
Tailscale Inc. Administrative networking; metadata and encrypted relayed traffic Canada, Germany, United States, United Kingdom Tailscale DPA: SCCs (Modules 2/3)
Google LLC (Google Workspace) Support email, attachments and correspondence As stated in Google's data processing terms, including the United States Cloud Data Processing Addendum (accepted 18 November 2026): SCCs
AC PM LLC (Postmark) Service and onboarding email delivery United States Postmark DPA (incorporated in its Terms of Service since 27 September 2021): SCCs
Functional Software, Inc. (Sentry) Browser and server error monitoring; diagnostic context may contain personal or financial information United States Sentry DPA (accepted 18 November 2026): EU-US Data Privacy Framework; SCCs (Modules 2/3)
Anthropic, PBC Primary provider for AI features, support drafting and attachment interpretation, category-rule assistance; engineering, support and security assistance United States and other countries Anthropic DPA (incorporated in its Commercial Terms): SCCs (Modules 2/3)
OpenAI, L.L.C. Support investigation, search embeddings, drafting, engineering assistance; fallback for AI features United States and other countries OpenAI Data Processing Addendum (signed 18 November 2026): SCCs

Fintable's own servers are hosted in Ukraine, except where an agreement or law requires otherwise (for example, data from Akoya connections is hosted in the United States).

Bank-connection providers and customer-selected destinations: bank data reaches Fintable through the provider of the connection the account holder chooses (Plaid, GoCardless Bank Account Data, Enable Banking, Akoya, SnapTrade or a direct bank integration), which acts under its own terms with the account holder. Spreadsheets, Notion and AI assistants the Customer connects receive data on the Customer's instructions under the Customer's own terms with them. They are not Fintable subprocessors.

Annex 4 — SCC selections

  • Instrument: the unmodified Standard Contractual Clauses in the Annex to Commission Implementing Decision (EU) 2021/914, incorporated by reference, where applicable to the transfer.
  • Modules: Module Two (Customer as controller, Fintable as processor) and Module Three (Customer as processor, Fintable as subprocessor), each applied only to the activities recorded for it in Annex 1.
  • Clause 7: docking clause included.
  • Clause 9(a): Option 2, general written authorization, with 30 calendar days' advance notice; Annex 3 is the current list.
  • Clause 11(a): optional independent dispute-resolution language not selected.
  • Clause 13: the supervisory authority of the EU Member State in which the Customer is established; where the Customer is not established in the EU, the authority of the Member State in which its Article 27 representative is established or, if it has none, of the Member State where the data subjects concerned are located.
  • Clause 17: Option 2 — the law of the EU Member State in which the Customer (data exporter) is established; where that law does not allow for third-party beneficiary rights, the law of Ireland.
  • Clause 18(b): the courts of that same Member State.
  • Annexes: SCC Annex I is Annex 1 above, Annex II is Annex 2, and the subprocessor list is Annex 3.
  • Clause 14: Fintable's transfer impact assessment is summarized in Annex 5.

Annex 5 — Transfer impact assessment (summary)

Fintable's servers are in Ukraine, which has no EU adequacy decision, so the Standard Contractual Clauses apply. Fintable has assessed Ukrainian law and practice under Clause 14. Ukrainian law requires a court ruling for access to bank and personal data and for interception, and Ukraine is bound by the European Convention on Human Rights and Council of Europe Convention 108. Under martial law, in force since February 2022, some judicial powers in criminal investigations may be exercised by prosecutors; Fintable discloses that risk. Fintable has never received a government request for customer data. Customer data is encrypted at rest and in transit, with an encrypted backup in Germany, and Fintable will challenge unlawful requests and notify affected customers where permitted. The assessment is reviewed at least every 12 months. The full assessment is available on request at [email protected].

Representatives

  • EU representative (Article 27 GDPR): Isa Hasenko, Larysy Rudenko St, 6A, Suite 58, Office 1, Kyiv, 02141, Ukraine; contact [email protected].
  • UK representative (Article 27 UK GDPR): Fintable UK Ltd, company no. 13490776, 20 Wenlock Road, London, England, N1 7GU.
Language / Idioma
Moneda
Formato de números