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).