Hosted service terms for the first Yrka launch

The initial hosted launch model uses Starter ($79/month), Team ($149/month), Ops ($249/month), and Managed ($799+/month scoped) packages. Standard paid plans can begin with a 30-day card-required trial when billing is enabled.

All core app features are included across paid hosted plans. Active employee capacity, pooled AI credits, support posture, location add-ons, overages, and managed rollout help scale by plan.

Cancellation normally takes effect at the end of the current billing period unless support approves an exception.

Payroll-prep, scheduling, tax estimate, policy, document, AI, and reporting features are operational tools. They do not provide payroll processing, tax filing, legal advice, HR advice, or compliance guarantees.

Customers remain responsible for reviewing pay rules, employment classifications, overtime treatment, leave rules, policy language, workplace notices, tax treatment, and any employee-facing decision before using the output operationally.

Yrka can organize evidence, drafts, reports, tasks, and exports, but the customer decides whether those materials are accurate and appropriate for the customer's legal, payroll, HR, safety, and compliance obligations.

Customers may not use Yrka to upload unlawful content, abuse employees or recipients, probe platform security, bypass access controls, or process data they do not have authority to manage.

Yrka may suspend access when needed to protect the platform, other customers, employees, recipients, or subprocessors.

AI features require customer review before use. Integration readiness pages describe product seams and provider setup posture, not a guarantee that a provider connection is live or approved.

AI-assisted writes should remain previewed, permission-checked, and auditable. A customer administrator should review warnings, source context, and proposed changes before confirming any action that affects employees, schedules, records, messages, resources, or tasks.

Connected-provider behavior depends on customer authorization, provider terms, provider availability, supported adapters, credentials, and the customer's configuration. Yrka is not responsible for provider-side decisions, outages, approval requirements, or data the customer chooses to move outside Yrka.

Support targets are described by plan, but this launch draft does not promise formal uptime, service credits, or response-time guarantees until those commitments are backed by monitoring, staffing, incident response, and contract terms.

Planned maintenance, provider outages, customer network problems, browser/device issues, payment-provider problems, and third-party authentication interruptions may affect access or delivery even when Yrka's own service is operating normally.

Customers should maintain their own continuity procedures for critical workforce operations, including how managers communicate urgent schedule, time, payroll, safety, or staffing changes if a system or provider is temporarily unavailable.

When paid access ends, Yrka expects to keep customer data available for export or reactivation for the documented post-cancellation window unless a support-approved exception applies.

After that window, organization data becomes eligible for deletion under the data retention and deletion runbooks. Backups may retain deleted data until the backup retention period expires, and support may need to verify account authority before assisting with export or deletion requests.