Privacy Policy

This Privacy Policy explains how Capelago SASU (“Capelago”, “we”, “us” or “our”) processes personal information when you use the Sleev mobile application, the Sleev website, and related services (“Sleev” or the “Service”).

Capelago SASU is a French simplified joint-stock company registered with the Toulouse Trade and Companies Register under SIREN 943 643 395. Capelago is the controller of the personal information described in this Policy.

Privacy contact: contact@trysleev.com

What changed in this version:

website waitlist interaction measurement and approximate country, region, and city reporting;
paid plans and purchases (RevenueCat);
optional advertising measurement (AppsFlyer);
crash reporting (Sentry);
what product analytics now include, such as coarse profile traits, Explore search text, and purchase events;
email sign-in;
the support inbox;
updated AI providers;
the legal bases for each use;
clearer retention and deletion rules.

1. Scope

Sleev lets users create a digital avatar, digitize garments, organize a digital wardrobe, combine garments, and save outfit images.

This Privacy Policy applies to information processed through the Sleev mobile application, the Sleev website at https://trysleev.com, their supporting infrastructure, and related support services.

2. Information we process

2.1 Account information

Sleev requires an account. You can create one with Sign in with Apple, Google Sign-In, or an email address and password. Authentication is managed using Supabase.

Depending on the sign-in method, we may process:

your email address;
your name (Sign in with Apple and Google may share it with us);
an Apple or Google authentication identifier;
a securely hashed password, if you use email sign-in (we never see or store the password itself);
an internal Sleev account identifier; and
authentication and account-status information.

2.2 Profile information

During onboarding or later in your profile, you may provide:

your name;
your date of birth or age;
gender;
height, weight, and waist measurement;
country;
what you want to use Sleev for, and your style preferences; and
other answers, preferences, or corrections entered in the app.

Except where the app marks a detail as required, these profile details are optional. We use them to create, adapt, or describe your avatar, to check the minimum age, and to make Sleev more relevant to you. They are not used to make medical, employment, credit, insurance, or other similarly significant decisions.

2.3 Photos and other uploaded content

Sleev may access the camera or photo library only after you grant the relevant device permission.

You may upload or capture:

face photographs (a selfie);
full-body or partial-body photographs;
garment photographs;
screenshots or product images;
reference images used for a requested generation; and
other images submitted for a supported Sleev feature.

Because these photographs can show your face and body, they are described in full in Section 3 (Face and body images).

2.4 Generated and saved content

We process and store content created through Sleev, including:

generated avatars;
digitized garments;
garment masks, crops, classifications, and related processing data;
saved outfits and outfit images;
generation status and error information; and
ratings, corrections, or reports you give about generated results.

2.5 Plans, purchases, and credits

Sleev offers a free plan with a limited number of credits, the paid Sleev Plus subscription, and credit packs.

Purchases are made through the Apple App Store or Google Play. Apple or Google processes your payment. We never receive your payment-card details.

We use RevenueCat to validate purchases and manage your access. RevenueCat receives:

your Sleev account identifier;
your purchase and subscription history (product, price, currency, purchase and renewal dates, renewal or cancellation status, store and store country); and
basic device and app information.

We keep a record of:

your plan and subscription status;
your credit balance and credit movements (credits granted, used, returned, or purchased);
the promotional codes redeemed by your account; and
technical information needed to enforce usage limits and prevent abuse.

2.6 Product analytics

We use product analytics, provided by PostHog, to understand whether Sleev works correctly and which features are useful.

Identifier. Analytics events are linked to a pseudonymous analytics identifier. That identifier is derived from your Sleev account identifier using a one-way salted hash, so PostHog never receives your account identifier itself. The identifier is nevertheless stable for your account, so we do not describe these events as anonymous.

What analytics may include:

the pseudonymous analytics identifier described above;
app version, build, and platform;
operating system and device characteristics;
approximate country;
when the app is opened or sent to the background;
screens or features used;
interaction events selected by Capelago, including steps of onboarding, purchase screens, and their outcomes (without payment details);
counts, durations, outcomes, and short reason codes for operations such as sign-in, avatar generation, garment digitization, and try-on;
summary account properties, such as your plan, whether onboarding is complete, how many garments and outfits you have, your app-language setting, and whether you allowed notifications and advertising measurement;
coarse profile traits used to group users: an age range (13-17, 18-24, 25-34, 35-44, or 45+), the gender shown in the profile step, which keeps its default value if you do not change it, the country you declared, and your multiple-choice onboarding answers (wardrobe scope, dressing habit, goal, style preferences, and where you heard about Sleev);
when your account was created, and the platform and app version used to create it;
what you type in Explore search, in the shortened form described below;
subscription and purchase events (start, renewal, expiry, cancellation, and credit purchases), including the amount in US dollars. These are sent by our backend when RevenueCat tells it that your subscription or purchase changed;
technical performance or error information included in the event.

Your IP address in the mobile app. PostHog uses your IP address only to determine your approximate country. Our PostHog project is configured to discard the IP address afterwards, and to remove more precise location details such as city, postal code, and coordinates.

Explore search. What you type in the Explore search box may be sent with the search event. Before it is sent, the text is trimmed, converted to lower case, and cut to 40 characters. It is left out completely, keeping only the length of the search and the number of results, when it contains an “@” or five or more digits in a row, because the text may then be an email address or a phone number. Search is a free-text field, so please avoid typing personal details into it.

What analytics never include. Session replay, screen recording, and automatic capture of your taps and typing are not used. We do not send uploaded images, generated images, image URLs, image crops, generation prompts, or AI-provider request or response payloads to PostHog. We also do not send your email address, your name, your date of birth or exact age, your height, weight, or body measurements, the free-text note you can add during onboarding, or the text of a support message. Advertising identifiers are never sent to PostHog; they are only used for advertising measurement, and only if you allow it (Section 2.8).

Server events. Our backend sends a small number of processing-outcome events, feedback and rating events, and the subscription and purchase events described above, using the same pseudonymous identifier.

Infrastructure logs. Infrastructure providers may separately process network and security logs, which can include IP addresses, request metadata, timestamps, user identifiers, and error details.

2.7 Crash reports

We use Sentry to detect and fix app crashes and errors.

What a report contains: the type of error, a technical stack trace, the app version, device and operating-system information, and the same pseudonymous analytics identifier described in Section 2.6, so that a crash can be matched with the product-analytics events around it.
What we remove before sending: error messages, request data, activity trails, and any other identity information. Sentry never receives your Sleev account identifier, your email address, your name, or your IP address from us.
What we don't use: screenshots or session replay.

2.8 Advertising measurement (only with your permission)

What it is for. With your permission only, Sleev uses AppsFlyer to measure which of our advertising campaigns lead people to install Sleev, use it, and subscribe.

When it is on.

On iPhone and iPad, AppsFlyer is started only if you tap Allow on Apple's tracking permission prompt.
On Android, it is started only if you tap Allow on Sleev's ad-measurement screen.

If you don't allow it, AppsFlyer is not started, and everything in Sleev, including purchases, works the same.

What is processed when you allow it:

your device's advertising identifier (IDFA on iOS, advertising ID on Android) and, on iOS, the identifier for vendors (IDFV);
an AppsFlyer installation identifier;
your IP address, used to estimate approximate location and to detect fraud;
device and app information, such as model, operating system, language, and app version;
the campaign, advertising network, ad, or link that led to the installation;
your Sleev account identifier, so that an installation can be linked to later purchases; and
three in-app events: an avatar was created, a garment was digitized, and an outfit was saved (with the number of garments in it).

Purchases. When you have allowed advertising measurement, RevenueCat also informs AppsFlyer of purchases, renewals, and cancellations.

Advertising networks. AppsFlyer may report campaign results to the advertising networks we use for our campaigns, so that those campaigns can be measured.

What is never sent. We never send your photos, generated images, profile details, or email address for advertising measurement. Images and data from your camera or photo library are never used for advertising or advertising measurement. This choice does not enable personalised advertising, and Sleev does not show ads.

What Sleev stores. We store the campaign information for your installation (campaign, network, ad, and install date) with your account. It is deleted when you delete your account.

Changing your mind. You can change your choice at any time:

in Account → Privacy → Ad measurement; or
on iPhone and iPad, in Settings → Privacy & Security → Tracking.

What withdrawing does. It stops new collection on that device and removes the attribution identifiers from RevenueCat. The choice applies to the device on which you make it.

AppsFlyer's own processing is described in the AppsFlyer Services Privacy Policy.

2.9 Links and promotional codes

Links. A link to Sleev, such as a trysleev.com/l/… link, can open a specific screen in the app.
Campaign links. If you have allowed advertising measurement, links from our campaigns may also be processed by AppsFlyer.
Promotional links. A promotional link may fill in a promotional code for you. The code is only redeemed when you confirm it.
Record of redemption. We keep a record of the codes redeemed by your account.

2.10 Push notifications

If you allow notifications, we process a push-notification token, your platform and language, your notification preferences, and delivery information. We send notifications through Expo and the notification services operated by Apple and Google.

Notifications may tell you:

that an avatar, garment, or other requested operation has finished or failed;
that you received credits or a message from our team; and
about product news, reminders, or style inspiration.

Once you allow notifications, these categories are on by default. You can turn off each category in the app, or disable notifications in your device settings.

2.11 Support, feedback, and account-deletion reasons

What we collect. If you contact us, rate a result, or send feedback, we process:

the content of your message;
your email address and Sleev account identifier;
basic account information that helps us answer (such as your plan or app version); and
any files or technical information you choose to provide.

Deletion reasons. If you delete your account, you can tell us why, and add a comment. That reason and comment are sent to our team together with your email address, signup date, and number of garments, just before the account is deleted.

Where it goes. These messages are delivered to our team through a private channel in Discord, and in-app messages and feedback are also stored in our database.

2.12 Website waitlist

If you submit your email address on the waitlist page at https://trysleev.com/waitlist, we store that address with our email provider, Resend, for the sole purpose of telling you when the Sleev iPhone app is available.

We do not use it for advertising or share it with anyone else.
Every message we send includes an unsubscribe link.
You can ask us to delete your address at any time by writing to contact@trysleev.com.

2.13 Website measurement

We measure how the Sleev website is used, using the same analytics provider as the app, PostHog.

The website sets no cookies. It does not use cookies, local storage, session storage, advertising identifiers, session replay, screen recording, or automatic interaction capture. Because no information is stored on your device for this purpose, no cookie banner is required.

How visits are grouped. Instead of an identifier stored in your browser, website events are grouped by a pseudonymous value that our analytics provider derives on its servers from:

your network address;
your browser's user-agent string; and
a secret that changes every day and is then deleted.

Unlike the app identifier described in Section 2.6, it cannot be used to recognise you from one day to the next.

Website analytics may include:

the pages viewed and the order they were viewed in;
the website or campaign parameters that referred you;
browser and device characteristics;
clicks on the App Store and Google Play buttons;
whether you started entering a waitlist email, attempted to submit it, or encountered a validation error, without recording what you typed;
whether a waitlist or contact submission succeeded or failed;
approximate country, region, and city derived by our website hosting provider from your network address; and
which frequently asked questions were opened.

Website location. We use approximate country, region, and city to understand where website visitors come from and how signup rates differ by location. We do not request your device’s GPS location or send postal codes, coordinates, or an additional raw IP address in these location fields. IP-derived location may be inaccurate, particularly with VPNs, privacy relays, or mobile networks. Location may be unavailable. These website fields are separate from the mobile app’s country-only analytics described in Section 2.6.

We do not send your email address, your name, or the text of a support message to PostHog. A waitlist address is transmitted only to our email provider, as described in Section 2.12.

3. Face and body images

Sleev’s avatar, garment-digitization, virtual try-on, and image-generation features work from photographs. Those photographs can show your face and your body. This section describes that processing in one place.

3.1 What we collect

Sleev can use your camera or photo library only after you grant the corresponding device permission. Inside a supported feature, you may provide:

face photographs used to create or refine your avatar;
full-body or partial-body photographs used to create or refine your avatar;
garment photographs, screenshots, and product images; and
reference images used to guide a requested generation.

These images may contain your face and your body. A photograph submitted for avatar creation will normally show your face, your body, or both. Sleev processes these photographs as personal information.

3.2 You select every image

Every image is chosen or captured by you and submitted for a feature you asked for.

Sleev does not scan, index, or read your photo library, and does not capture photographs in the background. The app opens the camera or the system picker only when you tap a control that starts that step, and it receives only the images you pick. If you do not select and submit an image, it is not uploaded and not processed.

3.3 What we use the images for

Capelago processes face and body images to provide, operate, secure, troubleshoot, and support the image-based features you request, namely:

creating, adapting, and regenerating your avatar;
running automated checks that confirm a photo can be used before a generation starts;
digitizing garments and separating a garment from its background;
producing virtual try-on and outfit visualizations;
generating, storing, and displaying the resulting images in your Sleev account; and
investigating a failed, rejected, or incorrect generation, including one that you report.

3.4 What we do not use the images for

Capelago does not:

perform facial recognition or face matching;
use the images to identify you, verify your identity, or authenticate you;
create, derive, or store a biometric face template, faceprint, or other biometric identifier;
process the images for the purpose of uniquely identifying a natural person;
use the images, or any data derived from your camera or photo library, for advertising, advertising measurement, ad targeting, profiling, or tracking;
send the images to AppsFlyer, RevenueCat, PostHog, or Sentry;
use the images to train Capelago's own AI models; or
process the images for unrelated background purposes.

Signing in to Sleev never uses your photographs.

3.5 Where the images are stored

Source images and generated images held by Sleev are stored in private Supabase storage buckets and associated with your account. These buckets are not publicly readable: the app obtains a short-lived signed link each time it needs to display an image.

Files are transmitted over encrypted HTTPS/TLS connections. Sleev's storage is not end-to-end encrypted: Capelago and the providers listed in Section 7 can technically access stored files in order to operate the Service.

3.6 Transmission to third parties

To produce the results you ask for, the images you select are transmitted to third-party AI providers and to the infrastructure that runs Sleev's image processing. The providers, the content sent, and the reasons are described in Section 5 (AI processing) and Section 7 (Service providers and recipients).

3.7 Retention and deletion

Original images you upload and images Sleev generates remain in your private Sleev account until you delete the relevant item or delete your account. They are not published and are not shared with other Sleev users.

While a generation runs, the images it needs are uploaded to our image-generation provider's temporary file-hosting service, as described in Section 5. To investigate processing problems, our pipeline may keep temporary technical copies of intermediate images for up to 7 days.

Deleting an item. Deleting an avatar, garment, outfit, or generation inside the app deletes the database records and every source and generated file controlled by Capelago that belongs exclusively to that item.
Deleting your account. Account → Settings → Delete account → Confirm permanently deletes your account and its stored images. You can also request deletion at https://trysleev.com/delete-account, or by writing to contact@trysleev.com.

Deletion from Sleev does not by itself remove a temporary copy already held by an AI provider. See Section 9 (Retention) and Section 10 (Account and data deletion).

4. How we use information, and on what legal basis

Under the EU General Data Protection Regulation (GDPR), we must have a legal basis for each use of your personal information. We use information for the following purposes:

To provide Sleev under our Terms (performance of a contract):

creating and authenticating your account;
providing the digital wardrobe, avatar, garment, try-on, and outfit features;
processing your photos with our AI and infrastructure providers to perform the operations you request (Section 5);
storing and synchronizing your content;
managing your plan, subscription, credits, and promotional codes; and
sending notifications about operations you requested and about your account.

With your consent (which you can withdraw at any time, without affecting earlier processing):

advertising measurement with AppsFlyer, including purchase events sent by RevenueCat (Section 2.8);
product news, reminders, and style-inspiration notifications (Section 2.10); and
device permissions such as camera, photos, and notifications, where consent is required.

For our legitimate interests, where these are not overridden by your rights:

product analytics with a pseudonymous identifier, to understand how Sleev is used and improve it (Section 2.6);
testing variations of features, screens, or offers with groups of users selected at random. You may be shown a different version or price than another user; the price that applies to you is always shown before you buy. Your group is chosen at random, not based on your profile or behaviour;
crash reporting and fixing errors (Section 2.7);
securing Sleev, preventing fraud and abuse, and enforcing our Terms;
answering support requests and feedback, and understanding why people leave (Section 2.11); and
defending legal claims.

To comply with legal obligations:

keeping records required by accounting and tax law;
answering lawful requests from authorities; and
handling your privacy requests.

We do not sell personal information. Sleev does not show ads and does not use your information for personalised advertising.

5. AI processing and third-party AI providers

Sleev uses third-party artificial-intelligence services to check submitted photos, create avatars, isolate and digitize garments, produce virtual try-on visualizations, and generate related images. These features cannot operate without sending the required content to those services.

Requests are transmitted through Capelago's backend rather than directly from the mobile application.

5.1 Which providers receive the content

Depending on the operation you request, and on the provider selected for that operation at the time, the content you submit may be processed by:

Kie.ai — AI image generation, such as virtual try-on visualizations and avatar generation. To run a generation, Sleev uploads the required images to Kie.ai's file-hosting service and then submits a generation task that refers to them. Kie.ai may route a task to an underlying model or infrastructure provider it selects, so those providers are further recipients of the content in the request.
OpenAI — AI image generation, such as avatars, digitized garments, and try-on visualizations.
Google (Gemini API) — automated visual checks, such as confirming that a garment photo is usable, locating a garment within an image, and checking and verifying avatar photos and generated avatars.
DeepSeek — automated visual checks of the photos you submit, such as confirming that avatar or garment photos are clear and usable.
Modal — the GPU infrastructure on which Sleev runs its own body-segmentation step.

More than one of these providers may be involved in a single request, and which provider performs a given operation can change as Sleev is improved.

5.2 What is transmitted

Depending on the requested operation, the content sent may include images that contain your face, your body, or garments, specifically:

original uploaded images;
cropped or downscaled face, body, or garment images;
generated or intermediate images;
reference or guideline images;
technical generation parameters; and
text instructions required for the requested transformation.

We do not send your name, email address, or profile details to AI providers, other than information strictly needed for the requested image, such as a garment category.

5.3 Why it is transmitted

Content is sent to these providers only to perform the image-processing or image-generation operation you requested. Sleev does not send your images to AI providers for analytics, advertising, profiling, identity verification, or background or bulk processing unrelated to a request you made.

5.4 What the providers may retain

AI providers process requests under their own service terms, technical controls, and retention practices. They may temporarily process or retain submitted content and generated results according to those policies, which Capelago does not control.

Kie.ai documents that it keeps generated media for 14 days, and task records and logs for about two months.
OpenAI states that content sent through its API is not used to train its models by default, and may be kept for up to 30 days for abuse monitoring.
For the other providers, retention is governed by the terms and settings applicable to the service Capelago uses.

Deleting an image or your account in Sleev removes it from the systems Capelago controls. It does not send a deletion instruction to an AI provider, and copies a provider already holds expire under that provider's own retention rules.

5.5 The basis on which providers process the content

These providers process information under their applicable service terms, data-processing terms, technical settings, and applicable law. Capelago selects and configures these services for the purpose of delivering the user-requested feature, and uses the privacy and retention settings each provider makes available.

Capelago does not use your photographs or generated content to train its own AI models. Whether a provider may use submitted content for its own purposes is governed by that provider's terms for the service Capelago uses.

5.6 Changes of provider

AI providers and models may change as Sleev is improved. We will update this Policy when a change materially affects how personal information is processed.

Before you can select and submit photographs for an AI-powered feature, Sleev shows a disclosure explaining that the photographs will be sent to AI service providers for the processing you asked for, and links to this Privacy Policy. The sign-in screen links to our Terms of Use, the Apple EULA, and this Privacy Policy.

6.1 Avatar creation

Before the photo picker opens, Sleev displays a disclosure that states:

The photos you upload will be securely sent to our AI providers to verify them and generate your avatar. By continuing, you accept this processing.

The words Privacy Policy below that sentence are a link that opens this Policy, where the current providers are described in Section 5. The disclosure appears together with guidance to use only your own photos.

The photo picker does not open until you continue from this disclosure. Until then no photograph has been selected and none has been transmitted. If you leave the screen instead of continuing, no image is chosen and nothing is sent.

Once you have chosen your photographs, transmission begins when you press Create my avatar. That screen also carries the notice “Your avatar is generated by AI.” next to the button.

6.2 Garment digitization

The first time you open the garment camera on a device, Sleev displays a disclosure before you take or choose a garment photograph. It states:

The photos you upload will be securely sent to our AI providers to verify them and digitize your clothes. By continuing, you accept this processing.

As with avatar creation, the words Privacy Policy below that sentence link to this Policy.

Continuing from this disclosure covers the verification check and the digitization that follow. It is shown before your first garment submission on that device and is not repeated before each later processing step. No garment photograph is taken, chosen, or transmitted before you continue, and you can leave the camera without taking or choosing a photograph.

6.3 Your privacy choices

Ad measurement: Account → Privacy → Ad measurement, and on iPhone and iPad, Settings → Privacy & Security → Tracking (Section 2.8).
Notifications: notification categories in the app, or your device settings (Section 2.10).
Camera and photos: your device settings. Withdrawing a permission may prevent the corresponding feature from working.
Declining AI processing: at either disclosure, leave the screen rather than continuing, or later, don't take, select, or submit a photograph. Declining leaves your account and the rest of Sleev unaffected, but avatar creation and garment digitization cannot produce a result without sending the required images.
Deleting content or your account: Sections 9 and 10.

No background collection. Sleev does not scan or index your photo library and does not capture photographs on its own. After you submit a garment photograph, its digitization continues while you carry on using the app. That is continued processing of an image you already submitted, not new collection.

7. Service providers and recipients

We disclose information only as needed to operate Sleev. Our service providers process it on our behalf and under our instructions, except where stated otherwise.

Providers that receive or process your images:

Supabase: account authentication, database, and private file storage for your source and generated images;
Render: hosting for Sleev's backend, through which image requests are transmitted, and operational logs;
Modal: GPU infrastructure for body segmentation;
Google and DeepSeek: automated visual checks on submitted and generated images (Section 5); and
OpenAI, and Kie.ai together with its file-hosting service and any underlying model or infrastructure providers to which it routes a task: AI image generation.

Providers that do not receive your images:

RevenueCat: purchase validation and subscription management;
Apple and Google: payment processing, sign-in, app distribution, and push-notification delivery;
AppsFlyer: advertising measurement, only if you allow it, and the advertising networks to which AppsFlyer reports campaign results;
PostHog: product analytics, using the pseudonymous identifier described in Section 2.6;
Sentry: crash reporting;
Expo: push-notification delivery and app updates;
Discord: delivery of support messages, feedback, and account-deletion reasons to our team;
Cloudflare and email providers: email routing and communication;
Resend: storage and delivery of the website waitlist described in Section 2.12; and
professional advisers, authorities, or other recipients where disclosure is legally required.

These providers process information under their applicable service terms, data-processing terms, technical settings, and applicable law.

We may also disclose information if reasonably necessary to protect users, investigate abuse or security incidents, enforce our Terms, or comply with a valid legal request. If Capelago is involved in a merger, acquisition, or sale of assets, information may be transferred as part of that transaction, subject to this Policy.

8. International processing

Capelago is established in France. Sleev's primary Supabase database and storage are hosted in Ireland.

Other providers, including hosting, infrastructure, AI, payment, analytics, crash-reporting, advertising-measurement, and communication providers, process information in the United States, in China, or in other countries outside the European Economic Area. Our product-analytics provider (PostHog) and our crash-reporting provider (Sentry) are both configured to United States regions, and our advertising-measurement provider (AppsFlyer) processes information outside the European Economic Area.

Privacy and data-protection standards in these countries may differ from those in the European Union, and not all of them are recognised by the European Commission as providing an adequate level of protection.

Transfer safeguards. Where a transfer requires safeguards under the GDPR, Capelago relies on the mechanisms that its providers make available, such as:

the EU–U.S. Data Privacy Framework;
the European Commission's standard contractual clauses included in providers' data-processing terms; or
where these are not available, the transfer being necessary to perform the service you request.

To find out the current position for a specific provider, contact contact@trysleev.com.

9. Retention

9.1 Data controlled by Capelago

Your account and content. Account information, profile information, uploaded source images, avatars, garments, outfits, credit balances, and notification settings are kept for as long as your account is active, unless you delete an item earlier. We do not apply a fixed expiry to your images.

Deleting an item. Deleting an avatar, garment, outfit, or generation deletes the corresponding database records and every source and generated file controlled by Capelago that belongs exclusively to that item.

Deleting your account. This deletes your data as described in Section 10.

Exceptions. Some information is kept after deletion, or for a set period:

Operational logs (records of processing calls and promotional-code redemptions) may keep your account identifier after your account is deleted, for cost accounting and fraud prevention.
Temporary pipeline copies of intermediate images are kept for up to 7 days.
Accounting records. Records we are legally required to keep are kept for the period required by law. For French accounting documents this is up to 10 years.
Support messages are kept for as long as reasonably necessary to handle the request and keep a record of its resolution.
Infrastructure logs and database backups, if enabled, expire on their provider's schedule.
Security, fraud, and legal claims. Information may be kept longer where needed for security, fraud prevention, or the establishment or defence of legal claims.

9.2 Information held by providers

RevenueCat: your purchase and subscription history is kept as a record of your transactions, for accounting, refunds, and fraud prevention.
AppsFlyer: if you allowed advertising measurement, attribution data is kept for up to 24 months.
PostHog: analytics events carry only the pseudonymous identifier described in Section 2.6 and are kept according to our project's retention settings.
Sentry: crash reports are kept for our plan's retention period. Crash reports use a pseudonymous identifier that allows correlation with product analytics, rather than your direct account identifier (Section 2.7).
AI providers: temporary copies expire under each provider's own retention rules (Section 5.4).

10. Account and data deletion

10.1 Deleting individual items

You can delete an avatar, garment, outfit, or generation inside the app. Sleev deletes the corresponding database records and every source and generated file controlled by Capelago that belongs exclusively to that item.

10.2 Deleting your account

You can delete your account inside the app:

Account → Settings → Delete account → Confirm

Deletion is immediate, automatic, and permanent, and is not a soft deletion. When you confirm:

your stored images are removed from Sleev's storage;
your authentication account, profile, wardrobe, avatars, outfits, credits, and the other database records associated with it are deleted.

Limited records held by our service providers are kept under their retention periods (Section 9.2): your purchase history at RevenueCat, pseudonymous analytics events at PostHog, and, if you allowed advertising measurement, attribution data at AppsFlyer.

Deleting your account does not cancel an App Store or Google Play subscription. Cancel your subscription in your store settings first. Apple and Google keep their own records of your purchases under their privacy policies.

You can also request account deletion without access to the app through:

https://trysleev.com/delete-account

The external page allows you to submit a deletion request using the email address associated with your Sleev account. We may ask you to verify control of that address before processing the request.

10.3 Privacy and deletion requests by email

For deletion requests, privacy questions, or any other request relating to your images or your account, contact contact@trysleev.com. We may request information reasonably necessary to verify that the request relates to your account.

11. Your rights

Depending on where you live, you may have rights relating to your personal information, including rights to:

access the information we hold about you;
correct inaccurate information;
have your information deleted;
object to processing based on our legitimate interests, including product analytics;
request that we restrict certain processing;
receive the information you provided in a portable format;
withdraw your consent at any time, for example to advertising measurement, without affecting processing carried out before; and
lodge a complaint with a data-protection authority. In France, this is the CNIL (www.cnil.fr), 3 place de Fontenoy, TSA 80715, 75334 Paris Cedex 07. You may also contact the authority where you live or work.

You can edit your profile details inside Sleev, change your privacy choices as described in Section 6.3, and delete your account using the in-app deletion flow. For a copy of your information or any other request, contact contact@trysleev.com. We answer within one month, and may request information reasonably necessary to verify that the request relates to your account.

Providing your account information is necessary to use Sleev. Other information, such as optional profile details, advertising-measurement permission, and notifications, is optional.

California and other US states. We do not sell personal information, and we do not share it for cross-context behavioural advertising other than the optional advertising measurement described in Section 2.8. You can switch that off at any time in Account → Privacy → Ad measurement.

12. Images containing other people

You must have the rights and permissions necessary to upload an image to Sleev.

Where an image contains another identifiable person, you must have that person's permission or another valid basis to upload and process the image. Sleev may use such an image to identify and crop a garment, but it does not permit users to create an avatar from another person's face or body without that person's permission.

Please do not upload intimate, nude, sexually explicit, exploitative, illegal, or otherwise harmful images, particularly images involving minors.

13. Children

Sleev is intended for users aged 13 or older and is not directed to children under 13.

Users who are under the age of majority where they live should use Sleev only with the permission of a parent or legal guardian. Where local law requires parental consent for processing based on consent, such as advertising measurement for users under 15 in France, that choice should be made with a parent or guardian.

If we learn that an account belongs to a child under 13, we may suspend or delete the account and its associated information. A parent or guardian who believes that a child under 13 has provided information to Sleev may contact contact@trysleev.com.

14. Security

We use reasonable technical and organizational safeguards designed to protect information, including:

encrypted transmission using HTTPS/TLS;
authentication and access controls;
private, non-public storage buckets for user files, served through short-lived signed links;
server-side transmission of AI requests, so provider credentials stay off the device;
restricted, password-protected access to production systems and internal tools;
removal of identifiers from crash reports; and
limitation of the data and identifiers sent to analytics.

Only Capelago's authorized personnel and service providers acting to deliver their services have access to production information.

Sleev is not end-to-end encrypted. No technical system is completely secure, and we cannot guarantee that unauthorized access, loss, or misuse will never occur.

15. Changes to this Policy

We may update this Privacy Policy when Sleev's features, providers, or data practices change.

The current version will be published on this page with an updated date. If a change materially affects how we use information or a permission you previously gave, we will provide a notice in the app and, where required, ask for your consent again.

16. Contact

For privacy questions, rights requests, or account-deletion assistance:

Capelago SASU
RCS Toulouse — SIREN 943 643 395
contact@trysleev.com