Privacy policy

This policy explains information handling in Wearvia for iOS. Wearvia is a local-first wardrobe, outfit, wear-history, and trip-capsule utility. It does not require an account, operate a Wearvia photo or wardrobe backend, include a social or shopping feed, or use a standalone product-analytics service.

Information that remains only on your device is not available to the operator. Apple, RevenueCat, and Google may process limited information for platform services, purchases, entitlement delivery, advertising, consent choices, security, fraud prevention, and related operations below.

Wearvia stores garment photos and cutouts, optional garment details, categories, colours, tags, outfits, wear history, cost-per-wear inputs, trip plans, packing states, preferences, and local backup records in the app's local container. The deterministic outfit engine uses only garments and details in your Wearvia closet.

Apple Vision foreground masking and manual cutout refinement run on the device. Wearvia does not send garment images, cutout masks, outfit contents, trip details, notes, prices, or wardrobe history to a Wearvia server or cloud AI service.

iOS backups may include app-container data according to your Apple backup settings. A portable Wearvia backup is created only when you request it and is then handled by the destination you select.

Wearvia requests camera access when you choose to photograph a garment. The system Photos picker provides access only to images you deliberately select; Wearvia does not scan your photo library in the background.

Selected images are copied into Wearvia-managed storage so the app can preserve its own original and edited cutout. Deleting a Wearvia garment removes only Wearvia's copies, not the original Photos item or an exported file stored elsewhere.

Location is optional and is not requested during onboarding. When you deliberately ask for local weather, Wearvia requests when-in-use approximate location and uses it for a one-shot Apple WeatherKit current-conditions request. The native weather module does not return coordinates to Wearvia's JavaScript layer.

Wearvia stores only a derived weather snapshot for up to approximately thirty minutes and keeps a manual-weather fallback. Apple may process location, network, device, and request information to provide Location Services and WeatherKit under Apple's terms. You can deny or revoke access in iOS Settings and continue with manual conditions.

Apple processes App Store purchases and payment credentials. Wearvia does not receive your card or bank details. RevenueCat provides localised product availability, purchase, entitlement, restore, and limited offline-entitlement functionality for Wearvia Plus.

Wearvia configures RevenueCat without a Wearvia account, name, email address, or custom profile. RevenueCat assigns an anonymous App User ID and may process Apple receipt data, purchase history, transaction and entitlement state, device or operating-system information, IP-derived information, and SDK diagnostics to provide the service and prevent fraud. Wardrobe photos, garment metadata, outfits, trips, and backups are not sent to RevenueCat.

Eligible free users may see a Google interstitial only after a garment, outfit, or trip has safely saved and the app has returned to the resulting screen. The app requires at least five minutes before the first eligible presentation and at least five minutes after a successful presentation. Wearvia has no banner, rewarded, native, or app-open ads. Active Wearvia Plus users do not receive ad requests.

Wearvia uses Google's certified User Messaging Platform consent form in regions where Google reports that privacy choices are required, including the European Economic Area, United Kingdom, and Switzerland under the published message configuration. That Google form is separate from Apple's App Tracking Transparency permission. Wearvia requests an update to Google's consent information on relevant launches and does not initialise or load Mobile Ads until Google reports that ads can be requested.

After onboarding reaches the real Today screen, Wearvia completes any required Google form, waits for the app and native presentation stack to settle, and may then request Apple's tracking permission once if the system status is still undetermined and the applicable Google choices permit that path. Mobile Ads is initialised only after this decision. No garment, outfit, or trip save is required to reach the permission, and completed-save advertising boundaries never request Google privacy choices or Apple tracking permission. Personalised advertising is permitted only when the applicable Google choices allow the required personalised-ad purposes and Apple reports tracking authorisation. Wearvia does not force personalisation or use another identifier to work around an Apple denial.

If you refuse or partially grant Google choices, deny or restrict Apple tracking permission, disable system-wide tracking requests, encounter an unavailable or failed form, or otherwise leave an uncertain state, Wearvia explicitly requests non-personalised treatment when Google permits it. Google may instead provide limited or technical delivery, return no fill, or prohibit the request; Wearvia then skips the ad. Refusal never removes, delays, or disables a core Wearvia feature.

When Google reports that privacy options are required, Settings → Privacy & Data shows Privacy Choices and opens Google's current privacy-options form. Apple's tracking permission can be changed separately in iOS Settings → Wearvia. Active Plus users receive no Wearvia ad requests and, once entitlement is known, no unnecessary UMP or ATT prompt.

Personalised, non-personalised, and limited advertising can all involve Google data processing. Depending on consent, ATT status, region, device settings, provider configuration, and the installed SDK, Google may process IP-derived coarse location, device or advertising identifiers, advertising data, product interactions, crash data, performance data, and other diagnostics for ad selection or delivery, personalisation when authorised, frequency limits, measurement, aggregated reporting, security, fraud prevention, and SDK operation. Wearvia does not send wardrobe photos, garment metadata, outfit contents, trip details, notes, prices, or wear history to Google and does not use advertising data to build a wardrobe profile.

If you email support, the operator receives the email address, message, and attachments you choose to send. Do not send passwords, Apple credentials, payment details, precise location, or unredacted personal images unless essential. Support correspondence is retained only as reasonably needed to respond, protect the service, resolve a dispute, or meet legal obligations.

App-controlled wardrobe records remain locally until you edit, archive, or delete them. Wearvia can create a portable backup containing local database records and Wearvia-managed files. A restore replaces applicable local records after your confirmation. Purchase access is refreshed independently from RevenueCat and is not granted by a backup file.

Deletion removes associated Wearvia-managed records and files according to the app's safe-deletion process. It cannot remove an original Photos item, a file exported elsewhere, Apple transaction history, provider-controlled records, or data retained in an iOS backup. Deleting Wearvia removes its app-container data subject to normal iOS and backup behaviour.

There is no Wearvia account or cloud wardrobe to search. Contact the operator for applicable privacy requests concerning support correspondence, and the relevant provider for records it controls.

Apple, RevenueCat, and Google may process information in countries other than your own under their terms, safeguards, and privacy policies.

Wearvia is a general-audience wardrobe utility and is not directed to children. Its advertising configuration is marked as not child-directed and not under-age-directed. If you believe a child provided personal information through an optional support message, contact the operator.

Wearvia uses iOS app storage and platform security controls, but no storage method is risk-free. Protect your device, review export destinations, remove personal details from support screenshots, and keep independent copies of records you cannot afford to lose.

You can use Wearvia without an account, decline Camera, Photos, Location, Google advertising choices, or Apple tracking permission, use manual weather, edit or delete local records, export a backup, restore eligible App Store purchases, reopen regional Google privacy choices when required, change Apple tracking permission in iOS Settings, and stop Wearvia ad requests by activating Wearvia Plus. Declining advertising personalisation or tracking does not remove access to core features. Rights concerning provider-controlled information depend on applicable law and the provider's process.

This policy may change when Wearvia's features, providers, configuration, or legal obligations change. The effective date identifies the latest published version. Material changes should be reflected in the app, public page, App Store privacy answers, and release evidence before submission.

For privacy questions or applicable access, correction, or deletion requests about operator-controlled support correspondence, contact Batuhan Tomo.