# Data Use · Olympus

Source: https://getolympus.ai/data-use

# Data Use

Last Revised September 26, 2026

Table of contents

-   [How AI requests work](#1-how-ai-requests-work)
-   [Model training](#2-model-training)
-   [Providers and retention](#3-model-providers-and-retention)
-   [Connected account data](#4-connected-account-data)
-   [Deleting your data](#5-deleting-your-data)
-   [Questions and agreements](#6-questions-and-agreements)

## 1\. How AI requests work

When you ask an agent to plan, write, research, or build, Olympus sends your request and the context it needs (such as your brand guide, the relevant campaign, or selected CRM fields) to an AI model provider. The model returns a result, and Olympus stores it in your workspace.

Review the information you include in a request and the permissions you grant to connected services. Do not include information you are not authorized to share, including Protected Health Information.

## 2\. Model training

Etho’s customer agreement states that identifiable customer data is not used to train a model for a competitor. That is a specific contractual restriction, not a promise that every provider processes every request without retention or model training. Provider use is governed by the applicable provider terms and agreements.

## 3\. Model providers and retention

AI processing depends on the feature, model, provider, account configuration, and applicable provider contract. Requests may include prompts, selected files, brand context, images, campaign details, or authorized CRM fields. Provider retention, abuse monitoring, and permitted human access can differ from retention of records in Olympus. A provider’s company country is not a promise about where data is processed. Discuss specific requirements with Etho before submitting sensitive information.

### Provider-specific requirements.

No universal zero-retention, no-human-access, or no-training commitment is made by listing a provider. Confirm the feature, provider contract, permitted data uses, and relevant settings before relying on a specific restriction. Access to private workspace content remains subject to the confidentiality and data-handling commitments in your customer agreement.

## 4\. Connected account data

Connecting a CRM, ad platform, messaging service, or another account authorizes the data exchange needed for enabled features. This can include integration tokens, contacts, campaign information, messages, consent records, and performance data. Give only the permissions you are entitled to grant. Imports do not establish messaging consent. Disconnecting an integration does not retract messages, published content, or data already received by another service.

## 5\. Deleting your data

After your subscription ends, the customer agreement allows seven days to export data. Etho may keep an archived copy for up to thirty days for recovery, then deletes or de-identifies it, apart from routine backups and legally required records. Data already sent to a connected service is also subject to that service’s terms.

## 6\. Questions and agreements

Before using Olympus for data subject to special contractual or regional requirements, agree the applicable processing terms with Etho. A Privacy page or provider list is not a substitute for an applicable data-processing agreement. Processing roles, international transfers, security schedules, and provider-specific commitments must reflect the service and contracts actually used. Contact us to discuss your requirements:

[hello@etho.net](mailto:hello@etho.net)