PrepAI Service Fulfillment & Delivery Policy

Effective Date: 1st October 2026
Last Updated: 23rd September 2026

PrepAI is a digital software service operated by DataToBiz Private Limited.

This Policy explains how PrepAI:

• Account access
• Subscriptions
• Licences
• Credits
• Add-ons
• APIs
• Integrations and institutional orders

are delivered and supported.

Standard PrepAI software purchases do not involve physical shipment.

1. Scope

This Policy applies to PrepAI:

• Websites
• WebApp access
• Subscriptions
• PAYG or credit purchases
• Add-ons
• APIs
• Integrations and institutional licences

purchased directly from DataToBiz unless a separate Order Form or agreement provides different fulfillment terms.

For users who purchased PrepAI before the Effective Date and affirmatively accept the updated Terms, this Policy governs the operational delivery and support of the Service prospectively from the date of acceptance, subject to any separately agreed entitlement and applicable law.

2. Digital Nature of PrepAI

PrepAI provides digitally delivered Services.

Unless a separate agreement specifically provides otherwise:

• No physical software is shipped
• No physical media is provided and delivery takes place through electronic account access, credits, credentials, configuration or digital provisioning

3. Order Confirmation

Following an authorised purchase, PrepAI or its payment provider may provide:

• An electronic confirmation
• Invoice
• Receipt
• Payment acknowledgement or account update

The:

• Checkout information
• Applicable invoice
• Order Form and written commercial terms

form part of the purchase record.

If you believe an order was placed without your authorisation, contact: [email protected] promptly.

4. Free Account Activation

Where free registration is available, access is ordinarily activated following successful account creation and any required account verification.

Free features, limits and usage allowances may change in accordance with the Terms & Conditions.

5. Paid Plan Activation

For self-service paid purchases, paid functionality is ordinarily activated shortly after successful payment or confirmation from the payment provider.

Some purchases may require:

• Email verification
• Account refresh
• Manual verification or another reasonable technical step

If payment succeeds but paid access is not activated within a reasonable time, contact: [email protected] with account email and transaction reference.

6. Institutional and Enterprise Orders

Institutional and enterprise licences may be provisioned according to the applicable:

• Order Form
• Invoice
• Purchase order
• Proposal or written agreement

Provisioning may depend on:

• Payment
• Accepted purchase order
• Administrator information
• User information
• Technical configuration
• Security review or other agreed onboarding requirements

7. Institutional Provisioning

Institutional access may include:

• Workspace setup
• Seat allocation
• Admin controls
• Licences
• User provisioning
• API credentials
• Integrations
• Support setup or configuration

A specific implementation deadline or SLA applies only where expressly agreed in writing.

8. Credits and Usage Packs

Purchased credits or usage packs are ordinarily credited to the applicable PrepAI account after successful payment or another agreed commercial trigger.

The applicable:

• Usage rules
• Expiry
• Transferability and restrictions

are governed by the purchase terms.

9. Promotional Credits

Trial, bonus, promotional or complimentary credits may:

• Have different limits
• Expire differently and have no cash value

10. Add-Ons

Digital add-ons are normally activated through:

• Account entitlement
• Feature activation
• Credits or configuration

The applicable delivery method will be stated during purchase or in the relevant Order Form.

11. API Provisioning

API access may require:

• Activation
• Credentials
• Keys
• Permissions or technical configuration

Where API access is included in a plan, delivery is governed by:

• Applicable technical documentation
• Plan terms and the relevant Order Form

API plans may have:

• Usage limits
• Rate limits and separate fair-use conditions

12. Integration Provisioning

LMS and other integrations may require:

• Supported third-party systems
• Authentication
• Configuration
• Setup
• Admin access or technical cooperation from the customer

Third-party changes may affect integration behaviour or continued compatibility.

13. Invoices

PrepAI may provide electronic invoices or receipts.

Customers are responsible for providing accurate:

• Billing address
• Company information
• Tax information and purchase-order information

where relevant.

14. Taxes

Prices may be inclusive or exclusive of taxes depending on the relevant:

• Geography
• Checkout
• Invoice or commercial arrangement

Applicable taxes will be handled according to the relevant transaction and law.

15. Payment Processing

Payments may be processed by authorised third-party payment providers.

Where card data is entered directly into a payment provider’s:

• Hosted
• Encrypted or tokenised

payment flow, PrepAI does not intentionally store the complete payment-card number or card-security code on its own systems.

16. Failed Payments

Where a payment is:

• Declined
• Incomplete
• Pending or rejected

paid access may not activate until successful confirmation is received.

If your bank shows a debit but PrepAI does not show a successful payment, contact support.

17. Plan Changes

Where plan changes are supported, the updated entitlement generally takes effect in accordance with the:

• Checkout terms
• Account flow
• Invoice or Order Form

Any applicable:

• Proration
• Credit adjustment
• Carry-forward or billing change

will be disclosed with the relevant change.

18. Subscription Expiry

When a fixed-term paid entitlement expires without renewal, access to paid features may end or the account may move to an available Free Plan.

Expiry does not affect Services already validly delivered during the paid period.

19. Service Availability

PrepAI is an internet-based Service.

Availability may be affected by:

• Scheduled maintenance
• Emergency maintenance
• Network failure
• Utility failure
• Cloud-service disruption
• AI-provider disruption
• Third-party integration changes
• Cyber incidents
• Legal requirements or other technical conditions

PrepAI uses reasonable efforts to maintain Service continuity appropriate to the applicable plan.

Unless a written Service Level Agreement applies, PrepAI does not guarantee uninterrupted Service or a specific uptime percentage.

20. Maintenance

PrepAI may perform:

• Routine maintenance
• Security maintenance
• Infrastructure upgrades
• Emergency maintenance and technical updates

Where reasonably practicable, significant planned maintenance affecting paid customers may be communicated in advance.

21. Fair Usage and Technical Controls

PrepAI may apply reasonable:

• Usage limits
• Rate limits
• Anti-abuse controls
• Account restrictions or technical safeguards

to maintain:

• Security
• Stability and fair availability

Where a plan is described as unlimited, the fair-usage provisions in the Terms & Conditions apply unless a specific written agreement states otherwise.

22. Third-Party Dependencies

Certain PrepAI functionality may rely on:

• Cloud infrastructure
• AI providers
• Payment systems
• Authentication systems
• LMS platforms
• Email providers
• Analytics providers and APIs

A third-party provider may:

• Experience an outage
• Change its system
• Modify its API
• Change its terms or discontinue functionality

PrepAI may replace or modify a dependency where reasonably necessary to maintain the Service.

23. Material Service Changes

PrepAI may update, replace or retire features for legitimate:

• Technical
• Security
• Legal
• Operational or business

reasons.

Material changes affecting an active paid entitlement will be handled in accordance with:

• The Terms & Conditions
• Applicable purchase terms
• Written agreements and mandatory law

Where a financial adjustment or refund is applicable, it will be handled in accordance with the Cancellation & Refund Policy.

Where appropriate, PrepAI will provide reasonable:

• Notice
• Transition information or support

24. Delivery or Fulfillment Issues

If you paid for a Service but did not receive the applicable:

• Account access
• Credits
• Licence
• Invoice
• Feature
• Credentials or agreed provisioning

contact: [email protected] with the relevant details.

PrepAI will investigate and, where appropriate:

• Activate the entitlement
• Correct the account
• Provide the missing credits
• Reissue records
• Correct the payment status or provide another appropriate remedy

Refund-related matters are governed by the Cancellation & Refund Policy.

25. Support

• Support Email: [email protected]
• Support Phone: +91-7009935623

Support availability may differ by plan.

An applicable:

• Order Form
• SLA or institutional agreement

may contain additional support commitments.

26. Consumer Grievances

Consumer Grievance Officer

• Name: Ankush Sharma
• Designation: Co-Founder & CEO
• Email: [email protected]
• Phone: +91-7009935623

We aim to acknowledge consumer grievances within 48 hours and redress them within one month, or within another period required by applicable law.

27. Changes to This Policy

PrepAI may update this Policy to reflect changes in:

• The Services
• Payment methods
• Fulfilment processes
• Technology or applicable law

The Effective Date at the beginning of this Policy identifies the current version.

---

Relationship Between PrepAI Policies and Policy Precedence

The PrepAI Terms & Conditions govern use of the Services. The Privacy Policy explains how personal data is handled. The Cancellation & Refund Policy governs cancellation, billing and refund matters. The Service Fulfillment & Delivery Policy explains how digital access, plans, credits and other Services are delivered.

Where DataToBiz and an Institutional Customer have entered into a separately signed Order Form, MSA, DPA or other written agreement that expressly conflicts with these website policies, the separately signed agreement will prevail to the extent of that conflict, subject to applicable law.