Clear rules for a product still earning production trust.

01 · Status of these terms

A useful operating draft, not a finished contract.

These terms describe the intended use of the current Naratake browser service during development, evaluation, and authorized pre-production testing. They document real product boundaries so testers do not assume that unconfigured or unverified services are available. They do not create a production service-level agreement.

If Naratake provides a signed order, launch agreement, or reviewed production terms later, that document will control where it conflicts with this draft.

02 · Accounts and authority

Use the workspace you are authorized to represent.

• You must be legally able to use the service and to act for the business or organization you place in a workspace.
• Keep account access and identity-provider credentials secure; do not share a session or impersonate another person.
• Workspace owners and admins are responsible for assigning appropriate application roles and reviewing access.
• Do not attempt to select or access another tenant by modifying URLs, requests, project files, or provider identifiers.
• Tell Naratake promptly if you believe an account, workspace, or published site has been compromised.

When Clerk is configured, it authenticates users and organizations. Naratake database membership remains the authority for ordinary application roles. Team invitation, provider-membership synchronization, role-revocation automation, and audit events are not yet presented as complete production capabilities.

03 · The browser service

The browser is the Studio.

Naratake provides a web workspace for creating and editing business sites, previewing responsive layouts and the business tools that run behind them, retaining project revisions, reviewing releases, and publishing. End users are not required to use the Local Studio desktop application.

What a project produces is a full Next.js application backed by a Postgres database, not a folder of static files. Eleven of the seventeen modules need a running backend: orders, payments, reservations, appointments, customers, promotions, the desk, collections, ads, platform links, and analytics. Only three — catalog, reviews, and content — can be baked to static files.

Cloud publishing today ships only the part of a project that runs without a database, because the managed database service is not connected yet. That is a limit on one delivery path at this moment, not a description of the product: every module can be authored, previewed, and versioned now.

Features can be unavailable when identity, database, object storage, billing, build, or deployment providers are not configured or healthy. Guarded routes are designed to fail closed rather than claim a successful durable save, payment action, export, or deployment when a required service is missing.

04 · Your content

You keep responsibility for what you put into the product.

You retain your rights in business information, copy, images, logos, and other material you submit. You grant Naratake a limited permission to host, copy, validate, transform, preview, build, publish, and display that content only as needed to operate the service and follow your workspace actions.

• Use only content you own or have permission to use.
• Verify prices, claims, contact details, policies, accessibility, licenses, and required disclosures before launch.
• Do not place secrets, private customer records, regulated health data, or raw payment-card data in public page content.
• Keep an independent copy of business-critical source material while production backup and restore procedures remain unverified.

05 · Publishing and operations

Go live is eligibility-gated.

The current cloud Go live path accepts projects whose reviewed revision runs without a database. Eligibility is derived from the actual components and required modules in that revision, not only from the starting-point label. Naratake may stop a publish request before any provider work if the project needs a managed database or another capability that the current publication path does not support yet.

An eligible publish freezes one project revision, builds and verifies an immutable artifact, and then promotes a stable release pointer. Release history and rollback do not replace your own review of the site’s content, legal copy, phone layout, links, payments, email, analytics, or other launch dependencies.

06 · Third-party services

Providers remain separate services.

Naratake may connect to identity, payment, database, private object-storage, hosting, build, and deployment providers when configured. Their availability, security, account decisions, and independent terms are outside Naratake’s direct control. You may need to accept provider terms or complete provider verification before a feature works.

The current build contains boundaries for Clerk and Stripe, but no production Clerk tenant, Stripe catalog, live price mapping, production webhook, or production-provider drill is claimed here. A final production agreement must name the approved providers and allocate provider-specific responsibilities.

07 · Billing

No hidden price invented by this page.

Naratake billing is inactive unless an approved server-side catalog, Stripe price mapping, matching test or live keys, signed webhook, canonical application URL, and dedicated billing database role are configured. The browser may only request a configured price alias; it does not supply a Stripe price ID or a checkout return URL.

Final prices, currency, billing cadence, taxes, renewal, cancellation, refund terms, and any trial must be disclosed in an approved order and at hosted Checkout before a production charge. Stripe’s hosted portal may provide supported account actions when configured. This draft does not promise a refund policy, a trial, or a cancellation outcome that has not been approved.

08 · Acceptable use

Do not use Naratake to harm people or systems.

You may not use the service to:

• break the law, violate another person’s rights, deceive visitors, or publish unlawful or malicious content;
• probe, bypass, disable, or interfere with authentication, tenant isolation, quotas, launch checks, or provider controls;
• upload malware, unsupported executable content, credential material, or intentionally malformed files;
• scrape, overload, automate abuse against, or reverse engineer the service, except where applicable law expressly allows it;
• process regulated or highly sensitive information with Naratake without a separate reviewed agreement and verified controls.

09 · Naratake ownership

The product remains Naratake’s; your business remains yours.

Naratake and its licensors retain rights in the software, editor, product design, templates, documentation, and branding, excluding your content. You may use product output only within the permissions of your approved plan or agreement. Do not use the Naratake name or marks to suggest sponsorship or endorsement without written permission.

If you voluntarily provide feedback, Naratake may use it to improve the product without an obligation to treat it as confidential. Do not submit third-party confidential information as feedback.

10 · Availability and changes

Pre-production software can change.

Naratake may change, limit, suspend, or remove pre-production capabilities while the product is being completed and verified. The current service does not offer a production uptime SLA, a response-time promise, a backup guarantee, a custom-domain promise, or a universal publishing entitlement. Planned maintenance, provider failures, security response, legal requirements, or misuse may also interrupt access.

Where practical, Naratake should give notice before a material customer-facing production change. That process and any contractual service levels must be defined in the final reviewed agreement.

11 · Disclaimers and open legal terms

Review every site before relying on it.

Naratake is a website and operations workspace, not legal, accounting, tax, medical, accessibility-certification, cybersecurity-certification, or marketing-performance advice. Templates, checks, previews, and documentation do not guarantee legal compliance, search ranking, accessibility conformance, revenue, uptime, data recovery, or business results.

Final warranty exclusions, liability caps, indemnities, governing law, dispute process, consumer rights, and termination effects are intentionally not asserted in this engineering draft. Those provisions depend materially on the contracting entity, sales model, customer location, and approved service scope, and must be supplied through production legal review.

Privacy handling is described in the Privacy Notice. The current technical control and verification status is described on Security & Trust.

12 · Contact

Ask before you assume.