PDF Textfix privacy policy

Version 1.4, effective October 13, 2026

This policy explains what personal data Pocket Implementation S.R.L. processes when you use PDF Textfix, when we issue and support a licence for it, when you write to us, and when you visit this website. The controller of that data is Pocket Implementation S.R.L., Bucharest, Romania; you can reach us at contact@pocketimplementation.com, and our company details are at the end of this page. The short version: the documents you open never leave your Mac and the app has no account. The only personal data it sends is the record of an in-app purchase, which the Mac App Store version sends to RevenueCat when you buy. The version downloaded from this website sends the licence with a hashed identifier of your Mac, to activate the licence on that Mac and to check it about once a week. We keep only what we need to sell, deliver and support a licence and to answer you. The website measures its visits with Google Analytics, which sets cookies only if you accept them.

Your documents

PDF Textfix edits PDFs on your Mac. The app reads only the files you open and writes only where you save. It never sends a document, a page, a line of text or a file name to us or to anyone else.

The app keeps a few things on your Mac only: your settings, the list of recent files macOS keeps for every app, and a record of the free line edits you have used, kept as a file in the app’s own container together with a copy in its preferences. That record holds a digest of each document and which of its lines were edited, not the text. None of it is sent anywhere. Deleting the app’s container removes it.

The app from the Mac App Store

The app has no account. Your files never leave your Mac: the app reads only the files you open and writes only where you save.

The purchase inside the app is made with Apple. Apple processes the payment and your Apple Account under its own privacy policy, and its sales reports to us do not identify buyers. Family Sharing of the purchase is handled by Apple in the same way. To confirm the purchase and keep our record of sales, the app uses RevenueCat, a service of RevenueCat, Inc. in the United States, which processes the data for us. The app contacts RevenueCat only when you buy or restore the purchase and, until you quit the app, a few times more to keep that confirmation current. It sends Apple’s signed record of the purchase, with the product, the price and currency, the App Store country, the date and Apple’s transaction numbers. It also sends a random identifier the app creates for RevenueCat, which is not your name, your email address or your Apple Account. Finally it sends the technical details RevenueCat needs to answer: the app’s version and build, the version of macOS and of RevenueCat’s code, the type of processor, your preferred languages and the system’s tracking setting. The app never asks for tracking and does no tracking. Like any connection, the request carries your IP address. RevenueCat uses it to tell the country when the purchase record does not, then discards it. RevenueCat may also record anonymous diagnostics of the purchase request itself, which hold details of the purchase such as the product, the price and the App Store country. RevenueCat never receives your documents, your file names, the free line edits you used or anything about how you use the app, and the app sends it nothing before you buy.

We use this record to perform our contract with you, the purchase you made (GDPR Article 6(1)(b)), and, in our legitimate interest, to count our sales and handle refunds (Article 6(1)(f)). A purchase in the app cannot be confirmed without it, so the only way to avoid it is not to buy in the app. The free version sends nothing to RevenueCat, and the version from this website never contacts RevenueCat: it activates its licence with our own licence service, as the next section describes. After a purchase you can ask us to erase your record at RevenueCat. The app stays unlocked, because it reads the purchase from the App Store on your Mac. RevenueCat stores the data on Amazon Web Services in the United States, under the European Commission’s standard contractual clauses in its data processing agreement, and keeps it while we use its service. RevenueCat’s privacy policy describes its own handling.

The app from this website

The app has no account. Your files never leave your Mac: the app reads only the files you open and writes only where you save. Without a licence, the app goes online only to check pdftextfix.com for updates, and only when you allow it. With a licence, it also contacts our licence service to activate the licence on your Mac and to check it about once a week, as described under Licence activation.

The update check uses Sparkle, an open-source updater. The first time, the app asks whether it may check automatically, and you can also check by hand with Help > Check for Updates…. A check is one HTTPS request for the list of releases at pdftextfix.com. Like any connection to a website it carries your IP address, and it names the app, its version and the version of Sparkle. Sparkle’s system profiling is turned off, so nothing about your Mac, such as its model or its version of macOS, is sent, and we build no profile from these requests. The website’s host keeps them in its logs as described under The website.

A licence for this version is a text you paste into the app, or a link from your licence email that opens the app. The app first checks the licence on your Mac, then activates it online, and stores it in its container together with the service’s signed confirmation. The licence carries the name you gave at checkout, which the app shows in its About and Licence windows. The link in the licence email opens the page pdftextfix.com/activate with the licence after a “#” in the address: browsers never send that part of an address to a website, so the licence does not reach the website’s server or its logs. That page and the lost-licence page load no analytics and show no cookie banner.

Licence activation

A licence can be active on 3 Macs at a time (3 for each person a team licence covers). To keep to that, the app from this website contacts our licence service, which runs on our web hosting provider’s servers at api.pdftextfix.com:

When you enter the licence on a Mac, or open the link from your licence email, the app activates it once. It sends the licence (which holds your licence ID, the name given at checkout and the edition), a hashed identifier of the Mac, the Mac’s name, its model and the app’s version. The hashed identifier is a one-way digest of the hardware identifier macOS gives the Mac, mixed with a value fixed in our app, so it cannot be turned back into the hardware identifier or the serial number, and it means nothing to any other app or company. The Mac’s name is the one set in System Settings, which often includes a first name, such as “Ana’s MacBook Air”. The service records the Mac against the licence and answers with a signed confirmation that the app keeps.
About once a week, when the Mac is online, the app checks the licence. It sends the licence ID, the same hashed identifier and the app’s version. The service notes the time of the check. If the check cannot reach the service, nothing is sent again until the next launch; after 30 days without a successful check, the app asks you to connect once.
When you open the Licence window, the app asks the service for the list of the Macs using the licence, and when you choose Remove, or Remove Licence…, it tells the service to remove that Mac. Anyone who holds the licence can see that list.
When a fourth Mac is activated, the service removes the Mac whose last activation or check is the oldest, and that Mac learns it at its next check.

Like any connection, each of these requests carries your IP address. The service uses it only to limit how many requests one address can make, keeps it for that only as a digest and deletes the digest within two days (the encrypted backup copies keep it until they expire); the host’s server logs keep the address as described under The website. The service’s own log names the licence ID and the first characters of the hashed identifier of each request, never the name of the Mac or the address. The free version never contacts the licence service, and none of these requests carries anything about your documents.

For each Mac, the service keeps the hashed identifier, the Mac’s name and model, the app’s version, the date of the first activation and of the last check, and, once a Mac is removed, the date and whether it was removed by you or replaced by a newer activation. We use these records to deliver the licence on your Macs, which is part of our contract with you (GDPR Article 6(1)(b)), and, in our legitimate interest, to keep a licence to the number of Macs it covers and to stop a licence from being shared or resold (Article 6(1)(f)). A licence cannot be activated without them, so the only way to avoid them is not to activate a licence; the free version works without them. If you ask us to erase them, the Macs on which the licence is still entered activate again at their next check.

Reporting a problem

Help > Report a Problem builds a text report and shows it to you before anything is sent. It holds the app’s version and build, which version it is (Mac App Store or website), the macOS version, the Mac model, the app’s recent log entries with private details removed, the codes of any refused edits, and the crash and performance reports macOS keeps for the app, when there are any. It holds no document text, no file names and no paths in your home folder. If you choose to send it, it is attached to an email in your own mail app, addressed to our support address; you can also save it instead and send nothing.

Help > Contact Support… opens a new message in your own mail app, addressed to our support address, with the app’s version, build and channel and the version of macOS written at the end. Nothing is sent until you send the message yourself.

Licences sold through Paddle

Our order process is conducted by our online reseller Paddle.com, which is the merchant of record for all our orders. Paddle collects your payment details, billing address and tax information and processes them as an independent controller under its own privacy notice at paddle.com. We never see your card or bank details.

From Paddle we receive what we need to issue and support your licence: your name, your email address, your country, the order and transaction identifiers, the product and the number of seats. We use them to create your licence, to email it to you, to send it again if you lose it, to handle refunds and to answer you. The order also records that, before the checkout opened, you agreed to the licence being delivered immediately after payment and acknowledged losing your right of withdrawal, with the time you did so; the licence email confirms it, and we keep the record as proof of that agreement. A Team of 5 licence also holds the names of the five people it covers, which the buyer gives us. With the order we also receive the campaign tags, when the link you arrived through carried them, and, if you accepted analytics, the two Google Analytics identifiers that the checkout passed to Paddle. We use them only to know which link and which visit led to the order.

We keep a register of the licences we issue: the licence identifier, the transaction, the customer, the edition and seats, the date and whether the licence is active or revoked. The records of the Macs a licence is activated on are described under Licence activation. When a licence is refunded, charged back or published for others to use, we mark it revoked and add its identifier to a list that later versions of the app carry, so that they no longer accept it. That identifier is a random code: the list holds no name and no email address.

If you dispute a payment with your bank or card issuer, Paddle and we use the order and the record of the licence’s delivery to answer the dispute, and Paddle passes them to the payment provider.

Backups of the licence records

Every day, our host makes an encrypted copy of the licence service’s records: the licence register, the records of the Macs each licence is activated on, the revocations, the agreements recorded with the orders and the digests the service keeps for its rate limits. The copy is encrypted on the host, before it leaves it, with a key that only we hold, and is stored in Cloudflare R2, a storage service of Cloudflare, Inc., which processes it for us and cannot read it; the storage is set to Western Europe, which Cloudflare treats as a location hint rather than a guarantee. Each copy is deleted 400 days after it is made. The copies are for recovery only: we read one only to restore the records after a loss or to test that a restore works, and never for any other purpose. A record erased from the live records at your request remains in the copies made before the erasure until they expire; if we ever restore a copy, we erase that record again before the service uses it.

Writing to us

When you email contact@pocketimplementation.com, we receive your email address, your name if you give it, your message and anything you attach. We use them only to answer you and to keep a record of the conversation.

If you send us a PDF so that we can look into a problem, we use it only for that problem. We delete it within 30 days of closing the conversation, and we never keep it as a test file unless you agree to that in writing. Please send only a file you are allowed to share; where you can, show the problem on one of the sample documents in the Help menu instead.

The website

pdftextfix.com loads no fonts or images from other companies. Apart from Google Analytics, which the next section describes, its pages run no code from another company until you open Paddle’s checkout.

The website and the update feed are served by our web hosting provider. To deliver pages and files and to protect the site from abuse, the host processes your IP address and the details every browser sends (the page requested, the time, the browser and the referring page) and keeps them in server logs for a short time. When the site is delivered through Cloudflare’s network, Cloudflare processes the same details for the same purposes. We use these logs only to run and secure the site and to count downloads and update checks in total, never to identify a visitor.

The pricing page loads Paddle’s checkout only when you choose to buy. Until then, no Paddle code runs on the page. Once the checkout is open, Paddle’s privacy notice applies to what you enter in it.

When you arrive through a link that carries campaign tags (utm_source, utm_medium, utm_campaign, utm_term, utm_content) while sales are open, a script on the page keeps those tags and the path of the page you arrived on in the browser’s session storage, which is cleared when you close the tab. If you open Paddle’s checkout, the script hands them to Paddle with the order, so that we know which link led to it. Nothing is stored when the link carries no such tags.

News of new versions comes through the releases feed, which you read in a feed reader of your choice; we see no list of its readers.

Analytics

We use Google Analytics 4 to count visits and to see which pages help people. It runs on every page of pdftextfix.com except pdftextfix.com/activate and pdftextfix.com/licence, the two pages whose address can carry a licence.

Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland, provides Google Analytics to us as our processor, under the Google Ads Data Processing Terms that are part of its Google Analytics terms. Google runs the service in data centers around the world, including in the United States through its affiliate Google LLC. For transfers to the United States, Google relies on the EU-U.S. Data Privacy Framework, under which Google LLC is certified.

What Google Analytics receives

Once you choose Accept in the banner, Google Analytics receives, for each page you view:

The address and title of the page, the address of the page you came from, and the campaign tags of the link you followed.
The type of page, such as the home page, the pricing page or a how-to article, which we add ourselves.
Whether you scroll to near the bottom of a page, the links you follow to other websites and the files you download.
The clicks we count ourselves: the app’s download link, a Mac App Store badge, the button that opens Paddle’s checkout, the press kit and the sample documents, each with where on the page it sits.
A completed order: Paddle’s transaction number, the total, its currency and the product, never your name, your email address or your licence.
Your browser and device: the kind of device, the operating system, the browser and their versions, the screen size and the language.
An approximate location (city, region and country), which Google derives from your IP address. For visitors in the EU, Switzerland and the UK, Google does this on servers there and discards the address without logging it; for other visitors it also uses the address to filter spam, and discards it after use.
Two random identifiers that it keeps in its cookies: one tells your browser apart from others, the other groups the pages of one visit.

It never receives the documents you edit, the names of files on your Mac, anything you type into a page, your email address or your licence. We send Google no user ID of our own. Google signals is off, so Google does not link your visits to a Google account, across your devices or to advertising. We have linked Google Analytics to no advertising service, and we show no ads.

If you accepted, the checkout also passes Paddle the two identifiers from the Google Analytics cookies, so that an order can be matched to the visit that led to it. After a Decline there are none to pass.

If you decline

When you choose Decline, or until you choose, Google Analytics sets and reads no cookie. Each page and each of the clicks above still sends Google a short signal with no cookie and no identifier for your browser. It holds the page, the time, the address of the page you came from, the event and what we add to it (such as the type of page, or an order’s transaction number and total), and your browser’s user agent and screen size. Your IP address arrives with it, as with any connection; Google uses it only to derive an approximate location (and, outside the EU, Switzerland and the UK, to filter spam) and does not keep it. From these signals Google cannot tell whether ten page views came from one person or from ten. It uses them to estimate our totals by modeling, from the visits of people who accepted.

The pages work the same whichever you choose.

How long Google keeps it

Google Analytics deletes the data of a single event 14 months after it is collected, and the data tied to a browser 14 months after that browser’s last visit. The totals in its standard reports, which identify no one, remain.

Cookies

Apart from a security cookie Cloudflare may set (described below the table), this website sets cookies only for Google Analytics, and only after you choose Accept in the banner at the bottom of the page. This is everything our pages store on your device:

Name and who sets it	What it is for	How long
`_ga`: a cookie set by Google Analytics, only after Accept	Tells one browser apart from another, with a random number	2 years from your last visit
`_ga_<container-id>`: a cookie set by Google Analytics, only after Accept (`<container-id>` is our measurement ID without its `G-`)	Keeps the state of the current visit	2 years from your last visit
`pdftextfix.analytics-consent`: local storage, set by our pages when you choose	Your answer, Accept or Decline, and when you gave it, so that the banner does not ask on every page	12 months, then the banner asks again
`pdftextfix.landing-campaign`: session storage, set by our pages only when the link you followed carries campaign tags	The campaign tags and the page you arrived on, for Paddle’s checkout	Until you close the tab
`pdftextfix.purchases-sent`: session storage, set by our pages after an order	The transaction numbers already reported, so that each order is counted once	Until you close the tab

Two years from the last visit is Google’s default for its cookies. Browsers may delete them sooner: Google notes a limit of 400 days in Chrome and 7 days in Safari for a visitor who does not come back. Your answer stays in your browser; Google Analytics learns only whether you accepted. Our pages set no other cookie. When the site is delivered through Cloudflare’s network with its protection against bots on, Cloudflare may set a security cookie of its own, such as __cf_bm, which expires after 30 minutes without activity, to tell visitors from bots; Cloudflare describes these cookies as strictly necessary for that protection. Paddle’s checkout, once you open it, works under Paddle’s privacy notice.

You choose in the banner, which offers Accept and Decline side by side, and you can change your answer at any time: choose Cookie settings at the foot of any page to open the banner again. Choosing Decline stops Google Analytics from using its cookies and deletes any it set from your browser. When this section changes what you are asked to agree to, the banner asks again.

If your browser sends the Global Privacy Control signal, we take it as Decline, whatever you chose in our banner before: the banner and Cookie settings do not appear, the cookies of an earlier Accept are deleted, and Google Analytics sends only the signals described under If you decline.

Google also offers a browser add-on that keeps Google Analytics from using data from your browser on any website, this one included: tools.google.com/dlpage/gaoptout.

Why we may process your data

To perform our contract with you: issuing, delivering and supporting your licence, activating it on your Macs and checking it, confirming an in-app purchase of the Mac App Store version with RevenueCat, and answering your questions about either (GDPR Article 6(1)(b)).
To meet legal obligations: keeping the records accounting and tax law require, confirming in the licence email your agreement to immediate delivery, and answering a public authority or a court when the law obliges us to (Article 6(1)(c)).
For our legitimate interests: delivering the website and the update feed and keeping them secure, offering updates, measuring visits and orders in total with the signals Google Analytics sends without cookies when you have not accepted, knowing which link led to an order, from the campaign tags kept in session storage, keeping our record of in-app sales at RevenueCat to count them and handle refunds, keeping a record of support conversations, keeping a licence to the number of Macs it covers and stopping it from being shared or resold, keeping refunded, charged-back and published licences revoked, keeping encrypted backup copies of the licence records so that they can be restored after a loss, and establishing, exercising or defending legal claims, such as a disputed payment (Article 6(1)(f)). You can object to this at any time, for example with Google’s add-on above.
With your consent: the Google Analytics cookies and the measurement that uses them, including the identifiers passed to Paddle with an order, and keeping a PDF you sent as a test file (Article 6(1)(a)). Storing cookies on your device and reading them needs your consent under Article 5(3) of the ePrivacy Directive, which Romania transposes in Law 506/2004. You can withdraw consent at any time, for Google Analytics with Cookie settings at the foot of any page; withdrawing does not affect what was done before.

We make no decision about you based solely on automated processing that has legal or similarly significant effects on you (Article 22), and we build no profile of you.

Transfers outside the European Economic Area

Where a provider processes personal data outside the European Economic Area, the transfer is protected as Chapter V of the GDPR requires:

RevenueCat, Inc. (United States), for the in-app purchase of the Mac App Store version: the European Commission’s standard contractual clauses, in RevenueCat’s data processing agreement.
Google LLC (United States), for Google Analytics: the EU-U.S. Data Privacy Framework, under which Google LLC is certified.
Cloudflare, Inc. (United States), when the website is delivered through Cloudflare’s network, and for the encrypted backup copies of the licence records in Cloudflare R2, stored with a location hint for Western Europe: the EU-U.S. Data Privacy Framework or the standard contractual clauses, as Cloudflare’s processing terms provide.
Paddle.com Market Ltd (United Kingdom), an independent controller for the checkout: the European Commission’s adequacy decision for the United Kingdom.

Any other provider that processes data for us outside the European Economic Area does so under an adequacy decision or the standard contractual clauses. You can ask us for a copy of the safeguards at the address above.

How long we keep it

Data	How long
Licence register entries	For the life of the licence, or until you ask us to erase them, except the records the law requires us to keep and what we need to keep a revoked licence revoked or to defend a claim
Activation records of your Macs (the hashed identifier, the Mac’s name and model, the app’s version, the dates of activation, of the last check and of removal)	While the licence exists, and one year after it is revoked or its register entry erased
Encrypted backup copies of the licence records, in Cloudflare R2	400 days from each copy; a record erased from the live records stays in the earlier copies until they expire
Identifiers of revoked licences, in the list later versions of the app carry	Permanently, since a revoked licence stays revoked; the list holds no name and no email address
Records of a refund or a disputed payment	Until the time limit for claims about it has passed, three years under Romanian law, or longer while a claim is open
Orders and invoices from Paddle	As long as Romanian accounting law requires
Records of in-app purchases at RevenueCat	While we use RevenueCat, or until you ask us to erase them
Support conversations	24 months after the last message
PDFs you send us	Deleted within 30 days of closing the conversation
Website and update-feed logs at our host	As long as the host keeps its server logs, and no longer than we need them to run and secure the site
Google Analytics data tied to a browser or an event	14 months after the event, or after the browser’s last visit; report totals that identify no one remain
The Google Analytics cookies in your browser	2 years from your last visit, or until you choose Decline or delete them
Your cookie choice in your browser	12 months, then the banner asks again
Campaign tags and reported orders in your browser’s session storage	Until you close the tab

Your rights

You can ask us for a copy of your data, to correct it, to erase it, to restrict or object to how we use it, and to receive it in a portable form. Write to contact@pocketimplementation.com; we answer within one month, or tell you within that month why we need up to two months more (Article 12(3)). Before we act on a request, we may ask you to confirm that the data is yours, for example by writing from the email address of your order. Where a request is manifestly unfounded or excessive, in particular because it repeats itself, we may refuse it or charge a reasonable fee, and we tell you why (Article 12(5)). Erasing a licence record means we can no longer send the licence again or confirm it, and it does not remove a revoked licence from the list the app carries.

You can also complain to the Romanian data protection authority, Autoritatea Națională de Supraveghere a Prelucrării Datelor cu Caracter Personal (ANSPDCP), at dataprotection.ro, or to the authority of the country where you live or work.

Children

PDF Textfix is not directed at children, and we do not knowingly collect data from anyone under 16.

Changes

When this policy changes, we publish the new version here with a new version number and date; the version at the top of this page is the one that applies. If a change affects how we use data we already hold, we tell the people concerned by email before it takes effect.

The other documents that apply are the terms and licence, the security policy and the legal notice.

Who processes your data with us

The policy above names the legal basis of each transfer; this list says who the companies are.

Paddle.com Market Ltd (United Kingdom): the order process, payment, sales tax and VAT, receipts and invoices of the licences it sells for us, as an independent controller and the merchant of record.
Apple Distribution International Ltd (Ireland): the in-app purchase of the Mac App Store version and its refunds, as an independent controller.
RevenueCat, Inc. (United States): confirming the in-app purchase of the Mac App Store version and keeping our record of those sales, as our processor.
Our web hosting provider: the server that delivers the website, the update feed and the downloads, and our mailboxes, as our processor.
Cloudflare, Inc. (United States): when the domain's name service or the delivery of the website runs through Cloudflare's network, that service and the protection of the website, and, in Cloudflare R2, the storage of the encrypted daily backups of the licence records, as our processor.
The providers of our licence service: issuing licences, activating them on Macs and checking them, keeping the licence register with the Macs each licence is active on, and sending licence emails, as our processors.
Google Ireland Limited (Gordon House, Barrow Street, Dublin 4, Ireland), with its affiliate Google LLC (United States): Google Analytics 4, which counts visits and the clicks on downloads, store links and the checkout, as our processor.

Google Analytics is on, as the cookies section describes.

Each processor handles the data only on our instructions, under a data processing agreement. We sell no personal data and share none for advertising.

Who we are

The controller of the personal data this policy describes:

Company: Pocket Implementation S.R.L.
Legal form: Societate cu răspundere limitată (S.R.L.), a Romanian limited liability company
Registered seat: Bucharest, Romania
Trade register number: J2021007099408
Unique registration code (CUI): 44137671
Email: contact@pocketimplementation.com

We have not appointed a data protection officer, as our processing is not one of the cases in which Article 37 of the GDPR requires one. Write to contact@pocketimplementation.com about anything in this policy, or to the registered seat above.