Privacy Policy

Last updated: November 2026

This Privacy Policy describes how AI Invoice Extractor ("the Application", "we", "our"), developed and maintained by Pedro Henrique Pereira Cardoso, handles, processes, and respects your data and personal information.

1. Information We Access via Google Workspace

AI Invoice Extractor integrates with your Google Workspace account via OAuth 2.0. The Application requests access strictly to the scopes necessary to execute invoice automation:

• Google Drive: Read access to inspect, parse, and download invoice documents (PDFs, images) from user-designated folders, and write access to organize or move processed files to designated archive folders.
• Google Sheets: Write and append access strictly to record structured invoice metadata (such as vendor name, invoice date, document ID, line items, and monetary totals) into spreadsheets selected by you.

2. How We Use Your Information

Data retrieved from your Google Workspace account is processed exclusively to deliver the functionality of the Application. Specifically, we do not:

• Use your documents, spreadsheet contents, or invoice data for advertising, profiling, marketing, or commercial brokerages.
• Sell, rent, or lease your invoice contents or personal data to any third party.
• Retain, collect, or upload your documents to external developer-owned servers.

3. Local Storage and Execution Environment

AI Invoice Extractor is built for self-hosted, containerized, or local user-managed deployments (e.g., Docker, local virtual environments). As such:

• All temporary files, cached tokens, and operational logs reside exclusively inside your deployment environment or on your local storage volumes.
• The Developer does not operate a central server collecting your invoices or Google credentials. You maintain physical and administrative custody of your data at all times.

4. Modular Architecture & User-Directed Data Routing

The Application is designed as a set of modular software building blocks (e.g., text parsing, image quality filters, LLM extraction endpoints, and validation gates). You, as the system administrator or workflow designer, determine how data flows between these components.

You are solely responsible for ensuring that any custom automation flows, webhooks, or third-party orchestrations (such as n8n workflows) you build using these modules route your sensitive data exclusively to authorized and secure destinations.

5. AI Processing: Cloud Providers vs. Local Inference

To extract structured fields from invoice text and images, the Application connects to artificial intelligence models chosen and configured by you:

• Third-Party Cloud AI Providers (e.g., OpenAI, Anthropic Claude, Google Cloud Gemini): If you configure the Application to use external cloud APIs, document text and image excerpts are transmitted over encrypted HTTPS connections to those providers. THIRD-PARTY PRIVACY DISCLAIMER: Once data reaches an external cloud provider, its storage, confidentiality, and retention are governed entirely by that provider's independent privacy policies and enterprise terms. The Developer does not control and cannot be held liable for third-party cloud data security or privacy practices. Users utilizing "Bring Your Own Credentials" (BYOC) must independently review their chosen provider's data protection agreements.
• Local / On-Premise Models (e.g., Ollama, Local LLMs): If you configure the Application to run against local models, all inference takes place entirely within your isolated computing environment. In this mode, no document text or image data is transmitted across the internet to commercial AI companies.

6. Google API Services User Data Policy Compliance

AI Invoice Extractor'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. Data Retention and Access Revocation

Because the Application runs in your self-hosted or local environment, you maintain direct control over data retention and can delete files, local databases, or Docker volumes at any time.

You can revoke the Application's access to your Google account at any moment through your Google Account Permissions management page.

8. Modifications to This Policy

We may update this Privacy Policy periodically to reflect enhancements, new supported engines, or regulatory changes. The latest version will always be published at this URL with an updated revision date.

9. Contact Information

If you have any questions or concerns regarding this Privacy Policy or data handling practices, please contact:

Pedro Henrique Pereira Cardoso
Email: support@pedro-cardoso.dev