Shared Template/Community Guidelines

These Guidelines apply to Coul canvases and templates submitted, linked, listed, previewed, duplicated, saved, liked, recommended, moderated, or republished through personal accounts and workspaces. They supplement the Terms, User Content & AI Output Policy, Acceptable Use Policy, Copyright/DMCA Policy, and Privacy Policy.

A template can contain node structure, configuration, instructions, prompts, labels, example text, references, and other workflow logic. It does not automatically carry a license to private data, connected accounts, credentials, media, competitor content, fonts, music, stock assets, voices, likenesses, brands, client material, or third-party services.

The standard Coul Community Template License below controls the user-to-user permission for an exact public or unlisted source version when both publisher and duplicator receive and accept that version. A separate asset or law can impose additional restrictions.

Private templates remain drafts accessible only within the authorized personal or workspace context. They are not processed through the public-share privacy-stripping transformation and should not be treated as safe for external disclosure merely because their visibility label says private.

Unlisted templates are omitted from the public library, but an authenticated Coul user who obtains the template identifier or link and has an active account or workspace can read and duplicate an approved version. Unlisted is not private, access-controlled to a named list, password-protected, expiring, or currently revocable through a link-reset control.

Public templates become discoverable in the community library only after approval. Public and unlisted submissions are versioned, privacy-transformed, and placed in pending review; users cannot lawfully duplicate the shared version until it is approved and the applicable license is presented and accepted.

A personal account can submit an eligible template. A workspace submission requires an owner role, and duplication into a workspace requires at least the product permission assigned to an editor. These are technical permissions; they do not prove authorship, client authority, employment ownership, or rights in every element.

By submitting a public or unlisted version, the publisher confirms that the properly identified account or workspace customer may share that exact version and grant the Community Template License, and that all required co-author, client, talent, employee, contractor, platform, asset, privacy, publicity, trademark, copyright, and confidentiality permissions are in place.

Do not publish another client's workflow, confidential method, prompt library, account data, licensed asset, or output merely because your workspace role permits it. A workspace should document who may publish, approve license terms, receive attribution, respond to complaints, and manage copies after a member leaves.

For public and unlisted submission, Coul attempts to remove or replace specified secret, credential, account, internal identifier, private URL, generated-output, media-asset, live competitor, manual-note, private-marked, storage, and provider fields and remaps internal identifiers. Community sharing must remain disabled until Coul gives the publisher a preview of the exact transformed graph before submission and records confirmation of that version.

Sanitization is heuristic. It can miss a secret stored under an ordinary key, personal or client data embedded in text, a public HTTPS URL that was not meant for community use, identifying prompts, sensitive examples, or an asset whose URL is public but license is restricted. The publisher remains responsible for inspecting the complete shared result. This privacy safeguard is not rights clearance.

The current moderation queue exposes metadata, preview URLs, graph summary, and a privacy manifest but not the full safe representation of nodes and edges. Approval therefore is not a representation that Coul inspected every element or verified privacy, security, rights, quality, compatibility, legality, or performance.

Coul Community Template License v1.0 — July 18, 2026. The publisher accepts this license when submitting an exact public or unlisted template version, and the duplicator accepts it when duplicating that version. Coul must log each assent with the user, account or workspace, template, source version, license version, policy version, and timestamp. A later license or Guidelines update does not retroactively replace an accepted license for an existing copy without fresh, informed assent.

When a user lawfully duplicates an available approved public or unlisted source version after accepting this license, the publisher grants that duplicator a non-exclusive, worldwide, royalty-free, perpetual and, to the extent permitted by law, irrevocable license to reproduce that template within Coul; modify and adapt it; combine it with material the duplicator is authorized to use; run it to create outputs; and use the resulting outputs for personal or commercial purposes.

The license attaches only to the exact source template version duplicated. A later publisher version is separately licensed and does not automatically update an existing canvas. The license is limited by the publisher's actual rights, the exclusions below, the Acceptable Use Policy, applicable law, destination rules, and every underlying asset license.

Authorized workspace members, employees, contractors, and operational service providers may operate the licensed copy only on the duplicator's behalf, within the duplicator's Coul context, and without independent template rights. Clients and connected platforms may receive and use lawful outputs as needed for the output's intended purpose, but receive no template right unless they separately duplicate an eligible version and accept the applicable license.

Subject to the conditions below, the publisher also grants a narrow right to republish a meaningfully modified derivative template within Coul only when that feature is enabled and the source template, source version, license version, and required attribution propagate. The duplicator may not sell, rent, sublicense, mirror, or redistribute the original or substantially unchanged template as a standalone product or library substitute.

A publisher can report a material breach of the Community Template License, and Coul can enforce the license and incorporated policies. Where safe and reasonable, the duplicator should receive the specific breach, affected source version, and a reasonable opportunity to cure before termination. Coul may immediately suspend access or use for infringement, privacy or confidentiality exposure, illegality, urgent safety risk, court or platform order, deliberate evasion, or another harm that cannot safely await cure.

After an uncured material breach or valid immediate ground, termination stops future template access, operation, duplication, modification, generation from the licensed copy, distribution, and derivative republication to the extent required by the decision. The duplicator must delete or isolate the affected copy when directed and must not evade the restriction through an export, replacement account, renamed derivative, or workspace transfer.

Lawful outputs completed before termination can remain usable unless the output itself infringes, violates law or policy, contains restricted source material, or an underlying right, platform rule, court order, or valid remedy requires restriction. Termination does not erase non-waivable statutory, author, moral, consumer, privacy, worker, or platform rights and does not let a publisher revoke an accepted license merely for convenience.

You may change licensed node structure, settings, instructions, prompts, labels, and authorized examples and may use lawful output for client, brand, campaign, educational, or other commercial work. You remain responsible for output rights, claims, disclosures, connected services, usage fees, approvals, and destination-platform terms.

A duplicated canvas becomes a separate private canvas tied to the source template and source version. The narrow derivative-republication right above may be exercised only when Coul expressly enables that action, the derivative is meaningfully modified, the upstream license and source-version provenance remain valid, and required attribution and notices propagate.

Until Coul reliably carries the source/license chain into a newly published derivative, duplicated canvases must not be republished as community templates. Cosmetic renaming, reordered nodes, removed credit, or a small value change does not erase upstream obligations or make the source the duplicator's original work.

Coul must preserve an internal record of the source title, publisher or workspace credit, source template identifier and version, license version, duplication time, duplicating account or workspace, and material derivative relationship. That record supports attribution, updates, rights cases, and surviving-copy analysis and must be retained with appropriate privacy limits.

Publisher credit and upstream source/version attribution must remain when the template itself or a derivative community template is shared. A final external post or output does not need to credit the template publisher unless the displayed license, an incorporated asset license, moral-right law, client agreement, or another applicable obligation requires it.

Do not remove required credit, provenance, copyright or trademark notice, asset attribution, sponsor disclosure, rights-management information, or synthetic-media label. Do not imply that the publisher, upstream creator, client, Coul, or a destination platform endorses your derivative or output.

The Community Template License grants only rights the publisher actually holds and does not grant rights to third-party music, video, images, stock, fonts, code, trademarks, confidential information, names, likenesses, voices, platform-only assets, client material, connected accounts, credentials, private data, live source records, or competitor expression.

Use competitor references only for factual metrics, themes, topics, general methods, unprotected formats, and original ideation. Do not publish a template that copies a protected script, caption, audiovisual sequence, music, voice, likeness, branding, or distinctive expression; routes competitor content into virality scoring or editing; or implies affiliation.

Privacy stripping and template approval do not verify a third-party license. If an asset requires attribution, share-alike, source disclosure, royalties, noncommercial use, a platform restriction, or no derivatives, the publisher and duplicator must preserve and comply with it or remove the asset.

Do not publish, duplicate, recommend, or use a template that contains, requests, facilitates, conceals, or is designed to produce conduct prohibited by the Acceptable Use Policy. This includes the following illustrative categories.

• Copyright, trademark, publicity, privacy, confidentiality, license, database, or platform-rights infringement; false authorship; removed provenance; or close copying of competitor expression.

• Leaked credentials, tokens, connected accounts, private or restricted URLs, client secrets, personal data, confidential workflows, data-exfiltration prompts, or deliberate evasion of privacy stripping.

• Deceptive impersonation or synthetic media, false affiliation, harassment, hate, threats, doxxing, non-consensual intimate imagery, sexual exploitation, or child sexual abuse material.

• Scams, phishing, fraud, malware, fake engagement, account compromise, platform-policy circumvention, unauthorized scraping, or unlawful personal-data enrichment.

• Illegal or materially deceptive advertising, regulated goods, medical or financial claims, paid political advertising, automated election persuasion, dangerous instructions, or other unlawful content in the relevant territory.

Public templates can be listed, searched, saved, liked, ranked, featured, or recommended using available metadata and product signals. Unlisted templates are excluded from ordinary discovery but remain accessible through their identifiers or links as described above.

Current backend endpoints can create at most one persistent like and one persistent save per user for a template. Coul has not verified an unlike, unsave, saved-template retrieval, ratings, comments, or production discovery interface. The UI must not claim those actions or states are available until their end-to-end behavior is implemented and tested.

Visible authors, download counts, likes, popularity, search ordering, or discovery examples can be static or illustrative until connected to verified production data and must be labeled accordingly.

A metric or recommendation can be incomplete, manipulated, stale, or based on limited signals and does not establish ownership, quality, safety, popularity, compatibility, endorsement, or expected results. Before launch, Coul must explain the main recommender parameters and provide any controls required by applicable law.

Ordinary policy reports, illegal-content notices, copyright/DMCA notices and counter-notices, privacy or public-data removal, trademark, impersonation or likeness claims, confidential-material complaints, and urgent safety reports have different elements and remedies. Coul should accept a mixed complaint once and route each part without forcing repetition.

Before launch, any person or entity must be able to use an accessible accountless electronic route where law requires it, identify the exact template/version/link and reason, provide minimum evidence and contact information, receive an acknowledgment and case identifier, add evidence, narrow or withdraw a report, and receive an outcome.

Urgent routes must cover child exploitation, non-consensual intimate imagery, imminent threats, trafficking, malware, impersonation, and election interference. Do not attach illegal imagery or expose unrelated private workspace content; provide the minimum locator through the secure channel.

One authenticated report currently changes an approved template to reported and removes it from normal listing and duplication. That automatic action is a temporary containment measure—not a finding that the report is true or the publisher violated a rule. The product must continue accepting relevant evidence even after quarantine.

Depending on risk and evidence, Coul may pause review; quarantine listing and link access; disable duplication, preview, embedding, retrieval, search, recommendation, export, scheduling, retry, or publishing; hide or reject a source version; remove affected elements; restore it; restrict a member or workspace; or preserve evidence and make a legally required report.

Before launch, moderators must be able to inspect the complete safe review representation rather than only summary metadata, apply a specific rule and version, record evidence and reasoning, distinguish temporary from final status, notify affected parties, and scope action to the relevant source/version and downstream copies.

Except where law or safety limits detail, Coul should tell the publisher or workspace the specific rule, affected version, material facts, action, duration, whether automation contributed, restoration conditions, and free appeal route. Reporters should receive an outcome without unnecessary disclosure about the publisher.

An appeal must receive a fresh evaluation of evidence, license, context, source version, independent changes, rights, and policy by a sufficiently independent human with authority to reverse and restore. The reviewer must not merely rubber-stamp the first human decision or automated signal.

Coul may act against repeated manifestly abusive reporting or appeals after considering intent, pattern, accuracy, withdrawal, and harm. One unsuccessful good-faith report or appeal is not abuse. Reporter identity is protected except when disclosure is legally required, and restoration must update listing, links, indexes, embeddings, and other affected systems.

Unpublishing or hiding a source version should stop future listing, link access, and duplication after the control takes effect. It does not automatically revoke the license for copies lawfully made while that exact version was available, recall exports or outputs, or update duplicated canvases.

The current product does not expose a reliable publisher-facing unpublish, link-revocation, or approved-version replacement control. Republishing a later canvas version can create a separate candidate while an earlier listing remains active. Coul must implement and explain these controls before promising immediate withdrawal or replacement.

A new source version is a separate version requiring review and license acceptance. A security, privacy, rights, legal, platform, or safety issue may require Coul to contain an old version and affected copies even though ordinary unpublishing would otherwise leave lawful copies licensed.

Account or workspace closure archives and redacts owned source templates and can empty source versions, while independently owned duplicate canvases can remain. Closing the publisher's account does not automatically invalidate a Community Template License lawfully granted before closure.

Existing-copy licenses are perpetual and irrevocable to the extent permitted by law, except for the duplicator's uncured material breach and subject to valid copyright, privacy, safety, illegality, court-order, source-license, or platform restrictions. A surviving license never expands rights the publisher lacked.

Coul must preserve only the minimum pseudonymous publisher credit, source/version, license acceptance, duplication, rights-hold, and enforcement evidence needed to support lawful copies and complaints while deleting or redacting personal data not needed for those purposes. Current cleanup can degrade provenance and must be corrected before sharing launches.

A valid rights complaint can require immediate containment of the identified source, preview, search record, embedding, schedule, and exact copied material. Coul must trace source-template and source-version relationships and assess whether each downstream canvas retains complained-of expression, private data, illegal content, or a restricted asset.

A complaint does not prove that every copy infringes. Independently modified material, unprotected ideas, user replacements, or a valid license or exception can change the outcome. Coul should remove or restrict affected elements and copies proportionately rather than assuming universal deletion or universal survival.

A rights hold must be checked before duplication, export, embedding, retrieval, scheduling, retry, and publication. A statutory copyright counter-notice can restore an eligible Coul location but does not automatically republish externally, recreate a schedule, reverse an independent AUP or privacy restriction, or recall third-party copies.

A member's departure, demotion, or account deletion does not decide whether the workspace, client, employee, contractor, co-author, or talent owns the template or has approval rights. Coul's roles control access, not private ownership allocation.

Workspace customers should maintain written ownership, licensing, attribution, confidentiality, client handoff, and publishing rules. Before closure or owner change, export appropriate records, transfer responsibility, resolve live links and schedules, and identify who can respond to claims.

Coul may preserve access and provenance evidence, quarantine disputed material, or require claimants to seek agreement or legal process. It does not adjudicate employment, agency, client, co-author, partnership, or accounting disputes beyond applying its product terms and valid legal orders.

Coul accounts and template publishing are intended for people at least 18 and the age of legal majority where they live. Signup does not yet collect an age attestation or record Terms, Guidelines, and license-version acceptance, so those controls are mandatory before community sharing launches.

Coul does not currently verify a template publisher's identity, authorship, credentials, brand affiliation, or client relationship. Do not describe an author, workspace, badge, or template as verified unless the specific verification and its limits are explained.

Do not impersonate a person or organization, publish another person's private workflow, falsely claim authorship, create a misleading endorsement, or use a child's identity or content without all required authority and safeguards. Report impersonation and child-safety concerns through the appropriate urgent route.

If Coul offers the template feature into the EU, it must determine whether the feature is a hosting service or online platform, its Member State of establishment or required legal representative, and whether a micro or small-enterprise or another exception applies. An exception cannot be assumed without documented headcount, turnover, group, and recipient calculations.

Potential baseline duties include clear moderation terms, an accountless notice-and-action route, acknowledgments, timely and objective decisions, statements of reasons, and transparency records. Additional online-platform duties can include a free complaint system, out-of-court redress information, trusted-flagger priority, misuse controls, recommender transparency, moderation reports, active-recipient reporting, and safeguards for minors.

An 18+ contract term does not resolve minor-safety risk when a younger person can access public pages or appear in a template. Coul must evaluate actual access, targeting, content, and risk and provide any locally required redress or regulator information.

Community sharing must not launch until Coul presents and logs the versioned Community Template License at publication and duplication; verifies the operator, address, monitored community/legal contact and any EU representative; and preserves real publisher/workspace attribution plus immutable source-version, derivative, license, and acceptance provenance.

Coul must add publisher preview of the exact stripped graph; moderator access to a complete safe representation; unpublish, link-revocation, version-replacement, and copy-status controls; derivative-license propagation; accountless reporting and urgent escalation; case IDs, notices, reasons, human appeals, restoration, continued evidence intake, and abuse safeguards.

Coul must connect quarantine and rights holds to listing, links, previews, search, recommendations, embeddings, duplicates, exports, schedules, retries, publishing, and backup restore; replace current provenance-destroying closure behavior; and add 18+ attestation plus stored Terms, Guidelines, and license-version acceptance. Until those controls are live, legal@coul.app is a proposed contact only and must not be represented as a monitored community case channel.