Privacy Policy
This draft describes the current service and identifies unresolved details. It is not a completed privacy notice.
1. Who is responsible
Pandus is operated by Artem Davydov, an individual residing in Poland and the owner and developer of Pandus. Postal address: Koziorożca 19B/3, 80-299 Gdańsk, Poland. The service is free and accepts no payments.
Confirmation required: commercial status and the exact allocation of controller and processor responsibilities, including documents containing other people's personal data. Proposed email: support@pandus.app; it is not configured and verified as a working contact channel.
2. Data and purposes
To provide the merger, we process uploaded PDF contents, file names, page information, editing selections, generated documents and temporary session/job identifiers. Documents may contain personal data chosen by the uploader. A session cookie associates requests with a workspace. The application does not require an account or payment information.
Infrastructure handles network information such as IP addresses and request metadata to deliver and protect the service. Origin error logs can contain request information. Support messages would include the information you choose to send once a working contact channel is available.
3. Legal bases — review required
Confirmation required: document the applicable basis for each purpose. Potential bases for review include Article 6(1)(b) GDPR for providing the requested service where its requirements are met, and Article 6(1)(f) for proportionate security and operation following an interests assessment. Support and any legal obligations need their own assessment. These are candidates, not confirmed blanket justifications for all uploaded data.
Uploads may include data about third parties or special categories of personal data. Their handling and the respective responsibilities of the user and operator require specific review. Agreement to make an unsigned PDF copy is not consent to advertising or a general GDPR legal basis.
4. Files and retention
Files are held in a dedicated volume on the processing server. Workspace access expires one hour after session creation. Cleanup checks every 30 seconds; busy workspaces are deferred and failed deletions are retried. Outages or filesystem failures can delay removal. You may delete the whole workspace after processing finishes. Closing the tab or removing a page in the editor does not immediately delete server files.
Failed uploads and incomplete merge outputs are removed on the application's error path where possible. Accepted originals and previous successful outputs remain until workspace deletion or expiry cleanup. Application restart clears old workspace directories.
Confirmation required: hosting backups and snapshots, provider retention, security-log retention and future support-mail retention. The application cannot promise deletion from unverified provider backups.
5. Infrastructure providers and international transfers
Traffic passes through Cloudflare before reaching our hosting server. The application uses its own PDF worker rather than an external PDF-conversion or AI service. Cloudflare and the hosting provider nevertheless participate in delivery and processing.
Confirmation required: hosting provider identity and server country, applicable provider entities and subprocessors, processing agreements, countries involved, and any adequacy decisions or other transfer safeguards and how to obtain them. The operator's residence in Poland does not establish that all processing stays in Poland or the EEA.
6. Cookies, analytics and diagnostics
The application sets folio_session, a necessary random session cookie scoped to /api, with Secure, HttpOnly and SameSite=Strict protections in production and a one-hour lifetime. Application code does not use localStorage or sessionStorage to persist the editor.
No Web Analytics beacon was found in the audited source or sampled live HTML. Account settings still need confirmation. Cloudflare Network Error Logging headers were observed; supporting browsers may send connection-failure metadata to Cloudflare. This is distinct from Web Analytics. Other Cloudflare security features and cookies must be checked in the account before finalising this notice.
Advertising is only a possible future funding model. This draft does not authorise advertising trackers. Any future processing requires assessment, updated information and, where required, an effective consent and withdrawal mechanism before it starts.
7. Your rights
Depending on the processing and applicable conditions, GDPR provides rights to access, rectification, erasure, restriction, portability and objection. Where processing relies on consent, consent can be withdrawn without affecting earlier lawful processing. You may complain to a competent supervisory authority, including Poland's UODO.
Confirmation required: a working request channel and procedures for identity checks and handling requests. Do not send a request to the proposed mailbox until it is confirmed. The temporary service may no longer hold files after cleanup; we should not collect extra identifying data simply to retain documents.
8. Other disclosures and updates
The current application does not use document contents for AI training, profiling or automated decisions about people. Providing a PDF and a session is necessary to perform a merge; you can choose not to upload. Changes to this draft will be recorded before a final notice is approved.
Draft prepared 31 October 2026. Reference: GDPR. No claim of completed legal compliance is made.