Skip to content

Last updated: July 27, 2026

This Privacy Policy applies specifically to the data practices associated with the Avanquest Developer Tools and related services. It outlines how we collect, use, disclose, and protect Personal Data from Developers and End Users interacting with Developer Applications. In addition to the provisions detailed here, this Privacy Policy incorporates and aligns with the Avanquest Global Privacy Policy, which provides a comprehensive overview of our general data-handling practices. For more details, please refer to the Avanquest Global Privacy Policy.

1. Introduction

Welcome to Avanquest Developer Tools Privacy Policy. We are committed to protecting the privacy of our customers and ensuring compliance with applicable privacy laws, and their End Users (as defined in the Developer License Agreement). This Privacy Policy explains how we collect, use, disclose, and protect your Personal Data when you interact with our Developer Tools and the SodaPDF platform. The Personal Data processing activities of End Users is governed by the applicable Data Processing Agreement (DPA), where Avanquest acts as a data processor.

2. Scope

This Privacy Policy applies to Personal Data collected from website visitors, service users, including account holders, and any other data subjects for whom Avanquest acts as a Data Controller. It explicitly excludes scenarios where Avanquest functions as a Data Processor, such as handling End User data from Developer Applications, which are governed by our Data Processing Agreement (DPA). This Policy serves as a supplement to, and does not replace, the Avanquest Global Privacy Policy.
In accordance with Quebec’s Charter of the French Language (Bill 96), this Privacy Policy is available in French on our website. Quebec residents may request any privacy-related communication in French by contacting us at dpo@avanquest.com.


The Developer Tools and associated services are intended for use by adults and business entities. Use of the Service is subject to the minimum age requirements set out in Section 10.3 below. We do not knowingly collect Personal Data from individuals below the applicable minimum age in their jurisdiction.

3. Beta and Feedback Data Disclaimer

Beta Services: Beta services may have reduced functionality, limited availability, or different operational characteristics compared to production services. Beta services may be modified or discontinued at any time. All data protection and security measures described in this Privacy Policy apply equally to beta and production services. The ‘beta’ designation relates to service maturity and feature completeness, not to the level of data protection applied.

Feedback Data: Data collected as part of feedback or user experience testing is anonymized where possible. By submitting feedback, you agree that we may use this information to improve our services without being obligated to implement suggested changes.

4. Data Controller and Contact Information

The data controller for this Service depends on the jurisdiction of the data subject:

  • For data subjects in the European Economic Area (EEA), United Kingdom, and Switzerland: The data controller is Avanquest Software SAS, a company incorporated under French law, registered at Immeuble Adamas 2 rue Berthelot 92400 Courbevoie, France. Data Protection Officer: dpo@avanquest.com.
  • For data subjects in Canada (including Quebec): The data controller is Avanquest Software (7270356 Canada Inc.), 400-1980 Rue Sherbrooke O, Montréal QC, H3H 1E8, Canada. Person responsible for the protection of personal information: dpo@avanquest.com.
  • For all other jurisdictions: The data controller is Avanquest Software SAS, contactable at dpo@avanquest.com.

The Canadian entity (7270356 Canada Inc.) operates the technical infrastructure for the Service. Where Avanquest Software SAS is the controller and the Canadian entity processes data on its behalf, the Canadian entity acts as a data processor under a Data Processing Agreement incorporating Standard Contractual Clauses for international transfers.

5. Definitions

In addition to the terms defined in the Developer License Agreement, the following terms and definitions apply specifically to this Privacy Policy: 

1. Personal Data: Any information relating to an identified or identifiable natural person. An identifiable person is one who can be identified, directly or indirectly, by reference to an identifier such as a name, identification number, location data, online identifier, or one or more factors specific to the physical, physiological, genetic, mental, economic, cultural, or social identity of that person.

2. Data Subject: The individual to whom Personal Data relates. For the purposes of this policy, Data Subjects may include both Developers who use our tools and End Users who interact with Developer Applications.

3. Controller: The entity that determines the purposes and means of processing Personal Data. In the context of our Developer Tools, the Developer typically acts as the Controller with respect to the End User data.

4. Processor: The entity that processes Personal Data on behalf of the Controller. Avanquest acts as a Processor when handling End User data as directed by Developers who use our Developer Tools.

5. Developer: A business or individual using the SodaPDF Developer Tools to build and manage applications. Developers are responsible for complying with applicable data protection laws and ensuring that End Users’ rights are respected.

6. End User: An individual who uses the Developer Applications created by Developers. End Users are Data Subjects whose Personal Data may be processed via the Developer Applications.

7. Applicable Laws: All relevant legislation and regulations that govern the processing of Personal Data, including but not limited to Law 25 (Quebec), the General Data Protection Regulation (GDPR), the California Consumer Privacy Act (CCPA), and the California Privacy Rights Act (CPRA).

8. Data Processing Agreement (DPA): A legally binding agreement between a Controller and a Processor that outlines the terms and conditions of data processing activities, ensuring compliance with applicable data protection laws.

9. GDPR (General Data Protection Regulation): A comprehensive data protection law enacted by the European Union, which sets out obligations for organizations that process Personal Data of EU residents and grants rights to Data Subjects.

10. CCPA and CPRA: The California Consumer Privacy Act (CCPA) and its amendment, the California Privacy Rights Act (CPRA), are state-level data protection laws that provide California residents with rights over their Personal Data and place obligations on businesses handling such data.

11. Technical and Organizational Measures (TOM): Security measures implemented by a Controller or Processor to ensure the protection of Personal Data. TOMs may include encryption, access controls, regular security assessments, and incident response plans.

6. Data Collection

We process different types of Personal Data from Data Subjects to deliver and enhance our services. The scope of data collection varies based on your interaction with the Avanquest Developer Platform (each or jointly, a Data Subject will be referred to as “Developer” and respective data processed will be referred to as “Developer Data” in this policy).

1. Website Visitors

Types of Data Collected: Information such as IP address, cookies information (consent-based), browser type, device information, and other online identifiers collected through website analytics and tracking tools. We may collect additional information provided to us directly by you in forms, subscriptions or registrations, or, if you reach out to us by email or any other form provided to you. When you first visit our website, a cookie consent banner is displayed allowing you to accept, decline, or customize your cookie preferences. Only strictly necessary cookies are placed before you make your choice. You can modify your preferences at any time by clicking the cookie settings icon available on each page. For more information in cookies, see our Cookie Policy.

Purpose: To analyze traffic, improve the user experience, and ensure website security. The purpose of any user-submitted data is provided in the context of the form or channel provided to you.

Lawful basis: Consent and Legitimate Interest

Retention: varied depending on the type of online tracker and your consent, rejection or deletion of data from your local storage.

2. Service Users and Account Holders

Types of Data Collected: Name, email address, company details, account credentials, billing information, and usage data related to the Developer Tools.

Purpose: To manage accounts, provide services, deliver customer support, facilitate billing, and ensure compliance with our legal obligations.

Lawful Basis: Processing is necessary for the performance of a contract and our legitimate interests, such as enhancing our services.

3. API File Processing Data

When Developers or their applications use our PDF processing API (including convert, merge, split, compress, rotate, delete, protect, unlock, OCR, and HTML-to-PDF services), the following data processing occurs:

File Upload: Files are submitted to our API via HTTPS (REST) using multipart/form-data or URL reference. API traffic, including file uploads, is routed through Cloudflare’s content delivery and web application firewall (WAF) network for security filtering before reaching our processing servers. Cloudflare does not retain file content.
Note on PDF Signing: The Sign PDF endpoint applies a visual signature stamp to the document. It does not create a cryptographic digital signature, an Advanced Electronic Signature (AES), or a Qualified Electronic Signature (QES) within the meaning of eIDAS Regulation (EU) 910/2014.

Processing: Uploaded files are processed on our servers solely for the purpose of performing the requested operation. File content is not read, analyzed, logged, or used for any purpose beyond the specific API operation requested.

Automatic Deletion: All uploaded and processed files are automatically and permanently deleted from our servers within 10 minutes of the completion of the processing operation. No copies are retained.

No Content Logging: We do not log, index, cache, or retain the content of files processed through our API. API request metadata (timestamp, operation type, file size, API key identifier, response status) is logged for operational monitoring and billing purposes. URL-to-PDF Processing: When a URL is provided to the HTML-to-PDF endpoint instead of a file upload, our server accesses the specified URL to retrieve its content for conversion. We do not log, store, or analyze the content retrieved beyond the conversion operation. Developers should ensure they have appropriate authorization to convert content from the URLs they submit.

Processing Location: File processing occurs on servers located in Canada (Quebec), hosted on Microsoft Azure infrastructure. Canada benefits from a European Commission adequacy decision (Decision 2002/2/EC) under GDPR Article 45 for activities covered by PIPEDA. Files are not transferred to any other location during processing.

The legal basis for processing file content is the performance of the contract with the Developer (Art. 6(1)(b) GDPR). Where the Developer submits files containing third-party personal data (e.g., End User documents), the Developer acts as the data controller for that content and Avanquest acts as a data processor under the terms of the Data Processing Agreement.

4. Other Relevant Data Subjects

Types of Data Collected: Data is collected through forms, support tickets, or interactions with Avanquest representatives, which may include job title, organization name, and communication content.

Purpose: To respond to inquiries, provide tailored support, and communicate about product updates or policy changes.

Note: Data collected as part of processing End User information on behalf of Developers is excluded from this Policy and is governed by our Data Processing Agreement (DPA).

7. Data Usage

We use the data collected from Developers for multiple purposes to deliver, improve, and secure our services:

1. Service Delivery: We use data to provide access to the Developer Tools, maintain service reliability, and address technical issues as they arise.

2. Customer Support: Data is utilized to deliver technical assistance, answer queries, and ensure a smooth and enhanced Developer experience.

3. Analytics: We analyze usage patterns to understand how our services are used, evaluate performance, and optimize the Developer Tools for efficiency.

4. Billing and Payments: Personal and payment data are processed securely to manage subscriptions, facilitate transactions, and implement fraud prevention measures.

5. Anti-Fraud and Fraud Detection: We monitor activity and use data to detect, prevent, and address fraudulent or unauthorized activity that may impact our platform or services.

6. Feedback and Feature Development: We collect feedback to improve our offerings and develop new features that align with user needs. This data informs our development roadmap and service enhancements.

7. Improvement and Delivery: Data is also used to tailor and deliver new features, updates, and improvements to the Developer Tools.

8. Monitoring: We monitor the use of our Developer Tools to ensure compliance with our terms, maintain system integrity, and improve service delivery.

9. Email Communications: With your consent, we may use your email address to send service updates, notifications, and promotional offers related to our products.

10. Other: as required for our legitimate business purposes or, as otherwise consented by you.

Retention Period

We retain Developer data only as long as necessary to fulfill the above purposes. This includes meeting contractual obligations, resolving disputes, and complying with legal requirements, including those related to transactions, taxes and billing. Data is periodically reviewed to ensure it is retained only for the minimum period required by law or legitimate business interests. When no longer needed, data is securely deleted or anonymized.

8. Data Sharing and using third-party tools and services

We take the privacy of Developers seriously and only share their data under specific, carefully controlled circumstances:

1. Service Providers and Processors. We engage trusted third-party service providers (“Processors”) to help us deliver our services. These include:

    • Payment Processors: These partners manage billing, process transactions, and handle refunds securely, ensuring financial information is protected and PCI-compliant.
    • Cloud Storage and Hosting Providers: We use cloud services for data storage, backup, and system reliability, ensuring your data is accessible yet secure through redundancy and disaster recovery measures.
    • Database and Infrastructure Providers: They support our database management, system performance, and network security to ensure efficient and safe data handling.
    • Customer Support Platforms: These tools enable effective communication and manage support tickets, helping us resolve issues and maintain high-quality service.
    • AI-Powered Support Tools: We use AI-powered chatbots and virtual assistants, such as ADA, to help answer questions and provide customer support. When you interact with an AI-powered tool, you will be informed that you are communicating with an AI system rather than a human. Any data shared through these tools is processed under the same contractual confidentiality and security obligations as our other Processors, and is not used to train AI models unless we inform you in advance and obtain any consent required by applicable law.
    • Analytics Providers: We use analytics services to collect and analyze usage patterns, which help us optimize service performance, improve the user experience, and make informed business decisions.

Each Processor is subject to contractual obligations to use the data only as instructed, maintain strict confidentiality, and implement robust security measures.

2. Affiliated Companies. We may share Developer data with our Affiliated Companies for purposes consistent with this Privacy Policy, such as enhancing service offerings, providing joint customer support, or conducting internal analysis. These affiliates are bound by similar privacy and security requirements.

3. Legal Requirements and Protection. We may disclose Developer data if we believe it is necessary to:

    • Comply with legal obligations: Such as responding to subpoenas, court orders, or other legal processes.
    • Protect rights and safety: To defend against legal claims, and protect the rights, property, or safety of Avanquest, our users, or the public.

4. Licensors: We may share data with our licensors or partners as necessary to ensure compliance with licensing agreements or to enable them to support our services.

5. Mergers and Acquisitions (M&A): In the event of a merger, acquisition, asset sale, or other corporate transaction, Personal Data may be transferred to or shared with the acquiring or merging entity. We will ensure that the receiving party upholds the same level of data protection and privacy commitments outlined in this policy.

6. Law Enforcement and Legal Requirements: We may disclose Personal Data to law enforcement agencies, regulators, or other authorities if we are legally required to do so or if we believe in good faith that such disclosure is necessary to comply with legal obligations, protect our rights, investigate fraud, or ensure the safety of our users.

7. Business Partners: On occasion, we may share aggregated, anonymized, or non-personally identifiable information with business partners for research, marketing, or other purposes that support the growth and improvement of our services.

8. Protecting Our Platforms: We may share data as necessary to protect the integrity and security of our platforms. This includes:

    • Monitoring and Auditing: Using data to monitor for compliance, conduct audits, and maintain system integrity.
    • Automation Tools: Leveraging automated systems to detect and prevent unauthorized access or activities.
    • Authorization and Authentication: Using data to authenticate users and manage access controls securely.
    • Security Tools: Implementing advanced security measures, such as firewalls, intrusion detection systems, and encryption, to safeguard data and prevent breaches.

9. Protecting Our Interests: We reserve the right to share Personal Data to protect the rights, property, or safety of Avanquest, our users, or the public. This includes sharing information to prevent fraud, reduce credit risk, or secure our network.

10. Consent-Based Sharing. If we need to share your data for purposes not covered in this section, we will obtain your explicit consent. This includes sharing information with partners for marketing or additional service integrations.

Key Service Providers (Sub-Processors)

The following third-party service providers process personal data on our behalf in connection with the Service. This list is updated periodically; material changes will be communicated to Developers via email or platform notification.

ProcessorPurposeData ProcessedLocation
Microsoft AzureInfrastructure and file processingAll service data including uploaded files (Canada (Quebec) – EU adequacy decision
CloudflareCDN, DDoS protection, WAFIP addresses, request metadataGlobal (edge nodes)
Google AnalyticsWebsite analyticsUsage data, IP (anonymized), device infoUSA (EU-US DPF)
Microsoft ClarityUX analytics (heatmaps, session replay)Usage patterns, mouse movements, IPUSA (EU-US DPF)
HubSpotCRM, marketing communicationsName, email, company, interactionsUSA (EU-US DPF)
Zendesk (Zopim)Live chat, support ticketsName, email, chat contentUSA (EU-US DPF)
Stripe / UpClickPayment processingBilling data, transaction recordsUSA (EU-US DPF)

9. Developer Responsibilities

Developers using the SodaPDF Developer Tools must adhere to strict data protection and transparency practices to safeguard End User privacy and comply with applicable laws.

1. Privacy Policy Requirement. Developers are obligated to create and maintain a comprehensive Privacy Policy that is easily accessible to End Users. This Privacy Policy must clearly and transparently outline the following:

  • Data Collection: A detailed description of the types of Personal Data collected from End Users, specifying what information is gathered and for what purposes.
  • Data Use: An explanation of how the collected data is processed, stored, and shared, including any third-party data sharing or integration.
  • User Rights: Information on End Users’ rights under applicable data protection laws, such as the GDPR and Law 25 in Quebec. This should cover the right to access, rectify, or delete Personal Data, and how users can exercise these rights.

2. Consent and Transparency. Developers are required to obtain valid and informed consent from End Users where necessary, ensuring compliance with laws such as the GDPR. This involves:

  • Clear Consent Mechanisms: Implementing straightforward options that allow End Users to easily give, withhold, or withdraw their consent for data processing activities. Consent requests should be unambiguous and specific to the intended purposes.
  • Transparency: Developers must communicate data processing practices in a way that is easy for End Users to understand. This includes providing clear information about how data is collected, used, and shared, in a format that is accessible and free from complex legal jargon.

By fulfilling these responsibilities, Developers help ensure the protection of End User privacy and uphold legal and ethical standards in data processing.

10. Compliance and Rights

We are committed to upholding the rights of Data Subjects under applicable privacy laws, including the GDPR and Law 25 in Quebec.

1. Developer: As Data Subjects, Developers have several rights concerning their Personal Data, including:

  • Right of Access: You have the right to request access to the Personal Data we hold about you, including information about how we use and share it.
  • Right to Rectification: You can request that we correct or update any inaccurate or incomplete Personal Data.
  • Right to Deletion: Also known as the “right to be forgotten,” you can request the deletion of your Personal Data, subject to legal or contractual restrictions.
  • Right to Restriction: You may request that we limit the processing of your data under certain conditions.
  • Right to Data Portability: You have the right to receive your Personal Data in a structured, commonly used, and machine-readable format and to transfer it to another data controller.
  • Right to Lodge a Complaint: If you believe that our processing of your personal data infringes applicable data protection laws, you have the right to lodge a complaint with a supervisory authority in your jurisdiction. Relevant authorities include:

– France (CNIL): Commission Nationale de l’Informatique et des Libertés — [www.cnil.fr](https://www.cnil.fr)

– United Kingdom (ICO): Information Commissioner’s Office — [www.ico.org.uk](https://www.ico.org.uk)

– Switzerland (FDPIC): Federal Data Protection and Information Commissioner — [www.edoeb.admin.ch](https://www.edoeb.admin.ch)

– Quebec (CAI): Commission d’accès à l’information du Québec — [www.cai.gouv.qc.ca](https://www.cai.gouv.qc.ca)

– Other EEA countries: You may lodge a complaint with the supervisory authority in your country of residence, place of work, or where the alleged infringement occurred. A list of EEA supervisory authorities is available at [edpb.europa.eu](https://www.edpb.europa.eu).

We encourage you to contact our DPO first at dpo@avanquest.com so we can address your concerns directly and promptly. However, this does not affect your right to lodge a complaint with a supervisory authority at any time, without prior recourse to us.

2. End Users: Developers who use the SodaPDF Developer Tools are responsible for addressing Data Subject rights requests from their End Users. This includes requests for access, correction, deletion, or data portability. As a Data Processor, Avanquest will assist Developers in fulfilling these requests to the extent required by law, and in accordance with our contractual obligations. Developers must notify us promptly if they receive such a request from an End User.
3. Minimum Age Requirements

Use of the Avanquest Developer Tools is restricted to individuals who meet the minimum age threshold applicable in their jurisdiction of residence. The following minimum ages apply:

Jurisdiction

Minimum Age

Legal Basis

European Economic Area (EEA)

16 years (or lower if permitted by Member State law, but not below 13)

GDPR Art. 8

United Kingdom

13 years

UK GDPR / Data Protection Act 2018

Switzerland

16 years

Swiss Federal Act on Data Protection (nFADP)

United States (general)

13 years

COPPA (Children’s Online Privacy Protection Act)

California, USA

16 years (for data selling/sharing without opt-in)

CCPA / CPRA

Canada (including Quebec)

14 years

Quebec Law 25 / PIPEDA

All other jurisdictions

16 years, or the applicable local minimum age if higher

Applicable local law

Where a Member State of the EEA has set a minimum age lower than 16 but not below 13, the lower age applies for users in that Member State. Avanquest applies 16 as the default threshold in the absence of confirmed jurisdiction-specific information.

Developers’ Obligations

Developers who integrate the SodaPDF Developer Tools into applications that may be accessed by minors are solely responsible for:

  • Implementing appropriate age verification or age-gating mechanisms within their own applications.
  • Obtaining verifiable parental or guardian consent where required by applicable law before collecting or processing Personal Data of minors.
  • Ensuring their own privacy notices and terms of service accurately reflect the age restrictions and consent requirements applicable to their End User base.
  • Notifying Avanquest promptly if they become aware that Personal Data of a minor below the applicable minimum age has been submitted to the API.

Avanquest does not assume responsibility for age verification of End Users of Developer Applications. Compliance with children’s privacy laws (including COPPA, GDPR Art. 8, and Quebec Law 25) in the context of End User data is the Developer’s responsibility as data controller.

If We Become Aware of a Minor’s Data

If Avanquest becomes aware that Personal Data has been collected from an individual below the applicable minimum age without appropriate consent, we will take prompt steps to delete such data and, where applicable, notify the relevant Developer and supervisory authority in accordance with our obligations under applicable law.

11. Legal Bases for Processing

Avanquest processes Personal Data based on various legal grounds to ensure compliance with data protection laws such as the GDPR and Law 25 in Quebec. These legal bases include:

1. Contractual Necessity: Processing is necessary to fulfil our contractual obligations to Developers. This includes providing access to the Developer Tools, managing accounts, delivering customer support, and processing payments. Without this data, we would be unable to perform these services.

2. Legitimate Interests: We process data to pursue our legitimate business interests, provided that such processing does not override the rights and freedoms of data subjects. Examples include improving our services, ensuring platform security, fraud prevention, and conducting business analytics.

3. Legal Obligations: We may process Personal Data to comply with legal requirements, such as financial reporting regulations, responding to legal requests from authorities, or enforcing our terms of service.

4. Consent: Where required by law, we rely on explicit consent from data subjects to process their Personal Data. This basis is often used for activities like sending promotional communications or collecting data that is not necessary for service delivery. Consent must be freely given, specific, informed, and revocable at any time.

5. Compliance with Data Protection Regulations: We adhere to laws like the GDPR and Law 25, ensuring that all data processing activities are lawful, fair, and transparent.

12. Automated decision-making

General Position

Avanquest does not use automated decision-making processes, including profiling, that produce legal effects or similarly significant effects on Developers or End Users within the meaning of Article 22 of the GDPR or equivalent provisions under applicable privacy laws (including Law 25 in Quebec and the CCPA/CPRA).

Limited Automated Processing

Certain automated processes are used in the operation of the Developer Tools and platform. These are operational or administrative in nature and do not constitute decision-making that significantly affects individuals:

  • Fraud and abuse detection: Automated systems monitor API usage patterns to detect potentially fraudulent, abusive, or unauthorized activity. Where suspicious activity is identified, the matter is reviewed by a human before any action affecting a Developer’s account is taken.

  • Billing and usage calculations: Subscription charges, usage limits, and billing thresholds are calculated automatically based on recorded API activity. These calculations are based on objective, pre-defined parameters and do not involve profiling.

  • API rate limiting and access controls: Automated enforcement of rate limits and access controls is applied uniformly based on account tier and usage, without individualized profiling.

No Solely Automated Consequential Decisions

No decisions with legal or similarly significant consequences — such as account suspension, termination, or denial of service — are made solely by automated means. Any such decision involves human review and, where required by applicable law, Developers will be informed and given the opportunity to contest the decision, request human intervention, and express their point of view.

Profiling

We do not engage in profiling of Developers or End Users for the purpose of evaluating personal aspects such as preferences, behavior, reliability, or location in a manner that produces legal or similarly significant effects.

Your Rights

To the extent that any automated processing activities change in the future and constitute automated decision-making within the meaning of Article 22 GDPR or equivalent legislation, we will update this section accordingly and ensure that appropriate safeguards, including the right to human review, are in place. If you have questions or concerns about how automated processing may affect you, please contact our Data Protection Officer at dpo@avanquest.com.

13. Use of Artificial Intelligence (AI)

Some of our Services include artificial intelligence (AI) features, such as AI assistants, chatbots, and tools that generate or edit content. Where you interact directly with an AI system, such as an AI chatbot, we will make this clear to you. Where our Services generate content using AI, that content is identified as AI-generated. These measures are provided in line with the EU Artificial Intelligence Act (Regulation (EU) 2024/1689).

AI outputs may be inaccurate or incomplete and should be reviewed before you rely on them. We will not use your Personal Information or your Content to train AI models unless we inform you in advance and obtain any consent required by applicable law.

14. Security Measures

We are committed to ensuring the security and integrity of Personal Data collected and processed using our Developer Tools. Our approach to information security involves the implementation of comprehensive Technical and Organizational Measures (TOM) and adherence to our internal Information Security Policy, which is summarized below:

Key Security Measures

1. Data Encryption: All sensitive data is encrypted using advanced encryption protocols, both when transmitted across networks and when stored on our servers. This ensures that data remains secure and protected from unauthorized access.

2. Access Controls and Authentication: We enforce stringent access control mechanisms to limit access to Personal Data. Only authorized personnel are granted access based on the principle of least privilege, and multi-factor authentication is used to enhance security further.

3. Secure Software Development: Our development processes include secure coding practices, regular vulnerability assessments, and thorough code reviews to identify and mitigate potential security threats.

4. Regular Security Audits and Assessments: We perform regular security audits and risk assessments to evaluate the effectiveness of our security practices and ensure ongoing protection of Personal Data.

5. Incident Response Plan: We have a well-defined incident response plan to address and mitigate any data breaches or security incidents promptly. This includes notifying affected parties and regulatory authorities, as required by law.

Data Breach Notification

Detection and Assessment

We maintain continuous monitoring and logging systems to detect potential security incidents. Upon detection of a suspected breach, our security team conducts an immediate assessment to determine the nature, scope, and likely consequences of the incident.

Notification to Supervisory Authorities

Where a personal data breach is likely to result in a risk to the rights and freedoms of natural persons, we will notify the relevant supervisory authority without undue delay and, where feasible, within the timeframes required by applicable law:

  • EEA and Switzerland: Within 72 hours of becoming aware of the breach (GDPR Art. 33). Where notification cannot be made within 72 hours, it will be accompanied by reasons for the delay.
  • United Kingdom: Within 72 hours of becoming aware of the breach (UK GDPR Art. 33).
  • Quebec (Law 25): Within 72 hours of becoming aware of a confidentiality incident presenting a risk of serious injury (Act respecting the protection of personal information in the private sector, s. 3.5).

Notifications to supervisory authorities will include, to the extent known at the time: a description of the nature of the breach, the categories and approximate number of individuals and records affected, the likely consequences of the breach, and the measures taken or proposed to address the breach.

Notification to Affected Individuals

Where a breach is likely to result in a high risk to the rights and freedoms of affected individuals, we will notify those individuals without undue delay, in clear and plain language, including:

  • A description of the nature of the breach.
  • The name and contact details of our Data Protection Officer.
  • The likely consequences of the breach.
  • The measures taken or proposed to mitigate any adverse effects.

Notification to Developers

Where a breach affects data processed on behalf of a Developer, we will notify the affected Developer without undue delay and within the timeframes required by our Data Processing Agreement (DPA), to enable the Developer to fulfil their own notification obligations as data controller.

Record-Keeping

We maintain an internal register of all personal data breaches, regardless of whether notification to a supervisory authority or affected individuals was required. This register includes the facts relating to the breach, its effects, and the remedial action taken, in accordance with GDPR Art. 33(5) and equivalent provisions under applicable law.

Exemptions

Notification to affected individuals may not be required where: (a) we have implemented appropriate technical and organizational measures that render the personal data unintelligible to unauthorized persons (e.g., encryption); (b) we have taken subsequent measures that ensure the high risk to individuals is no longer likely to materialize; or (c) notification would involve disproportionate effort, in which case a public communication or equivalent measure may be used instead.

15. Data Retention

We retain personal data only for as long as necessary to fulfill the purposes described in this Policy, after which it is securely deleted or anonymized. The following retention periods apply:
Data Retention Schedule

Data Category

Retention Period

Justification

API-processed files – direct API calls (uploaded PDFs, output files)

10 minutes after processing completion

Results available for download for 10 minutes, then auto-deleted

API-processed files – MCP integration (uploaded PDFs, output files)

Immediately after processing completion

Files deleted as soon as processing completes and result is returned to MCP client

API request metadata (timestamps, operation type, file size, status codes)

12 months

Operational monitoring, debugging, billing reconciliation

Developer account data (name, email, company, credentials)

Duration of account + 12 months

Contractual necessity; 12-month post-termination period for billing disputes and legal compliance

Billing and payment records

Duration of account + 7 years

Tax and accounting legal obligations (French Commercial Code Art. L123-22; Canada Income Tax Act s. 230)

Support tickets and correspondence

3 years after resolution

Limitation period for contractual claims

Website analytics / cookies

See Cookie Policy

Per cookie-specific retention in Cookie Policy

Security and access logs

12 months

Security incident detection and investigation

Upon expiration of the applicable retention period, personal data is securely deleted using industry-standard methods. Where deletion is not technically feasible (e.g., data in backup systems), the data is isolated and protected from further processing until deletion is possible.

16. International Transfers

We may transfer and process Personal Data to countries outside of your jurisdiction, including regions where data protection laws may differ from those in your home country. These transfers are necessary to deliver our services and manage our global operations.

Transfers from the European Economic Area (EEA) and Switzerland

  • Standard Contractual Clauses (SCCs): For data transfers outside of the EEA and Switzerland, we use SCCs approved by the European Commission. These are legally binding agreements that ensure the same level of data protection as guaranteed under the GDPR.
  • Adequacy Decisions: Where possible, we rely on adequacy decisions from the European Commission, which confirm that a country outside the EEA provides an adequate level of data protection.
  • Supplementary Measures: We may implement additional safeguards, such as encryption and data pseudonymization, to ensure data remains protected during and after the transfer.

Transfers from Quebec and Canada

  • Compliance with Law 25: Transfers from Quebec must ensure that the recipient country offers an equivalent level of data protection. We evaluate the legal framework of the destination country and, where necessary, use measures like SCCs or binding corporate rules.
  • PIPEDA and Cross-Border Transfers: For data transfers under the Personal Information Protection and Electronic Documents Act (PIPEDA), we ensure contractual protections are in place to maintain privacy and security standards.

Third-Party Service Providers

We may transfer data to third-party service providers or affiliates in various jurisdictions to provide infrastructure, support, or other operational services. These providers are contractually obligated to uphold strict data protection standards and are subject to regular audits.

Data Subject Rights in Cross-Border Transfers

Individuals have rights under the GDPR and Law 25 related to how their data is transferred and processed internationally. If you have concerns about these transfers or wish to know more about the safeguards in place, please contact us using the details provided in the Contact Information section.

17. MCP (Model Context Protocol) Integration

MCP (Model Context Protocol) Integration

Our PDF processing API is available as an MCP server, allowing AI assistants (such as Claude, ChatGPT, or other MCP-compatible applications) to invoke our PDF tools on behalf of their users. The MCP server is distributed as a self-contained package that runs locally on the user’s machine or infrastructure.

How MCP works:

1. Local execution: The MCP server runs as a Node.js process on the user’s own machine. It is not a cloud-hosted service operated by Avanquest – it is software installed and operated by the user.

2. API key authentication: The MCP server authenticates to our API using the user’s own API key (AVANQUEST_PDF_API_KEY), transmitted via the X-API-KEY HTTP header over HTTPS. The API key is stored locally in the user’s environment.

3. File handling: When the AI assistant requests a PDF operation, the MCP server reads the file from the user’s local filesystem, uploads it to our API at https://api-developers.avanquest.com/ via HTTPS (multipart/form-data), polls for completion, downloads the result, and saves it locally. Files processed via MCP are deleted immediately after processing – they are not retained on our servers for any period after the operation completes.

Session management: The MCP server supports both stdio (local) and HTTP/SSE (remote) transport modes. HTTP sessions are identified by unique session IDs (UUID v4) and cleaned up on session close.

4. MCP tools available: The following PDF operations are exposed as MCP tools: pdf_convert_to_word, pdf_convert_to_powerpoint, pdf_convert_to_excel, pdf_merge, pdf_compress, pdf_split, pdf_to_text, pdf_delete_pages, pdf_rotate. Each tool accepts local file paths and saves results locally. Maximum file size per tool: 10MB.

Data processed via MCP:

  • File content: PDF files are read from the user’s local disk, transmitted to our API over HTTPS, processed, and the result is downloaded and saved locally. Files processed via MCP are deleted from our servers immediately after processing completes – no retention period applies.
  • API key: Stored locally in the user’s environment variables. Transmitted with each API call for authentication.
  • Operation metadata: Operation IDs (UUID), status, and progress data are exchanged during processing. This metadata is logged as part of normal API usage monitoring.
  • No conversation data: The MCP server does not access, log, or transmit any content from conversations between the user and their AI assistant. It only processes explicit tool calls with file paths.
  • No telemetry: The MCP server does not send analytics, telemetry, or usage data to Avanquest beyond the standard API calls. Debug information is output to stderr only and is not persisted to any log file.

Role Clarification: When our API is accessed via MCP:

  • The End User (or their organization) is the data controller for files they choose to process.
  • The AI Assistant Provider (e.g., Anthropic, OpenAI) has its own data processing relationship with the user, governed by its own privacy policy. Avanquest has no contractual or data protection relationship with the AI Assistant Provider.
  • Avanquest acts as a data processor for the file processing operation. The same Data Processing Agreement (DPA) terms apply as for direct API usage.

Transparency obligation: Users of the MCP server should be aware that files submitted for processing are transmitted to Avanquest’s API servers ( https://api-developers.avanquest.com/) and are subject to this Privacy Policy. AI Assistant Providers integrating our MCP server are responsible for informing their users accordingly.

18. Updates to the Policy

We may update this Privacy Policy to reflect changes in our practices, technology, or legal requirements.

1. Review and Updates: The Privacy Policy is reviewed periodically, and significant changes will be communicated to users through the Developer Console, email, or other appropriate means. The “Last Updated” date will be revised accordingly.

2. User Notification: When changes materially affect your rights or how your data is processed, we will provide notice and, if required by law, obtain your consent before implementing changes.

19. Contact Information

For privacy-related inquiries, questions about this Privacy Policy, or to exercise your data protection rights, please contact us:

20. Version History

July 27, 2026 – Added a new “Use of Artificial Intelligence (AI)” section disclosing our use of AI features and chatbots, added an AI-chatbot disclosure for ADA in the Data Sharing section.
March 19, 2026 – Added MCP (Model Context Protocol) integration section (Section 16), including file handling, role clarification, and transparency obligations. Added minimum age requirements (Section 10.3), expanded right to lodge a complaint to include ICO and FDPIC references (Section 10.1), added automated decision-making and profiling section (Section 12), added version history, added Cloudflare transit disclosure, added HTML-to-PDF URL processing disclosure, added Sign PDF clarification, added MCP telemetry confirmation.

November 10, 2024 – Previous version.