What we never do
The hard boundaries on data access, sharing, payment data, AI access and model training that you can quote in a vendor review.
- Read or transmit your source code. ARCY never sees your repository, and there is nothing to install into your build.
- Hold a standing credential to your Product, or sign in to it.
- Take an action inside your Product that you did not author as a flow step.
- Share session data across organizations.
- Give an ARCY team member access to your production session data without a support request you opened.
- Sell or share your data with third parties.
- Store payment or credential data. A card number, a bank account number (IBAN) or an API key is refused on every path in and never logged, and no attribute may be named for a card, a security code, a PIN, a password or an IBAN (Attributes).
- Send an attribute value to an AI model once its AI access has been off for a minute. A Person summary written before you switched it off keeps its text until the next one is written. Your team, your flows and your filters keep using the value.
- Use your conversation data, session data or any other customer data to train our own AI models. The model provider does not train on it either; see How AI request content is handled.