Privacy Policy

Information we collect

We collect account email address and name, authentication and organization records, application and deployment metadata, and information needed to operate the account. Account, billing and other control-plane records remain on PlanetScale. The control plane runs on Akter 0.1; it does not hold customer runtime data. Alchemy infrastructure state also remains on PlanetScale.

Akter holds customer runtime data in one S3-compatible store bucket per environment incarnation, created and managed by Akter. The store contains the action log, checkpoints, pages, index and retained history. Tigris is the selected customer runtime storage provider. Customers do not supply a runtime database or bucket. Jobs may use ordinary customer variables, including DATABASE_URL, to call customer-selected services; those external services remain under the customer’s control. Customer environment variables are encrypted at rest in the control-plane database and supplied to the customer’s runner when needed.

We collect usage and operational information such as committed actions, stored bytes, retained history bytes, job-attempt seconds, compute unit-hours, deployment activity, service events, logs and support communications. Job seconds are shown but not billed; views, reads and watches are not metered. Stripe receives payment and billing details for paid plans; Rika Labs does not need to store full payment-card numbers. We may receive delivery and bounce information from Resend when we send account or support email.

How we use information

We use information to authenticate users, host customer applications and their stores, meter usage, apply plan quotas, process payments, send transactional messages, prevent abuse, troubleshoot incidents, improve reliability and answer support requests. We use security and operational logs to protect customers and the service.

Cookies

The console uses Better Auth session cookies to keep you signed in. They are required for authentication and are configured as HTTP-only and secure in production. The site does not currently use analytics cookies or advertising cookies. See the Cookies Policy for details.

Sharing and subprocessors

We share data with service providers that help us operate Akter Cloud, including Tigris, Fly.io, PlanetScale, Cloudflare, Vercel, Resend, Axiom, Stripe, Better Stack and GitHub, as described in the Subprocessors page. Storage placement is not a guarantee that all processing stays in one jurisdiction. We may disclose information when required by law or to protect rights, safety and security.

Retention and security

We retain account and service data while the account is active and as needed for billing, security, dispute resolution and legal obligations. Retention periods vary by data type and service. Customer runtime stores are separate per environment incarnation, not merely bucket prefixes. Runner storage access is limited to its environment’s bucket, and platform storage credentials are kept out of customer-variable listings and builders. We use account access controls, encryption for customer environment variables, transport security and operational monitoring, but no system can be guaranteed perfectly secure.

Runtime history is removed by framework garbage collection after the plan’s retention window: 7 days on Free and 30 days on paid tiers. Per-actor deletion followed by garbage collection is the erasure path for individual end-user data; deleting live state is not an immediate purge of retained history.

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. This retirement period is separate from history retention. There is no customer-facing undelete and no promise of immediate provider purge or deletion completed exactly at the 30-day boundary. A recreated environment gets a new store. Akter does not add store versioning, replication or a separate backup copy in 0.2.0.

After account deletion, we retain historical billing and accounting records, including billing operation receipts, as required for tax and accounting obligations; those records are included in a personal-data export before deletion. Organization deletion cancels current subscriptions immediately without automatic proration and bills outstanding metered usage in a final invoice. Existing invoices and lawful accounting obligations remain due; deletion does not promise a refund. We may also retain user suspension records to prevent abuse; authenticated personal-data exports include the user’s retained suspension record. Staff security audit records retain the operator and reason under an anonymized account tombstone, and email/IP spam-limit windows remain until their normal short expiry; deletion does not impose an email denylist on re-registration. Deleting a personal account does not delete a surviving organization’s stores. A sole owner must transfer ownership or complete organization deletion first. Organization deletion retires its stores under the 30-day process above. Deletion does not manage external services a customer’s jobs call. Deployment author names and author images are kept as the organization’s operational history after an individual member deletes their personal account, and are removed when the organization is deleted.

Your choices and rights

Depending on where you live, you may have rights to access, correct, delete, export or restrict processing of personal data. Contact support@akter.dev to make a request. We may verify your identity and apply lawful exceptions. The account personal-data export identifies stores and retirement dates; it is not an export of all application actor data or a SQL database dump.

Contact

Privacy questions and requests go to support@akter.dev. Security reports go to security@akter.dev.