Terms of Service

By executing the JalpiForm Javascript SDK or interacting with the JalpiForm architectural Dashboard, you agree to comply with and be bound by the following terms and conditions of use natively.

1. Wallet and Credits Architecture

Our entire pricing model leverages prepaid Wallet tokens mapping directly to system infrastructure costs. You agree that:

• A flat deduction of exactly 5 Credits is triggered unconditionally when you generate a new Form Configuration inside the database.
• Authyo OTP verifications are entirely dynamic. The base SDK evaluates the telecom payload and subtracts credits factoring an exact `Margin Percentage` set by JalpiForm Operators.
• Credits dropping strictly to zero will yield localized `HTTP 402 Insufficient Funds` drops causing physical SDK errors on the client's payload. JalpiForm is not liable for dropped lead captures caused by empty wallets.

2. Appropriate Payload Constraints

Developers utilizing JalpiForm API paths remain entirely liable for the JSON schemas they configure. We expressly prohibit capturing explicit PCI fragments (Credit Cards), Government Credentials, or malicious binaries traversing custom text inputs.

3. SLA & Infrastructure Uptime

JalpiForm provisions high-availability load balancers guaranteeing `99.9%` continuous network integrity. However, because SDK OTP validations depend asynchronously on Authyo server uptimes natively, outages impacting Authyo SMS/Email dispatchers remain strictly outside JalpiForm operational jurisdictions.

4. Limitation of Liability

In no operational event shall JalpiForm be strictly liable for lost lead conversions or operational data omissions arising out of API failures, syntax SDK implementation flaws strictly written by developers, or zero-day environment outages.