Skip to main content

Privacy Policy

Last updated: 19 November 2026

Published by Diip Solutions OÜ, registry code 17527757, Tallinn, Estonia.

Who we are

ProcuLink is a product operated by Diip Solutions OÜ, registry code 17527757, registered at Uus-Sadama tn 15-2, 10120 Tallinn, Estonia. In this policy, "ProcuLink", "we", "us", and "our" refer to Diip Solutions OÜ as operator of the ProcuLink platform at proculink.eu, which processes business documents such as invoices, purchase orders and delivery notes for businesses. ProcuLink is a service for business and professional use; it is not offered to consumers.

Our role: controller or processor

We are the controller for the personal data we need to run ProcuLink as a business: visits to this website, the accounts of the people who sign in, billing and invoicing records, our own product analytics and error monitoring, security logs, and the messages you send us. This policy describes that data.

We are normally a processor for the personal data inside the documents our customers send us and the files we make from them, and in the records they keep in their workspace. Our customer decides why that data is processed; we process it on their instructions, under the Data Processing Addendum. If your details reached us that way — for example, you are a contact named on an invoice — the organisation that sent the document is the controller, and requests about that data are best made to them. If you contact us instead, we pass the request on and help them answer it.

What data we collect

  • Account data — name, work email, organisation name, collected via Clerk authentication on sign-up.
  • Document data — the documents you send us, such as invoices, purchase orders and delivery notes; the data we read from them; and the files we generate from them. When a document reaches us by email we also keep the address it was sent from, and the text of the message if it has no attachment we can read. These documents can carry personal data: contact names, email addresses, phone numbers and postal addresses, and bank account details such as IBAN and payment references.
  • Workspace records — the flows, destinations and lookup lists you set up, and a record of who checked, changed or sent each document.
  • Usage data — page views, feature interactions, error events, and the site or campaign that brought you here, collected via product analytics.
  • Billing data — subscription plan and status, handled by Stripe. We never store your card numbers or payment credentials.
  • Connection details — the addresses and credentials you give us for collecting documents from your systems and delivering files to them, such as a mailbox, a file server, a storage bucket or a web address. Credentials are encrypted at rest.

For the data we control, each use and the GDPR legal basis we rely on for it:

  • Running your account and the service — signing you in, operating your organisation's workspace, and support. Basis: performance of our contract with your organisation (Art. 6(1)(b)), and, for the people your organisation adds as users, our legitimate interest in providing the service they use for work (Art. 6(1)(f)).
  • Service emails — such as notifications about your documents, billing receipts and notices about your account. Basis: performance of our contract (Art. 6(1)(b)).
  • Billing, invoicing and tax records. Basis: performance of our contract (Art. 6(1)(b)), and our legal obligation to keep accounting records (Art. 6(1)(c)).
  • Keeping the service secure and working — error monitoring, security and access logs, and preventing abuse. Basis: our legitimate interest in a secure, reliable service (Art. 6(1)(f)).
  • Product analytics in your browser — only if you accept analytics cookies in the cookie banner. Basis: your consent (Art. 6(1)(a)). You can withdraw it at any time: clear this site's cookies and stored data in your browser, and the banner asks again.
  • Pseudonymous service events recorded by our servers — for example, that a workspace was created, sent a document or changed plan. Basis: our legitimate interest in understanding how the product is used, so we can improve it (Art. 6(1)(f)).
  • Answering enquiries and demo requests. Basis: our legitimate interest in responding to you, or steps you asked for before entering a contract (Art. 6(1)(f) and 6(1)(b)).
  • Meeting legal obligations and handling legal claims. Basis: legal obligation (Art. 6(1)(c)) and our legitimate interest in establishing or defending legal claims (Art. 6(1)(f)).

Where we rely on legitimate interests, you can object, as described under "Your rights" below. We do not sell your data to third parties. We do not use the content of your documents to train AI models.

Data storage and residency

These providers hold your document files, the database, and the API that serves them:

  • File storage: Cloudflare R2 (EU-region bucket)
  • Database: PostgreSQL hosted on Neon (EU region)
  • API hosting: Railway (EU region)
  • Error monitoring: Sentry (EU region instance)
  • Frontend: Vercel (global CDN — document files do not pass through it)

Some processing happens outside the EEA, under Standard Contractual Clauses. These providers are not a rare exception — they sit on the normal path a document takes:

  • Authentication: Clerk (US-based, EU data residency available on request)
  • AI document extraction and mapping suggestions: OpenAI (US) — receives the content of your documents, unless we have turned AI extraction off for your organisation
  • Payments: Stripe (US, EU establishment) — billing data only, no document content
  • Email in and out: Postmark (US) — carries documents emailed to your ProcuLink address, and the files we email to the recipients you set, as attachments

If you turn on phone alerts, we keep the push address your browser gives us for that device until you turn them off or sign out. Each alert goes through your browser's push service, run by Google, Apple, Mozilla or Microsoft depending on your device. It is encrypted, and it holds no document content: only a count, a fixed sentence such as "2 documents need you", and a link to a ProcuLink page.

Turning AI off. If you do not want your documents sent to OpenAI, email support@proculink.eu and we will turn AI extraction off for your organisation and tell you when it is done. It is not a setting in the product; we switch it on our side. With it off, nothing from your documents reaches OpenAI: only our own readers are used, documents they cannot read are not read, and AI suggestions are not offered. It does not change where your files are stored.

Where your data is stored and the route it travels to reach its destination are two different questions. The outbound network path is chosen by our hosting provider and is not pinned to a region by us, so we cannot tell you today which country an outbound delivery leaves from. The Security page explains this in full.

How long we keep data

  • Workspace data — the documents you send us, the data we read from them, the files we generate, and your flows and settings — is kept for as long as your account exists. There is no automatic age limit on it today.
  • After a subscription ends or a Trial expires, nothing is deleted automatically. Your workspace stays readable, so you can sign in and view or download what you have processed for as long as it exists. There is no fixed export window: it stays until you ask us to delete it — see "Deleting your data" below.
  • History — the record of what happened to each document, and of changes made in the workspace — is deleted automatically once it is 180 days old. The documents themselves stay.
  • Your sign-in account is held by our authentication provider while your account exists, and is removed when you ask us to delete your account.
  • Billing and tax records are kept for as long as accounting law requires, including after an account is deleted.
  • Backups. Our database provider keeps a rolling point-in-time history of the database so it can be recovered after a failure. Deleted data drops out of that history automatically once it is older than the provider's recovery window. We keep no separate long-term backup copies, and we do not restore deleted data from backups.

Your rights under GDPR

As an EU/EEA data subject you have the right to:

  • Access the personal data we hold about you
  • Rectification of inaccurate data
  • Erasure ("right to be forgotten") where no overriding legal basis exists
  • Data portability — receive your data in a structured, machine-readable format
  • Objection to processing based on legitimate interests
  • Restriction of processing where accuracy is contested or objection is pending
  • Withdraw consent where we rely on it, without affecting processing that happened before

To exercise any of these rights, email privacy@proculink.eu. We respond within one month, which is the period the GDPR sets. If a request is complex we may extend that by up to two further months, and we will tell you inside the first month if we need to. For data we hold as a processor, see "Our role" above: we pass the request to the organisation that controls it.

You also have the right to complain to a data protection supervisory authority. Ours is the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon, www.aki.ee); you can also complain to the authority in the EU or EEA country where you live or work, or where you think the problem happened. You do not have to contact us first.

Deleting your data

To have documents deleted, email privacy@proculink.eu from the address on your account and tell us what to delete: particular documents, everything received before a date, or the whole workspace. We check that the address belongs to the workspace you name, and we confirm the scope with you in writing before anything is deleted. Deletion is carried out by us rather than from a button in the product, and it cannot be undone.

What gets deleted

  • The document you sent us, as held in our file storage.
  • The data we read from it, including the names, addresses and contact details it carried.
  • The files we generated from it.
  • The record of what happened to it.

What we keep, and why

  • A short record that the deletion took place — the date, who carried it out and what it covered. It holds none of your document content. We keep it because we have to be able to demonstrate what we did and when, which is what GDPR Article 5(2) asks of us.
  • Workspace settings — your flows, destinations, lookup lists and stored credentials, and the note of which files we have already collected from your own systems, so that they are not collected again. Deleting documents leaves these in place and the workspace keeps working. Ask us if you want them removed as well.
  • Billing and tax records — kept for as long as accounting law requires us to keep them.
  • Backup copies — until they age out of our database provider's recovery window, as described under "How long we keep data". We do not restore deleted data from a backup.

Two things sit outside this. Your sign-in account is held by our authentication provider, and deleting documents does not remove it — ask us and we will. And a file we have already sent on is in the recipient's systems from that point on, which we have no way to reach.

Closing your account. Ending a subscription does not close the account or delete anything. To close it and have the workspace deleted — documents, the data read from them, the files generated from them, settings, and your users' sign-in accounts — email privacy@proculink.eu from an address on the account. We confirm the request with you in writing and complete it within 30 days of that confirmation. Billing and tax records are kept as described above, and so is a short record that the deletion took place.

Google accounts you connect

If a workspace admin connects a Google account so that a flow can send files to Google Drive or add rows to Google Sheets:

  • What we access. The account's email address, and only the Drive folders, files and spreadsheets you choose in Google's file picker or that ProcuLink creates. We cannot see any other file in your Google Drive.
  • How we use it. Only to deliver the documents your flows produce to the folder or spreadsheet you chose, and to show which account is connected. Before we add a file, we check whether ProcuLink already put a file with the same name in that folder, so a re-send replaces it instead of making a copy. Before we add rows, we read the spreadsheet's tab names and its first row, so a repeated header row is not added again.
  • What we store. The account's email address and an encrypted token issued by Google that lets ProcuLink reach the items you chose. We do not keep copies of anything we read from your Google account.
  • Sharing. We do not share data from your Google account with anyone. We do not use it for advertising, and we do not use it to train AI models.
  • Removing access. Disconnect the account in ProcuLink, and we delete its token at once. If a destination still uses the account, remove or change that destination first. You can also remove ProcuLink from your Google account's third-party access at any time. Deleting your workspace deletes the connection too.

ProcuLink's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Cookies

We use only functional cookies (authentication session, CSRF protection) and analytics cookies (product usage — pseudonymous). Analytics cookies are set only if you accept them in the cookie banner. We do not use advertising or cross-site tracking cookies.

Subprocessors

The authoritative list of subprocessors is maintained at /subprocessors with a 30-day change-notification commitment. The current snapshot:

ProcessorPurposeLocation
RailwayAPI and background-worker hostingEU region
NeonPostgreSQL database hostingEU region
CloudflareR2 object storage (the documents you send us and the output files we generate), DNS, and the relay that passes inbound email to our APIEU-region bucket; the relay runs on Cloudflare's global network
VercelWebsite and app hosting (document files do not pass through it)Global CDN
ClerkAuthentication and session managementUS, EU data residency available
OpenAIAI document extraction and mapping suggestions (API data is not used for model training under OpenAI's API terms)US
StripePayment processing and subscription managementUS, EU establishment
PostmarkEmail in and out: documents emailed to your ProcuLink address, and the files we email to the recipients you setUS
PostHogPseudonymous product analyticsEU (eu.posthog.com)
SentryError monitoring and diagnosticsEU region

Privacy contact

For privacy questions or to exercise your rights: privacy@proculink.eu
General support: support@proculink.eu
Registered address: Diip Solutions OÜ, Uus-Sadama tn 15-2, 10120 Tallinn, Estonia

Back to the top