ProdaDoc Service Supplement
Service-specific terms and data-handling details for the ProdaDoc document API.
Service-specific terms and data-handling details for the ProdaDoc document API.
Table of Contents
Scope
This ProdaDoc Service Supplement applies to your use of ProdaDoc through ScaleAPIs.
This supplement is intended to be read together with the ScaleAPIs Privacy Policy, Terms of Service, Refund Policy, and Acceptable Use Policy. If there is a conflict between this supplement and a separately signed enterprise agreement or order form, the signed agreement or order form will control to the extent of the conflict.
What ProdaDoc Does
ProdaDoc is a document-generation service that can render PDFs and related document outputs from customer-submitted content and instructions.
Depending on the workflow, plan, and enabled product features, ProdaDoc may support:
HTML-to-PDF generation
URL-to-PDF generation
template-based document generation
document-processing workflows associated with the selected plan
synchronous or job-based processing
bounded output handling associated with the selected workflow
Customer Inputs
To provide the ProdaDoc service, Scale APIs may process inputs such as:
HTML content
URLs
template data
document-generation settings
filenames, metadata inputs, or merge-related inputs where supported
request identifiers, idempotency keys, and similar operational metadata
These inputs may contain personal data, confidential information, or commercially sensitive information.
You should not send highly sensitive information to ProdaDoc unless it is necessary for your intended workflow and you understand the applicable storage, retention, and delivery behavior associated with that workflow.
Outputs And Retention
ProdaDoc generates PDF or related document outputs based on your submitted request.
For direct synchronous document-generation flows, ProdaDoc is intended to process request content and generated outputs transiently for the time needed to fulfill the request.
Scale APIs does not describe ProdaDoc as a universal no-retention service. Output handling depends on the selected workflow, plan, storage settings, delivery method, logging environment, and any enabled output or job features.
Where outputs or related metadata are retained to support delivery, replay protection, async processing, troubleshooting, abuse prevention, or other operational needs, Scale APIs uses bounded retention periods and operational controls appropriate to the selected workflow.
Customer-Designated Destinations
Some ProdaDoc workflows may allow delivery to customer-designated destinations or customer-controlled storage environments.
If you use a customer-designated destination, storage location, or callback endpoint, you are responsible for:
ensuring the destination is correct and under your control
configuring destination security and access appropriately
ensuring that destination-side handling complies with applicable law and your own policies
Scale APIs is not responsible for how data is stored, shared, retained, or secured after it has been delivered to a destination that you designate or control.
Third-Party URLs And Rendering Limitations
When you use URL-based document generation, ProdaDoc may request the target URL and any externally referenced assets needed for rendering.
Results may depend on factors outside the control of Scale APIs, including:
target-site availability
anti-bot or anti-automation measures
CAPTCHA or verification walls
paywalls, login requirements, or access restrictions
content changes made by the target site
unsupported or unstable dynamic behavior in the target environment
Scale APIs does not guarantee successful rendering, identical fidelity, or compatibility for every website, application, storefront, or workflow.
Some requests may be blocked, degraded, delayed, or rejected where the target environment prevents reliable or authorized rendering. Where supported by the service behavior, ProdaDoc may return structured blocked, timeout, validation, or similar classified error outcomes instead of a completed document.
Logging, Security, And Operational Handling
Scale APIs applies operational, security, and abuse-prevention controls to ProdaDoc, which may include:
authentication and access controls
request validation
rate limiting and abuse controls
logging, monitoring, and troubleshooting controls
worker, queue, and output controls associated with the selected workflow
bounded delivery and retention controls associated with the selected workflow
Scale APIs may also process technical and operational metadata relating to ProdaDoc requests for reliability, security, support, billing administration, abuse prevention, and legal compliance.
Customer Responsibilities
You are responsible for:
ensuring that your use of ProdaDoc is lawful and authorized
obtaining any rights, permissions, or consents needed for the requested document generation
ensuring that submitted HTML, URLs, template data, and other inputs are lawful and appropriate
reviewing whether ProdaDoc is suitable for your intended use case
ensuring that your handling of generated outputs complies with applicable law and third-party rights
You may not use ProdaDoc for prohibited uses described in the ScaleAPIs Acceptable Use Policy, including unlawful scraping, unauthorized access, credential misuse, unlawful surveillance, or other abusive or unlawful workflows.
Service Evolution
Scale APIs may add, remove, or modify ProdaDoc capabilities, delivery methods, plans, usage limits, and technical controls from time to time.
Updated product behavior will be governed by the then-current platform terms, policies, and applicable written agreements.
Questions about this document?
If you have questions about this policy, contact us at legal@scaleapis.com.
Contact Us