AI processing disclosure

ARCY AI uses a third-party AI model to power Chat, and to run the Flows an operator authors inside a product. If you operate in a jurisdiction with automated-decision-making disclosure requirements (GDPR Article 22 and similar), your privacy policy likely needs a specific disclosure for this, distinct from the general data-collection paragraph.

What to paste

Automated Processing and AI Features

[Your Product Name] uses an AI assistant, powered by ARCY AI, that may:

- Answer your questions using context about your account and how you use
  [Your Product Name] ("Chat")
- Carry out a pre-authored sequence of steps inside [Your Product Name] on
  your behalf, such as navigating to a page, clicking a button, or filling in
  a form, when you ask for help with a task we've built a guided flow for

Every step the assistant runs was authored by our own team in advance and points at a
specific element of [Your Product Name]; the assistant does not decide on its own what
actions to take or invent a path through the product it hasn't been given.

This feature is powered by a third-party AI model. Neither [Your Company Name] nor ARCY AI
uses your conversation content, session data, or behavioral data to train AI models, ours or
the underlying model provider's. This feature is not used to make legal or similarly
significant decisions about you (for example, decisions about eligibility, pricing, or
account status) without human review.

You can decline this feature at any time by [describe your opt-out mechanism, e.g. "closing
the assistant panel" or "disabling it in account settings"].

Notes on filling this in

• The claim "not used to make legal or similarly significant decisions about you" is only accurate if that's actually true of the Flows you've authored. If a Flow in your product can take an action with real consequence (for example, submitting a payment or deleting data), get specific legal advice about whether GDPR Article 22 applies, rather than relying on this paragraph as-is.
• List only the Flows you've actually published for your users, not every capability ARCY offers in general. What a user can trigger is exactly what you built and published for that environment; see Flows for how a Flow is authored, published, and can be unpublished at any time.
• The model provider retains no request content, and ARCY's own call log records cost rather than content. Conversations themselves are stored so you can review them, and can be turned off in your workspace settings. See How AI request content is handled before referencing any of this in your own disclosure.