Proposed service terms

01 · Status of these terms

What these terms cover

These terms describe the Naratake browser service as it runs today: who may use a workspace, what you keep, what publishing does, and how billing works. They state real product boundaries so nobody assumes a service exists that has not shipped.

If you later sign a separate order or agreement with Naratake, that document controls where it differs from this page.

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.

Publishing offers two deliveries. The full delivery gives each site its own database and back office and requires a plan that includes them; the storefront delivery ships the same site without its write-side features, and every removed section is named in the publish report. Which deliveries your workspace may request follows from your plan.

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.

Cloud Go live delivers an eligible project one of two ways. The full delivery provisions the site its own managed database and back office, and is available only to a workspace whose plan carries both the commerce and bookings modules. The storefront delivery publishes the same site without the parts a visitor writes to, and every removed section is named in the publish report. Which delivery applies is determined on Naratake’s servers when the request is submitted — from the actual components and required modules in the reviewed revision, and from the workspace’s entitlements at that moment — not from the starting-point label and not from the browser. Naratake may stop a publish request before any provider work if the project needs a delivery the workspace’s plan does not cover, or a capability 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.

Account sign-in is provided through Clerk, and subscription payments through Stripe. Hosting, databases, storage and publishing also depend on the providers identified in the Privacy Notice and the services configured for your workspace. Their own terms and availability apply alongside these terms.

07 · Billing

No hidden price invented by this page.

Subscriptions and payments are handled through Stripe for the workspace you select. Review the plan, currency, billing period, taxes and renewal information shown before confirming a payment or plan change.

Prices, currency, billing cadence, taxes and renewal are shown on the pricing page and again at Stripe’s hosted Checkout before any charge. Plan changes and cancellation are self-serve from the billing page in your workspace. Each Naratake account gets one 7-day refund window starting with its first cloud subscription payment. Email us within that window with the workspace name. Renewals, canceling and resubscribing, and additional workspaces do not create a new window. This guarantee covers only that first cloud subscription; additional workspace subscriptions are not covered, even within the original 7 days. An upgrade within the same billing cycle does not restart the original 7-day refund window. A full refund requested within that window includes the first payment and any upgrade difference you actually paid for that original subscription. We stop renewal on your behalf; you do not need to cancel separately in the billing portal. For cancellation without a refund, paid benefits continue until the paid period ends. Once we confirm a full refund for your current paid period, paid benefits end. From that confirmation, your hosted site stays online for 7 days and its operational data is retained for 30 days.

Upgrading within the same billing cycle — monthly to monthly or annual to annual — costs the difference for the time remaining in your current period. The higher plan starts as soon as payment succeeds, and your renewal date stays the same.

A confirmed switch between monthly and annual billing takes effect at the next renewal. Your current paid period continues under its existing schedule; the billing page shows the proposed date and price before confirmation.

A voluntary Storefront Pro downgrade takes effect after your confirmation, billing adjustment and website transition are complete. We aim to finish the same day; an incomplete request stays visibly pending. The cycle and renewal date stay the same. Eligible unused paid time is prorated into credit for future subscription invoices for that workspace, not an automatic cash refund. When cancelling or closing an account, contact support to check any remaining credit and eligible refund together; the same amount cannot be refunded and used as credit.

Before confirming a downgrade, you select the retained website and editable projects and review the features that will stop. Extra projects are archived for reading. Pro features stop accepting new orders or bookings after the transition. A downgrade does not delete your account or start cancellation retention for a workspace that remains subscribed.

Affected operational data has a 30-day retrieval period starting when the downgrade is effective, new transactions have stopped and the complete download is first available, whichever is latest. Before deletion, we provide at least seven days of actual notice and retrieval opportunity. Export or notice failures extend the deadline. Data needed for unresolved orders or bookings remains until 30 days after resolution; shared active databases are protected.

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

Service availability and changes.

Published features and limits follow the plan or agreement you purchase. Maintenance, provider failures, security response, legal requirements or misuse may interrupt access. No uptime or incident-response service level is guaranteed unless a separate agreement states one.

Material changes affecting an existing customer follow the advance-notice and transition rules stated above. A change does not retroactively remove the refund conditions of an earlier payment or an already accepted support commitment.

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.

Warranty exclusions, liability caps, indemnities, governing law and dispute forum will be stated in the counsel-reviewed revision of these terms; until then, nothing on this page limits a right the law gives you, and Naratake’s liability is what the applicable law says it is.

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.

Support and security-report commitments for this version:

We will reply as soon as possible. We do not promise a fixed time for a first reply or resolution. For a live site outage or a billing concern, put URGENT in the subject. This inbox is not monitored 24/7. Legally required deadlines still apply.

Found a vulnerability? Same inbox, subject “Security”. We review reports and reply as soon as possible, and will not take action against good-faith research.