YYayaw
Service terms

The operating rules for Yayaw

Terms for the public site, dashboard, paid offers, source-code access, CMS, API, and MCP workflows unless a signed agreement says otherwise.

Operator

YAYAW SAS, SIREN 953 834 272, 42 rue de la Côte, 78220 Viroflay, France.

Professional use

Built for founders, teams, and organizations operating software products.

Agreement hierarchy

Signed orders, source-code licenses, repository terms, or written agreements override these terms where they conflict.

Plain-language deal

Four things to keep clean

The detailed clauses below mostly expand these practical commitments.

01

Access | Keep account, organization, billing, and credentials accurate and secure.

02

Operations | Review CMS, API, MCP, and dashboard actions before running them.

03

Code | Respect the license or order attached to source-code access.

04

Payment | Pay for paid access and follow checkout, invoice, order, or written terms.

Commercial stack

Accounts, admins, and billing

The commercial rules are grouped by who can act and what those actions change.

Account data

You must keep account, organization, billing, and contact information accurate.

Admin authority

Owners and admins may invite users, assign roles, manage billing, configure content, and bind the organization.

Paid access

Prices, currencies, seats, quotas, taxes, renewals, coupons, and promotion codes appear in checkout, dashboard, invoices, orders, or written terms.

Cancellation

Unless stated otherwise, subscriptions renew until cancelled. Cancellation stops future renewal, not necessarily periods already started.

Operational surface

CMS, API, MCP, and source code

These surfaces can publish, configure, trigger providers, and change customer-facing behavior.

Content rights

You retain rights to submitted content and grant Yayaw the rights needed to host, process, display, back up, transmit, and secure it.

Operational responsibility

Dashboard, CMS, API, and MCP actions may publish content, change settings, affect billing, or trigger external providers.

Source-code boundary

Repository access, licenses, handoff, and implementation support follow the applicable order, license, repository terms, or signed agreement.

Boundaries

Misuse, suspension, liability, law

The legal closing section is operational: what Yayaw may stop, log, moderate, or limit.

No abuse

Do not violate laws, infringe rights, send unlawful content, attack systems, bypass limits, scrape without permission, or attempt unauthorized access.

Audit and moderation

Yayaw may log administrative and control-plane actions, investigate misuse, suspend access, remove unlawful content, or preserve records for security, compliance, or disputes.

Liability

Yayaw provides software and implementation support, not legal, tax, accounting, financial, certification, or investment advice. Liability is limited to the maximum extent permitted by law.

French law

French law governs these terms, subject to mandatory rules. Disputes should first be handled amicably before competent French courts where legally permitted.

Need a contractual clarification?

Contact team@yayaw.app before relying on an interpretation of these terms.