Privacy Policy

As of 2026-11-06.

1. Who is responsible

Nursultan Imanov, Drorygasse 4a/70, 1030 Wien, Austria. E-mail: extracttablefrompdf@gmail.com. We are based in the EU, so the EU General Data Protection Regulation (GDPR) applies to all visitors, wherever they are. This policy covers the website extracttablefrompdf.com and the Extract Table from PDF Chrome extension.

2. The short version

PDFs can contain personal data, for example in a bank statement or an invoice. Please upload only files you are allowed to share with us.

3. What we process and why

a) Your PDF and the results. When you upload a PDF on the site or in the extension, we store the file, its name, size and page count, and the upload time. We read the file to find the tables and create the Excel and CSV files you download. This is needed to give you the service you asked for (Art. 6(1)(b) GDPR).

b) AI preview and deep extraction. Deep extraction uses Anthropic's Claude models. For a paid AI run, each page of the file is sent to Anthropic, which returns the tables. For the free preview, we pick the one page most likely to hold a table and send it to Anthropic. While payments are switched on, the preview starts automatically once the AI offer appears for your file, without a separate click. We keep the preview result with your file and count previews per install to cap them per day (Art. 6(1)(b) and (f) GDPR).

c) Install ID. The site and the extension create a random ID, stored in your browser, and send it with each upload. It links paid page credits, free bank statement pages and previews to your browser, and it lets us count unique users and repeat use (Art. 6(1)(b) and (f) GDPR). It does not contain your name or e-mail.

d) Payments. Purchases are completed on a Stripe checkout page. The sale is made through Stripe Managed Payments, with Link, a Stripe company, acting as merchant of record: it processes your payment details, calculates sales tax or VAT, issues the receipt and handles payment support under its own privacy policy. Our database keeps the checkout reference, your install ID, the page credits or statement pages bought, the amount, the currency and the date. It also keeps your restore code (for example ETP-XXXX-XXXX-XXXX), which moves your credits to another browser. Your e-mail address is not stored in our database, but we can see it in our Stripe account, along with the payment status and country, for support and tax records (Art. 6(1)(b) and (c) GDPR). Stripe: stripe.com/privacy, Link: link.com/privacy.

e) Google Analytics 4, only with consent. If you click Accept, we load Google Analytics. It records the pages viewed, the referring page, browser, operating system, device type and country, plus events such as "file uploaded", "export clicked" or "checkout started" with details like the page count range. We use this to see where people get stuck (Art. 6(1)(a) GDPR, § 165(3) Austrian Telecommunications Act 2021). Google sets cookies such as _ga and _ga_*. Ad personalization and Google signals are switched off. Google may process data in the USA; Google LLC is certified under the EU-US Data Privacy Framework. You can withdraw consent at any time via Cookie settings in the footer; we then delete these cookies.

f) Usage steps on our server, without cookies. To see where people get stuck, also for visitors who declined cookies, our server records steps of using the tool: page viewed, file selected, upload finished or failed, extraction finished, result shown, free pages used, price shown, plan clicked, checkout started, finished or abandoned, and file downloaded. An entry holds the step, the time, the page path, whether it came from the site or the extension, and numbers such as page count, file size, processing time, the price shown and whether a statement's balances add up. From the upload on, it also holds the random file ID and your install ID, so the entries are pseudonymous. For page views and other steps before an upload we send no ID at all. Entries never hold your file name, file content, IP address, name or e-mail, and we set no cookie for this. We delete them after 90 days (Art. 6(1)(f) GDPR, our interest in improving the service).

g) Error reports. If the site or the extension crashes, it sends the error message, technical trace, page path and, for the extension, version number to our server log. We use this to fix bugs (Art. 6(1)(f) GDPR).

h) Server logs. Our hosting provider records technical access logs (IP address, time, requested address, browser) for security and troubleshooting (Art. 6(1)(f) GDPR).

i) E-mail. If you write to us, we use your e-mail and message to answer (Art. 6(1)(b) or (f) GDPR) and delete the conversation when it is no longer needed, unless we must keep it by law.

4. Storage on your device

NameWherePurposeWithout consent
install_idlocal storage, extension storagerandom ID for credits, free pages and usage countsyes (needed for the tool)
pending_premium_filelocal storageremembers the file while you payyes (needed for payment)
pending_statement_downloadlocal storageremembers the download while you payyes (needed for payment)
checkout_started_filesession storagedetects a return from checkoutyes (needed for payment)
etp-consentlocal storageremembers your cookie choiceyes (needed)
_ga, _ga_*cookiesGoogle Analyticsonly after Accept

5. Recipients and where data is processed

Data is transferred outside the EU only to providers covered by an adequacy decision (such as the EU-US Data Privacy Framework) or standard contractual clauses (Art. 45, 46 GDPR).

6. How long we keep data

7. Your rights

You can ask for access, correction, deletion, restriction and data portability, and object to processing based on legitimate interest (Art. 15-21 GDPR). You can withdraw consent at any time with effect for the future. Write to extracttablefrompdf@gmail.com. You can also complain to a supervisory authority, in Austria the Datenschutzbehörde (dsb.gv.at).

8. US visitors

We do not sell or share personal information for cross-context behavioral advertising. You can make the requests listed in section 7 from anywhere.

9. Changes

We update this policy when the site changes. The date at the top shows the current version.