Privacy Policy for Android

Effective 17 October 2026. Drapiqo is provided by Ibrahim Cakir. Contact: ibrahim22ckr@gmail.com.

On your device

Your wardrobe, clothing photos, saved outfits, wear history, plans, style preferences and display name are stored in the app’s private Android storage. You can choose photos with the Android Photo Picker or explicitly grant full or selected library access for a wardrobe scan. Starting with Android 1.1.0, clothing is found and cut out entirely on your phone by open-source models that ship with the app (OWL-ViT, SAM 2.1 and CLIP); scanned photos are not uploaded and no server is involved. In Only me mode, a reference selfie is processed on your device into an encrypted face embedding; the temporary selfie copy is deleted, and neither that selfie nor the embedding leaves your phone. Face matching and person-context segmentation also run on your device. Removing a piece does not delete its original from your gallery. Android cloud backup of app data is disabled.

Anonymous account and app security

When you use cloud features or send feedback, Firebase Authentication creates an anonymous account ID. No email, password or phone number is required. Firebase and Google Play Integrity process app/device information, integrity tokens, SDK/user-agent information and network information including IP addresses to authenticate requests and prevent abuse. Your account ID is used to associate your cloud results, permissions and usage allowances with your account.

Optional cloud features

• Clothing analysis (earlier versions only): Android versions before 1.1.0 uploaded selected wardrobe photos, or locally matched photos in Only me mode, to our garment-analysis service on Google Cloud (EU region). That service was shut down on 13 October 2026; any remaining uploads are deleted automatically within seven days. Android 1.1.0 and later analyse clothing only on your phone.
• AI Stylist: after your permission, clothing details, style preferences, occasion and your typed request are sent to Google’s Gemini models through Vertex AI in the EU. No photos are sent for styling. Validated replies are cached privately for up to seven days; clothing descriptions and typed styling requests are not stored in that cache.
• Garment Studio: after your permission, the selected garment image, which may show visible body context, is sent to Google’s Gemini API to make a product-photo preview. Your original remains unchanged. Results and request records are stored privately for recovery.
• Virtual try-on: after your permission, selected garment images and a selected body silhouette are sent to Google’s Gemini API. If you choose personal mode and separately consent, a face crop from the photo you select is also sent. Optional height and weight are approximate styling context, not medical or fitness advice. The original face photo is not saved on our servers. The generated preview can resemble you and is stored privately so you can reopen it. Provider request storage is disabled for image generation.

AI previews can change garment details and body proportions and are not guarantees of fit, size or appearance. A new generation always requires your action. You can revoke AI permissions inside each feature.

Feedback and AI content reports

When you tap Send in a feedback/report form, your message, anonymous account ID, feature name and optional result/item reference are stored privately on our Firebase backend for review. Photos are not automatically attached. Please do not include sensitive information in your message. Feedback is retained until account deletion or until removed after review.

Use, providers and retention

We use data to provide the features you request, recover results, handle reports, enforce quotas and secure the service. Google Cloud, Firebase, Vertex AI and the Gemini API process data on our behalf. Data is encrypted in transit using HTTPS. Providers may process data outside your country. There are no advertisements or advertising trackers. Starting with Android 1.0.1, supported subscriptions use Google Play Billing when the store products and server verification are available. Google Play handles your payment information; Drapiqo does not receive card details. The app sends purchase tokens and its anonymous account ID to our Firebase service, which verifies subscriptions with Google Play. Tokens are stored privately on the server for renewal, restoration, refund and cancellation verification; they are not exposed in public entitlement records. A subscription can be restored using the Google Play account that purchased it. Purchase verification records are deleted when your Drapiqo account is deleted. We do not sell personal data or use it for advertising or to train our own models. Usage and operational records are retained to enforce limits and diagnose failures. Private AI results and account records remain until deletion; on-device records remain until you delete them, delete your app data or uninstall.

Deletion and your choices

In the app, open Profile → Account → Delete my data to delete your cloud account, private AI results, reports and usage records, followed by local wardrobe and profile data. If cloud deletion fails, local data is kept so you can retry. Your original gallery photos are not removed. Deleting your Drapiqo data does not cancel your Google Play subscription: manage or cancel it separately in Google Play subscriptions. Your encrypted on-device face reference is erased when you delete app data. You can also request account and data deletion outside the app. Anonymous accounts cannot be restored by an email sign-in after uninstalling. Copy your Cloud account ID from Profile if you need it for a support request; never send authentication tokens.

Children and rights

Drapiqo is not directed to children under 13 or the minimum age applicable in your country, and we do not knowingly collect their data. Depending on your location, you may have rights to access, correct, delete, restrict or object to processing, or complain to a regulator. Contact us using the address above. We will update this page and its effective date when this policy changes.