Amo.ng Terms of Use

Amo.ng is a free, public, no-sign-in prompt library. You may browse, copy, adapt, and run individual prompts in AI tools for personal, educational, internal business, client, research, coding, automation, marketing, and operational work.

These terms cover the Amo.ng prompt library and related resources, Workplace, Amo Build, and temporary project hosting under *.build.amo.ng.

Third-party AI providers and independently chosen hosting services have their own terms, limits and charges.

Free access does not permit resale of the Amo.ng prompt library.

By using Amo.ng, you agree to these terms.

1. Permitted use

You may:

1. Browse Amo.ng without signing in.
2. Copy individual prompts for your own use.
3. Adapt prompts for your own projects, workflows, teams, or clients.
4. Run prompts in AI tools such as ChatGPT, Claude, Gemini, Codex, and similar tools.
5. Use outputs generated from your own use of the prompts, subject to the terms of the AI tool you use and your own responsibilities.

Educators, lecturers, students, student associations, libraries and facilitators may link to Amo.ng and share or print individual Amo.ng prompts for non-commercial teaching, learning, workshops, assignments or research, provided the attribution ‘Amo.ng by RichlyAI’ and the prompt’s canonical URL remain visible.

This permission includes enrolled learners and participants in non-commercial university, school, library or community workshops.

2. Restricted use

You may not, without prior written permission from Amo.ng or RichlyAI:

1. Sell Amo.ng prompts.
2. License, sublicense, or package Amo.ng prompts as a paid or free product.
3. Republish substantial parts of the Amo.ng prompt library.
4. Mirror, clone, or recreate Amo.ng as another prompt library or directory.
5. Scrape, crawl, bulk download, harvest, or extract prompts for redistribution.
6. Include Amo.ng prompts in another marketplace, SaaS product, database, AI tool, prompt pack, commercial content library, or substantially republished course or newsletter archive. The limited educational permission in Section 1 allows links to Amo.ng and the sharing or printing of individual attributed prompts, but it does not permit bulk copying or importing the library into an LMS, database, course repository or other content collection without prior written permission.
7. Redistribute a collection or prompt pack made from Amo.ng content, sublicense it, remove required attribution, or make substantial parts of the library available through an LMS or another shared repository without prior written permission.
8. Remove Amo.ng or RichlyAI attribution when publicly quoting, referencing, or sharing prompt content.
9. Use Amo.ng in a way that harms, overloads, disrupts, or abuses the service.

3. No bulk harvesting

Automated scraping, bulk harvesting, dataset creation, commercial indexing, model training collection, or large-scale extraction of Amo.ng prompt content is not allowed without written permission.

Amo.ng may block, rate-limit, challenge, or restrict abusive traffic, bots, crawlers, scrapers, or activity that appears to misuse the service.

4. Ownership and permission

Amo.ng and RichlyAI retain rights in their platform and branding, the prompt library, prompt structure, prompt pages, summaries, descriptions, metadata, and related platform and library content.

You receive a free, limited, revocable, non-exclusive, non-transferable permission to access and use individual prompts as allowed by these terms.

This permission does not transfer ownership of Amo.ng or RichlyAI’s platform, branding or prompt-library content. It does not give Amo.ng ownership of your own inputs or materials. Generated project files are addressed in Section 10.

This includes the limited non-commercial educational permission described in Section 1. It does not transfer ownership or permit bulk copying, mirroring, sublicensing, resale or substantial republication.

5. User responsibility

You are responsible for how you use prompts and AI outputs.

Do not paste confidential, sensitive, regulated, private, proprietary, or restricted information into any AI tool unless you have permission and have reviewed the relevant tool's data and privacy terms.

You should review, verify, and adapt AI outputs before relying on them.

6. No professional advice

Amo.ng prompts and generated outputs are for informational and productivity purposes only.

They are not legal, financial, tax, medical, security, regulatory, compliance, or professional advice.

You should consult qualified professionals where appropriate.

7. Privacy and aggregate usage

Amo.ng may record aggregate first-party usage signals such as page views, successful copy actions, and optional Yes/No usefulness feedback to improve public content. Feedback requires no account. Temporary IP-based rate limiting may be processed to deter abuse, but Usage Intelligence does not store raw IP addresses, persistent visitor IDs, device fingerprints, or individual browsing histories.

Workplace: access, provider charges and data

Amo.ng and Workplace are free to use. No Amo.ng account is required. Running prompts in Workplace requires your own provider API key; your provider’s usage charges apply.

When you run a prompt, your browser sends the provider API key and submitted task information over HTTPS to the Workplace server. Workplace processes them transiently to construct and forward your request to the selected AI provider, then relays the generated response to your browser. Continuation requests also send the relevant earlier output and edits as context. The execution application does not save these keys, submitted task information or generated responses to its database or application logs.

Operational data is separate: temporary rate-limit records and concurrency locks protect execution capacity, and hosting and security services may retain request metadata in access or security logs. The selected provider processes the request under its own terms, privacy policy and retention rules. Review those rules before submitting information; provider charges and any provider-side retention are outside Amo.ng’s control.

Information entered into a prompt and unsaved output remain in the current browser page. If you choose to save provider keys in the vault or save Private Results, Workplace encrypts that data in your browser and stores it locally in that browser’s IndexedDB storage. Unlocking uses your vault passphrase locally; the passphrase is not sent to the Workplace server. Saved data is not synced to an Amo.ng account or stored as a server-side vault. Browser data can persist after the page closes until you delete it, and clearing site data can remove it.

Copies, downloads and exported vault backups are under your control. Protect your device, passphrase and exported files; plain-text copies and downloads are not protected by the vault’s encryption. Codex preparation creates a task for you to hand off separately; Workplace does not run a coding agent. Preparing or copying that task does not send it to an AI provider.

8. Changes

Amo.ng may update, remove, edit, reorganize, or restrict access to any prompt or page at any time.

Amo.ng may update these Terms of Use from time to time. Continued use of Amo.ng means you accept the updated terms.

9. Permission requests

For permission to reuse, license, syndicate, integrate, commercially distribute, import into an LMS or database, include in a prompt pack, or otherwise republish Amo.ng content beyond the individual non-commercial educational use allowed in Section 1, contact RichlyAI at support@richlyai.com.

10. Amo Build

10.1 Building, saving and publishing

Amo Build lets you describe a project or import a published Amo.ng prompt, generate and edit supported websites or browser-based tools, preview your work, manually save supported projects in your browser, download files and use the available publishing options. Its supported website files use HTML, CSS and JavaScript; it does not currently provide databases, server-side applications or framework execution.

Users build and edit with Amo Build, save projects in their browser, download their files, or publish through a hosting account they control. Amo-hosted sharing is temporary, not an unlimited or permanent hosting service.

10.2 Free access, provider keys and charges

Amo Build is free to use and does not require an Amo account. Running an AI build or revision requires your own supported provider access and API key. Your provider’s usage charges may apply.

You manage your provider account, permissions, available credit or quota, and spending limits. Amo does not supply free API credit or guarantee provider availability. Stopping a request may not prevent provider charges for work already performed; Amo cannot reverse those charges.

10.3 Requests, keys and data handling

For generation or revision, your browser sends your provider API key, submitted request and required context over HTTPS through Amo’s execution service to the selected provider. Context can include your brief, imported prompt, supplied inputs and previous project text files. The current Perplexity option routes generation to OpenAI, so both Perplexity and OpenAI process the request. Attached project images are retained with the project and are not sent for generation.

The execution service handles provider keys transiently. Keys are cleared from the Build interface after use, provider change or inactivity, and are excluded from saved projects, exports and application logs. This key-handling statement does not mean that published files or operational metadata are never stored.

Hosting and security services may process request and security metadata separately from project content. Publishing access uses Cloudflare Turnstile, which processes browser and network signals such as IP address and user agent; project files, prompts, provider keys and recovery codes are excluded from that verification. AI providers and infrastructure providers apply their own privacy and retention rules.

10.4 Browser-local projects and backups

Saving a project is manual. Browser-local projects are unencrypted and may be accessible to anyone using the same browser profile. They are not Workplace’s encrypted vault, and Amo Build does not provide automatic saving, account sync or cloud backup. Browser-data clearing, private-browsing expiry or device loss can remove saved work.

Protect browser saves, downloads and editable project backups, and keep your own backup copies. A project backup preserves supported editable work; it is different from the private publishing recovery file. Possession of that unencrypted recovery file can grant management access to a hosted site. Keep it secure and separate from project backups, and never publish or share it.

10.5 Amo-hosted sharing and removal

Deliberately publishing uploads the selected website files and images to Amo’s hosting infrastructure and makes their contents publicly accessible. Unselected project records are not automatically included. Review selected files, code and image metadata for information you do not intend to publish.

Amo hosts your project for 30 days from its first successful publication. Save your project or download a backup to keep your work. For long-term publishing, use your own hosting account.

The hosting period is a fixed 30 × 24 hours, recorded using server time. Registration, file preparation and an unsuccessful first publication do not start this period. The publishing interface shows the hosting-expiry date and time in UTC.

Updating, restoring, unpublishing, recovering management access or republishing the same site does not restart or extend its hosting period. Visits do not extend it. Management-session expiry is separate from hosting expiry.

Connecting a verified custom domain to an Amo-hosted project does not transfer its hosting away from Amo or require you to export the project or open your own Cloudflare hosting account. The temporary Amo address and every connected custom domain share the same 30-day hosting period, measured from the project’s first successful publication. Connecting, changing or reconnecting a domain does not restart or extend that period. At expiry, the project stops being served through all associated addresses.

Unpublishing stops new public delivery. Retained hosted versions remain private and may be explicitly restored before the original hosting deadline, making the selected version public again. At or after that deadline, Amo stops new public delivery and rejects publication or restoration of that site. There is no additional recovery period after hosting expiry. Files already delivered or downloaded cannot be recalled.

At the hosting deadline, hosted files, retained versions and unfinished staged content become eligible for automatic deletion. Public access expires independently of physical deletion. Cleanup runs in bounded batches, and failed cleanup is retried. Physical deletion may take longer because of queued work, service interruptions or delayed uploads. Amo does not promise instantaneous physical deletion.

Necessary ownership, security, reservation, audit and abuse-prevention records may remain. Third-party logs follow their own retention rules.

Browser-saved projects, downloaded files and independently hosted copies are unaffected by expiry or removal of the Amo-hosted copy. Keep your own backups. Amo does not promise unlimited storage, traffic, availability or permanent hosting. Existing admission and capacity limits still apply to new sites.

10.6 Independent hosting and domains

You may download supported website files and deploy them through a hosting provider you control, including your own Cloudflare account where its free offering supports the project. Deployment is your responsibility; Amo Build does not currently provide one-click deployment to your external hosting account.

Provider eligibility, terms, limits, domain renewals and any resulting charges are governed by your agreement with that provider. A free offering is not a guarantee of permanently free hosting.

Exporting and deploying files to your own hosting account is different from connecting a domain to a site still hosted by Amo. Changing a domain does not itself transfer hosting responsibility. Exporting or independently deploying a project does not automatically remove an existing Amo-hosted copy; use the available unpublish controls if you want it taken offline.

10.7 Project rights and responsible use

You retain your rights in your own inputs and materials and must have permission to submit and publish them. You give Amo only the permission needed to process those materials, display and host them as you request, and operate and protect the service. This is not a permission to resell your materials or use them for advertising or AI training.

You may use, deliver to clients or sell generated websites and tools, subject to AI-provider terms and any applicable third-party rights or licences. Creating a project with Amo Build does not itself prohibit those uses. This does not permit prohibited resale or redistribution of Amo’s prompt library. Amo does not guarantee that AI output is unique, copyrightable, exclusively yours or free from third-party restrictions.

You are responsible for reviewing generated code, calculations, content, security, accessibility and suitability before real-world use. Automated or manual project checks are not certification or a guarantee of correctness. The confidentiality and permission requirements in Section 5 also apply to Build submissions.

Do not use Amo Build or its hosting for phishing, malware, impersonation, unlawful or infringing content, publication of others’ private information without appropriate permission, or attempts to evade resource limits. Amo may proportionately restrict abusive use or suspend affected hosting to protect the service. This does not remove Amo’s own responsibilities or any rights or remedies that applicable law does not allow to be excluded.

Amo.ng is free for everyone to use. You can copy prompts, adapt them, and run them in your preferred AI tools. You cannot harvest the library and sell, clone, republish, or redistribute it as your own product.