Data Retention & Privacy

This guide consolidates all information about FASHN's data retention policies and privacy features to help you build data-sensitive applications with confidence.

What FASHN Stores vs. What We Don't

What We Store

• Request metadata: Who sent the API request, what the inputs were (request body), and when the request was made (timestamp).
• Image URLs: The URLs you provide for model_image and garment_image are saved as part of the request body
• Base64 placeholders: For base64 inputs, we store <base64> in request history, not the actual string

What We Don't Store

• Actual images: Never stored on our servers, regardless of input method
• Base64 image data: The actual base64 strings are never retained
• Output images: Outputs returned through our CDN are automatically deleted after 72 hours (when using return_base64: true, outputs are never stored)

Data Retention Timeline and Purpose

Image outputs generated via the API are temporarily stored for up to 72 hours for the following purposes:

1. Dashboard Preview: To allow you to conveniently preview your API outputs through the API dashboard.
2. Data Transfer Window: To provide sufficient time for you to transfer the data to your own storage, or to support use cases that do not require long-term storage.
3. Support & Troubleshooting: To enable us to assist effectively in the event that issues are reported with the outputs.
4. Content Moderation & Abuse Prevention: To allow us to conduct content moderation, review policy compliance, and investigate potential misuse of the technology.

After 72 hours, image outputs are automatically deleted and are no longer accessible.

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

• Request parameters and metadata
• URLs (but images at those URLs may be expired/inaccessible)
• <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)

Most effective approach for balanced privacy and performance. While FASHN stores URLs in request history, this becomes privacy-neutral when URLs expire.

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-v1.6",
           "inputs": {
             "model_image": "https://your-cdn.com/signed-url?expires=1735689600",
             "garment_image": "https://your-cdn.com/signed-url?expires=1735689600",
             "return_base64": true
           }
         }'

Privacy benefits: URLs become inaccessible after expiry, no output images stored

Base64 Strategy (Maximum Privacy)

For highly sensitive content where any URL storage is unacceptable. Only <base64> placeholders appear in request history, never actual image data.

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-v1.6",
           "inputs": {
             "model_image": "data:image/jpeg;base64,/9j/4AAQSkZJRgABAQEAYABgAAD...",
             "garment_image": "data:image/jpeg;base64,/9j/4AAQSkZJRgABAQEAYABgAAD...",
             "return_base64": true,
             "output_format": "png"
           }
         }'

Privacy benefits: Zero image data touches FASHN's storage systems—all data stays within your API request/response cycle

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-v1.6",
           "inputs": {
             "model_image": "data:image/jpeg;base64,/9j/4AAQSkZJRgABAQEAYABgAAD...",
             "garment_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).