Documents and local records
FolioForge processes documents on your device. It opens files through Android’s file picker or another app’s sharing action. Recent-file names and file references are kept in local preferences. Imported copies, working files and generated outputs may remain in app-private storage. Removing a recent entry removes its list reference, not the original document.
Save, Share and Print send a selected output to the destination or system app you choose. File providers and destinations can be cloud services with their own privacy rules and network requirements. FolioForge does not provide a document-cloud account or remote document-conversion service.
Simple HTML import reads a bounded file into an editable local text draft. Scripts, styles, links, images, tables and unsupported markup are rejected; accepted text reflows without its original formatting. The parser does not run scripts or fetch embedded resources. Drafts kept in memory can be lost when the app process exits.
App backup settings restrict Android backup, but should not be treated as protection against every manufacturer transfer or external-provider backup. App-private storage is not an encrypted-vault guarantee. Clearing FolioForge storage does not remove copies held by another service or recipient.
Optional usage statistics and crash capture
Usage statistics and local crash capture have separate saved choices that default off. Some builds may make reporting unavailable. You can still turn off a previously saved on choice. An allowed saved choice can resume on restart; if saving a change fails, retry before closing the app.
App-authored Analytics events are limited to opening Settings, opening Pro, completing a purchase and completing a restore. They do not include document contents, filenames, file references, PDF passwords, form fields, signatures or arbitrary exception text. Google/Firebase SDKs may also process app or installation identifiers, automatic interactions, coarse location derived from IP addresses, device/OS/app details and diagnostic data. These SDK operations are separate from the app-authored events. FolioForge does not display ads.
FolioForge disables automatic crash upload after initialization and offers Send, Delete or Not now for the available report batch. An earlier saved SDK upload setting can take effect before startup controls are reapplied. Turning off local capture may require restarting the app before an already installed crash handler stops capturing. Send queues an SDK request and cannot recall an earlier upload. Delete requests removal of the available local batch; it is not a confirmation that previously transmitted provider records were erased. Not now leaves the batch for a later choice.
The app reduces exception detail before forwarding a fixed message and code stack, and blocks sending a batch that may have been captured before that protection was installed. This does not guarantee that every SDK-generated diagnostic field is free of sensitive information. Disabling or resetting optional reporting does not delete earlier remote records or guarantee that SDKs made no network requests.
Purchases and access
Google Play and RevenueCat handle store purchases and restoration. Opening Pro starts the configured store service, checks customer status and loads the app’s lifetime offering. Anonymous billing identifiers, transaction records, entitlement status and operational app/store/device metadata may be processed independently of the optional Firebase choices. FolioForge does not ask for payment-card numbers or require a developer account.
A local last-verified lifetime grant supports offline access after confirmation. Network failures can preserve that cached grant; cached access is not a guarantee of current remote entitlement. An unavailable price or unsuccessful status check is not a completed purchase or restore. Removing local app data does not erase Google Play transaction or legal records.
Review instructions may provide a separate offline code for local review access. It is not a purchase. The masked input field clears before activation or removal, while the submitted code remains temporarily in memory during activation. A separate authenticated receipt is stored using AndroidKeyStore encryption. The code is reusable without expiry and should be kept private. Removing review access preserves documents and genuine paid access; if removal fails, local access may remain active until you retry successfully. Older offline builds cannot remotely revoke a leaked code.
Retention and deletion
Remove a recent entry to remove its list reference. Use the chosen file provider or destination to manage original and exported files. Working-file cleanup can fail or preserve files used by active work. Android Clear storage or uninstall removes app-private copies, preferences, recent references, local access receipts and billing/SDK storage; it does not remove externally saved or shared copies. Keep an independent copy before clearing data you still need.
FolioForge’s configured Analytics retention periods are two months for identifier-associated events and fourteen months for user data, with reset on new activity enabled. New activity can extend the user-identifier period; expiration is processed monthly. These controls do not cover most aggregate reports or establish erasure of every earlier record. Google retention information.
Firebase describes a ninety-day retention period for Crashlytics traces and associated identifiers before removal from live and backup systems begins. This is not an app-specific completed-deletion date. Firebase privacy information.
To request help with provider-held FolioForge data, email developer@blackandblue.co.in. Applicable anonymous billing records need to be identified safely before a request can be handled. A RevenueCat record operation does not cancel or erase Google Play transaction history. No automatic remote purge, fixed RevenueCat retention period or completed erasure is promised. See deletion choices.
Providers and website
Optional reporting uses Google/Firebase. Store services use Google Play and RevenueCat. Providers may process information outside your country. Their privacy information describes their practices: Google, Firebase, RevenueCat.
This website contains no scripts, forms, tracking pixels, remote fonts or site-set cookies. Hosting can process network and security metadata. Following an external link uses that provider’s website and privacy rules. Files you export or share are subject to your chosen destination’s controls.
Audience and contact
FolioForge is intended for people aged 13 and older and is not directed to children under 13. This statement does not verify a user’s age or parental authorization, or establish eligibility for optional reporting in every region. The reporting choices described above remain separate.
Publisher: Black and Blue. For support, privacy or deletion requests, contact developer@blackandblue.co.in with FolioForge and the minimum information needed. Do not send private documents, exported files, passwords, tokens, reviewer codes or payment-card information. Request handling may require proportionate identity verification and is subject to provider and legal limits. No response deadline is promised. Material policy changes will be reflected here.