Privacy Policy

Flipp is a browser-based file and PDF processing platform designed around a simple principle: your documents should not need to leave your device merely because you want to convert, merge, compress, split, protect, unlock, sign, or otherwise modify them.

This Privacy Policy explains what information Flipp handles, what happens to documents when you use our tools, what information may be collected by website infrastructure or analytics services, and the technical limitations you should understand before using the service.

Our Privacy-First Architecture

Flipp is designed around client-side processing.

When you use one of Flipp's supported file tools, the intended processing flow is:

Your file → Your browser → Processing on your device → Generated result → Your device

rather than:

Your file → Upload → Remote server → Processing → Download

This distinction is important. Flipp's core file-processing architecture does not require your PDF or other input document to be uploaded to a Flipp application server for processing. The processing logic runs inside your web browser using JavaScript and browser APIs.

This architecture is also reflected in the way Flipp's tools are implemented: PDF parsing, rendering, manipulation, compression, bundling, OCR, and PDF generation are performed using browser-side code and libraries. Because the document-processing work happens locally, Flipp does not need to maintain a central copy of your documents in order to provide the core conversion functionality.

What Happens When You Select a File?

When you select or drag a file into a Flipp tool, your browser gives the webpage access to that file through the browser's local file-handling mechanisms. Flipp can then read the file in your browser and perform the requested operation locally.

For example:

• PDF → PNG reads and renders PDF pages in your browser.
• Images → PDF reads selected images and constructs a PDF in your browser.
• Merge PDF reads multiple PDFs and combines them locally.
• Split PDF reads the selected document and creates the requested output locally.
• Compress PDF processes the document locally according to the selected compression method.
• Add Page Numbers modifies the document locally.
• Protect PDF applies the supported protection operation locally.
• Unlock PDF processes supported password/restriction removal locally.
• PDF → Text extracts text locally where supported.
• Text → PDF generates a PDF locally.
• Watermarking, signing, rearranging, and similar operations are likewise performed in the browser.

The exact capabilities and limitations can vary by tool and by the PDF itself.

Your Files Are Not Uploaded for Core Processing

Flipp's core PDF tools are designed so that the files you select remain on your device during processing. Your document is not intentionally transmitted to a Flipp processing server merely because you selected it in one of our tools.

This means there is no normal Flipp workflow in which:

1. you select a PDF,
2. Flipp uploads that PDF to a backend,
3. a remote server processes it,
4. the server stores the result, and
5. you download the processed document.

Instead, processing takes place within your browser. This architecture significantly reduces the amount of sensitive document data that needs to leave your device.

What Flipp Can and Cannot See

Because core document processing occurs locally, Flipp's application does not normally receive the contents of the files you process through those tools. This means Flipp is not designed to inspect, index, read, or maintain a server-side copy of the text, images, signatures, or other document content contained in your PDF.

However, this should not be interpreted as a promise that your entire interaction with the website is invisible to every third party. Website hosting, analytics, security infrastructure, your browser, your operating system, and your network provider can operate independently of Flipp's document-processing code. This distinction is why this policy separates document data from website usage data.

Document Data vs. Website Usage Data

These are two different categories of information:

Document data includes information contained inside files you select, such as:

• PDF text
• photographs and scanned pages
• names appearing inside documents
• signatures
• metadata contained in files
• other information embedded in the document

Flipp's client-side architecture is designed to keep this information on your device during core processing.

Website usage data is information associated with interacting with a website, such as browser/device information, pages visited, approximate geographic information, referral information, or technical request information, depending on the services currently enabled on the website. Website usage data should not be confused with the contents of a PDF.

No Flipp Document Storage

Flipp does not maintain a document-storage system for files processed through its core browser-based tools. There is therefore no Flipp document library where your processed PDFs are retained for later retrieval.

Generated files are made available to you through your browser so that you can save them to your device. Once you have saved a generated document, that copy is controlled by your device and operating system rather than by Flipp. Flipp cannot retrieve a file from your Downloads folder simply because it was previously generated using the website.

Temporary Browser Memory

Client-side processing does not mean that a file exists nowhere. Your browser must temporarily hold and process file data in memory while an operation is running. Depending on the tool, a browser may also use temporary browser-managed resources while reading, rendering, generating, or manipulating a document. This is necessary for local processing.

Flipp does not treat this temporary browser memory as permanent document storage. Users should nevertheless understand that browser memory is part of their local computing environment. The operating system, browser, extensions, malware, screen-recording software, or other software already present on a device can potentially access information on that device. Flipp cannot protect a device from threats that exist outside Flipp's application.

Browser Storage

Some web applications may use browser-managed storage or memory for technical reasons. Where Flipp uses browser storage, that storage is controlled by the browser on your device rather than by a Flipp document-storage server.

Browser storage can generally be cleared through your browser's controls, and its lifetime depends on the specific storage mechanism and browser behavior. Flipp does not use browser storage as a replacement for a remote document-storage system.

Downloaded Files

When Flipp finishes processing a document, the resulting file is delivered to your browser for you to save. The downloaded copy becomes a file on your device. Flipp does not control what happens to that copy after it has been downloaded.

If a document contains sensitive information, you are responsible for protecting the resulting file using appropriate device security, filesystem permissions, encryption, password protection, or other measures available on your device.

Network Requests and Website Infrastructure

"Client-side processing" specifically describes the processing of your files. It does not mean that loading a website requires absolutely no network communication.

Your browser must retrieve the Flipp website and its JavaScript, CSS, fonts, libraries, images, and other resources before the application can run. The website may also communicate with infrastructure used to host, deliver, secure, analyze, or otherwise operate the website. These website-level requests are separate from uploading your PDF for remote processing. Flipp's architecture is intentionally designed so that downloading the application and processing your document are separate operations.

Hosting and Cloudflare

Flipp is deployed using static web hosting infrastructure (such as Cloudflare Pages).

Hosting infrastructure is responsible for delivering the website's static files to your browser. It is not used as the processing environment for the PDFs handled by Flipp's core tools. Hosting providers may necessarily process technical request information associated with serving a website, such as IP addresses, timestamps, browser information, requested resources, and security-related information, according to their own infrastructure and privacy practices.

The hosting provider's ability to deliver Flipp's website should not be interpreted as the hosting provider receiving the contents of every PDF that you process.

Analytics

Flipp may use website analytics to understand how the website is used and which features are useful.

When analytics services are enabled, they can provide information such as:

• pages visited
• interactions with the website
• approximate geographic information
• browser/device characteristics
• traffic sources
• general usage patterns

Analytics are configured so that document contents are not intentionally sent as analytics data. Flipp does not use analytics as a mechanism for uploading PDF contents for processing. In the current implementation of this website, no third-party tracking scripts or web analytics trackers are embedded in the application code. If analytics providers or their configuration change in the future, this section will be updated accordingly.

Cookies

Flipp may use cookies or similar browser technologies where required for website functionality, analytics, security, or other technical purposes.

Cookies or browser storage used for website operations do not contain the contents of the PDFs processed through Flipp's core tools. You can manage or delete cookies through your browser's privacy settings. Disabling certain cookies may affect some website functionality or analytics behavior.

Third-Party Libraries

Flipp uses browser-side open-source libraries to provide PDF functionality. Depending on the tool, these include technologies such as:

• PDF.js for PDF parsing and rendering
• jsPDF for PDF generation
• PDF-lib for PDF manipulation
• JSZip for creating ZIP archives
• Tesseract.js for OCR/text recognition
• SignaturePad for visual signature drawing inputs

These libraries execute as part of the browser application. Using a third-party open-source library does not automatically mean that your PDF is uploaded to that library's developer or organization. In Flipp's client-side architecture, the library code operates locally against the file data supplied to it by your browser.

PDF Passwords, Protection, and Unlocking

Some Flipp tools interact with password-protected or restricted PDFs. These operations are particularly sensitive, so the same client-side architecture applies: supported password and PDF-protection operations are performed in your browser rather than by sending the document to a remote processing server.

When a PDF requires an opening password, that password is supplied by you to the local browser application for the operation. Flipp does not need to receive the password on a backend server in order to perform supported client-side processing.

We do not describe this security as military-grade, bank-grade, or unbreakable. PDF password protection itself also has technical limitations determined by the PDF format specification and the specific PDF library being used.

Digital Signatures

Flipp's Sign PDF functionality allows users to place a visual signature into a PDF.

A visual signature inserted into a PDF should not automatically be described as a legally certified digital signature, cryptographic signature, electronic-signature service, or identity-verification service unless the implementation explicitly provides those capabilities. Users should distinguish between adding a visual signature to a document and using a certified digital-signature system.

Security Model

Flipp's primary privacy/security advantage comes from minimizing data movement. If a sensitive PDF does not need to leave the device, there is no need for Flipp to maintain a server-side copy of that PDF merely to perform the conversion. This reduces an important category of risk: centralized document collection.

However, no web application can guarantee absolute security. The security of a locally processed document also depends on:

• the security of the user's device
• the user's operating system
• browser security
• installed browser extensions
• malware or other malicious software
• network security
• the integrity of the website code delivered to the browser
• the security of third-party infrastructure used to deliver the website

Flipp's client-side architecture reduces unnecessary document transmission, but it does not make a compromised device or browser secure.

Why Local Processing Matters

Traditional online document converters commonly need to receive a document before they can process it. That creates an additional data-transfer step:

Device → Internet → Server → Processing → Internet → Device

Flipp is designed around:

Device → Browser → Processing → Device

Keeping processing local means sensitive documents such as personal records, academic documents, contracts, scanned IDs, forms, or business files do not need to be routinely transferred to a remote processing backend merely to perform a conversion. This is the core privacy principle behind Flipp.

What We Do Not Collect Through Core PDF Processing

Flipp's core browser-based PDF processing is not designed to collect:

• the contents of your PDFs
• copies of your uploaded documents
• generated PDF contents
• document text for server-side processing
• images contained in your documents
• signatures contained in your documents
• PDF passwords for server-side processing

This list describes the document-processing architecture. It should not be interpreted as a guarantee that no technical information whatsoever is generated when visiting a website.

Information We May Collect

Depending on the features and services currently enabled on Flipp, we may receive limited website-related information such as:

• technical request information
• browser and device information
• approximate geographic information
• pages or features visited
• referral/traffic information
• analytics events
• information voluntarily provided when contacting us

We do not require an account for the core PDF-processing tools. If additional account-based or interactive features are introduced in the future, this Privacy Policy should be updated to explain what additional information those features require.

Information We Do Not Need

The core Flipp tools do not require users to create an account merely to process a PDF. Therefore, core processing does not require us to maintain a profile containing your:

• name
• email address
• phone number
• home address
• payment information

unless you voluntarily provide such information through another part of the website or a future service that explicitly requires it.

Data Retention

Flipp does not maintain a document-storage system for the files processed by its core browser tools. Because the core processing is performed locally, there is no normal server-side document-processing queue or document library from which Flipp needs to later delete your PDF.

Website analytics and infrastructure providers may retain technical or usage information according to their own retention policies. Those records are different from the contents of documents processed locally in your browser.

Your Responsibility

Privacy is shared between the application and the device on which it runs.

If you process highly sensitive documents, use a trusted and up-to-date browser and operating system, keep your device secure, avoid untrusted browser extensions, and protect downloaded files appropriately. If your device is compromised, local processing cannot prevent malicious software that already has access to your device from reading information available to the browser or filesystem.

Children's Privacy

Flipp's core tools are general-purpose file-processing tools and are not specifically directed at children. We do not intentionally request personal information from children through the core PDF-processing workflow.

If you believe a child has provided personal information through Flipp, contact us so the situation can be reviewed.

International Users

Flipp can be accessed from different countries. Because core document processing occurs in your browser, the document-processing operation itself is designed not to require transferring your document to a Flipp processing server in another country.

Website hosting, security, analytics, and other infrastructure may operate across different locations depending on the providers and services currently used by Flipp. Users should consider the laws and requirements applicable to them when processing particularly sensitive documents.

Your Privacy Rights

Because Flipp does not maintain user accounts or a server-side library of documents for its core tools, traditional requests such as "delete my stored PDF" may not apply to documents that were processed entirely in your browser.

You control local copies of documents through your device and browser. Where Flipp or a third-party service does process website-related personal information, applicable privacy rights may depend on the nature of the information, the service involved, and the laws applicable to you.

Changes to This Privacy Policy

Flipp may update this Privacy Policy when its tools, infrastructure, analytics configuration, or other relevant practices change. When material changes are made, the "Last Updated" date at the beginning of this page will be updated.

We encourage users to review this page periodically, particularly before processing highly sensitive documents.

Contact

If you have questions about this Privacy Policy, Flipp's client-side processing architecture, document handling, or privacy practices, contact us through the contact method provided on the Flipp website or repository.

If you believe you have identified a security or privacy issue, please report it responsibly so that it can be investigated.