LegalService Level Agreement
Legal Document

Service Level
Agreement

This SLA sets forth Engineersmind Corp's commitments regarding the availability, performance, and support of the PDFFillr platform and describes the remedies available to Customers in the event those commitments are not met. This SLA represents the Customer's sole and exclusive remedy for any failure by the Company to meet the service level commitments described herein.

Last Updated: April 8, 2026Jersey City, NJ, United StatesEngineersmind Corp

Exclusive Remedy

This SLA is incorporated into the Terms of Use and, for enterprise customers, the SaaS Agreement and applicable Order Form. Where a conflict exists between this SLA and the SaaS Agreement, the SaaS Agreement controls. Service Credits described herein are the Customer's sole and exclusive remedy for any SLA failure.

01

Definitions

Availability

The percentage of time during a calendar month during which the key components of the Service are operational and accessible to Users, calculated as set forth in Section 3.

Downtime

Any period during which the Service is unavailable to Users, excluding Excluded Events.

Excluded Events

The circumstances described in Section 2.2 that are excluded from Downtime calculations.

Incident

An unplanned interruption to or reduction in the quality of the Service.

Maintenance Window

A scheduled period during which the Service may be temporarily unavailable due to planned maintenance, upgrades, or updates.

Resolution Time

The elapsed time from the Company's acknowledgment of a reported Incident to the restoration of the affected Service to normal operation.

Response Time

The elapsed time from submission of a support request to the Company's initial acknowledgment of that request.

Service Credit

A credit applied to the Customer's future invoice as a remedy for a failure to meet the Availability commitment.

Subscription Term

The period specified in the applicable Order Form or plan description during which the Customer has access to the Service.

02

Availability Commitment

2.1 Uptime Target

The Company commits to achieving System Availability of at least 99.9% during each calendar month of the Subscription Term, measured in accordance with Section 3. For enterprise customers, System Availability targets applicable to a specific Order Form supersede this general commitment. This target equates to a maximum of approximately 43.8 minutes of Downtime per month.

2.2 Excluded Events

The following are excluded from Downtime calculations: scheduled Maintenance Windows; Force Majeure events including acts of God, war, fire, flood, earthquake, pandemic, or governmental action; malicious attacks on the Service that the Company is actively working to mitigate; issues associated with Customer's own computing devices, networks, or internet service provider connections; Downtime caused by Customer's or any User's acts or omissions; issues arising from third-party software, APIs, or services not within the Company's reasonable control, including AI model providers such as AWS Bedrock; and beta or experimental features, which are excluded from all SLA commitments.

2.3 Pilot and Beta Services

System Availability commitments do not apply to pilot programs, beta services, free tier access, or any feature or functionality designated as experimental. Such services are provided "as is" without any availability guarantee.
03

Measurement Methodology

3.1 Calculation

System Availability is calculated on a calendar month basis as follows:

Availability (%) = ((Total Minutes − Downtime Minutes) ÷ Total Minutes) × 100

Downtime is measured from the time the Company confirms an Incident that renders the Service unavailable or substantially degraded, to the time the Company confirms restoration of normal Service operation. Periods of partial degradation may be counted as partial Downtime at the Company's reasonable discretion.

3.2 Monitoring

The Company maintains a status page providing real-time and historical availability information. Customers are encouraged to subscribe to status page notifications. The Company's internal monitoring data constitutes the authoritative record for SLA calculations.

3.3 Customer Reporting

Customers must report Incidents to the Company promptly via Support@pdffillr.ai to be included in SLA calculations. Incidents that are not reported within the calendar month in which they occur may not be counted for SLA credit purposes.
04

Service Credits

4.1 Credit Calculation

If the Company fails to meet the System Availability commitment in any calendar month, the Customer is entitled to a Service Credit as follows:
Monthly AvailabilityService Credit
99.0%-99.9% (below SLA)5% of monthly fee
95.0%-98.99%10% of monthly fee
Below 95.0%25% of monthly fee

For annual plan customers, the monthly fee for SLA credit purposes is calculated as the annual fee divided by twelve (12).

4.2 Maximum Credit

Service Credits shall not exceed the Customer's total fees for the affected Service in the calendar month in which the SLA failure occurred. Service Credits are the Customer's sole and exclusive remedy for any SLA failure.

4.3 Credit Request

To receive a Service Credit, the Customer must submit a written request to Support@pdffillr.ai within thirty (30) days after the end of the calendar month in which the Availability failure occurred. Requests must include the dates and times of the claimed Downtime and a description of the impact. Failure to submit a timely request waives the right to a Service Credit for that period.

4.4 Credit Application

Approved Service Credits will be applied to the Customer's next invoice. If the Customer has paid fees in advance, Service Credits may, at the Customer's election, be applied as a credit toward additional plan capacity or a term extension of equivalent value. Service Credits have no cash value and may not be redeemed for cash.

4.5 Termination Right for Sustained SLA Failure

If the Service fails to meet the Availability commitment for three (3) or more consecutive calendar months, the Customer may terminate the affected subscription upon thirty (30) days' written notice without early termination penalty, and shall be entitled to a pro-rata refund of prepaid fees for the unused portion of the Subscription Term.

Credits must be requested within 30 days of the end of the affected month. Total credits in any calendar month shall not exceed 100% of the monthly fee for the affected Service.

05

Scheduled Maintenance

5.1 Maintenance Windows

The Company may perform scheduled maintenance during the following standard Maintenance Window: Sundays, 12:00 AM-4:00 AM CST. Scheduled maintenance performed within this window is excluded from Downtime calculations.

5.2 Advance Notice

The Company will provide at least seventy-two (72) hours' advance notice of scheduled maintenance expected to result in Service unavailability, via the status page and, for enterprise customers, by email to the designated account contact.

5.3 Emergency Maintenance

The Company reserves the right to perform emergency maintenance outside of standard Maintenance Windows where necessary to address security vulnerabilities, critical bugs, or other urgent issues. The Company will provide as much advance notice as practicable and will notify Customers promptly through the status page and, for enterprise customers, by email.
06

Incident Classification and Response

6.1 Priority Levels

Incidents are classified by priority, with the following response and resolution targets:
PriorityDescriptionInitial ResponseResolution Target
P1 · CriticalComplete Service unavailability or loss of core functionality; data loss risk1 hour4 hours
P2 · HighSignificant degradation affecting a material subset of Users; core functionality partially available4 hours24 hours
P3 · MediumNon-critical feature impairment, intermittent errors, or performance degradation with workaround1 business day5 business days
P4 · LowGeneral inquiries, minor cosmetic issues, or feature requests2 business daysVaries

6.2 Business Hours

Response and Resolution Time targets are measured during business hours (8:00 AM-6:00 PM CST, Monday through Friday, excluding public holidays) for P3 and P4 incidents. P1 and P2 targets apply on a 24/7 basis. These targets are objectives and not guarantees; failure to meet Response or Resolution Time targets does not independently give rise to a Service Credit.

6.3 Escalation

Enterprise customers may escalate unresolved P1 or P2 incidents to a designated escalation contact as specified in their Order Form. If no escalation contact is designated, escalations should be directed to Support@pdffillr.ai with the subject line "ESCALATION-[Incident Description]."
07

AI Processing Accuracy

The Company does not make representations or warranties as to the accuracy, completeness, or reliability of AI-generated outputs produced by the Service. AI processing accuracy is explicitly excluded from this SLA and from any service level commitment.

Customers are solely responsible for reviewing and verifying all AI-generated outputs before use or reliance. See the Terms of Use for the full AI processing disclaimer.

08

Backup and Recovery

8.1 Backup

The Company performs regular automated backups of User Content and account data. Backup frequency and retention periods are as described in the Privacy Policy. Backup data is stored in encrypted form and is not actively accessed except for disaster recovery purposes.

8.2 Recovery Objectives

The Company targets the following recovery objectives in the event of a system failure requiring restoration from backup, subject to the nature and scope of the failure:
ObjectiveTargetScope
Recovery Time Objective (RTO)4 hoursCritical system components
Recovery Point Objective (RPO)24 hoursMaximum data loss window

These are objectives and not guarantees. The Company shall not be liable for data loss or extended recovery times resulting from causes outside its reasonable control.

09

Reporting and Transparency

The Company will maintain and make available a public status page providing real-time Service status, historical availability data, and incident history. For enterprise customers, the Company will provide a monthly availability report upon written request, summarizing System Availability, any Downtime events, and any applied Service Credits for the preceding calendar month.

10

Force Majeure

Neither party shall be liable for any failure or delay in performance due to causes beyond its reasonable control, including acts of God, war, riot, fire, flood, earthquake, pandemic, governmental action, or telecommunications or internet service provider failures. The Company will use commercially reasonable efforts to resume the Service as quickly as practicable following a Force Majeure event and will notify Customers through the status page.

If a Force Majeure event causes Service unavailability for a continuous period exceeding thirty (30) days, either party may terminate the affected subscription without penalty upon written notice.

11

Changes to This SLA

The Company reserves the right to modify this SLA at any time. Material changes will be communicated with reasonable advance notice via the status page and, for enterprise customers, by email. For enterprise customers, SLA modifications do not take effect until the expiration of the then-current Order Form term unless otherwise agreed in writing. Your continued use of the Service after changes take effect constitutes your acceptance of the revised SLA.

Effective DateApril 8, 2026
Last UpdatedApril 8, 2026