Data Retention & Privacy

This guide explains the API's current data flows and delivery options so you can choose controls appropriate to your application.

Request History and Output Availability

• Request history: The API records the request timestamp, status, model, parameters, input URLs, and output references.
• Base64 in request records: Full base64 image data is used only to process and deliver the request. Request history and stored prediction metadata contain <base64> placeholders instead of the full image strings.
• CDN-delivered outputs: Standard API outputs are scheduled for expiry after three days.
• Base64-delivered outputs: With return_base64: true, the status endpoint returns the output for up to 60 minutes instead of the standard three-day window.

Data Retention Timeline and Purpose

Output availability depends on your chosen delivery method:

CDN Delivery (Default)

API outputs are scheduled for deletion after three days. Download them to your own storage if you need longer access.

Base64 Delivery (return_base64: true)

Base64 outputs are available through the status endpoint for 60 minutes after completion. After this availability limit:

• The status endpoint will return "<base64>_expired" instead of the actual base64 data

Your request history ↗ remains visible in the web app interface for monitoring and debugging purposes, showing:

• Request parameters and metadata
• Submitted URLs
• <base64> placeholders for base64 inputs
• Status and error information

Privacy-Enhanced Options

FASHN provides several API parameters to enhance privacy for data-sensitive applications:

Best Practices for Data-Sensitive Applications

Choose the privacy strategy that best fits your application's requirements:

URL Expiry Strategy (Recommended)

Use short-lived signed URLs to limit how long images can be accessed from your origin. Submitted URLs appear in request history.

Implementation:

• Configure URL expiry: Set your image hosting to make URLs inaccessible after your required timeframe
• Use signed URLs: Employ temporary, signed URLs that automatically expire

curl -X POST https://api.fashn.ai/v1/run \
     -H "Content-Type: application/json" \
     -H "Authorization: Bearer YOUR_API_KEY_HERE" \
     -d '{
           "model_name": "tryon-max",
           "inputs": {
             "model_image": "https://your-cdn.com/signed-url?expires=1735689600",
             "product_image": "https://your-cdn.com/signed-url?expires=1735689600",
             "return_base64": true
           }
         }'

Benefit: Your source URL becomes inaccessible after its expiry.

Base64 Strategy (Privacy-Focused)

For applications that prefer not to place image URLs or full image data in request history. Full base64 data is used only to process and deliver the request. Request history and stored prediction metadata contain <base64> placeholders, and base64 outputs are available for up to 60 minutes instead of the standard three-day window.

curl -X POST https://api.fashn.ai/v1/run \
     -H "Content-Type: application/json" \
     -H "Authorization: Bearer YOUR_API_KEY_HERE" \
     -d '{
           "model_name": "tryon-max",
           "inputs": {
             "model_image": "data:image/jpeg;base64,/9j/4AAQSkZJRgABAQEAYABgAAD...",
             "product_image": "data:image/jpeg;base64,/9j/4AAQSkZJRgABAQEAYABgAAD...",
             "return_base64": true,
             "output_format": "png"
           }
         }'

Privacy benefit: Full base64 image strings do not appear in request history or stored prediction metadata. Outputs are available for up to 60 minutes instead of the standard three-day window.

Hybrid Approach

For applications with mixed privacy requirements:

curl -X POST https://api.fashn.ai/v1/run \
     -H "Content-Type: application/json" \
     -H "Authorization: Bearer YOUR_API_KEY_HERE" \
     -d '{
           "model_name": "tryon-max",
           "inputs": {
             "model_image": "data:image/jpeg;base64,/9j/4AAQSkZJRgABAQEAYABgAAD...",
             "product_image": "https://your-cdn.com/catalog-image.jpg",
             "return_base64": true
           }
         }'

Use standard URLs for non-sensitive images (product catalogs) and base64 for sensitive images (customer photos).