Privacy & file handling
This page describes the current implementation. Personal PDF exports and subscription checkout are not enabled in this preview.
Browser editing and local drafts
Opening and editing your PDF runs in your browser. Folio saves a copy of the current document, filename and changes in this browser's IndexedDB so you can return to your draft. This draft belongs to the browser profile, not a Google account. Anyone using the same unlocked browser profile may see it.
Use Clear local draft in the editor to remove the saved draft and close the current document. Signing out also clears the current local workspace. Close other Folio editor tabs before clearing a draft; another open editor can save again. Clearing site data in your browser removes this local storage. A downloaded file remains on your device until you delete it.
When files leave your browser
When personal-file export is enabled, requesting an export uploads your original PDF, filename and edit instructions to Folio's server. Subscription checkout itself does not upload the PDF. The server checks export support and stores the source, edit snapshot and generated PDF. These server files are associated with the signed-in user. The demo export endpoint accepts only changes to the fictional built-in demo, not an arbitrary uploaded PDF.
Access and retention
File and order APIs require the application's signed-in user and check document ownership. Server document access expires after seven days. Expiry is an access limit, not an automatic deletion promise. The optional maintenance job deletes expired storage objects in bounded batches when enabled. Expiry does not guarantee immediate object deletion; cleanup must be monitored by the operator.
Clearing a local draft does not delete copies previously uploaded to the server or payment records. The current authenticated deletion API can delete an accessible uploaded document and its stored file objects. An uploaded file can be deleted from the editor using its server-file deletion control, including after access expiry. Deleting a file does not delete financial records. Avoid uploading sensitive documents during the preview.
Sign-in and payments
When enabled, Google sign-in requests an account identifier, verified email address, display name and profile image. Application sessions use a secure, HttpOnly cookie. Stripe and PayPal checkout are hosted by those providers; Folio does not collect card numbers. Payment and order records are separate from PDF files.
Site hosting
Website access depends on the hosting configuration. Google sign-in is the application identity used for file and order access when enabled. Making the website publicly accessible does not grant access to another user's authenticated file or order APIs.
Current availability
This deployment remains an editor preview. Configuring credentials alone is not evidence that real login, payment-provider testing, merchant support, refund terms and file cleanup have passed production acceptance.