Privacy
Policy

1. Data Controller

The controller of your personal data is Martia Labs spółka z ograniczoną odpowiedzialnością (limited liability company) with its registered office in Sopot at ul. Aleja Niepodległości 942, 81-861 Sopot, Poland, entered in the Register of Entrepreneurs of the National Court Register kept by the District Court Gdańsk-Północ in Gdańsk, 8th Commercial Division of the National Court Register, under KRS number 0001244962, NIP (tax ID): 5851511387, REGON: 544885885, share capital: PLN 10,000.00.

We have not appointed a data protection officer (DPO). For all matters concerning your data and this policy, please contact us at support@martia.ai.

2. What Martia is

Martia is an AI-powered assistant you talk to about your money. It is available as a mobile app (iOS and Android), a web app (app.martia.ai, martia.ai), and an API, in 6 languages. You chat with Martia in your own language, and answers are based on your real bank transactions.

You are talking to an AI system

You are talking to an artificial-intelligence system, not a human. Martia's answers may contain mistakes and do not constitute professional financial, legal, or tax advice. Before you add a voice recording or an image, we show a short in-app notice explaining how that material is processed.

3. What data we process, for what purpose, and on what basis

Below we describe the categories of data we process — together with the purpose, legal basis (Art. 6 GDPR), retention period, and recipients. You will find the list of providers in Section 5 and the retention details in Section 8.

Account and identity data

• Scope: email address, optionally your first name, and your Auth0 user identifier (the “sub”).
• Purpose: creating and running your account, sign-in, and account-related communication.
• Legal basis: Art. 6(1)(b) GDPR (performance of a contract).
• Retention: for the life of the account.
• Recipients: Auth0 (Okta).

Bank data

• Scope: list of accounts, balances, and transaction history, including account identifiers (such as IBANs), descriptions, and counterparty details contained in transactions.
• Purpose: showing your balance, spending history, and categories, and answering your questions about your finances.
• Legal basis: Art. 6(1)(b) GDPR (performance of a contract). You authorise the bank connection separately by granting bank consent within your account-information service provider's flow.
• Retention: for the life of the account.
• Sources and recipients: depending on the chosen method, Enable Banking (a licensed AIS provider) or Synci and the connectivity provider used for your bank connection. For the Synci Managed pilot for Polish banks, that provider is GoCardless. Google Cloud stores the data in Martia.

Where available, you can choose a Synci connection paid for by Martia (Synci Managed). We provide Synci with your email address and an internal user reference to create a separate managed user for your Martia account. You authorise the bank connection in Synci's portal and the bank's or connectivity provider's flow. You do not need a personal Synci account or subscription. We obtain your account details, balances and transactions from Synci through the connectivity provider you connect through. Account identifiers, including IBANs, help us match your accounts when you change connection providers.

Martia Labs, identified in Section 1, is the controller of this financial data. Synci processes it on our behalf; GoCardless acts as an independent controller for the bank connection. Both are recipients of data needed to provide the connection. Martia has access to every account you connect through its Synci portal, including accounts you add later. There is no separate choice in that portal of which connected accounts to share with Martia. Only connect accounts whose data you want Martia to receive. See the Synci Portal Privacy Notice and the GoCardless Bank Account Data End User Terms, which apply to your connection. Synci's notice also describes its limited activities as a controller for platform security and administration, its subprocessors and international transfers.

If you instead choose to connect your own Synci account, we receive data only for the accounts you authorise Synci to share with Martia. Synci operates that personal account as an independent controller under its privacy policy. Martia is the controller of the imported data in both options and uses it for the purposes above. We store encrypted access credentials for subsequent imports. We do not receive your bank or Synci password.

Google Sheets integration

After you connect your Google account and select your own bank accounts, Martia sends the available transactions, balances and balance history for those accounts to a spreadsheet in your Google Drive. Data is transferred when the spreadsheet is created and during subsequent automatic or manually requested refreshes.

To refresh the spreadsheet, Martia stores your Google OAuth token in encrypted form. The permission covers files created through the integration. You control other people’s access to the created spreadsheet in Google.

Disconnecting the integration in Martia under Settings → Integrations stops further data transfers and removes the stored Google access. It does not delete the created spreadsheet or previously transferred data. The file remains in your Google Drive until you delete it yourself.

AI-assistant connectors

• Scope: the read-only connector tools can return accounts and their balances (with only the last four digits of an IBAN), daily balance history, bank connections (bank name, status, consent end date), transactions including descriptions and counterparty names, category totals, monthly summaries, and net worth including declared assets and liabilities.
• When data flows: only after you connect an AI assistant yourself, sign in to Martia, and approve the OAuth consent screen. The assistant receives data when it calls a tool on your behalf.
• Purpose and legal basis: answering your questions about your finances through the assistant you chose; Art. 6(1)(b) GDPR (performance of a contract).
• Recipients and roles: for connector use, Anthropic (Claude), OpenAI (ChatGPT), or the provider of any other assistant you connect yourself processes the data as an independent controller under its own terms and privacy policy. This is separate from AI model providers, including Anthropic, that Martia engages as processors for in-app chat.
• Martia's MCP logs: for every connector tool call, we record who called, through which assistant, which tool, whether the call succeeded (or was refused for lack of access to Martia) and how long it took. We also record when you connect an assistant and when you disconnect one in Martia. We never record tool arguments or results. We use these records to run and improve the service and to see which assistants people use, as internal service monitoring (including connection notices and a daily summary for our team), based on our legitimate interest (Art. 6(1)(f) GDPR). They are deleted after 90 days. Separately, if a connector tool fails, our technical logs may record which tool failed and the error, so we can diagnose it, again without arguments or results. These logs are kept for up to 12 months, like our other technical logs.
• Disconnecting: you can disconnect an assistant in Martia under Settings → Integrations, which stops its access immediately. You can also disconnect the connector in the assistant's connector settings. This removes Martia from that assistant, so it should stop initiating calls, but access tokens are not revoked at that moment and may remain usable until they expire. Data already sent to the assistant is handled under that provider's terms.

Community forum

• Scope: for every Martia account with a verified email address we create an account on our community forum (community.martia.ai) and share with it your Martia account identifier, email address and app language. We share no name and no financial data; your forum username is neutral and you can change it.
• Purpose and legal basis: signing in to the forum with your Martia account and emailing you summaries of what is happening on the forum; Art. 6(1)(f) GDPR (our legitimate interest in building a community of Martia users).
• Forum emails: the forum sends a summary of popular threads when you have not visited it for a while. Every such email has an unsubscribe link, and you can change your email settings in your forum profile.
• Deletion: deleting your Martia account also deletes your forum account; posts made from it stay on the forum, anonymised. You can delete the forum account on its own in its settings or by writing to support@martia.ai.
• Recipients: the forum runs on our own server in the EU (Google Cloud, region europe-west1); emails are delivered by Resend.

Content you provide

• Scope: chat messages (including images and voice recordings, if you add them), CSV/PDF imports, and notes.
• Purpose: holding the conversation, analysing and categorising your finances, and personalising answers.
• Legal basis: Art. 6(1)(b) GDPR (performance of a contract) and Art. 6(1)(f) GDPR (our legitimate interest in personalising and improving answers — see Section 4).
• Retention: for the life of the account; you can delete individual conversations yourself.
• Recipients: AI model providers routed via OpenRouter (see Section 5) — for chat, context, and categorisation; OpenAI — for transcribing voice recordings; Google Cloud.

Onboarding answers and preferences

• Scope: answers from the onboarding survey and your settings and preferences.
• Purpose: fitting the product to your needs and configuring the app.
• Legal basis: Art. 6(1)(b) GDPR (performance of a contract) and Art. 6(1)(f) GDPR (product fit).
• Retention: for the life of the account.
• Recipients: Google Cloud.

Payments and subscription

• Scope: email address, billing address, and tax identification number (if you provide it).
• Purpose: handling payments, issuing invoices, and accounting.
• Legal basis: Art. 6(1)(b) GDPR (performance of a contract) and Art. 6(1)(c) GDPR (legal obligation — accounting rules).
• Retention: accounting documents for the period required by law (in Poland, 5 years counting from the end of the tax year).
• Recipients: Stripe.

Technical and security logs

• Scope: technical logs, which may include an account identifier and information about the operations performed.
• Purpose: security, abuse detection, and diagnostics.
• Legal basis: Art. 6(1)(f) GDPR (legitimate interest — security and reliability of the service).
• Retention: up to 12 months.
• Recipients: Google Cloud.

Optional product analytics

• Scope: a pseudonymous account identifier and allowlisted usage events. It does not include chat content, transactions, or onboarding answers.
• Purpose: understanding how you use the app so we can improve it.
• Legal basis: our legitimate interest (Art. 6(1)(f) GDPR) in improving how Martia works. Product analytics is enabled by default and links usage events to a pseudonymous account identifier. You can object by turning it off in Settings → Privacy; collection stops immediately. Analytics identifiers are held only in memory for the current app session, without persisting them in cookies or device storage.
• Retention: up to 12 months.
• Recipients: PostHog (EU Cloud).

Optional marketing-site analytics

• Scope: Approximate location, device type, public pages visited, selected clicks, traffic source, campaign parameters and pseudonymous browser identifiers. This does not include bank data, chat messages or form contents.
• Purpose: understanding how the marketing site is used.
• Legal basis: Art. 6(1)(a) GDPR (consent). We ask on the cookie banner. Refusing does not change how the site works. You can change or withdraw analytics and advertising consent independently in Cookie settings in the marketing-site footer. We remember your choices for 180 days.
• Retention: up to 14 months (GA4’s default retention).
• Recipients: Google Ireland Limited / Google LLC (Google Analytics) and PostHog (EU Cloud), only with analytics consent.

Optional advertising and conversion measurement

After we configure and enable the advertising services, and only with your separate advertising consent, Google Ads and Meta Pixel through Google Tag Manager may be used to show you Martia ads and measure their effectiveness. Without that configuration, advertising tags remain inactive.

Advertising signals cover visits and selected clicks on public marketing pages, campaign parameters and ad click identifiers, plus verified Martia subscription purchases: transaction reference, amount, currency, plan and whether the purchase starts a trial. We do not send bank balances, bank transactions, chat messages or form contents to these advertising tools. With your advertising consent, Google may link these visit signals with data from the Google account you are signed in to, including across devices, if you have Google Ads Personalization turned on.

The legal basis is your consent (Art. 6(1)(a) GDPR). Advertising is optional and independent of analytics. You can refuse or withdraw it at any time in Cookie settings, without losing access to the service. Withdrawal stops further advertising measurement and does not affect the lawfulness of earlier processing.

Operational notifications and support emails

• Scope: service notifications sent to a private team chat (e.g. signup, onboarding completed, purchase, account-deletion request) and support correspondence.
• Purpose: operating and running the service correctly and contacting you.
• Legal basis: Art. 6(1)(f) GDPR (legitimate interest — operating the service).
• Retention: cleaned up on a 12-month cycle.
• Recipients: Telegram (internal operational notifications), Resend (email delivery), and authorised team members.

4. Financial profile, memory, and no automated decisions

To answer more accurately, Martia builds a profile of your financial situation from your data, along with a “memory” — it remembers context from earlier conversations to personalise answers. We do this to perform our contract (Art. 6(1)(b) GDPR) and in our legitimate interest in providing a useful, personalised assistant (Art. 6(1)(f) GDPR). You can delete individual conversations in the app at any time.

We do not make automated decisions about you that produce legal effects or similarly significantly affect you within the meaning of Art. 22 GDPR. Martia does not perform credit scoring, does not make credit decisions, and does not provide regulated investment advice.

5. Who we share data with

We do not sell your personal or financial data. We use the following providers as processors and, where applicable, independent controllers. Advertising providers receive only the signals described in Section 3, after the services are enabled and you give separate advertising consent.

The current list of those providers — what each one does, which data it receives, and where it processes it — is on our subprocessors page. We update it before a new provider starts processing personal data.

We conclude the required data-processing agreements with our providers.

6. Transfers outside the EEA

Some providers — especially AI model providers and US-based entities — may process data outside the European Economic Area, including in the United States and in China (Z.ai). Where this happens, we rely on the transfer mechanisms provided for by law: standard contractual clauses or an adequacy decision (including the EU–US Data Privacy Framework, where applicable).

7. Whether your conversations train AI models

We do not use your data to train our own models. We engage AI model providers under API terms that — per their current policies — do not grant them the right to train on customer content. We do not sell data. Bank data and conversation content are not shared with advertising providers.

8. How long we retain data

We keep data only for as long as it is needed:

• Account data, transactions, and content (chat, imports) — for the life of the account; deleted when the account is deleted.
• Technical logs — up to 12 months.
• Analytics data — up to 12 months.
• Raw bank-sync archives — up to 90 days.
• Backups — age out on a cycle of up to 30 days; we do not restore them into production systems without checking for prior deletion requests.
• Accounting documents — for the period required by law (in Poland, 5 years from the end of the tax year).
• Notification emails — cleaned up on a 12-month cycle.

We retain data imported from Synci for the life of the Martia account, including after disconnection or access revocation, to continue providing history and analysis. You can permanently delete that data in Martia earlier. Disconnecting in Martia deletes our stored access credentials and stops imports. Disconnecting a Managed connection also deletes the managed user and its connections and financial data at Synci. Revoking the bank authorisation prevents further collection from the bank. For Managed connections, Synci retains its copy within the history window set for Martia's plan, as described in the Synci Portal Privacy Notice. This is separate from the history already imported into Martia.

9. Your rights (GDPR)

In connection with the processing of your data, you have the following rights:

• Right of access — you may request a copy of the data we process about you.
• Right to rectification — you may request correction of inaccurate data.
• Right to erasure — you may request deletion of your data (right to be forgotten).
• Right to data portability — you may receive your data in a machine-readable format.
• Right to restriction of processing — in certain circumstances.
• Right to object — you may object to processing based on legitimate interest.
• Right to withdraw consent — at any time, where we process data based on consent (e.g. analytics); withdrawal does not affect the lawfulness of earlier processing.

To exercise these rights, write to support@martia.ai or use the in-app option. We confirm receipt within 24 hours and fulfil requests without undue delay, at the latest within one month.

You also have the right to lodge a complaint with a supervisory authority. For Martia, the lead supervisory authority is the President of the Polish Personal Data Protection Office (UODO); you may also contact the authority in your country of residence.

10. Deleting your account and data

You can delete your account and data yourself in the app (Settings → Delete account and data) or at https://martia.ai/delete-account.

Once we receive your request, we block the account, cancel any active Martia subscription, and permanently delete data from our active systems and from our providers: from Auth0, from PostHog, from Google Cloud storage, and we revoke the Enable Banking session. We retain Stripe invoices for the period required by tax law. Backups age out on a cycle of up to 30 days.

If you used Synci Managed, deleting your Martia account also includes deleting the managed user, its connections and its financial data at Synci. Synci removes the deleted financial data from backups within 30 days; records it holds for its own security or legal obligations follow the periods in its Portal Privacy Notice.

For your own Synci account, we delete the data imported into Martia and our stored access credentials, which stops imports. Deleting the Martia account does not delete your Synci account or its data, or cancel a Synci subscription. You can also revoke Martia's access in your Synci settings.

11. Security

We implement appropriate technical and organizational measures to protect your data against unauthorized access, loss, or destruction. All data is transmitted exclusively over encrypted HTTPS connections.

The bank connection operates in read-only mode — we never know your banking password and cannot perform transactions on your account.

12. Cookies and analytics

We use technical cookies and browser storage for sessions and sign-in, and to remember your analytics and advertising choices for 180 days. Marketing-site analytics uses Google Analytics and PostHog only with analytics consent. Advertising cookies are used only when advertising services are enabled and you separately consent. Cookie settings in the marketing-site footer let you change or withdraw either choice. The marketing sites run on their own domains (for example martia.pl, martia.it) and the app on app.martia.ai, so cookies set on one are not visible on the other. When you go from a marketing site to the app, the link carries your advertising choice and the date you made it, so we do not ask again. The app saves it only when you arrive directly from our marketing site. If you have not chosen yet, the app asks on the sign-in, sign-up and onboarding screens, and you can change it in Settings → Privacy. Product analytics in the app is enabled by default, links events to your account and can be turned off in Settings → Privacy. We do not sell data.

13. Changes to this policy

Version 2026-10-26 adds the optional Synci Managed pilot: registration using your email and internal reference, the roles of Martia, Synci and GoCardless, access to every account connected in the portal, and deletion of the managed user.

Version 2026-10-23 describes the community forum account we create for every Martia account: the data shared with the forum, its summary emails and how to stop them, and what deleting your Martia account does to it.

Version 2026-10-22 describes optional imports from your own Synci account: the data involved, controller roles, retention after access ends, and the effects of disconnection and Martia account deletion.

Version 2026-10-08 adds the disclosure about AI assistants you connect yourself: the data their read-only tools can receive, provider roles, what Martia records for every connector tool call (never arguments or results, deleted after 90 days) and logs when a tool fails, what Martia uses those records for, and disconnecting an assistant, including under Settings → Integrations.

Version 2026-10-07 describes how your advertising cookie choice travels from the marketing sites to the app and where the app asks for it.

Version 2026-10-03 changes product analytics to on by default, with an off switch in Settings. Events remain linked to the account. The current account setting replaces the previous consent model and starts enabled.

We will notify you of material changes in advance — in the app or by email — explaining what the change involves. This policy is informational and is not a contract; continued use of the app does not constitute “acceptance” of its contents.

Version 2026-09-03 replaces the document dated 2026-07-11. It adds consent for Google Analytics on the marketing sites.

Version 2026-09-07 replaces the document dated 2026-09-03. The PostgreSQL database moved to Google Cloud SQL in the EU region, so Neon is no longer a processor. Nothing else changed.

Version 2026-09-21 replaces the document dated 2026-09-07. Internal operational notifications moved from company mailboxes to a private team chat delivered through Telegram. User and support emails remain on Resend.

Version 2026-09-22 replaces the document dated 2026-09-21. Transaction categorisation can now be performed by a decision model from TypeSafe, routed through OpenRouter like our other models. It receives the transaction description and the counterparty name — the same text the previous models received; no new category of data leaves the app.

Version 2026-09-23 replaces the document dated 2026-09-22. Section 5 no longer lists providers itself; the list moved to a separate subprocessors page that we keep up to date. That list also names providers the previous version did not: DeepInfra (a host for one of the AI models), OneSignal (push notifications), and RevenueCat and Apple (in-app purchases on iOS).