Privacy-first FAQ generation designed to minimize retained data.

Auto-FAQ processes your PDF to generate bilingual FAQs, applies a best-effort sensitive-data scrub before AI processing, and leaves final publication decisions under human review.

Last updated: April 5, 2026

What We Process

The service processes the uploaded PDF, your selected target language, optional topic hints, and the FAQ rows you approve for export.

What We Do Not Save

Auto-FAQ does not intentionally store PDFs, account profiles, or a permanent history of generated FAQ outputs on its own server.

Sensitive Data Redaction

Before text is sent to Gemini, Auto-FAQ performs a best-effort privacy scrub for common emails, phone numbers, payment card numbers, IBANs, and U.S. Social Security numbers.

Human Review

The generated FAQs are shown to you first, so you can remove anything you do not want included before exporting the final CSV.

1. Data We Process

We process the PDF content you upload, the target language you choose, short optional topic hints, and the FAQ items you approve for CSV export. This information is used only to generate, review, and export your FAQ draft for the current request flow.

2. Data Minimization

Auto-FAQ is designed to minimize retained data. The application does not intentionally store uploaded PDFs or a permanent FAQ history on its own server after request completion. Export file names are generic, and unnecessary file metadata is not forwarded to the AI model.

3. AI Processing And Redaction

Extracted PDF text is processed through Google's Gemini API to generate the bilingual FAQ draft. Before that request is made, Auto-FAQ applies a best-effort automated redaction pass for common sensitive patterns such as email addresses, phone numbers, payment card numbers, IBANs, and U.S. Social Security numbers.

This redaction step reduces risk, but it is not a guarantee that every type of personal or regulated information will be detected. Do not upload highly confidential, regulated, or special-category data unless you are authorized to do so and your deployment is configured for that use case.

4. Human Review And Export

Generated FAQs are shown to you first. You decide which FAQ cards to keep, remove, and export. Only the selected FAQ rows are sent to the export endpoint to create the final CSV file.

5. Security Measures

Auto-FAQ uses upload size limits, prompt-injection filtering, spreadsheet formula protection, basic rate limiting, and no-store/no-cache response headers on the FAQ endpoints. These measures are intended to reduce accidental exposure and abusive use.

6. Third-Party Processing

When FAQ generation runs, relevant extracted text is sent to the configured AI provider, currently Google Gemini. The provider may process data according to its own service terms, security controls, and logging settings for the API project used by the deployment.

7. Your Responsibilities

You are responsible for ensuring that you have the right to upload the source document and to process its contents. If you operate Auto-FAQ for others, you are also responsible for providing a lawful basis for processing, a public privacy notice, and any required vendor or transfer agreements.

8. Contact

Privacy questions should be directed to the organization or individual operating the specific Auto-FAQ deployment you are using. If you are preparing this project for public release, add your organization name and privacy contact details before launch.