Legal
Privacy Policy
Last updated: October 2026
1. Who we are & Controller Identity
EInvoiceFile (https://einvoicefile.com) provides an automated REST API for European e-invoicing format generation, conversion, and validation.
The service is operated by Md Adil Khan (“EInvoiceFile”, “we”, “us”), an individual proprietor based in India. We act as the Data Controller for your account details, billing metadata, workspace identifiers, and support messages.
For inquiries concerning data protection, GDPR compliance, or this policy, contact our data protection lead, Md Adil Khan, directly at mdadil.khan@einvoicefile.com or via our contact form.
2. Roles: Controller vs. Processor
- Data Controller: We determine the purposes and means of processing for user registration, authentication, API usage metrics, and customer support communications.
- Data Processor (Art. 28 GDPR): For electronic invoice files and payloads (XML, JSON, PDF) that you submit to the API, you (or your organization) act as the Data Controller, and we act as your Data Processor. Invoice payloads are processed strictly on your documented instructions pursuant to our binding Data Processing Agreement (DPA).
3. Data we collect
- Account & Workspace data: Work email, full name, account type (developer or company), country, company name, workspace identifiers, and encrypted session credentials.
- API keys and usage: Key identifiers, active plan, endpoint paths, response status codes, call counts, and timestamps. We do not log or retain invoice XML/PDF payload content in API logs.
- Billing & Subscriptions: Plan status and subscription identifiers. Subscription billing, tax collection, and payment processing are handled by Polar as Merchant of Record. We do not store payment card details on our servers.
- Support messages: Name, email address, and the query you send via Contact or email.
- Invoice documents: Processed ephemerally in volatile memory (RAM) strictly to complete the requested API conversion or validation and discarded immediately once the HTTP response is sent. Invoice bodies are never stored in databases or persistent disk archives.
4. Infrastructure & Cross-Border Transfers (GDPR Chapter V)
EU Data Residency: Our production application compute and database clusters are hosted exclusively within the European Union on Amazon Web Services in Frankfurt (eu-central-1) and MongoDB Atlas (EU Region).
International Operations & Support: Technical maintenance, infrastructure monitoring, and customer support are conducted by our engineering team located in India. Under Chapter V of the GDPR, remote administration and support from outside the EEA constitute an international transfer. To ensure full protection of account and operational data:
- Transfers are governed by the European Commission Standard Contractual Clauses (SCCs - Implementing Decision (EU) 2021/914) incorporated into our Data Processing Agreement.
- Operational access requires least-privilege role permissions, multi-factor authentication (MFA), and encrypted management tunnels.
5. Legal basis (GDPR)
Account, workspace, and billing coordination: Art. 6(1)(b) GDPR (performance of a contract). Operational security and fraud prevention: Art. 6(1)(f) (legitimate interests). Support inquiries: Art. 6(1)(b) or (f). Processing of invoice payloads: executed as a processor on the instructions of the customer (Art. 28 GDPR).
6. Recipients & Subprocessors
- AWS EMEA SARL: Cloud compute, API hosting, and networking in Frankfurt, Germany.
- MongoDB Ltd.: Account and operational workspace database in the EU.
- Polar Signals Inc. (Polar): Merchant of Record for checkout, subscription management, invoicing, and VAT compliance (independent controller for payment data).
- EInvoiceFile Operator Team (India): Technical maintenance and support under EU Standard Contractual Clauses (SCCs).
- Transactional Email Provider: Delivery of one-time passwords (OTP) and service notices.
7. Cookies & Local Storage
We do not use tracking cookies, advertising networks, or analytics beacons. We utilize only strictly necessary mechanisms:
einvoicefile_session: Encrypted, HTTP-only cookie essential for user authentication.localStorage: Used strictly to save local interface preferences (e.g. dark/light theme). Any API keys stored in client playground tools remain on your device and are never sent to third parties.
8. Retention
Account and workspace metadata are retained while your account remains active and are deleted upon account closure, except where statutory tax or accounting regulations require longer record-keeping. Technical API metrics follow your plan's rolling retention window. Invoice payloads are discarded immediately after the HTTP response and are not retained.
9. Your rights
Under GDPR Articles 15–22, you may request access, correction, erasure, restriction, portability, or objection regarding your account data. To close your account and request data erasure, email mdadil.khan@einvoicefile.com or use our contact form.
10. Security
Production traffic requires modern TLS in transit. Sessions use an encrypted cookie. See Trust & Security for architecture details. Report security vulnerabilities to security@einvoicefile.com.
11. Changes
We may update this policy as our service evolves. Material revisions affecting paid accounts will be notified by email where a valid contact address exists.