Acceptable use draft
Use Yrka for legitimate workforce operations
This draft describes expected customer behavior for launch. It should be reviewed by counsel before public use.
Allowed Use
Yrka is intended for customer-managed workforce operations, including scheduling, timekeeping, employee records, communications, resources, training, tasks, imports, reports, and payroll-prep handoff.
Appropriate use includes organizing employee-facing work, routing operational approvals, maintaining customer-owned records, sending workplace communications, reviewing imports before they affect live operations, and preparing files or summaries that a customer reviews before using elsewhere.
Customers remain responsible for confirming that their own policies, notices, data collection practices, pay rules, scheduling rules, and employee communications are lawful and appropriate for their workforce.
Prohibited Use
Customers may not use Yrka to upload unlawful content, harass employees or recipients, process data without authority, reverse engineer the service, probe platform security, bypass access controls, or interfere with other customers.
Customers may not use AI features to produce or rely on legal, HR, payroll, tax, safety, medical, or compliance determinations without independent qualified review.
Customers may not use Yrka to make hidden surveillance claims, collect data they have not disclosed to employees where disclosure is required, impersonate another person, send deceptive communications, or route sensitive decisions through the product in a way that avoids the customer's own required review.
Customers may not upload malware, attempt credential harvesting, overload the service, scrape another customer's data, or use integrations to move provider data outside the permissions granted by the relevant provider and customer account.
Integrations
Integration readiness does not mean a provider connection is live until customer setup, authorization, and provider-specific proof are complete.
Provider connections must be configured by an authorized customer administrator, use approved credentials or OAuth flows, and stay within the scope the provider grants. Customers are responsible for disconnecting providers they no longer want Yrka to use.
Imports, calendar sync, source sync, notification delivery, and payroll handoff features are designed for review-first operations. Customers should not treat a staged import, draft source, prepared export, or delivery attempt as a final provider action until the relevant review and provider-side confirmation are complete.
AI Review Responsibilities
AI-assisted answers, summaries, drafts, and suggested actions are support tools for customer review. Yrka's review-first posture means customers should inspect source context, previewed changes, warnings, and permissions before relying on the output.
Customers should not use AI output as the sole basis for employment actions, payroll decisions, compliance determinations, safety instructions, medical conclusions, legal notices, or tax treatment. Qualified human review remains required where the decision or communication calls for it.