These data processing terms explain how LINGYANG handles operational personal data for business users. Local Mode statement contents stay in the user's browser and are not received by LINGYANG.
Last updated: 2 July 2026
For statement contents processed in Local Mode, the user remains responsible for the files because LINGYANG does not receive them. For support, purchase and license records, LINGYANG acts according to the privacy policy and applicable provider terms.
Operational processing is limited to website delivery, anonymous analytics, payment processing, license validation, support, refunds and security.
Cloudflare, Gumroad, Plausible Analytics and support mailbox infrastructure may process operational records. Current OCR has no cloud subprocessor.
Statement contents are not retained by LINGYANG. Purchase and support records can be requested for deletion by emailing support@antelope.tools, subject to tax, fraud-prevention and legal retention needs.
Operational data may be processed in the United States and European Union/EEA through the providers listed on the subprocessor page.
Statement files, OCR images, extracted rows, exports and support attachments are not used to train AI or machine-learning models.
Cloud OCR is not enabled today. If it is added, the upload, OCR and download pipeline must be treated as a separate security product and must pass this launch gate before any production traffic is accepted. Uploaded statement contents would require explicit opt-in, listed subprocessors, short retention, deletion verification records, isolated OCR workers and logs that exclude file names, transaction content, amounts and account numbers.
| Control | Required implementation before cloud OCR launch |
|---|---|
| File identity | Validate allow-listed extensions and server-detected MIME/magic bytes. Do not trust client headers or extensions alone. |
| Size and structure limits | Set maximum file size, PDF page count, image dimensions, object count and decompressed size/ratio before parsing. |
| Compressed and container files | Reject abnormal archives, archive bombs, nested containers and malformed compressed streams. |
| Private storage | Store uploads outside any public web root using randomized object names that do not include the original file name. |
| Signed access | Use short-lived signed URLs for upload and download; no public bucket reads and no permanent file URLs. |
| Access control | Only authenticated or licensed users may upload; authorization must be checked again for status and download requests. |
| Malware handling | Run uploads through antivirus, sandboxing or content disarm and reconstruction where practical for PDFs, images and office files. |
| OCR isolation | Run OCR workers in containers with deny-by-default outbound network access and only the minimum internal services required. |
| Resource limits | Enforce per-job CPU, memory, wall-clock time, concurrency and queue limits, including PDF parser resource-exhaustion protections. |
| Deletion and evidence | Automatically delete uploads, derivatives and exports; deletion jobs must write verification records without storing contents. |
| Safe logging | Logs must not contain original file names, transaction text, statement contents, amounts or account numbers. |
| API abuse protection | Rate limit upload, OCR, status and download APIs by IP, license/user and job state. |
| Dependency maintenance | Regularly update PDF, Excel and image parsing dependencies, OCR images and container base images; run dependency audits. |
| Security testing | Test polyglot files, MIME spoofing, malformed PDFs, oversized PDFs, image bombs, archive bombs and timeout paths before release. |
For a signed DPA or vendor review, email support@antelope.tools. Include your legal entity name, country/region and any required security questionnaire.
In Local Mode, statement contents are processed on the user's device and are not received by LINGYANG. Operational records such as support, payment and license validation may still be personal data.
Email support@antelope.tools with your organization name, jurisdiction and intended use.
No. LINGYANG does not use statement files or conversion outputs to train models.