Folio
Effective 25 September 2026 · replaces the version of 15 September 2026
Folio edits PDF documents on your device. This policy explains what the app touches, what it keeps, and — the shortest section of all — what leaves your device. It describes the app as it actually behaves.
The short version. Nothing leaves your device. Folio has no account, no server and no network code. The documents you open, the edits you make and the files you export exist only where you put them. There is no advertising, no analytics and no crash reporting. The one optional thing the app stores for itself — a recoverable draft of the document you are working on — is off by default, lives on your device, and is deleted when you delete it or the app. Recognising text on a scan and converting a document to Word or Excel also happen on the device, with no service behind them.
This policy covers the iPhone app, the Android app and the web app at the same address. Where they differ, the difference is stated in the section concerned.
Folio is published by Apex Root Solutions LLC ("we", "us"), a limited liability company organised under the laws of the State of Delaware, with its registered office in Wilmington, New Castle County, Delaware, and its principal place of business in Cedar Hill, Dallas County, Texas.
Contact us at support@apsoluts.com for any question about this policy.
Folio reads the PDF files and images you choose to open — through the system file picker, the share sheet, drag and drop, or the photo picker when you insert a picture. It reads what you gave it and nothing else. It does not scan your files, your photo library or your storage on its own.
It checks a file's contents to confirm it really is a PDF.
Password-protected files. If a file is protected, Folio asks you for its password and uses it to decrypt the document in memory so the rest of the app can work on it. The file on your disk is never changed. The password is checked against the file's own verifier — it is never guessed, recovered or sent anywhere — and it is discarded as soon as the file is open. We never store it, it is never written into a saved draft, and it is never written into a file you export unless you ask for protection there as well.
One consequence is worth stating plainly: once a protected file is open, the copy Folio is working on is decrypted. If you have turned draft recovery on (see section 4), the draft it saves on your device contains that decrypted copy, and it can be recovered without the password until you delete it. If that matters for a particular document, leave draft recovery off while you work on it.
Everything happens on your device. Pages are rendered by the platform's own
PDF engine (PDFKit on iPhone, Android's PdfRenderer, pdf.js in the
browser), edits are held in memory, and the exported PDF is written by a library
running locally. On the web the export runs in a worker inside your browser
tab.
Recognising text on a scan (OCR) also runs on the device, and so does the model it uses: Apple's Vision framework on iPhone, ML Kit bundled inside the APK on Android — not fetched from Google Play services — and Tesseract compiled to WebAssembly on the web, served from the same address as the app. The page is rasterised in memory, recognised, and the words are written back into the document as an invisible text layer. No image of your page is sent anywhere.
Converting to Word or Excel builds the .docx or .xlsx file on the device from the text the document already contains. There is no conversion service.
The Android app does not request the Internet permission at all. The iPhone app contains no networking code. The web app loads its own code, bundled fonts and recognition model from the address you opened it at and makes no other request; once loaded it works offline.
The app keeps no history of the files you opened beyond what a saved draft contains.
Nothing. We receive no data from the app and have no server for it. The only way information leaves your device is when you export or share a file, and then it goes where you sent it.
A signature in Folio is a picture you draw or insert. The app places it on the page as an image. It does not create a cryptographic digital signature, does not certify the document and does not record who signed it or when. Treat it as you would a signature on paper: it is only as trustworthy as the process around it.
None. No advertising network, no analytics service, no crash reporter and no cloud service is built into the app. The app stores (Apple, Google) handle installation and updates under their own policies, and your browser vendor handles the web app's storage under its own.
Folio is not directed to children. We do not knowingly collect personal data from a child; in practice we do not collect personal data from anyone, because there is nowhere for it to go.
Your documents and drafts are protected by your device's own file encryption and, on the web, by your browser's site isolation. We retain nothing because we receive nothing. Your data lives for as long as you keep it on your device.
No system is perfectly secure and we do not claim otherwise. Having no account and no server limits what any breach of ours could expose, but it does not protect your device itself if it is lost, stolen or unlocked in someone else's hand.
Everything the app holds is on your device and under your control: open, edit, export or delete anything, and delete drafts in Settings. Depending on where you live you may also have rights to access, portability, objection and to complain to a supervisory authority; if you are in the European Economic Area or the United Kingdom, we do not process your personal data on our own systems at all. We do not sell personal information or share it for cross-context behavioural advertising as those terms are used in California law.
We operate from Texas, in the United States. Because we receive no personal data from the app, there is no transfer of your data to describe.
If we change this policy we will update the date at the top of this page. If a change materially affects how we handle your data, we will say so in the app before it takes effect.