Terms of Service

1. Services

Rika Labs provides the Akter framework under its open-source license and Akter Cloud as a hosted application service with a console, control-plane API, runners, logs, usage metering and customer runtime storage. Akter creates and holds one S3-compatible store bucket per environment incarnation on Tigris. Customers do not supply a runtime database or bucket. Jobs may use customer variables, including DATABASE_URL, for external I/O; these are not runtime database requirements. Account, billing and other control-plane records, and Alchemy infrastructure state, remain on PlanetScale; the control plane runs on Akter 0.1 and holds no customer runtime data.

Stores start empty: there is no migration or adopt command for 0.1 actor data. Existing 0.1 applications must redeploy on 0.2. Akter does not add store versioning, replication or a separate backup copy in 0.2.0. Features and limits are those described in the applicable service documentation and published catalog.

2. Accounts and organizations

You must provide accurate account information, keep your credentials secure and promptly tell us about unauthorized use. You are responsible for activity performed through your account and for ensuring that people in your organization have the permissions they need. You must be old enough and authorized to enter this agreement.

3. Customer content

You retain your rights in application code, organization data, customer app data and other content you submit. You give Rika Labs the limited rights needed to host, store, transmit, secure, meter and support that content. You must have the rights and permissions required to submit it and must not use the service in violation of law or the Acceptable Use Policy.

4. Plans, usage and payment

Plan allowances, usage rates and limits are governed by the applicable published catalog and order or checkout flow. Base subscriptions and compute unit-hours continue alongside committed-action, stored-data and retained-history meters. Actions count durable commits, not replays, deduplicated retries or declared failures that discard uncommitted changes. Stored data and history are measured in GB-months; shared pages within a store count once. Views, reads and watches are not metered. Job-attempt seconds are shown but not billed. This page does not set prices. Stripe processes card payments and may collect applicable taxes. You are responsible for charges incurred by your account. Spend caps cannot undo work already admitted.

The Free plan has monthly hard caps of 250,000 actions, 1 GB of stored data and 1 GB of history, pooled across the organization’s stores. The minimum interval between shard log appends is 250 ms on Free and 50 ms on paid tiers, not a response-time guarantee. Paid allowances and overages follow the applicable published catalog. Action and storage admission limits can refuse new actions; accepted work remains durable, and storage-cap refusal leaves reads, views and watches available.

Cancellation and refunds

You can cancel a paid plan at any time from the billing portal. Cancellation takes effect at the end of the current billing period, and the plan stays available until then. Deleting an organization ends its subscription immediately without automatic proration and bills outstanding metered usage. We do not refund partial billing periods, and billed compute usage is non-refundable. We refund billing errors and duplicate charges in full. Other refund requests made to support@akter.dev within 14 days of a charge are at Rika Labs’ discretion.

5. Availability and changes

We will use reasonable care to operate the hosted service, but availability is not guaranteed. We may change the service, limits or terms as it evolves. We will provide notice of material changes where required. Neither multi-region deployment nor point-in-time restore is included in Akter Cloud at launch unless a later written service description says otherwise.

6. Suspension and termination

We may suspend or terminate access for non-payment, a security risk, unlawful use, a breach of these terms or the Acceptable Use Policy, or to protect the service and other customers. You may stop using the service at any time.

Environment, project or organization deletion immediately fences serving and retires the affected stores. After 30 days, a durable job empties and deletes each retired bucket; failed provider steps remain pending and retry. There is no customer-facing undelete or promise of immediate provider purge or completion exactly at the 30-day boundary. A recreated environment gets a new store. Personal account deletion leaves a surviving organization’s stores intact and requires a sole owner to transfer ownership or complete organization deletion first.

History garbage collection is separate: the retention window is 7 days on Free and 30 days on paid tiers. Per-actor deletion followed by garbage collection is the individual end-user erasure path. The account personal-data export identifies stores and retirement dates, not all actor contents or a SQL dump. Contact support@akter.dev for requests that the service cannot complete; these terms promise no additional runtime export or restore facility. Lawful billing, security and accounting retention is described in the Privacy Policy.

7. Confidentiality and privacy

Each party will protect non-public information received from the other and use it only for the relationship. The Privacy Policy describes personal-data handling. Where Rika Labs processes customer app data on your behalf, the DPA applies to that processing.

8. Disclaimers and liability

To the extent permitted by law, the service is provided as available without warranties beyond those expressly stated. Neither party is liable for indirect, incidental, special or consequential damages. Liability caps, exclusions and consumer-law rights are subject to the applicable agreement and law.

9. Contact

Questions about these terms go to support@akter.dev. Security reports go to security@akter.dev.