> ## Documentation Index
> Fetch the complete documentation index at: https://www.macaly.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Using AI responsibly

> What Macaly discloses about AI, and what stays with you when you publish

Everything you create in Macaly is built with AI. Some laws, including the EU AI Act, require people to be told when they are interacting with an AI system or looking at AI-generated content. For the projects you publish, Macaly handles part of this for you and part of it stays your responsibility.

<Note>
  This page describes what Macaly does for you and where your responsibility sits. It is not legal advice. Whether disclosing AI interactions or AI content applies to you depends on applicable law and how you use your project. If you are unsure, talk to a legal advisor.
</Note>

## What's built in

### On published projects

Projects you publish carry two markers:

* **A machine-readable tag.** Macaly adds `<meta name="ai-generated" content="true">` to the site's head when you publish.
* **A visible badge.** Published projects show a **Made with AI in Macaly** badge. On the Free plan this badge cannot be hidden. On Pro and above you can hide it in **Settings → General**.

### On generated media

Images, audio, and video produced through Macaly carry whatever provenance markings the underlying provider applies, such as SynthID or C2PA. Macaly does not strip these markings.

<Warning>
  Do not intentionally remove or circumvent these markers where doing so would break the law that applies to you, see section 3.13 of the [Terms of Service](https://www.macaly.com/terms-of-service).
</Warning>

## What's in your hands

Macaly's disclosures cover Macaly. They say nothing about what your published project does, or what you do with its output. Those obligations stay with you.

### AI features you add to your project

If your project includes something like a chatbot, content generation, AI summaries, or anything else powered by AI, your end users need to know they are communicating with AI. Macaly does not add that notice for you, because it is part of your application rather than the platform itself.

You can ask the agent to add it, for example as a short note above the chat window.

### Content you publish

The **Made with AI in Macaly** badge discloses how the site was built. It does not disclose anything about the content on it. If you publish text, images, or media that were generated by AI and your context calls for a disclosure, adding it is up to you.

### Synthetic media

Content that convincingly depicts real people, places, or events but is generated or manipulated by AI carries stricter obligations under the EU AI Act. If your project produces or publishes this kind of media, look into which rules apply to you before you ship.

## Practical examples

<AccordionGroup>
  <Accordion title="I published a marketing site with AI-generated copy">
    The badge on your published site shows the site was built with AI in Macaly. Whether you also need to disclose that the copy itself is AI-generated depends on applicable law and the specific use case.
  </Accordion>

  <Accordion title="I built a customer support chatbot into my app">
    Your end users need to know they are talking to AI rather than a person. Ask the agent to add a visible notice at the start of the conversation or above the chat window. Macaly's own in-app notice does not carry over to your project.
  </Accordion>

  <Accordion title="I'm on Pro and I hid the Macaly badge">
    That is fine. What changes is that your site no longer carries a visible AI disclosure, so if your use case needs one, showing it is now entirely up to you.
  </Accordion>

  <Accordion title="My app generates images of people using AI">
    Images generated through Macaly carry whatever provenance markings the provider applies. If the images could pass for real people or real events, additional transparency obligations may apply to you.
  </Accordion>

  <Accordion title="I'm building an internal tool that nobody outside my company uses">
    Transparency obligations still apply to the people using the tool, even when they are your own colleagues.
  </Accordion>
</AccordionGroup>

## Reviewing your project with the agent

The agent can help you find the places where a disclosure might belong. Ask it in plain language:

```
Go through my project and list every feature that uses AI,
including anything that talks to an AI model. For each one,
tell me whether an end user would be able to tell it's AI.
```

```
Add a short notice above the chat window telling users they
are talking to an AI assistant, and make it match the rest
of the site's styling.
```

See [Building secure apps](/docs/en/security/building-secure-apps) for more on working with the agent.

## Related documents

* [AI Transparency Notice](https://www.macaly.com/ai-transparency-notice)
* [Terms of Service](https://www.macaly.com/terms-of-service)
* [Privacy Policy](https://www.macaly.com/privacy-policy)