Privacy Policy for PDF Page Atelier

Privacy Policy for PDF Page Atelier

Developer: It as a service
Privacy contact: info@itservice.fun

Scope

This policy describes how the current Android application PDF Page Atelier handles information when you view, organize, annotate, save, and share PDFs.

Information accessed and stored

The app accesses PDF files you select through Android’s document picker. It reads document contents, filenames, file sizes, page counts, page dimensions, permissions, encryption status, and available metadata such as title, author, subject, and creation or modification dates. Documents and annotations may contain personal information, depending on what you open or enter.

The app processes PDFs on your device to display pages, combine documents, extract and reorder pages, add text and drawings, and create exported copies. Text annotations remain editable in compatible readers; drawings are flattened into exported pages.

To restore your work, the app stores local workspace information, including document references, page selections and order, rotations, current page, annotation text and drawing coordinates, output filename, selected ranges, and unsaved-change status. It also stores library and export references, filenames, page counts, file sizes, and preferences such as dimension units and the default output name. These records are stored in the app’s private preferences.

The app requests continued access to selected document locations so it can reopen them later. If you enter a PDF password, the app uses it in memory to open the selected file. Passwords are not saved to preferences.

Collection and purposes

The inspected application does not implement accounts or developer-operated collection of document contents, personal profiles, usage analytics, advertising identifiers, or location data. Local access and storage support document processing, workspace restoration, preferences, and the recent-document and saved-export library.

When processing fails, the app writes exception types and technical stack traces to Android’s local diagnostic log. Its logging code excludes exception messages and does not intentionally log document names or contents. No remote diagnostic-reporting service is implemented in the inspected source.

Sharing and third-party components

The app does not implement automatic uploads of your PDFs or annotations to the developer or an advertising or analytics service. No advertising, analytics, or remote crash-reporting SDK is configured in the inspected application. The app uses PDFBox for Android to process PDFs locally, along with Android and Compose components for its interface and file interactions.

When you choose Share, the app gives the receiving application access to the selected PDF through Android’s sharing interface. The PDF may contain document content, metadata, and annotations. The receiving app handles that information under its own practices.

You choose where exported PDFs are saved through Android’s document interface. If you select a cloud-backed document provider, that provider may transfer or synchronize files under its own settings and privacy policy. Although PDF processing occurs on your device, your chosen storage or sharing provider may use network services.

Android backup is enabled in the application configuration. Depending on your device, system settings, and backup service, app preferences and other eligible app data may be included in system-managed backup or restoration.

Security

The app uses Android’s document picker and document access permissions to access files you select, and stores workspace records in app-private storage. Exporting creates an intermediate PDF in the app’s private files directory; the code deletes that intermediate file after a successful export and attempts to delete it when export processing fails.

The Android manifest includes internet permission, but the inspected active PDF workflow does not implement a developer-operated network transfer. There is therefore no app-operated transmission encryption practice to describe for that workflow. Transfers performed by a storage, sharing, or backup provider depend on that provider. The inspected source does not establish additional encryption for stored workspace records or exported copies. No storage or security method can guarantee complete protection.

Retention

Local preferences, workspace records, and library references remain available across app sessions until replaced or removed, or until app data is cleared. No fixed retention period is implemented. Clearing recent history removes recent references while retaining saved-export entries, source files, and the stored workspace. Removing a source document from the library removes its reference rather than deleting the original file.

Exported PDFs remain in the destination you choose until deleted there or through the app’s saved-file deletion control, where supported by the document provider. Files already shared, synchronized, or backed up may remain with the receiving app or provider. Interrupted operations may leave intermediate app-private files until app data is cleared or the app is uninstalled.

Deletion and your controls

You can clear recent history in Settings, remove source references from the library, and request deletion of saved PDFs through the app’s saved-file deletion control. You can clear the app’s local preferences and workspace data using Android’s app storage controls. Uninstalling removes local app-private data, but does not necessarily remove exported documents or provider-managed backups.

To remove exported files or copies held by another app, storage service, or backup provider, use that provider’s controls. Clearing recent history alone does not erase stored workspace annotations or exported files.

For privacy questions or deletion-related assistance, contact info@itservice.fun. The inspected app does not implement a server-side account or deletion-request system, and the developer cannot directly delete files held only on your device or by a provider you choose.

Children’s privacy

No intended age groups have been specified. The inspected app does not include a child-specific service, accounts, advertising, or developer-operated personal-data collection. Personal information about children may nevertheless appear in documents selected or annotations entered by a user and will be processed locally in the same way as other document content. Contact the developer with any related privacy concerns.

Policy changes

This policy may be updated to reflect changes in the application or its data practices. Review the current policy when using an updated version of PDF Page Atelier.

Contact

It as a service
info@itservice.fun