VESILY · MOBILE APP & WEBSITE

Privacy policy.

Effective and last updated: October 16, 2026

1. Who is responsible

Vesily is operated by Mehmet Ali Çuhacı, an independent developer based in Türkiye. For privacy questions or requests, email vesily@vesily.app. For help using the app, contact destek@vesily.app.

2. Information we handle

• Account and security: email address, display name, account identifier, password hash, verification and session records, sign-in/sign-out times, and account status. Passwords are stored as hashes rather than readable passwords.
• Profile and preferences: gender selection, style preferences, profile photo, and any height, weight, clothing sizes, preferred brands or colors you choose to provide. Body measurements and profile preferences are used for clothing personalization, not medical assessment.
• Clothing and outfits: the photos you select or take, uploaded originals, processed images, clothing categories and attributes, wardrobe items, selected catalog items, outfit instructions, generated outfits, saved layouts, and sharing choices. Photos may contain background details or other personal information; select images you are comfortable uploading.
• Support and output feedback: support messages, bug reports, suggestions and replies, together with related account and request identifiers. If you rate an image negatively, a copy of that output may be retained with its rating to investigate the result.
• Operational records: IP address, device/browser information, request identifiers, account activity, processing stages and durations, model/job metadata, and errors. These support security, troubleshooting and service operation. Authorized administrators can review relevant records and feedback images.
• Optional location and settings: a selected city or device coordinates for weather features, notification permissions, reminder times, theme and consent settings. Location coordinates are stored in the app's local web storage and sent to weather/geocoding providers when you use those features. The app does not require continuous background location.

3. Why we use this information

We use information to create and secure accounts, verify email addresses, maintain wardrobes, prepare clothing images, personalize outfit suggestions, save or publish content at your request, deliver reminders, answer support requests, and diagnose problems. Required account and service data is used to provide the features you request. Optional permissions, marketing preferences and analytics/advertising choices can be managed separately.

Clothing image processing sends selected photos and relevant instructions to our processing infrastructure. A wardrobe is not made public simply because you upload a photo. Generated results may be inaccurate and should be reviewed before saving.

4. What other users can see

If you publish an outfit in Explore, other users can see the published outfit, your display name and profile image, and the public sharing information associated with that post. Your account email, private wardrobe and body measurements are not automatically displayed in Explore. You can manage or remove your own shared outfits in the app. Content other people have already copied or captured may remain outside our control.

5. Service providers and international processing

We use the following services to operate Vesily. They receive the information needed for the feature being used:

• Amazon Web Services (AWS): hosts our backend and stores application files, clothing photos and generated media. The current media storage region is US East (N. Virginia), United States.
• RunPod: provides remote GPU processing for clothing detection, segmentation and image generation. Relevant input images, prompts and processing results are transmitted to the selected worker infrastructure.
• Resend: sends verification, password reset, email-change and support emails. It receives the recipient address and message content needed to deliver the email. Support correspondence may also be processed by the mailbox provider used for our vesily.app addresses.
• Open-Meteo and BigDataCloud: receive city searches or coordinates for weather forecasts and location names. A connection to these services also exposes normal network information such as your IP address.
• Apple and Expo/EAS: support distribution and testing of the iOS app. TestFlight feedback, crash reports and testing activity may be handled under Apple's and Expo's own privacy notices.

These providers may process data outside your country, including the United States and other countries where their infrastructure operates. This page does not assert that a particular international-transfer legal mechanism has already been completed. Contact us with questions about recipients or cross-border processing before uploading sensitive information.

Provider notices: AWS, RunPod, Resend, Open-Meteo, BigDataCloud, Apple, and Expo.

6. Analytics, advertising and marketing

The current beta includes preparations for Google Analytics and Google advertising, including a native WebView advertising SDK. Live analytics measurement and advertising units have not been configured for this beta release. Their presence in the code does not mean that advertising is active.

If enabled in a later configuration, analytics and advertising are subject to the separate choices provided in Settings → Privacy, the provider's consent controls, and any required device permission. Google services can process usage, device and network information under Google's Privacy Policy. Our screen analytics implementation does not attach email addresses, uploaded photos or body measurements to its events. We will update this policy when the active configuration changes.

Email marketing permission is optional and can be withdrawn in Settings → Privacy. Account verification, password reset and necessary support/security messages are separate from marketing permission. The current beta does not run an automatic promotional email campaign.

7. Permissions and your choices

• Camera and photos: used to take or choose clothing and profile images. We do not automatically upload your entire photo library.
• Location: optional for local weather. You can choose a city manually instead.
• Notifications: optional for reminders scheduled on your device. Changing the permission in iOS Settings can disable them.
• Profile, sharing and consent: update optional profile information, manage published outfits and change available privacy preferences in the app. Device permissions can be changed in your operating system settings.

8. Local storage and website use

The app's web interface stores session information, theme and privacy preferences, location/city settings, caches and pending upload-recovery data in local storage, session storage or IndexedDB. This helps maintain sign-in, recover interrupted work and remember your choices. Some information can remain on a device until you sign out, remove it or clear app/browser storage. Clearing local storage does not by itself delete server-side account data.

The marketing website does not provide account registration or clothing upload forms and currently has no advertising or analytics scripts. Its example outfits are displayed locally in the browser. It stores a theme preference. Email links open your email app; messages you choose to send are used to respond to your enquiry. Hosting systems may record network and request logs.

9. Retention and account deletion

Account and wardrobe records are retained while the account is in use so that saved content remains available. Production input/output files, feedback records, operational logs and backups do not currently have a single fixed automatic expiry period during the beta. They can remain until account deletion, a privacy request or service maintenance removes the relevant records. We do not promise deletion after an unimplemented number of days.

To delete your account, open Profile → Settings → Delete Account (Profil → Ayarlar → Hesabı Sil) and confirm with your password. Stop any active generation and wait for it to end first. The deletion flow removes the active account and its associated wardrobe, owned processing files and saved outfits. Some security/audit records, provider delivery records or backup copies can remain separately from the active account. Deleting a single wardrobe item does not necessarily remove every original processing file or diagnostic record.

If you cannot access the app, or want remaining records reviewed, contact vesily@vesily.app from your registered email address. We may ask for information needed to verify account ownership. Do not send your password.

10. Privacy requests

You can contact us to request access to information associated with your account, correction of inaccurate details, deletion, or withdrawal of optional consent. Depending on the law that applies to you, additional rights may include receiving a copy of your data, objecting to or restricting certain processing, and making a complaint to a data protection authority. We review requests against the applicable requirements and may need to verify your identity.

For users in Türkiye, requests concerning rights under Article 11 of the Personal Data Protection Law (KVKK) can be sent to the privacy contact below. This policy describes current beta operation; it does not replace any additional notices or transfer arrangements required by applicable law.

11. Security

We use HTTPS for app/API connections, password hashing, account access controls and private cloud media storage. Service access is restricted to authorized roles. No internet service can guarantee absolute security. Report suspected account access or exposure to destek@vesily.app.

12. Children and changes

The beta is not designed for children under 13. If you believe a child has provided personal information, contact us so we can review and address it. We will update this page when our practices change; the effective date above identifies the current version. Material changes to optional processing will also be reflected in the relevant app notices or choices.