How Yrka handles customer and workforce operations data

Yrka stores organization, user profile, employee record, timecard, schedule, job, message, company resource, training, task, acknowledgement, notification, import, search, payroll-prep, document metadata, uploaded file, billing account, support, and audit information entered into or generated by the service.

Stripe handles standard payment details. Yrka stores Stripe customer, subscription, plan, billing status, and webhook event metadata, but not full card numbers.

We use customer data to provide the hosted product, authenticate users, enforce account permissions, support billing account operations, run imports, produce permission-scoped search results, route notifications, support AI-assisted product features when enabled, debug errors, investigate abuse, and maintain audit history.

Customer workforce data should not be used for advertising. Marketing analytics, when enabled in production, should be limited to public-site usage measurement and should be described in the cookie notice.

AI-assisted admin, official Manual, and Resources chat features may send prompts and selected product context to a configured AI provider when the feature is enabled. Resources chat uses approved prepared records rather than every uploaded draft or file. Customers should review AI outputs before relying on them.

AI output is not legal advice, HR advice, payroll processing, tax filing, safety advice, or a compliance determination.

The product uses authentication/session storage required to operate the service. The public site may use Vercel Analytics in production for aggregate page and performance measurement and Google Analytics 4 only after the visitor accepts the marketing analytics cookie.

Yrka should not add advertising pixels or cross-site behavioral advertising without updating this policy, the cookie notice, and the subprocessor list.

When paid access ends, customer data remains available for export or reactivation for 30 days unless a support-approved exception applies.

After that window, organization data is eligible for deletion. Backups may retain deleted data until the backup retention period expires.

Customers are responsible for assigning owner/admin access carefully, entering accurate information, reviewing outputs before relying on them, and meeting their own payroll, tax, legal, HR, recordkeeping, and employee-notice obligations.