Privacy Policy
for the PaperHopper app · Last updated: 13 November 2026
Contents
In short: PaperHopper runs no servers of its own, and we receive no data about you. Scans, PDFs, recognised text and settings are stored on your device. Your documents leave the device only when you set up an export destination yourself and send a scan there.
1. Controller
Florian Garding
Speemannsweg 14
47506 Neukirchen-Vluyn
Germany
Email: support@flogar.de
2. Data on the device
The app stores in its protected app directory on your device:
- raw photos, processed pages, thumbnails and the generated PDFs of your scans,
- the text obtained by text recognition (as an invisible text layer in the PDF),
- export profiles and settings (destination address, folder, file name pattern, filters),
- credentials for export destinations (passwords, API tokens, OAuth refresh tokens) in the system keychain (iOS) or keystore (Android); freely entered additional headers and form fields of the HTTP destination, by contrast, are stored with the export profiles, so do not enter any keys there,
- the supporter status, if you support the app as a supporter (see section 10).
This data is not transmitted to us. When you delete a document in the app, it is removed from the device; uninstalling the app deletes the app data. Credentials in the iOS keychain can survive an uninstall: so disconnect the cloud accounts and delete the export profiles beforehand. Deleting a profile alone does not revoke access at the provider. Depending on your device settings, app data may be included in device backups (iCloud, Google One); the privacy policies of Apple or Google apply to those.
3. Permissions
| Permission | Purpose |
|---|---|
| Camera | Capturing documents. The camera stream is analysed on the device only, for edge detection. |
| Photo picker (system dialog) | Only when you choose to import an existing image as a scan; the app does not get permanent access to your photos. |
| Internet / network | For uploads to the export destinations you configured, signing in with cloud providers, querying the supporter status from the store (section 10) and technical diagnostic data from text recognition (section 4). |
| Folder access (Files app / storage access) | Only for the folder you selected yourself in the “Folder” export destination. |
4. Text recognition (OCR)
Text recognition uses Google ML Kit in on-device mode. Images are processed on the device and are not transmitted to Google or third parties for analysis. The recognition model is bundled with the app on both platforms.
Irrespective of the content of your scans, the ML Kit library, according to Google, transmits technical diagnostic and usage data to Google: device model and operating system version, identifier and version of the app, an installation-specific identifier, performance metrics (for example the duration of recognition), configuration, type of event and error codes. Images and recognised text are not included. We do not receive this data. The recipient is Google (Google Ireland Limited or Google LLC, USA); Google processes this data under its own responsibility, and it may also be transferred to the USA in the process; Google’s privacy policy applies. The legal basis is our legitimate interest in text recognition that works without a server (Art. 6(1)(f) GDPR).
5. Export destinations in general
An export transfers the finished PDF (and, depending on the destination, title, file name and tags) directly from your device to the destination you configured: a folder, a Paperless-ngx server, WebDAV/Nextcloud, FTP, FTPS, SFTP, an HTTP endpoint, Google Drive, Dropbox, Microsoft OneDrive or the system share sheet. We operate no intermediate server. The operator of the destination is responsible for processing there. Note: plain FTP and HTTP transmit content unencrypted; use FTPS, SFTP, HTTPS or WebDAV over HTTPS where possible.
6. Google Drive
When you set up a Google Drive profile, you sign in with Google in the system browser (OAuth 2.0). The app requests only the https://www.googleapis.com/auth/drive.file scope. With it, PaperHopper can see and modify only files and folders it created itself; the rest of your Drive is not visible to the app.
Which Google user data the app accesses
- the email address of the connected Google account, to show in the export profile which account is connected,
- names and IDs of the folders PaperHopper created in your Drive, for the folder picker in the export profile,
- a refresh token that lets the app upload later without signing in again.
How the app uses this data
Only to upload your scan PDFs to the selected folder, to create a folder when needed and to show you the connection status. The data is not used for advertising, profiling or any other purpose and is not shared with third parties.
Where the data is stored
The email address and folder name are stored with the export profile on the device, the refresh token in the keychain or keystore. We have no access to them.
Revocation and deletion
“Disconnect” in the export profile revokes the token with Google and deletes it from the device. You can additionally revoke access at myaccount.google.com/permissions. PDFs uploaded by the app remain in your Drive until you delete them there.
PaperHopper’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
7. Dropbox
When you set up a Dropbox profile, you sign in with Dropbox in the system browser (OAuth 2.0). The app requests the permissions files.content.write (upload files, create folders), files.metadata.read (list folders for the folder picker and the connection test) and account_info.read (account name and email address for display).
Which Dropbox data the app accesses
- the email address of the connected Dropbox account, to show in the export profile which account is connected,
- the entries of the folders you open in the folder picker (only folders are shown and stored),
- a refresh token that lets the app upload later without signing in again.
How the app uses this data
Only to upload your scan PDFs to the selected folder, to create a folder when needed and to show you the connection status. The data is not used for advertising, profiling or any other purpose and is not shared with third parties.
Where the data is stored
The email address and folder path are stored with the export profile on the device, the refresh token in the keychain or keystore. We have no access to them.
Revocation and deletion
“Disconnect” in the export profile revokes the token with Dropbox and deletes it from the device. You can additionally revoke access at dropbox.com/account/connected_apps. PDFs uploaded by the app remain in your Dropbox until you delete them there.
8. Microsoft OneDrive
When you set up a OneDrive profile, you sign in with Microsoft in the system browser (OAuth 2.0). The app requests the permissions User.Read (email address or sign-in name of the account, for display), Files.ReadWrite (list and create folders, upload files) and offline_access (renew the sign-in). Files.ReadWrite technically permits access to all files in your OneDrive; PaperHopper uses the permission only to list folders for the folder picker, to create folders and to upload your scan PDFs. Other files are neither opened nor modified or deleted.
Which Microsoft data the app accesses
- the email address or sign-in name of the connected Microsoft account, to show in the export profile which account is connected,
- the folders in your OneDrive that you open in the folder picker,
- a refresh token that lets the app upload later without signing in again.
How the app uses this data
Only to upload your scan PDFs to the selected folder, to create a folder when needed and to show you the connection status. The data is not used for advertising, profiling or any other purpose and is not shared with third parties.
Where the data is stored
The account label and folder are stored with the export profile on the device, the refresh token in the keychain or keystore. We have no access to them.
Revocation and deletion
“Disconnect” in the export profile deletes the token from the device. With Microsoft itself, you revoke access at account.microsoft.com/privacy/app-access. PDFs uploaded by the app remain in your OneDrive until you delete them there.
9. No tracking, no advertising
The app contains no advertising or tracking services and uses no advertising identifiers; we receive no usage or crash data. Without any action on your part, the app transmits only the technical diagnostic data from text recognition (section 4) and the status query to the store (section 10), during which Apple’s or Google’s purchase component may send its own technical diagnostic data to the store operator. Independently of this, Apple (App Store) and Google (Google Play) process data under their own terms when you obtain the app.
10. Purchases (supporters)
If you decide to support the app as a supporter (subscription or one-off purchase), the purchase is handled entirely by Apple (App Store) or Google (Google Play). The app receives no payment details, no billing address and no account information; the privacy policy of Apple or Google applies to the payment. On the device, the app stores only the supporter status (active or not, selected product and, for subscriptions, the expiry date reported by the store) and silently queries it from the store when the app starts, in order to detect renewals, cancellations or refunds. This information is not transmitted to us.
11. Contact by email
If you write to support@flogar.de, we process your email address, the content, attachments and the time of the message in order to answer your request (Art. 6(1)(b) and (f) GDPR). In connection with the app, this is the only case in which we process personal data about you outside your device. Please send only what is needed for your question, and no passwords, access keys or scans with confidential content. Details on the mailbox provider and retention period can be found in the website privacy policy.
12. Legal basis and your rights
Processing on your device takes place for the performance of the contract of use (Art. 6(1)(b) GDPR); uploads to cloud services happen at your explicit request. You have the right to access, rectification, erasure, restriction of processing and data portability (Art. 15 to 20 GDPR). Where we process data on the basis of legitimate interests (Art. 6(1)(f) GDPR), you can object to the processing at any time (Art. 21 GDPR). Since we store no personal data about you apart from contact by email (section 11), you exercise these rights for the data on your device directly in the app or by disconnecting accounts and uninstalling; for everything else, an email to the address above is sufficient. You can also lodge a complaint with a data protection supervisory authority, for example at your place of residence (Art. 77 GDPR); the authority responsible for us is the State Commissioner for Data Protection and Freedom of Information of North Rhine-Westphalia, Germany.
13. Changes
This policy is updated when the app’s range of functions changes. The current version is always available at this address; the date above shows the revision.
14. Website flogar.de
The app itself contains no analytics or tracking tools of our own (for the diagnostic data from text recognition, see section 4). This privacy policy is published on our website flogar.de. When you visit the website, the hosting provider stores technically necessary server logs (truncated IP address, time, requested file), which are deleted after 30 days. We also use the web analytics software Matomo there, which we operate ourselves on our web space with the hosting provider; no data is passed on to third parties. It records the page visited, the referrer, clicks on outbound links (for example to the app stores), the time, browser, operating system, device type and browser language and the truncated, anonymised IP address. Matomo sets no cookies and stores nothing on your device; we cannot attribute the data to a person. Details are in the website privacy policy.
You can object to collection by Matomo here:
Only if you object is a cookie named “mtm_consent_removed” stored in your browser; the objection applies to this browser only, and if you delete your cookies you need to set it again.