Data Handling & Privacy

This guide explains how SeeAPI handles content submitted through the API, how stored files and request records are retained, and how to request deletion. It covers SeeAPI’s handling of API data and complements our Privacy Policy and Terms of Service.

Your Content & AI Training

SeeAPI does not use your API inputs or outputs to train AI models.

We process your content to fulfill the requests you submit and return results. We also retain request records to support your usage history and help investigate service issues.

Data We Process

Depending on the service you use, an API request may involve:

Input content: prompts, images, videos, audio, and other material submitted for processing.

Generated outputs: content returned in response to your request.

Task information: information about the request, its status, and its result.

Moderation results: information produced by applicable content checks.

Request records and logs: records associated with processing and supporting API requests.

These categories serve different purposes. A task record, a generated file, and a moderation result are separate types of data, even when they relate to the same request.

Storage & Retention

SeeAPI retains stored data according to the following retention periods:

This allows you to return to stored results and review your API activity. Under this default policy, data does not enter an automatic expiry countdown when a task is submitted or completed.

We recommend keeping your own copies of files that are important to your application. If we change our retention policy, we will notify affected users in advance so they have time to back up their data.

The table describes data stored by SeeAPI. It does not set the retention period for files hosted on your own systems or establish a retention commitment for other service providers.

Files, URLs & Request Logs

A file’s availability and the lifetime of a URL used to access it are different things.

For example, an input URL may expire on your storage service while a copy already retrieved for processing remains elsewhere. Expiring or revoking the original URL should therefore not be treated as a request to delete data previously submitted for processing.

Similarly, request history and media storage are distinct. Information about a task can remain relevant even when no output file was generated.

This guide does not specify a field-by-field inventory of diagnostic logs. Applications with requirements concerning source URLs, signed URL parameters, or image content in logs should have those requirements reviewed for the relevant workflow.

Requesting Data Deletion

You can request deletion of files or request records through our support team. A request may relate to an individual task or a specified set of data.

To help us identify the relevant records, include:

The email address associated with your SeeAPI account.

The relevant task IDs, if available.

A brief description of what you would like removed, such as input files, generated outputs, or request records.

Our team will review the request and explain the applicable scope and next steps. Where a request concerns backups or copies held by another service provider, those should be included in the review rather than assumed to be covered by the removal of a task record.

You do not need to include API keys, passwords, or private media files in your initial request.

Service Providers

We work with service providers, including those supporting the model you choose, to process your API requests.

Model-specific requirements—such as processing locations, provider retention, or contractual data-processing arrangements—need to be considered for the service you intend to use. This guide describes SeeAPI’s practices and does not replace a model provider’s applicable terms.

Policy Updates & Questions

Read this guide alongside the SeeAPI Privacy Policy and Terms of Service.

For any other questions or help with a data request, please contact [email protected].