Legal
Privacy Policy
Last updated: September 18, 2026
This Privacy Policy describes how ParseMania (“ParseMania,” “we,” “us,” or “our”) collects, uses, stores, discloses, and otherwise processes personal data when you visit parsemania.com, create an account, connect third-party services (including Google), or use our accounts-payable automation, invoice capture, matching, export, and related software (the “Services”). It is written for customers, their authorized users, website visitors, and Google OAuth verification reviewers. It is intended to meet Google API Services User Data Policy (including Limited Use), the EU/UK GDPR, the Swiss Federal Act on Data Protection (FADP), and U.S. state privacy laws such as the CCPA/CPRA.
Controller for personal data processed through the Services: ParseMania, Switzerland. Privacy contact: privacy@parsemania.com. Legal: legal@parsemania.com. Support: support@parsemania.com.
1. Scope and roles
We act as an independent controller for account, billing, website, security, and product-improvement data. For invoice files, email attachments, Drive documents, vendor records, and accounting exports that you and your organization place in the product, we generally act as a processor on behalf of the customer organization (the controller). Your organization is responsible for having a lawful basis to connect mailboxes and Drive folders and to process invoices that may contain personal data of vendors, employees, or counterparties.
This Policy applies to the public website, authenticated product, APIs, webhooks, background workers, Google push notifications, email we send, and cookies. It does not apply to third-party sites linked from the Services (Google, Intuit QuickBooks, Stripe, OpenAI or other model providers, hosting, analytics) except as described in the sharing sections below.
2. Summary for Google API verification
ParseMania is an accounts-payable and document-processing product. Customers optionally connect a Google account so we can find invoice-like documents and process them into structured bills. This is not a general-purpose email client, not a Drive file manager for unrelated files, and not an advertising product.
- Gmail (restricted): scope
https://www.googleapis.com/auth/gmail.readonly— read-only access to Gmail to discover messages that look like they contain invoices or similar documents, download those attachments, and ingest them. - Google Drive (sensitive / Drive): scope
https://www.googleapis.com/auth/drive— used so the customer can pick folders to monitor, list files in those folders, download candidate documents, and receive change notifications. We do not use Drive as a general dump of the user's entire Drive for unrelated purposes. - Basic profile:
openid,email,profile— identify which Google account was connected. - Background operation: after a mailbox or folder is connected, our servers continue to watch and ingest documents even if no one has the ParseMania website open in a browser.
- Limited Use:Google user data obtained via Google APIs is used only to provide and improve user-facing features of the invoice capture workflow. We do not sell it. We do not use it for advertising. We do not use it to train generalized AI/ML models independent of providing the customer's own features. Human access is limited as described in Section 8.
3. Categories of information we collect
3.1 Account and organization data
When you register or are invited, we collect name, work email, authentication identifiers (including hashed credentials or OAuth identifiers), organization name, role, subscription and billing status, and settings (for example CSV column layouts, QuickBooks mapping preferences, notification preferences).
3.2 Payment data
If you purchase a subscription, payment is processed by Stripe. We receive limited billing metadata (customer id, subscription status, last four digits or similar non-sensitive descriptors). We do not store full payment card numbers on our servers.
3.3 Customer content (invoices and AP data)
We process PDFs, images, spreadsheets, extracted invoice fields (vendor name, address, invoice number, amounts, line items, tax, dates), vendor master data, matching results, exception queues, chat/agent transcripts related to processing those documents, export files, and accounting payloads (for example QuickBooks bills and GL mappings). This content often includes personal data of vendors and may include employee names on invoices.
3.4 Google account connection data
If you connect Google, we store OAuth access and refresh tokens in encrypted form, the Google account email and display name, connection status, watch/channel identifiers for Gmail and Drive push notifications, history or page tokens needed to resume sync, and identifiers of the Drive folders you chose to monitor. We store copies of ingested files and relevant message metadata needed to avoid re-processing the same attachment (for example Gmail message id, attachment id, Drive file id, checksums).
3.5 Technical, security, and usage data
We collect IP address, user-agent, timestamps, authentication events, error logs, job queue status, approximate device/browser information, and, if you consent to marketing cookies, advertising or analytics identifiers. We use Sentry or similar tools for application error tracing. Server logs may include request paths and truncated error messages.
3.6 Communications
If you email us, book a demo, or submit the contact form, we collect the content of that communication and contact details you provide.
3.7 Information we do not seek
We do not require special-category data (health, religion, biometrics) to use the Services. Invoice documents may incidentally contain such data if a customer uploads it; we process it only as part of the document the customer submitted. The Services are not directed to children.
4. Google Gmail — restricted scope (read email)
With your organization's explicit OAuth consent, we request gmail.readonly. This scope allows our servers to list and read Gmail messages and attachments. We cannot send mail, delete mail, or change labels through this scope.
4.1 Why we need read access
Customers receive supplier invoices as email attachments. To automate capture, we must search the connected mailbox for messages that match document-oriented queries (for example PDF or image attachments that look like invoices), download those attachments, and pass them through our extraction and matching pipeline. Read-only access is the minimum Gmail scope that supports attachment discovery and download at scale.
4.2 What we actually read
In practice we filter for invoice-like messages using search queries and attachment type checks (PDF and common image types). We use message headers (From, Subject, Date, Message-ID) and attachment metadata to de-duplicate and to show source context in the product. We do not build a general email archive, we do not surface your entire inbox in a mail UI, and we do not use Gmail content for advertising or for contacting people in your inbox.
4.3 What we store from Gmail
- OAuth tokens (encrypted) and mailbox identity (email address).
- Identifiers of processed messages/attachments so we do not ingest the same file twice.
- Copied attachment files that we classified as candidate invoices, plus extracted structured fields.
- Watch state (history id and expiration) so Gmail push can resume after restarts.
4.4 What we do not do with Gmail data
- We do not sell Gmail data.
- We do not use Gmail data for ads, retargeting, or credit scoring.
- We do not transfer Gmail data to third parties except subprocessors needed to run the capture pipeline (hosting, encrypted storage, AI extraction for that customer's documents) under Section 9.
- We do not allow employees to browse customer mailboxes as a matter of course.
- We do not use Gmail to send mail on your behalf.
5. Google Drive — monitoring folders
With your organization's explicit OAuth consent, we request Google Drive access so you can select one or more folders (for example an “Invoices” shared drive folder). We list those folders, watch for new or changed files, download candidate documents, and ingest them the same way as email attachments.
5.1 Why this access is needed
Many finance teams drop supplier PDFs into a Drive folder instead of (or in addition to) email. Monitoring requires listing children of the chosen folder, reading file metadata, downloading file content, and registering a changes channel so Google can notify our webhook when files appear. The Drive scope we request is used to implement folder picking, watches, and downloads for those selected locations.
5.2 What we monitor
We monitor folders the customer configures. We are not a backup product for the rest of Drive. Files outside configured sources are not ingested as invoices. We may list parent/child folder names as needed for the folder picker UI.
5.3 What we store from Drive
- Folder ids and names you selected as sources.
- File ids, names, mime types, and modification tokens of ingested files.
- Copied file bytes for candidate invoices and extracted fields.
- Watch channel id, resource id, and page token for change notifications.
5.4 What we do not do with Drive data
- We do not use Drive files to train public models.
- We do not share Drive contents with other ParseMania customers.
- We do not use Drive as a marketing list or to scrape unrelated personal files.
6. Background processing when the browser is closed
Invoice capture is a server-side, always-on workflow. After you connect Gmail or Drive and leave sources enabled, ParseMania continues to operate even if you are not signed in and even if no browser tab is open.
6.1 How background ingest works
- Gmail push: we register a Gmail
users.watchagainst a Google Cloud Pub/Sub topic. When new mail arrives, Google notifies our webhook. Our backend then reads only the new history and downloads matching attachments. - Drive push: we register a Drive changes channel pointing at our Drive webhook. Google notifies us of changes; we then fetch new files in monitored folders.
- Polling fallback: if push is unavailable or expired, scheduled jobs poll Gmail and Drive on the server.
- Watch renewal: Gmail and Drive watches expire. Our servers renew them in the background so monitoring does not stop overnight.
- Agent jobs: extraction, vendor matching, duplicate checks, GL suggestions, and exports run as background jobs. Chat in the product is a UI over that pipeline; the pipeline does not require the UI to be open.
6.2 What this means for you
Connecting Google is not a one-time import while you watch the screen. It is an ongoing authorization for our servers to read new invoice-like mail and folder files until you disconnect the integration, revoke access in your Google Account, or close the customer account. You can stop background access at any time as described in Section 15.
7. How we use information (purposes and legal bases)
Under GDPR/UK GDPR/FADP we rely on one or more of: performance of a contract (providing the Services you subscribed to); legitimate interests (securing the product, preventing abuse, limited product analytics); consent (marketing cookies, optional Google connection, optional marketing email); and legal obligation (tax, accounting, responding to lawful requests).
- Create and authenticate accounts; enforce roles inside an organization.
- Ingest documents from uploads, email, Gmail, Drive, and APIs; extract fields with automated systems including third-party AI models acting as subprocessors.
- Match invoices to vendors and purchase data; surface exceptions.
- Export bills to CSV or QuickBooks and store mapping history.
- Bill subscriptions and prevent fraud.
- Send transactional email (verification, incidents, product notices).
- Debug errors, monitor uptime, and improve reliability.
- Comply with law and enforce our Terms of Service.
We do not use Google user data obtained via restricted scopes for purposes other than the user-facing invoice capture, review, matching, and export features.
8. Google Limited Use, AI, and human access
ParseMania's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
- Gmail and Drive data is used solely to provide features that are prominent in the requesting application's user interface: finding invoices, extracting them, matching them, and exporting them to the customer's accounting workflow.
- We do not use that data to serve advertisements. We do not sell it. We do not use it for determining creditworthiness or for unrelated profiling.
- We do not allow humans to read Google user data unless: (a) we have the user's consent for specific messages/files (for example a support ticket where you paste an invoice); (b) it is necessary for security, abuse investigation, or complying with law; (c) the data is aggregated and no longer attributable; or (d) an operation is performed by automated systems with limited, logged, need-to-know engineering access to keep the service running.
- AI/ML: we may send document images or text you submitted (including Gmail attachments and Drive files ingested as invoices) to model providers solely to extract invoice fields for that customer. We do not use Google-sourced Gmail or Drive data to train generalized models that serve other customers. We instruct providers not to use customer content to train their foundation models where the provider offers that contractual control.
9. Sharing and subprocessors
We do not sell personal information. We share data with:
- Google: to authenticate, watch, and fetch Gmail/Drive data you authorized.
- Hosting and database providers: to store encrypted tokens, files, and application data.
- AI extraction providers: to parse invoice documents into structured fields.
- Stripe: payments.
- Intuit QuickBooks: if you connect QuickBooks, we send bills and related accounting data you approve.
- Email delivery: transactional messages.
- Error monitoring (e.g. Sentry): diagnostic events; we minimize payload content.
- Advertising/analytics pixels: only if enabled by us and accepted by you (see Cookies).
- Professional advisers and authorities: where required by law or to protect rights.
- Corporate transactions: if we merge or sell assets, data may transfer under continuing confidentiality and this Policy or a successor notice.
Organization admins and teammates you invite can see customer content in that organization, including ingested invoices.
11. Retention
How long we keep each category of data, how we delete it, and how often we review those rules is set out in the Data Retention and Deletion Policy. That policy is reviewed at least once every 12 months. In short: account data is kept for the life of the account and then up to 24 months; bank data from Plaid is deleted when the bank is disconnected; accounting records may be kept for the statutory period (up to 10 years); server logs are kept 30–90 days; backups roll off within 90 days.
12. Security
We use HTTPS, encryption of Google OAuth tokens at rest, access-controlled databases, organization-scoped authorization checks, and monitoring. Optional authenticator-app secrets are encrypted at rest, and a second factor is required before a bank is connected. No method of transmission or storage is 100% secure. You must protect account credentials and only connect Google accounts your organization is authorized to use.
If we become aware of a personal data breach likely to result in a high risk to individuals, we will notify affected customers and, where required, supervisory authorities without undue delay in line with GDPR Articles 33–34 and Swiss FADP.
13. International transfers
ParseMania is established in Switzerland. Personal data may be processed in Switzerland, the European Economic Area, the United Kingdom, and the United States (for example cloud hosting, Google, Stripe, model providers). Where GDPR applies to a transfer to a country without an adequacy decision, we use appropriate safeguards such as the European Commission Standard Contractual Clauses (and UK/Swiss addenda as needed), plus supplementary measures where appropriate. Switzerland has issued adequacy decisions for certain countries; transfers still follow FADP requirements.
14. GDPR, UK GDPR, and Swiss FADP rights
If you are in the EEA, UK, or Switzerland (or otherwise protected by these laws), you may have the right to: access; rectification; erasure; restriction; objection to processing based on legitimate interests or direct marketing; data portability; withdraw consent without affecting prior lawful processing; and lodge a complaint with a supervisory authority (in Switzerland, the FDPIC; in the EU, your local DPA; in the UK, the ICO).
To exercise rights, email privacy@parsemania.com. We may need to verify your identity and, if you are an end user of a customer organization, we may redirect the request to that organization when they are the controller of the invoice content.
We do not use automated decision-making that produces legal or similarly significant effects solely by automated means without human involvement in the sense of GDPR Article 22. Invoice extraction and matching are assistive; users can review exceptions and accounting exports.
15. How to disconnect Google and delete data
- In ParseMania, disconnect the Gmail or Drive source / Google connection. We will stop watches, stop polling, and drop stored refresh tokens for that connection.
- In your Google Account, open Third-party connections and revoke ParseMania. This independently invalidates our tokens.
- Request deletion of ingested files and account data via privacy@parsemania.com or in-product account deletion where available. Organization admins control teammate access.
Revoking Google access stops new Gmail/Drive reads. Copies of invoices already ingested into your ParseMania workspace remain until deleted under our retention rules, because they have become part of your AP records in the product.
16. United States privacy (CCPA/CPRA and similar state laws)
If you are a resident of California, Colorado, Connecticut, Utah, Virginia, or another U.S. state with a comprehensive privacy law, you may have rights to know / access, correct, delete, and obtain a portable copy of personal information, and to opt out of sale, sharing for cross-context behavioral advertising, and certain profiling.
We do not sell personal information for money. If marketing pixels are enabled and you accept them, some disclosures to advertising networks may be “sharing” or a “sale” under California law. You may opt out via Cookie settings. We do not use or disclose sensitive personal information for purposes other than those permitted by CPRA for providing the Services (for example, account login). We do not use Google mailbox or Drive contents for cross-context advertising.
Categories collected: identifiers; commercial information; internet/electronic activity; professional information (vendor/AP data); inferences limited to product operation (for example suggested GL codes); and customer content. Sources: you, your organization, Google if connected, payment processors, and automatic collection. Business purposes: as in Section 7. We do not discriminate for exercising privacy rights. Authorized agents may submit requests with proof of authority. Shine the Light: we do not disclose personal information to third parties for their own direct marketing in the manner regulated by Cal. Civ. Code § 1798.83 as a selling practice.
17. Children
The Services are for business users and are not directed to children under 16 (or under 13 where COPPA applies). We do not knowingly collect personal information from children. If you believe a child provided data, contact privacy@parsemania.com and we will delete it.
18. Do Not Track and global privacy controls
Our cookie banner and Cookie settings are the primary mechanism for non-essential tracking. Where we detect a legally recognized opt-out preference signal for sale/share of personal information and marketing tags are in use, we will treat it as an opt-out of those tags to the extent required and technically feasible.
19. Third-party services and your configuration
Google, Intuit, Stripe, and model providers have their own privacy policies. Your organization must configure Google Workspace sharing, Drive permissions, and mailbox access in line with your internal policies. You represent that you have authority to connect any mailbox or Drive folder you authorize.
20. Changes
We may update this Policy to reflect product, legal, or Google policy changes. The “Last updated” date will change. Material changes will be indicated on this page and, where required, by email or in-product notice. Continued use after the effective date constitutes acceptance where permitted by law. For Google restricted scopes, we will not expand use of Gmail/Drive user data beyond this Policy without appropriate notice and, where required, new consent.
21. Contact, complaints, and representatives
Privacy requests: privacy@parsemania.com. We aim to respond within 30 days (or sooner if a state law requires). EU/UK users may also complain to their supervisory authority. Swiss users may contact the Federal Data Protection and Information Commissioner (FDPIC).
If we appoint an EU Article 27 representative, we will publish those details here. Until then, contact the controller at the email above.
22. Additional disclosures for Google App Verification reviewers
Application name: ParseMania. Domain: parsemania.com. Scopes requested include gmail.readonly (restricted), Drive (sensitive), and standard OpenID profile scopes. User data is stored in our production datastore with encryption of OAuth secrets. Access is organization-scoped. Background workers and Google push webhooks are first-class parts of the product, not optional client-only scripts. Demonstration video and this Policy are intended to show: (1) OAuth consent, (2) folder/mailbox connection, (3) automatic ingest without the UI open, (4) invoice review in product, (5) disconnect/revoke. We request only scopes used by these features.