Lova Terms of Service

Effective date: May 17, 2026

These Lova-specific terms (“Lova Terms”) govern your use of the Lova product (the “Service” in this document) provided by Lovex AB (“we”, “us”). They supplement the umbrella Terms of Service; the Acceptable Use Policy; the Data Processing Agreement for processing of personal data; and, for customers on paid Order Forms, the Master Services Agreement and Service Level Agreement. Where a provision in these Lova Terms conflicts with the umbrella Terms of Service for Lova’s use of the Service specifically, these Lova Terms control; for everything else, the order of precedence in the MSA applies.

Maturity disclosure. Lova is currently labeled Preview on the public products page. Preview features may be modified, removed, rate-limited, or replaced as the product evolves. Material reductions in core functionality during a paid Subscription Term are limited to those required by law, security, or sub-processor change. The trust posture published at /trust applies fully.

1. The Service

Lova is an AI-assisted project management product. The core capabilities are: conversational AI board shaping, task and project management, sprints, AI-narrated activity, team and project chat, automations, integrations, and an Agent API for external programmatic access.

Some capabilities are subject to per-tier limits and AI usage quotas — Free, Pro, Team, Business, Enterprise. The current tier limits are stated on the pricing page at /lova/pricing; we may adjust them with notice, including AI usage caps where third-party inference costs change materially.

2. Accounts, teams, and roles

Lova organizes work into Teams, Projects, and Boards. A team has one or more members. Each member holds one of two built-in roles: Lead or Member. Custom roles for the Business tier are on the roadmap.

• Lead. Can invite and remove members, change roles, configure integrations and AI behavior, manage billing, and delete projects. Has full chat-level access to the AI for project shaping. Bears administrative responsibility for the team.
• Member. Can be assigned to tasks, comment, pick up work, and chat with the AI on task-level scopes within projects they are added to.

The team is the contracting party for paid plans. The Lead who creates the team is responsible for accepting the order, paying invoices, and binding the team to these Lova Terms unless an authorized representative of the customer organization is substituted on the Order Form. Adding or removing members does not transfer the contracting party.

3. AI features

Lova uses third-party large language model providers under written DPAs (see /subprocessors) to generate suggestions, narrations, board proposals, summaries, and other content (“AI Output”). The following applies to every AI feature:

• Drafts, not authoritative. AI Output is a draft. You accept, edit, or reject it. Lova does not represent that AI Output is correct, complete, or suitable for any specific purpose, including legal, medical, financial, regulatory, or safety decisions.
• Human oversight. AI features that mutate the workspace (create or modify tasks, run automations, send messages, change board structure) are reversible and surface a clear authorship signal to the affected team members.
• No training on Customer Content. We do not use your content to train our own models. Our AI providers are contractually constrained from using customer content to train their general-purpose models where they offer that commitment.
• Quotas. AI usage is metered per team. Exceeding a per-cycle quota may pause AI features for that team until the next cycle, top-up purchase, or plan upgrade.
• Workspace opt-out.A Lead may disable AI features for the team entirely. While disabled, no AI inference is performed on that team’s data (subject to the rollout schedule of this control — currently on the in-product roadmap).

4. Customer Content and ownership

Your content.You retain ownership of tasks, projects, comments, chat messages, attachments, and any other content you or your team members submit to the Service (“Customer Content”). You grant Lovex AB a worldwide, non-exclusive, royalty-free license to host, transmit, and process Customer Content solely to provide, secure, support, and improve the Service for you.

AI Output. As between you and us, you own AI Output generated for you in response to your prompts, subject to the rights of any third party whose input contributed to that output and to the limitations of applicable intellectual-property law. You may not represent AI Output as solely human-authored where the distinction is material to a decision being made (per /aup).

Our intellectual property. The Service, including software, design, brand, and Documentation, remains our property and that of our licensors. These Lova Terms grant you a limited, non-exclusive, non-transferable right to access and use the Service.

Feedback. Feedback you give us about the Service is given freely. We may use it without restriction or compensation.

Aggregated and de-identified usage data. We retain a perpetual, irrevocable, non-exclusive license to use anonymous, aggregated, or de-identified usage and performance data derived from your use of the Service to operate, secure, and improve the Service. We do not re-identify aggregated data.

5. Agent tokens and the Agent API

Lova exposes an Agent API documented at /agents. Customers may create agent tokens (the agt_ bearer tokens) scoped to a project to allow external automation to read and write the board on their behalf.

• Bearer-token responsibility. Whoever holds a valid agent token can act on the project. Treat agent tokens as secrets. We do not validate which natural person or system is using a token beyond the cryptographic check.
• Token revocation. Leads can mint, list, and revoke agent tokens at any time. Revocation is immediate; any in-flight request authenticated with a revoked token fails on its next round trip.
• Agent actions are your actions. An agent token authenticated as your team is, for purposes of these Lova Terms and the AUP, acting on your behalf. You are responsible for the conduct of agents you authorize, the rate at which they consume the Service, and any content they submit.
• Rate limits. Agent endpoints are rate-limited. Excessive use may throttle the token or, in the case of sustained abuse, suspend the team consistent with the AUP.

6. Automations

Lova allows you to configure automations that run in response to board events (status changes, comments, scheduled triggers). Automations execute as the team that owns them; their actions are attributable to that team for audit purposes.

• You are responsible for the side effects of automations you create, including any messages they send, integrations they trigger, or data they move.
• We may pause automations that are exhibiting failing behavior (repeated errors, suspected loops, abusive volume) and notify the team Lead. Resumption requires acknowledgment that the failing behavior has been investigated.
• Automations that integrate with third-party systems (Slack, GitHub, webhooks, etc.) are subject to the rate limits, authentication scopes, and terms of those systems. We do not warrant that integrations will work uninterruptedly when the third party changes.

7. Integrations

Integrations with third-party systems (notably Slack, GitHub, calendar feeds, email) are optional. To enable an integration you (or another authorized Lead) grant the permissions described at the connection point. We use those permissions only to provide the integration. We may rely on the third party’s availability and terms; if the third party changes or restricts its API, the integration may degrade or fail without constituting a breach of these Lova Terms.

8. Plans, seats, and billing

Lova is offered on multiple plans (currently Free, Pro, Team, Business, Enterprise). Pricing and seat-based mechanics are at /lova/pricing. The umbrella Terms of Service and, for Enterprise customers, the MSA govern fees, taxes (EUR + moms), invoicing cadence, and non-payment consequences.

• Seat changes. Adding members to a paid plan that has reached its seat allowance prompts plan upgrade or prorated seat-purchase. Removing seats is effective at the next billing cycle (no prorated refund for in-cycle reductions).
• Plan downgrade. Downgrading may remove access to AI usage tiers, integrations, or audit data tied to the higher tier. We do not delete content on downgrade; we restrict access to features the new plan does not include.
• Free tier limits. The Free tier exists for evaluation, side projects, and small teams. It is subject to caps on members, projects, and AI usage. Free-tier accounts are best-effort for support per /sla.

9. Data export and deletion

Export. Any team member can export the data tied to their user account via /api/account/export. Workspace-level export tools for Leads are on the in-product roadmap.

Deletion. Account deletion is immediate per /api/account/delete: personal-data tables are hard-deleted via FK cascade; authored content in shared workspaces is anonymized by setting user_id to NULL so teammates are not left with confusing gaps. There is no user-recoverable grace period; backups containing personal data rotate out typically within 30 days. See /trust for the full retention narrative.

Team deletion.A Lead may delete an entire team only when they are the sole remaining member (a guardrail against destroying other members’ work). Otherwise, the Lead may transfer ownership to another Lead before leaving.

10. Service availability and support

We target 99.9% monthly availability on paid Lova tiers for the core control plane (sign-in, board read/write, AI chat). Per /sla, this is a target, not a credit-backed SLA, except where an Enterprise Order Form expressly provides credits. Free-tier support is best-effort. Tier-based response times are at /sla.

11. Special-category data and prohibited content

Without prejudice to /aup, you must not submit to Lova any content that is unlawful, fraudulent, malicious, or that constitutes special-category personal data under Article 9 GDPR unless expressly agreed in writing in advance. Lova is not a HIPAA business associate; Protected Health Information must not be submitted.

12. Liability

For paying customers, the liability framework in the MSA §12applies. For Free-tier users, the umbrella Terms of Service §11applies — including a per-incident cap of the greater of the fees you paid us in the twelve months preceding the event or one hundred euro (€100), and exclusion of indirect, incidental, consequential, special, or punitive damages, except for liability that cannot be limited under applicable law.

13. Changes to these Lova Terms

We may update these Lova Terms to reflect product evolution, new features, or new regulatory requirements. Material changes affecting paying customers are announced at least 30 days in advance via in-product notice and email to the Lead. Continued use after a change indicates acceptance.

14. Governing law and forum

These Lova Terms are governed by the laws of Sweden, without regard to its conflict-of-laws rules. The courts of Stockholm, Sweden have exclusive jurisdiction over disputes, without prejudice to Data Subjects’ rights to bring claims in the courts of their habitual residence as permitted by the GDPR.

15. Order of precedence

For matters concerning Lova specifically, the documents that make up the agreement apply in this order, top down: (a) a signed Lova Order Form for Enterprise customers, (b) the DPA with respect to personal data, (c) the MSA for Enterprise customers, (d) these Lova Terms, (e) the umbrella Terms of Service, (f) the AUP, (g) published documentation. Where a higher-precedence document is silent on a topic, the next-highest applies.

Contact

Questions about these Lova Terms or product-specific commitments: hello@lovex.dev. Legal and contractual matters: legal@lovex.dev.