Export & Data Portability Policy

This Policy applies to data and content that Asiyst makes available for export through supported functionality.

It may apply to:

• Account information.
• Project information.
• Workspace information.
• Configuration data.
• AI assistant configuration.
• Avatar configuration.
• Knowledge-source configuration.
• Uploaded content where export is supported.
• Conversations where export is supported.
• API-related information.
• Usage information where export is supported.
• Other customer-controlled information made available through the Services.

Not every category of information is necessarily exportable.

Data portability means providing supported customer data in a format that allows the customer to retrieve, store, or reuse that information outside Asiyst.

Where technically supported, Asiyst may provide data through:

• Direct downloads.
• Structured files.
• Export packages.
• API responses.
• Dashboard export functionality.
• Other supported mechanisms.

The format available may depend on the type of data being exported.

Customers generally retain rights they otherwise have in their own content and data, subject to applicable agreements and third-party rights.

Exporting data does not transfer ownership of Asiyst software, proprietary technology, documentation, APIs, SDKs, models, or other Asiyst intellectual property.

Where self-service export functionality is available, customers may initiate an export through the relevant Asiyst interface.

Where self-service export is not available for a particular data category, customers may contact Asiyst through an appropriate support channel.

Export requests may require account verification.

Depending on available functionality, account exports may include information such as:

• Account profile information.
• Account settings.
• Organization information.
• Workspace information.
• Project associations.
• Configuration information.

Certain authentication, security, or internal system information may not be included.

Where supported, customers may export project-related information such as:

• Project configuration.
• Project settings.
• Assistant configuration.
• Integration configuration.
• Knowledge-source configuration.
• Domain configuration.
• API-related configuration.
• Other project metadata.

Export availability depends on the specific project functionality.

For organizations or workspaces, export availability may depend on the user's permissions.

Workspace administrators or other authorized users may be required to initiate certain exports.

Asiyst may restrict export requests where the requesting user does not have appropriate authorization.

Where conversation export is supported, customers may be able to retrieve applicable conversation information.

An export may include available:

• Messages.
• Timestamps.
• Conversation identifiers.
• Relevant metadata.

Conversation exports may not include every internal processing record, model trace, system instruction, security record, or internal diagnostic record.

Where supported, customers may export configuration associated with an AI assistant.

This may include:

• Assistant name.
• Instructions.
• Configuration settings.
• Supported behavior settings.
• Knowledge-source references.
• Appearance settings.
• Integration settings.

Internal Asiyst system configuration may not be included.

Where supported, export functionality may include customer-controlled avatar configuration or associated assets.

Export availability may depend on:

• The origin of the avatar.
• Applicable licenses.
• Third-party rights.
• File format.
• Storage configuration.
• Product functionality.

Third-party assets may remain subject to their applicable licenses and restrictions.

Customers may be able to export information associated with connected knowledge sources where technically supported.

This may include:

• Source metadata.
• Source identifiers.
• Configuration.
• Imported documents where supported.
• Connection settings.

An export may not reproduce an external source in its entirety.

Where supported, customers may retrieve files they uploaded to Asiyst.

Availability may depend on:

• File type.
• Storage configuration.
• Account status.
• Retention requirements.
• Third-party rights.
• Technical limitations.

Files subject to legal restrictions, security controls, or third-party licensing limitations may not be available for export.

Where supported, developers may retrieve certain data through Asiyst APIs.

API access may be subject to:

• Authentication requirements.
• Rate limits.
• API versioning.
• Usage limits.
• Permissions.
• Available endpoints.
• Applicable API Terms.

Not all internal Asiyst data is accessible through the API.

For security reasons, Asiyst may not provide previously displayed secrets or credentials in export packages.

For example, a previously generated secret may be displayed only at the time it is created.

Customers may need to revoke and generate a new credential instead of exporting an existing secret.

Third-party API keys, OAuth tokens, passwords, payment credentials, and other sensitive authentication information may be excluded from exports.

This restriction may apply even where configuration referencing the third-party service is exportable.

Customers may need to reconnect third-party services after migrating to another platform.

Payment information may be subject to separate processing and retention requirements.

Exports may include transaction or billing information where supported, but may not include:

• Full payment-card numbers.
• Security codes.
• Authentication secrets.
• Other sensitive payment credentials.

Payment information handled by payment processors may be subject to the processor's own policies.

Where supported, Asiyst may provide access to certain usage information.

Usage data may include information such as:

• API requests.
• Credit usage.
• Token usage.
• Project activity.
• Service activity.
• Usage timestamps.

Internal operational metrics, security information, proprietary calculations, or data concerning other users may not be included.

Certain analytics information may be exportable depending on the relevant product functionality.

Analytics exports may contain aggregated or structured information rather than raw internal event streams.

Asiyst may restrict export of information that contains:

• Other users' personal information.
• Security-sensitive information.
• Internal system information.
• Confidential business information.
• Information subject to third-party restrictions.

Export formats may vary by data type.

Examples may include:

• JSON.
• CSV.
• Plain text.
• Downloadable files.
• Structured archives.
• Other commonly supported formats.

Asiyst may determine the appropriate format based on the nature of the information and the available technical functionality.

Where multiple categories of data are exported together, Asiyst may provide an export package containing multiple files or directories.

The package may contain:

• Data files.
• Metadata.
• Configuration files.
• File attachments.
• Documentation explaining the export structure.

The exact contents will depend on the applicable export functionality.

Some exports may be generated immediately.

Larger or more complex exports may require additional processing time.

Processing time may depend on:

• Data volume.
• Number of files.
• Storage requirements.
• System capacity.
• Export format.
• Security verification.
• Technical processing requirements.

Asiyst may require verification before providing an export.

Verification may include:

• Account authentication.
• Email verification.
• Administrator authorization.
• Identity verification where appropriate.
• Confirmation through an authorized account.

These measures are intended to reduce unauthorized access to customer data.

For accounts containing multiple users, export rights may depend on role and permissions.

An administrator may be able to request information that an individual member cannot access.

Asiyst may restrict exports containing information belonging to other users where the requesting user lacks appropriate authorization.

You must not use export functionality to obtain another person's information without appropriate authorization.

Where an export contains information relating to multiple users, applicable privacy and access restrictions continue to apply.

Customer exports may contain personal information concerning