AllDocs Privacy Policy
Effective date: 19 September 2026
Last updated: 22 September 2026
AllDocs - PDF & Document Tools ("AllDocs", "the App") is published under the brand Ba2 Labs and operated by Batuhan Şahin, an independent developer based in Trabzon, Türkiye.
Data controller: Batuhan Şahin
Brand: Ba2 Labs
Contact: support@ba2labs.com
Location: Trabzon, Türkiye
This Privacy Policy applies to users worldwide and describes processing under applicable privacy laws, including, where applicable, the EU GDPR, the UK GDPR, Türkiye's Law No. 6698 on the Protection of Personal Data ("KVKK") and other local privacy laws. It also serves as the information notice required by Article 10 of the KVKK. It is information about how your data is handled; you are not asked to accept it.
You can read it at any time in the App under Settings → Legal.
1. Scope
AllDocs is a document and PDF utility application. Depending on the feature, processing happens entirely on your device or uses the third-party infrastructure described below.
AllDocs does not require a traditional account, name, email address, telephone number or password.
2. Information stored on your device
AllDocs may store, in the App's private storage:
- scanned and imported documents;
- generated PDF, DOCX and XLSX files;
- OCR text and OCR confidence/correction information;
- document name, page count, size, folder and favorite status;
- AI results saved with a document (summaries, main points, exam questions, flashcards, translations, document information, extracted dates);
- questions and answers asked about a document, and selected-text answers;
- flashcard progress;
- the anonymous AI account identifier and token (Section 7);
- whether the AI notice has been shown, and which documents' text is currently on the AI service;
- rolling seven-day free-operation usage events (operation name and time);
- which version of the Terms of Service was shown to you, and when;
- for users in Türkiye, whether and when you gave or withdrew explicit consent to transfers abroad (Section 16).
The software components described in Sections 8 and 9 also keep their own records on your device: Google's User Messaging Platform stores your advertising consent choices, and the RevenueCat SDK caches your subscription status and its app user identifier.
Android automatic backup is disabled for AllDocs. App-private data is excluded from cloud backup and from device-to-device transfer, so none of it is copied to your Google account.
3. Camera and scanning
Camera access is requested only when you start scanning. It is used to capture document pages. Camera images are stored in the App's private storage and are not uploaded.
4. OCR and Google ML Kit
Free OCR runs on the device using Google ML Kit. AllDocs does not send the scanned image or the recognized text to Google.
ML Kit sends its own diagnostic information to Google: device information (such as manufacturer, model, OS version and build), package name and app version, a per-installation identifier, performance metrics (such as latency), API configuration, input/output sizes, feature versions, event types and error codes. Google states that ML Kit encrypts this data in transit and does not transfer it to third parties.
5. On-device document features
Ask Document / Belgeye Sor (showing the passages that answer a question) and Compare Documents / Belgeleri Karşılaştır run on the device. Their document content is not uploaded.
If you separately request a cloud AI operation, that operation is governed by Section 6.
6. Cloud AI
Cloud AI features run on Cloudflare Workers and Cloudflare Workers AI. They are available with Plus, and a user without Plus can use a single-right AI operation with a right earned by watching a rewarded advertisement (Section 8.3).
Current production models:
@cf/qwen/qwen3-30b-a3b-fp8for generation;@cf/qwen/qwen3-embedding-0.6bfor indexing/retrieval.
What is sent depends on the feature:
- document-wide operations (summary, main points, exam questions, flashcards, invoice/receipt extraction, important dates, translation): the document's text, page by page;
- questions about a document: the document's text is uploaded and indexed; the model receives your question, the most relevant passages and, for a follow-up question, up to four earlier questions and answers of the same conversation;
- selected-text operations: only the selected text (up to 4,000 characters);
- AI comparison summaries: only the sections that differ (up to 300 changes) and the two file names.
The original document file and page images are never sent.
Server-side document text, passages, search indexes, vectors and AI task data are deleted no later than 24 hours after upload, plus the cleanup interval (cleanup runs about every five minutes). They are deleted earlier when you delete the document, use a deletion control in Settings, or the document's text changes and is uploaded again.
Questions, answers, selected text and comparison differences are processed to serve the request and are not stored on the server.
Cloudflare states that it does not use customer content sent to Workers AI to train AI models or to improve Cloudflare or third-party services.
AI results you keep are stored on your device until the document is deleted.
6.1 Reporting AI output
Every AI answer and result in the App has a Report button. A report is sent to us only when you choose to send it, and contains the reason you pick, your optional comment, your request (for example your question) and the AI output you are reporting. It may therefore contain text from your document. The report does not contain your account identifier and is not linked to your account. We read reports to find and prevent offensive, harmful or inaccurate AI output. Reports are deleted 90 days after they are sent.
7. Anonymous AI account
An anonymous account is created the first time you use a cloud AI feature, or when you choose to watch a rewarded advertisement (the reward must be credited to an account). It consists of a randomly generated identifier (UUID) and a random token; the server stores only a SHA-256 hash of the token, together with the account's creation and last-use times.
The anonymous account does not contain your name, email address or telephone number. Its identifier is also given to RevenueCat as your subscription user identifier (Section 9) and to Google with a rewarded advertisement, so that Google's server can tell our server which account earned the reward (Section 8.3).
An account that has not been used for 12 months is deleted automatically, together with its subscription status, usage counters and earned rights, unless a Plus subscription on it is still active.
8. Advertising and Google AdMob
AllDocs shows advertisements from Google AdMob (Google Mobile Ads SDK) to users without an active Plus subscription.
Plus: subscribers see no advertisements. For a user whose Plus subscription is active when the App starts, the advertising SDK and the consent form are not started at all; after a purchase, no further advertisements are requested.
8.1 Advertising formats
- Banner: one banner at the bottom of the App's main screens. The first banner of a session may open larger, with Google's own control to fold it back. No banner is shown while a document, the scanner, an editor or the AI assistant is open.
- Full-screen advertisement: when you leave a document after completing an operation on it (for example a conversion, compression, watermark, page numbers, crop, text recognition, annotation, text, signature or page operation), at most once every three minutes. Opening and closing a document without working on it shows none.
- Rewarded advertisement (optional): see Section 8.3.
8.2 What the advertising SDK collects
According to Google, the Google Mobile Ads SDK automatically collects and shares with Google, for advertising, analytics and fraud prevention:
- IP address, which may be used to estimate the general location of the device;
- product interactions, such as app launches, taps and video views;
- diagnostic information, such as app launch time, hang rate and energy usage;
- device and account identifiers, such as the Android advertising ID and the app set ID.
Google states that this data is encrypted in transit (TLS). Google processes advertising data as an independent controller under its own privacy policy: https://policies.google.com/privacy and https://policies.google.com/technologies/partner-sites.
Your document content, recognized text, file names and AI questions are never used for advertising and are never given to the advertising SDK.
AllDocs does not use Android's Privacy Sandbox advertising permissions (Topics and attribution reporting); they are removed from the App.
You can reset or delete your Android advertising ID in your device's settings.
8.3 Rewarded advertisements
When a user without Plus asks for an AI operation that costs one right (a question, a selected-text operation or a comparison summary), AllDocs may offer to play a short advertisement in exchange for one AI right. Watching it is always optional.
- One watched advertisement earns one right, up to three per rolling seven days.
- The right is granted by our server only after Google's server confirms the view with a signed callback. With the advertisement, AllDocs gives Google your anonymous account identifier; Google's callback returns it to our server together with Google's transaction identifier, the reward amount and the time.
- Our server stores the transaction identifier, the anonymous account identifier and the time for 30 days (to enforce the weekly limit and to count each view once), and the balance of unspent earned rights until they are spent or you use "Delete all my data".
8.4 Consent
EEA, United Kingdom and Switzerland. AllDocs uses Google's User Messaging Platform (UMP), an IAB TCF-registered consent solution, and shows its consent form where required. No advertisement is requested before the form has been answered; if consent information cannot be obtained, the App relies only on a choice you made earlier and otherwise requests no advertisement. Your choices are passed to Google in the form's standard signal, and Google serves personalized, non-personalized or limited advertisements accordingly. You can change or withdraw your choices at any time in Settings → Ad privacy choices, which appears wherever the form applies.
Other regions, including Türkiye. AllDocs requests non-personalized advertisements. These are selected using contextual information such as the App and general location, not a profile of you. Google still uses the data listed in Section 8.2, including device identifiers, for frequency capping, aggregated reporting and fraud prevention.
This configuration may change if the advertising or consent implementation changes; this policy will be updated first.
9. Google Play and payments
AllDocs is distributed through Google Play. Plus payments are processed by Google Play; payment card details are never provided to AllDocs.
RevenueCat manages subscription status. The RevenueCat SDK starts when the App starts, so that the App knows whether Plus is active and can show the available offers; for users in Türkiye, only once they have given the consent described in Section 16. RevenueCat receives a RevenueCat-generated app user identifier, which becomes the anonymous account identifier once one exists (Section 7), purchase and subscription records received from Google Play, and technical information such as device model, operating system, app and SDK version, locale and store country, together with request metadata such as IP address. Google Play keeps its own purchase records under Google's terms.
10. Service providers and other recipients
| Recipient | Role | What it receives | Why |
|---|---|---|---|
| Cloudflare, Inc. (USA) | Processor | Document text, questions and conversation turns, selected text, comparison differences and file names, reports about AI output, anonymous account data, request metadata including IP address | Hosting the AI service, temporary storage, search and vector indexes, AI inference |
| RevenueCat, Inc. (USA) | Processor | App user identifier, purchase and subscription records, device/app technical data, request metadata | Subscription management |
| Google LLC / Google Ireland Limited (AdMob) | Independent controller | Data listed in Section 8.2; the anonymous account identifier with a rewarded advertisement | Advertising, measurement, fraud prevention; verifying rewarded views |
| Google (ML Kit) | — | Diagnostic data listed in Section 4 | On-device text recognition |
| Google (Google Play) | Independent controller | Purchase and payment data | Distribution and billing |
| Your calendar app | — | Only the date you choose, when you tap "Add to calendar" | Your own action; AllDocs does not read your calendar |
We do not sell personal data.
11. Logs
The AllDocs server writes only error names and HTTP status information to its application logs. It does not write document text, questions, AI answers or user identifiers to them.
Cloud infrastructure may generate its own technical and security logs, such as IP address, URL and time.
12. Aggregated AI cost records
AllDocs keeps an operational cost record containing the day, operation type, operation count and token totals. It contains no account identifier, document identifier, document text, question or answer, and is kept after an account is deleted.
13. Retention
| Data | Retention |
|---|---|
| Document text, passages, search index, vectors, AI task data (server) | At most 24 hours after upload, plus the ~5-minute cleanup interval; earlier on deletion |
| Questions, answers, selected text, comparison differences (server) | Not stored; processed only to serve the request |
| Reports about AI output you choose to send | 90 days; not linked to your account |
| Anonymous AI account (identifier, token hash, creation and last-use time) | Until you use "Delete all my data", or 12 months after its last use (not while a Plus subscription is active) |
| Subscription status record (active, expiry, last check) | Same as the account |
| Monthly AI usage counters (rights and token totals per UTC month) | Same as the account |
| Rewarded-view records (transaction id, account id, time) | 30 days; earlier with "Delete all my data" |
| Unspent earned AI rights | Until spent, or deleted with the account |
| Temporary charge records | Removed when the operation finishes; unfinished ones are refunded and removed after 30 minutes |
| Aggregated AI cost records | Kept; contain no account, document or text identifiers |
| Data on your device | Until you delete it or uninstall the App |
| RevenueCat, Google (AdMob, ML Kit, Play) | Under each provider's own retention policy |
14. Deletion
Delete one document: removes its local copy and its server-side document data. Other documents are not affected.
Settings → Delete my AI data: deletes all server-side document text, passages, search indexes, vectors and AI results made from them. It does not delete the anonymous account, subscription/usage records or anything on your device.
Settings → Delete all my data: additionally deletes the anonymous account, its subscription status record, monthly usage counters, rewarded-view records, unspent earned rights and open temporary charge records. The token stops working immediately. Using AI again creates a new anonymous account; an active Plus subscription can be restored with "Restore purchases".
Neither control deletes documents or saved results on your device, and neither deletes records held by RevenueCat, Google Play or Google AdMob. To have RevenueCat's record deleted, write to us (Section 15); for Google, use Google's own controls, such as your device's advertising-ID settings and https://myaccount.google.com.
Uninstalling removes the App's data on the device. It is not a server-side deletion request; server-side document data is still deleted within 24 hours, and the anonymous account is deleted automatically 12 months after its last use (Section 7).
Reports about AI output are not linked to your account, so neither control can find them; they are deleted after 90 days.
15. Your rights
Depending on your location, you may have the right to access, correct, delete, restrict or object to processing, to data portability, to withdraw consent, to be informed about international transfers, and to complain to a data-protection authority. Under Article 11 of the KVKK you may, among other things, learn whether your data is processed, request information about it, learn the purpose of processing, know the recipients in Türkiye and abroad, request correction or deletion, object to results produced solely by automated analysis, and claim compensation for damage caused by unlawful processing. In Türkiye you may complain to the Personal Data Protection Board (Kişisel Verileri Koruma Kurulu).
Requests: support@ba2labs.com. We answer within 30 days (KVKK Article 13) and within one month (GDPR Article 12).
The two deletion controls in Settings carry out deletion immediately. Because the account is anonymous, we can link an emailed request to server records only with information from your device; we may ask for it.
16. International transfers
AllDocs's providers are based outside Türkiye and the EEA, and processing takes place outside your country.
| Provider | Where data may be processed | Safeguard for EEA/UK/Swiss transfers |
|---|---|---|
| Cloudflare, Inc. | Cloudflare's global network, including the United States | Cloudflare Data Processing Addendum, incorporating the EU Standard Contractual Clauses (Commission Decision 2021/914), the UK International Data Transfer Addendum and Swiss amendments; Cloudflare also participates in the EU–U.S. Data Privacy Framework and its UK and Swiss extensions |
| RevenueCat, Inc. | United States | RevenueCat Data Processing Addendum, incorporating the EU Standard Contractual Clauses, the UK International Data Transfer Addendum and Swiss amendments |
| Google (AdMob, ML Kit, Play) | Google's global infrastructure, including the United States | For AdMob, the Google Ads Controller-Controller Data Protection Terms, incorporating controller-to-controller Standard Contractual Clauses; Google LLC also participates in the EU–U.S. Data Privacy Framework |
Transfers from Türkiye (KVKK Article 9). Türkiye has made no adequacy decision for these countries. The lasting mechanism the law provides for regular transfers is a standard contract announced by the Personal Data Protection Board, signed with each recipient and notified to the Personal Data Protection Authority; this policy will be updated when such contracts are in place.
Until then, for users in Türkiye, data is transferred to Cloudflare and RevenueCat only with your explicit consent, which the App asks for on a separate screen before your first use of Plus or the AI features, after telling you who receives what and the possible risks. Without it, RevenueCat is not started and nothing is sent to the AI service: Plus cannot be bought, restored or used, and everything else in the App works. You can withdraw the consent at any time in Settings → Privacy and data → Consent to transfer abroad; withdrawal does not affect transfers already made.
This consent covers Cloudflare and RevenueCat. Google collects the data described in Sections 4, 8 and 9 through its own SDKs and services, under its own terms.
17. Legal bases
| Processing | Data | EEA/UK (GDPR) | Türkiye (KVKK Art. 5) |
|---|---|---|---|
| Cloud AI features you request | Document text, questions, selected text, comparison differences, file names | Performance of a contract (Art. 6(1)(b)) | Necessary for the performance of a contract (5/2-c) |
| Anonymous account, AI allowance, abuse and cost limits | Account identifier, token hash, counters | Contract (6(1)(b)); legitimate interests in preventing abuse (6(1)(f)) | 5/2-c; legitimate interests (5/2-f) |
| Crediting rewarded advertisements | Account identifier, transaction id, time | Contract (6(1)(b)) | 5/2-c |
| Subscriptions | Purchase records, app user identifier | Contract (6(1)(b)); legal obligations (6(1)(c)) | 5/2-c; legal obligation (5/2-ç) |
| Personalized advertising (EEA/UK/Switzerland only) | Data in Section 8.2 | Consent (6(1)(a)), collected through the UMP form | — |
| Non-personalized advertising, frequency capping, measurement, fraud prevention | Data in Section 8.2 | As recorded in the consent form where it applies; otherwise legitimate interests in funding the free tier (6(1)(f)) | Legitimate interests (5/2-f) |
| Reports about AI output you send | Reason, comment, request, flagged output | Legitimate interests in keeping AI output safe and meeting app-store content rules (6(1)(f)) | 5/2-f |
| Deleting accounts unused for 12 months | Account data | Legitimate interests in not keeping data longer than needed (6(1)(f)) | 5/2-f; KVKK Art. 4 and 7 (storage limitation) |
| Transfers abroad to Cloudflare and RevenueCat (users in Türkiye) | Data in Sections 6, 7 and 9 | — (see Section 16) | Explicit consent (KVKK Art. 9), asked in the App before Plus |
| Security and technical logs | IP address, URL, time | Legitimate interests (6(1)(f)) | 5/2-f |
| Answering your requests | Your message and email address | Legal obligation (6(1)(c)) | 5/2-ç |
Personal data is collected by automated means through the App and its components.
18. Children's privacy
AllDocs is a general-purpose productivity app and is not directed to children under 13. Children under 13 should not use the App.
19. Security
AllDocs uses TLS for every connection, embeds no cloud secret keys in the App, stores only a SHA-256 hash of the authentication token, scopes search and vector retrieval to the user and document, requests only the Android permissions it needs, disables Android automatic backup, and uses no App-owned analytics or crash-reporting SDK.
No method of electronic storage or transmission is completely secure.
20. Changes
This Policy is updated when features, providers, data practices or legal requirements change. The "Last updated" date changes with every material revision.
21. Contact
Batuhan Şahin / Ba2 Labs
support@ba2labs.com
Trabzon, Türkiye