TextToPDF LogoTextToPDF.net

Google Workspace API Limited Use Disclosure

The use of raw or derived user data received from Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.

  • Zero AI/ML Model Training: Raw, aggregated, or derived user data received from Google Workspace APIs (Google Docs™, Google Sheets™, Google Slides™) is processed strictly in-memory for real-time PDF generation and document utilities requested by the user. It is NEVER used, transferred, or sold to create, train, or improve foundational or generalized machine learning (ML) or artificial intelligence (AI) models.
  • Data Isolation & Retention: User document data is processed transiently during active API requests and is automatically purged within 15 minutes. No Google Workspace user data is permanently stored or logged.

Security and Privacy Framework

Last Updated: August 15, 2026

When you use TextToPDF to convert or extract document content, you need exact answers about where your files go, how long they exist, and who has access to them. We do not rely on vague terms like "files are deleted shortly." This page provides exact technical answers to how your files and data are processed.

Quick Summary of File Handling Rules

Security QuestionExact Answer & Technical Detail
Where is Text to PDF processed?Server Conversion Route: Text is sent to the PDF conversion route to generate the document. The route processes the request transiently and does not save the document content.
Where is PDF to Text processed?Local / Isolated Server: Text-layer extraction runs in-browser or on our isolated conversion server.
Where does OCR happen?Isolated Worker Server: Runs on our Linux worker servers (PyMuPDF & Tesseract) or in-browser Web Workers. No third-party AI APIs process your files.
How long are files retained?15 Minutes Maximum: Ephemeral server temporary files auto-delete after 15 minutes. Browser-processed tools retain files for 0 minutes.
Are files stored permanently?No: Permanent storage of uploaded document files is strictly prohibited by system architecture.
Are files used for AI training?No: Uploaded files and converted text are never used to train AI models or machine learning algorithms.
Does the [Google Workspace Add-on](https://workspace.google.com/marketplace/app/texttopdf_for_google_docs/842939753419) use AI services?No: The add-on uses Google-native PDF export and local document utilities. Google Docs, Sheets, or Slides content is not sent to AI services. TextToPDF’s optional AI tools are separate website-only features.
Are file contents logged?No: Document text and file payloads are never logged or inspected. Only anonymized technical HTTP status codes are recorded.
What happens to conversion history?Transient browser state for guests. Account dashboards record metadata only; server files purge within 15 minutes regardless.
Which third parties process files?None for document content. Cloudflare (CDN) and AWS (ephemeral hosting) handle infrastructure with 15-minute auto-purge lifecycle rules.
How to request manual deletion?Server files purge automatically after 15 minutes. For immediate manual purge, email support@texttopdf.net.

Detailed Tool-by-Tool Processing Routes

1. Text to PDF and Rich Text to PDF

  • Processing Location: Server conversion route. Text and Rich Text content is sent to the PDF conversion route to generate the document.
  • Data Transmission: Editor content is sent to the conversion route to create the PDF in memory. The document content is not saved or used to train AI models.
  • Retention Period: Transient processing. The route returns the generated PDF and does not retain the document content as a stored file.

2. Markdown to PDF

  • Processing Location: Local browser. Markdown files are read in the browser and converted through browser print.
  • Data Transmission: Markdown content is not sent to the TextToPDF backend.
  • Retention Period: 0 minutes (browser-only processing).

3. PDF to Text (Searchable PDFs)

  • Processing Location: In-browser text parser or isolated backend server engine for large documents.
  • Data Transmission: Searchable PDF files are read to extract embedded vector font layers.
  • Retention Period: Files uploaded for backend processing are stored in temporary storage and automatically deleted within 15 minutes.

4. Scanned PDF & Image to Text (OCR)

  • Processing Location: Isolated Linux worker servers (ocr-worker running PyMuPDF and Tesseract OCR) or in-browser Tesseract Web Workers.
  • Data Transmission: Scanned PDF pages are converted into temporary image frames for optical character recognition. No third-party AI processors, external cloud vision APIs, or data brokers are involved.
  • Retention Period: Temporary page images are purged immediately upon conversion completion, with a hard automated deletion limit of 15 minutes.

5. Google Workspace Add-on

  • Processing Location: Google-native PDF export and local document utilities.
  • Data Transmission: The add-on does not send Google Docs, Sheets, or Slides content to AI services.
  • AI Feature Separation: TextToPDF’s optional AI tools are separate website-only features and are not part of the add-on workflow.

AI Training Policy

We hold a firm policy regarding AI model training: Your document content is yours alone.

  • We do not use uploaded files to train AI, LLMs, or OCR recognition models.
  • We do not sell, license, or share user text with third-party AI companies.
  • We do not aggregate document text for data analytics.

Logging, Metadata, and Infrastructure

What We Log

  • Anonymized technical metrics (HTTP response codes, request duration, error rates, and IP-based rate limiting counters) to prevent DDoS attacks and ensure system stability.

What We NEVER Log

  • Document text, pasted content, file names, converted PDF bytes, or OCR extraction results.

Third-Party Infrastructure Providers

  • Cloudflare: Provides SSL encryption, DDoS mitigation, and global CDN caching for web assets. Cloudflare does not inspect or store document payloads.
  • Amazon Web Services (AWS): Provides ephemeral server hosting for backend OCR processing. Temporary storage buckets enforce automated 15-minute lifecycle deletion policies.

Manual Deletion Requests & Contact

All temporary files on TextToPDF servers are automatically destroyed within 15 minutes. If you wish to confirm an immediate manual deletion of any temporary session logs, contact our technical team:

  • Email: support@texttopdf.net
  • Response Time: All privacy and data deletion enquiries are acknowledged and processed within 48 hours.