Transparency & Trust

DocuNexa Privacy Policy

Last updated: September 30, 2026 • Canonical Domain: https://docunexa.pro.et

Privacy Summary at a Glance

Zero Document Uploads: Document processing for all 34 tools runs locally in your browser memory.
No Server Storage: Your documents are never stored, logged, or inspected on DocuNexa servers.
No Mandatory Accounts: All tools are free to use without creating an account or providing an email.
Transparent Advertising: Monetag advertising technology is integrated to fund free hosting; document processing remains client-side.

1. Introduction & Scope

DocuNexa ("we", "us", or "our") operates the website https://docunexa.pro.et. This Privacy Policy describes how we handle information when you access our website and use our client-side document utilities.

We believe your documents belong exclusively to you. Our architecture is designed from the ground up to minimize data collection and execute document processing directly on your personal device.

2. How Your Documents Are Processed (Client-Side Architecture)

DocuNexa features 34 specialized tools across PDF organization, optimization, conversion, editing, security, and intelligence.

Technical Data Flow for Supported Tools:

  • In-Memory Loading: When you drag or select a PDF, image, or document, the file is read into your browser's volatile RAM using standard browser APIs (FileReader, ArrayBuffer, and Uint8Array).
  • Local Execution: PDF manipulation (merging, splitting, chapter cutting, vector watermarking, password encryption/decryption, rotation, and reordering) is executed locally using client-side JavaScript, WebAssembly, and Web Worker threads.
  • Zero Transmission: The contents of your uploaded documents are never transmitted over the network to DocuNexa servers.
  • Immediate Disposal: Document data exists only during your active browsing session. When you navigate away, reload, or close your browser tab, the memory allocated for your document is reclaimed by your operating system.

3. Tool-Specific Disclosures & Technical Limitations

OCR PDF (Optical Character Recognition)

OCR is powered by Tesseract.js running in a local WebAssembly Web Worker. To recognize characters, the engine downloads public language trained data files (such as English or Amharic .traineddata.gz) from standard public open-source CDN repositories (jsdelivr) on-demand into your local browser cache/IndexedDB upon first use. The actual image rendering, canvas analysis, and text recognition occur entirely on your device; your document pages and images are never uploaded or transmitted to external servers.

Document Summarizer & Translation

Our Document Summarizer and Translation tools run local rule-based heuristic algorithms directly in your browser. They extract headings, overview paragraphs, and glossary matches locally. They do NOT transmit your document contents to cloud Large Language Models (LLMs) or external generative AI APIs.

Sign PDF & Redact PDF

Sign PDF stamps a visual signature appearance onto PDF pages and does not generate cryptographic X.509 digital certificates. Redact PDF applies visual blackout vector overlays to visually obscure content; for forensic low-level binary stream removal, specialized desktop tools should be used.

4. Cookies & Browser Local Storage

First-Party Cookies: DocuNexa does not currently set tracking or profiling cookies.

Local Storage: We use your browser's localStorage solely for functional interface preferences:

  • docunexa-theme: Stores your theme preference (light or dark) so the website displays correctly when you return.

You can clear this storage at any time through your browser settings without affecting the core functionality of the tools.

5. Third-Party Services, External Resources & Server Logs

DocuNexa strictly distinguishes local document processing from external resource downloads:

A. Document Processing (Local Only):

Document bytes, extracted text, and generated files are processed entirely in browser memory. No document content is transmitted to third parties or remote servers.

B. On-Demand OCR Language Data Retrieval:

When you initiate OCR recognition, the client-side Tesseract.js engine downloads public language model weights (e.g. .traineddata.gz) from the public jsDelivr CDN into your browser cache. This is an incoming download of optical recognition dictionary weights; your documents are never uploaded.

C. Typography & Fonts:

DocuNexa loads font stylesheets and font binaries (Inter and JetBrains Mono) from Google Fonts CDN (fonts.googleapis.com and fonts.gstatic.com).

D. Web Hosting Infrastructure Logs:

Like virtually all web applications, our edge serverless hosting provider records standard HTTP connection metadata (IP address, browser user-agent, operating system, and request timestamps) strictly for technical network routing, DDoS mitigation, and system performance. DocuNexa does not harvest or sell personal usage telemetry.

E. Advertising Delivery (Monetag & Plan Distinctions):

DocuNexa integrates Monetag (via tag.min.js and service worker) to display advertisements that support operating costs for free users. For anonymous visitors and registered Free plan users, Monetag advertising technology is used to deliver, measure, and optimize advertising impressions. For authenticated Ad-Free users, DocuNexa does not intentionally initialize Monetag advertising scripts or service workers for their account. In all cases, advertising scripts run in standard web isolation and have strictly zero access to your document files or local document processing memory.

F. Cryptocurrency Payment Processing & Bybit Verification:

When you choose to upgrade to the $2 USD Ad-Free plan, payments are made directly in cryptocurrency (USDT on the Polygon PoS network) to a Bybit-hosted deposit address. DocuNexa queries Bybit's read-only deposit record API (GET /v5/asset/deposit/query-record) to match and verify your on-chain payment. Public blockchain transaction information (including transaction hash, recipient address, block timestamp, confirmations, and amount) is retrieved and processed to confirm payment. Our database (Supabase) stores the minimum payment/order metadata (order ID, user ID, status, transaction ID, and timestamp) necessary to activate and maintain your Ad-Free entitlement. We do not process or store private keys, fund passwords, or personal financial account credentials. We do not claim 100% anonymity, zero data processing, or zero third-party requests; network operations and payment verifications require strictly disclosed server communications.

6. Advertising and Monetization Disclosures

DocuNexa offers free PDF tools supported by advertisements, alongside an optional $2 USD one-time Ad-Free plan.

Advertising Technologies & Plan Safeguards:

  • Free Users: For anonymous visitors and registered Free plan accounts, DocuNexa uses Monetag advertising technology. Monetag and its advertising partners may use cookies, device identifiers, IP addresses, and browsing telemetry to deliver, measure, and optimize advertisements.
  • Ad-Free Users: For authenticated accounts that have purchased the Ad-Free upgrade, DocuNexa does not intentionally initialize Monetag advertising for their account. The Monetag script tag is excluded from server-rendered pages and any previously active Monetag service worker registration is safely unregistered.
  • Document Isolation Guarantee: Third-party advertising tags run with standard web client permissions and have strictly zero access to your document bytes, in-memory PDF structures, or local file processing pipelines.
  • Google AdSense Status: Google AdSense is not currently active on DocuNexa. If AdSense or other providers are enabled in the future, this policy will be updated accordingly.
  • Ad Placement Boundaries: Advertisements are strictly separated from tool workspaces and will never disguise themselves as fake download buttons, deceive visitors, or overlay file upload and document manipulation controls.

7. Optional Accounts, Coupon Codes & Cryptocurrency Payments

While public PDF tools remain completely anonymous and account-free, users who voluntarily register an account or upgrade to Ad-Free provide limited information necessary to deliver and verify the service:

  • Account Identification: When creating an optional account, we store your email address and chosen plan status (Free or Ad-Free) managed securely through Supabase Authentication and PostgreSQL database.
  • Payment & Order Metadata: When initiating an Ad-Free upgrade, we record order identifiers, the required payment amount (USDT), expiration timestamps, and public blockchain deposit transaction hashes (txID) to confirm payment. We do not store or collect personal banking credentials, credit card numbers, or crypto private keys.
  • Coupon Code Redemptions: If you apply a promotional coupon code, we store the normalized code, the discount amount granted, and redemption timestamps associated with your payment order to enforce per-user redemption limits and prevent abuse.
  • Data Minimization: Payment and account records are used solely to verify entitlements, provide administrative support, and enforce usage policies. They are never sold or shared with marketing third parties.

8. Inquiries, Bug Reports & Communications

If you contact us via email or submit an issue on our public GitHub repository, we receive the information you provide (such as your email address, name or GitHub handle, and message details). This information is used exclusively to respond to your inquiry, troubleshoot bug reports, or consider feature recommendations. We do not sell, rent, or use contact information for unsolicited marketing.

9. User Rights & Data Retention

Because DocuNexa does not require accounts or store document contents, you retain complete sovereignty over your documents. If you have created an optional account, you may request deletion of your account and associated profile data by contacting us.

10. Changes to this Privacy Policy

We may update this Privacy Policy periodically to reflect technological adjustments, new tool features, or future advertising configurations. Any revisions will be published on this page with an updated "Last Updated" date.

11. Contact Us

If you have any questions, suggestions, or concerns regarding this Privacy Policy or our client-side architecture, please contact the maintainer:

Maintainer Contact: natanemyalew10@gmail.com

Issue Tracker & Repository: https://github.com/Nati-13/DocuNexa-

Dedicated Contact Page: Visit /contact

Privacy Policy — DocuNexa | DocuNexa