HATO API

1. Account registration and responsibility

2. Authorization and target API permissions

SFTP deliveries require a trusted server host-key fingerprint. You are responsible for your saved Directory values, credentials and keys, and for authorizing any regional transfers needed by your configured flows. Only grant integration permissions, including Directory access to secrets, to parties you trust.

Template evaluations run with CPU, memory, and time limits. Expressions that exceed these limits fail without completing the component. Upload and key-generation grants are single-use, and operation admissions are rate limited.

You represent and warrant that you own or have explicit authorization and permission to access, query, and interact with every target endpoint, URL, server, and service configured in your Letterflows.

3. Acceptable use policy

You agree not to use Hato API for any unlawful, harmful, or abusive purpose. Specifically prohibited activities include:

• Denial of service and flooding.

  Launching distributed denial of service (DDoS) attacks, brute-force requests, or overwhelming target infrastructure with abusive traffic volumes.

• Vulnerability scanning & exploitation.

  Using Hato API to probe for vulnerabilities, scan ports, or deliver malicious payloads without explicit written authorization from the system owner.

• Bypassing quotas or access controls.

  Attempting to bypass subscription tier quotas, rate limits, IP restrictions, or multi-tenant boundaries of Hato API or third-party APIs.

• Spam and deceptive traffic.

  Sending unsolicited bulk communications, deceptive webhook triggers, or spoofed request origins.

4. Plans, limits and billing

Current plan prices, features and default limits are published in the homepage section: Subscription & Plan.

Your use is subject to your applicable plan limits. Allowances are shared across your account and regions; account-specific exceptions may apply.

Outbound attempts and schedules

Reachable outbound attempts, including retries and redirect hops, count toward the rolling hourly allowance. Manual, API and scheduled deliveries share that allowance. Admission reserves capacity; deleting history does not restore it. Notification email has separate allowances.

Capacity limits may delay or prevent admission, and schedules may be paused. Enabled queues have no automatic waiting expiry; you can cancel waiting deliveries. Submission freezes inputs, so later edits do not change a waiting delivery. A schedule does not guarantee delivery at every occurrence.

Integration permissions

API keys require explicitly selected permissions permitted by your plan. Current resource eligibility still applies, and password changes revoke existing keys.

Paid subscriptions and cancellation

For paid purchases, Paddle is the authorized reseller and merchant of record; Hato provides the service. Monthly subscriptions renew automatically until canceled. Checkout displays the currency, applicable taxes, total and renewal terms before you buy. Website currency conversions are estimates. Only plans offered for purchase are available; a listed future tier does not make it purchasable.

Use Manage Billing in Settings or the Paddle support link to manage payment methods, invoices and cancellation. Ordinary cancellation stops renewal at the end of the current billing period. Previously confirmed paid access continues during payment recovery, but an unpaid initial purchase does not grant paid access. Canceled or paused subscriptions lose paid entitlement under the applicable billing state.

Deleting your account cancels billing immediately before removing your data. If cancellation cannot be confirmed, your account is kept. Refunds are handled separately.

Cancellation does not automatically refund unused subscription time. Refund and withdrawal requests are assessed under Paddle's Buyer Terms and Refund Policy and applicable consumer law. Contact Hato about service problems and Paddle about payment or refund requests. Nothing in these terms excludes mandatory consumer guarantees, withdrawal rights or other non-excludable remedies.

Paddle — Buyer Terms · Paddle — Refund Policy · Paddle — Payment support

Plan changes and retained results

After a downgrade, excess saved resources become read-only and cannot run; ineligible schedules are paused. Excess API keys are disabled, and permissions outside the new plan are removed. Upgrading does not automatically resume schedules or restore removed permissions.

A downgrade that leaves retained entries above the storage allowance freezes retention of new results until deletions bring the count below the allowance or an upgrade accommodates the entries. Runs may still execute and consume quota without retaining their content. Existing entries keep their established expiry deadlines; pinned content still counts toward capacity. Normal expiry, FIFO removal, clearing, and explicit deletion follow the Privacy Policy.

5. Service availability and disclaimers

Service limitations and disclaimers apply only to the extent permitted by law. They do not exclude consumer guarantees or liability that cannot lawfully be excluded. Your applicable mandatory consumer rights continue to apply to the service.

6. Suspension, termination, and revisions

We may suspend or terminate access for unlawful use, abuse, security threats or breaches of these terms, subject to applicable notice requirements and consumer rights. Revisions will be published here with an updated date; changes do not remove rights that cannot legally be excluded. Contact us through the public contact form about these terms or service complaints.

Contact us about these terms

Privacy Policy