Terms of Service

These Terms of Service ("Terms") govern your access to and use of the Apider platform, including the SDK, API, cloud execution runtime, and management dashboard (collectively, the "Service"). By using the Service, you agree to these Terms.

1. The Service

Apider provides a cloud-native Python automation runtime. Your code is executed on our infrastructure (Microsoft Azure Functions). The thin-client SDK you install locally sends encrypted requests to the cloud — business logic runs on our servers, not on your machine.

2. Accounts and API Keys

You are responsible for maintaining the confidentiality of your API keys (APIDER_FUNCTION_KEY, APIDER_ENCRYPTION_KEY) and any credentials stored in your .env file. You are responsible for all activity that occurs under your account or keys.

• Do not share your function key publicly (e.g., in public GitHub repos).
• Rotate keys immediately if you suspect compromise.
• You are solely responsible for the credentials of third-party services (Telegram, Gmail, Slack, etc.) configured in your environment.

3. Acceptable Use

You may use Apider to automate tasks, connect services, and build workflows using Python. You agree not to:

• Use the Service for illegal activities, spam, or harassment.
• Attempt to reverse-engineer or extract server-side business logic.
• Abuse the execution infrastructure (e.g., deliberate DDoS or resource exhaustion attacks).
• Resell or sublicense access to the Service without written permission.

4. Execution Limits and Overage

Execution counters reset every 30 days from your registration date, not on a fixed calendar day. We reserve the right to adjust plan limits with 30 days' notice.

5. Credentials and Security

Your third-party credentials travel Fernet-encrypted in every request and are decrypted in-memory only during execution. They are never logged or stored in plain text by Apider. Two components — Webhooks and CloudScheduler — persist your encrypted environment in Azure Table Storage so they can operate without an active session. This storage is protected by Azure RBAC and Fernet encryption at rest.

6. Service Availability

The Service is built on Microsoft Azure Functions (Consumption plan), which carries a 99.95% uptime SLA from Microsoft. We make no additional availability guarantees beyond the underlying infrastructure SLA.

7. Billing

Paid plans are billed through Paddle, our Merchant of Record. Paddle handles all payment processing and tax compliance. Pricing is displayed at apider-io.github.io/#pricing.

8. Termination

You may cancel your subscription at any time through Paddle or by contacting us. We reserve the right to suspend or terminate your access for violations of these Terms, without prior notice if necessary to protect the integrity of the Service.

9. Limitation of Liability

The Service is provided "as is." To the maximum extent permitted by applicable law, Apider shall not be liable for any indirect, incidental, special, or consequential damages, including loss of data or revenue. Our total liability for direct damages shall not exceed the amount you paid us in the 3 months preceding the claim.

10. Changes to These Terms

We may update these Terms from time to time. Material changes will be communicated via email or a notice on the site. Continued use after changes take effect constitutes acceptance.

11. Contact

Questions about these Terms? frostcore@jafa.dev