ggno.sh
FeaturesIntegrationsDocsPublishFAQ
Publisher sign inInstall GNO
FeaturesIntegrationsDocsPublishFAQ
Install GNOSign in to gno.sh publishing

Legal

Terms of Service

The rules for using gno.sh, including account access, published content, subscriptions, moderation, and service limits.

Last updatedSeptember 6, 2026

Service

gno.sh is a hosted publishing layer for GNO. It lets you upload and publish compiled knowledge artifacts as public, secret-link, invite-only, or encrypted reading surfaces.

Accounts

You are responsible for your account, credentials, and anyone who uses your organization workspace. Do not share access in ways that bypass plan limits or security controls.

Your content

You keep ownership of the content you publish. You give gno.sh the limited rights needed to host, store, transmit, render, secure, and moderate that content.

Public vs private modes

  • public shares are intended to be reachable by anyone with the URL and may be indexed
  • secret-link routes rely on token secrecy and operational controls
  • invite-only routes require valid account access and membership checks
  • encrypted routes contain client-encrypted ciphertext; gno.sh does not receive the passphrase and cannot recover or server-decrypt the share

Personal invite-only shares allow the owner by default; organization shares use the organization membership and access settings shown in Studio. A secret link can be forwarded by anyone who receives it. Changing into or out of encrypted mode requires a new local export; gno.sh never receives the passphrase or decrypts a share.

Unpublishing and deleting content

Owners can unpublish public, secret-link, invite-only, and encrypted publications in Studio. Unpublish stops hosted reader access and keeps the source and publication history so the source can be published again. Changing a local GNO collection policy or deleting a local file does not retract an uploaded artifact. Hosted operations do not delete your local vault files.

Delete permanently applies to the selected hosted library item, its associated publications and history, and assets no longer referenced elsewhere. Review the affected counts before confirming. Access is denied when deletion is accepted; cleanup then continues in the background. Deleting and Cleanup failed mean payload cleanup is not complete. A cleanup failure keeps access denied and can be retried.

Separately published notes or copies and shared assets still used by another item are not removed. Unpublishing or deletion cannot recall copies already downloaded, cached by others, or independently published. Deletion does not promise immediate erasure from backups. Legal or operational retention exceptions are described in the Privacy Policy.

Acceptable use

You may not use gno.sh to publish or distribute illegal content, exploitative material, targeted harassment, threats, doxxing, malware, credential theft, spam, or content that infringes the rights of others. See the Acceptable Use Policy for details.

Moderation and takedown

I may investigate reports, remove or disable access to content, suspend publishing, or terminate accounts when needed to address abuse, legal risk, security incidents, or violations of these Terms.

Use Report Abuse to email a public page URL and your concern. I review reports manually; a report alone does not establish a violation or trigger automatic takedown. Opening an email draft does not submit a report, and I do not promise a fixed response time.

A moderation restriction denies hosted access to the affected publication and its history and assets. Changing its route, rotating a token, publishing again, or importing an exact copy under the same owner does not clear the restriction. This exact-copy check does not guarantee detection of edited content or copies under another account.

Affected owners see Restricted and a policy explanation in Studio. To request review, email abuse@gno.sh with the publication identifier and your explanation. Owners can still delete their hosted content. Reinstatement clears only the moderation restriction: it does not undo deletion, unpublishing, expiry, or access revocation, restore old secret tokens, or automatically republish a withdrawn source. Report handling and retained restriction records are described in the Privacy Policy.

Billing

Paid features and limits depend on your current plan. Subscriptions, renewals, and cancellations are handled through the billing provider shown at checkout.

Availability

gno.sh is provided on an as-available basis. I may change, improve, restrict, or remove features, limits, or integrations at any time.

Liability

To the maximum extent permitted by law, gno.sh is not liable for indirect, incidental, special, consequential, or exemplary damages, or for loss of data, revenue, profit, or goodwill. Nothing here excludes liability that cannot be excluded by law.

Contact

Legal and service contact: legal@gno.sh. Security reports: security@gno.sh.

ggno.sh

GNO is a local knowledge workspace for humans and agents. gno.sh is the hosted publishing layer on top, for when you need to share beyond your machine.

Product

  • All features
  • Hybrid search
  • Context Capsules
  • Verified answers
  • Knowledge Delta
  • Web UI
  • Agent skills

Docs & Resources

  • Install GNO
  • Documentation
  • Quickstart
  • CLI reference
  • REST API
  • Integrations
  • Comparisons
  • llms.txt
  • Ecosystem
  • FAQ

gno.sh Publishing

  • Publish platform
  • Read the atlas sample
  • Create account
  • Sign in
  • Your dashboard

Legal

  • Terms
  • Privacy
  • Acceptable use
  • Report abuse
  • Imprint & contact
© 2026 GNO — built by Gordon MickelLocal by default. Yours to share when ready.
  • GitHubGitHub
  • X@gmickel