Skip to content
Our appsAbout us
Support
All apps & documents
Wearvia

Privacy policy.

How Wearvia handles local wardrobe records, optional weather, purchases, consent-based advertising, export, and deletion.

Privacy policyApp supportTerms of use
Effective date
October 19, 2026
Application
Wearvia for iOS and Android
Operator
REKL0W LTD
Account
Not required
ON THIS PAGE
01Scope02On-device wardrobe03Camera and Photos04Location and weather05Wearvia Plus purchases06Advertising, regional privacy choices, and Apple tracking permission07Optional offers and store reviews08Support messages09Export and deletion10Service providers11Children12Security13Choices and rights14Changes and contact
01

Scope

Wearvia is operated by REKL0W LTD. Contact: [email protected].

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

Information stored only on your device is not available to the operator. Apple, Google, RevenueCat and, for optional Android weather, MET Norway may process the limited information described below. Android availability and purchase products depend on the current Google Play release.

02

On-device wardrobe

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 backup records in app-managed storage on your device. The deterministic outfit engine uses only garments and details in your Wearvia closet.

Background removal and manual erase/restore run on your device: Apple Vision on iOS and OpenCV-based processing on Android. Garment images, masks, outfit contents, trip details, notes, prices and wardrobe history are not sent to a Wearvia server, advertising provider or cloud AI service.

iOS device backups may include app-container data according to your Apple backup settings. The current Android release disables automatic app backup. A portable Wearvia backup is created only when you request it and is handled by the destination you select.

03

Camera and Photos

Wearvia requests Camera permission only when you choose to photograph a garment. The iOS or Android system photo picker provides the images you deliberately select; Wearvia does not scan your photo library in the background or require broad photo-library access on Android.

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

04

Location and weather

Location is optional and is not requested during onboarding. Only when you ask for local weather does Wearvia request foreground approximate location. You can decline it and enter weather conditions manually without losing a core feature.

On iOS, a one-shot Apple WeatherKit request provides current conditions. The native iOS module does not return coordinates to Wearvia's JavaScript layer. The weather card displays Apple Weather attribution and its legal data-source link. Apple may process location, network, device and request information under its terms.

On Android, Wearvia uses approximate foreground location, rounds latitude and longitude to two decimal places, and sends those rounded coordinates directly over HTTPS to MET Norway's locationforecast service. No Wearvia weather proxy or background location tracking is used. MET Norway receives the rounded coordinates, IP address and normal request information needed to serve the request. Wardrobe photos and trip details are never sent with weather requests.

Wearvia caches only derived conditions for approximately thirty minutes, not a coordinate history. Attribution and a source link identify the active weather provider. You can revoke location in your device's app-permission settings and continue manually. Weather is not a safety-warning service.

05

Wearvia Plus purchases

Apple handles App Store purchases; Google handles Google Play purchases when offered. Wearvia does not receive your payment-card or bank details. RevenueCat supplies localised product availability, purchase, entitlement, restore and limited offline-entitlement functionality for Wearvia Plus.

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

Use the account and store that made the purchase to restore access. Local backups do not grant Plus or transfer a purchase between Apple and Google Play.

06

Advertising, regional privacy choices, and Apple tracking permission

Eligible free users may see a Google banner at the end of Today, in the normal scroll layout below the content, and one Google interstitial only after a garment, outfit or trip has safely saved and the save screen has dismissed. Interstitials require at least five minutes before the first eligible presentation and at least five minutes after a successful presentation. Wearvia has no rewarded, native-format or app-open ads. Active Wearvia Plus users receive no ad requests, preload or Mobile Ads initialisation once entitlement is known; unresolved entitlement also prevents ad startup. Banners are withheld during work, permission or purchase flows, uncertain consent and offline conditions, and never cover app controls.

Wearvia requests an update to Google's User Messaging Platform (UMP) consent information on relevant launches. When Google requires regional privacy choices, its certified European regulations form covers the European Economic Area, United Kingdom and Switzerland under the app-specific message configuration. Mobile Ads is not initialised and ads are not loaded until UMP permits requests. A form error, unavailable form or offline state never blocks wardrobe features.

Apple's App Tracking Transparency (ATT) permission is separate and applies only on iOS. After onboarding reaches Today, Wearvia completes any required UMP form, waits for the app and native presentation stack to settle, and may request ATT once if it is undetermined and the applicable Google choices permit the personalised path. Android does not display Apple's ATT permission. Save boundaries never request UMP or ATT; they only consider an already prepared ad.

Personalised advertising is eligible only when the applicable Google choices permit it and, on iOS, Apple tracking authorisation is also granted. Wearvia does not override UMP choices, fabricate an age or use another identifier to evade an Apple denial. Refusal, partial consent, iOS tracking denial or restriction, disabled tracking requests, form error or uncertainty triggers explicitly requested non-personalised treatment when Google permits requests. Google may serve limited or technical ads, return no fill or prohibit the request, in which case Wearvia skips the ad. Refusal never removes, delays or disables a core feature.

When Google reports privacy options are required, Settings → Privacy → Privacy Choices opens the actual UMP privacy-options form. The row is hidden when no server-delivered form applies. Apple tracking permission can be changed independently in iOS Settings → Wearvia; Android advertising-ID controls are provided by Android Settings. Privacy choices are not a Plus feature. Confirmed Plus users are not prompted unnecessarily.

Personalised, non-personalised and limited ads can all involve Google processing. Depending on consent, device settings, region and SDK configuration, Google may collect and share IP-derived approximate location, advertising/device identifiers, app and advertising interactions, crash/performance information and diagnostics for advertising, measurement, aggregated reporting, security, fraud prevention and SDK operation. Wearvia does not send garment photos, names, closet searches, outfits, trip details, notes, prices or wear history to Google, and does not use ad data to build a wardrobe profile.

07

Optional offers and store reviews

After actual first-run onboarding completion, eligible free users may see the existing dismissible Plus screen once when products, connectivity and the presentation surface are ready. Skipping that opportunity also consumes it; replaying onboarding does not reset it. This choice does not gate the free app.

Wearvia keeps a small on-device record of unique successful actions and review-attempt timing to avoid premature or repeated native store-review requests. These records are not sent to the operator or an analytics service and do not contain a rating or review result. Apple or Google controls whether its native review sheet appears and processes any review you choose to submit. Wearvia does not screen for positive opinions, reward reviews or read your rating. Network availability is checked on-device to avoid presenting unavailable optional services; Wearvia does not request your IP address through this check.

08

Support messages

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.

09

Export and deletion

App-controlled wardrobe records remain local until you edit, archive or delete them. Wearvia can create a portable backup of local database records and app-managed files. Restore replaces applicable local records after confirmation. Purchase access is refreshed separately through RevenueCat and the purchasing store, never imported from a backup.

Deletion removes associated Wearvia-managed records and files. It cannot remove original Photos or gallery items, independent exports, Apple or Google transaction history, provider-controlled records or data retained in a device backup. Uninstalling Wearvia removes local app-container data subject to normal platform behaviour.

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

10

Service providers

Apple, Google, RevenueCat and MET Norway may process service information outside your country under their terms, safeguards and privacy policies. The app does not add a separate analytics or crash-reporting SDK.

Apple Privacy Policy RevenueCat Privacy Policy Google Privacy Policy Google partner data MET Norway privacy MET Norway licensing and crediting
11

Children

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.

12

Security

Wearvia uses app-managed storage and iOS/Android platform security controls. Weather and purchase/ad service connections use HTTPS; Android Release disallows cleartext network traffic. No storage or transfer method is risk-free. Protect your device, review export destinations, redact personal support screenshots and keep independent copies of important records.

13

Choices and rights

You can use Wearvia without an account; decline optional Camera, Photos, Location, regional Google choices or iOS tracking permission; set weather manually; edit/delete local records; create or restore your own backup; restore eligible purchases through the purchasing store; and reopen regional Google privacy choices when required. Apple tracking permission and Android advertising-ID controls are managed separately in device Settings. Plus removes Wearvia ad requests but is not required to refuse personalisation. Rights concerning provider-controlled information depend on applicable law and the provider's process.

14

Changes and contact

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 REKL0W LTD.

[email protected]
SOURCE RETRIEVED2026-10-19
View published source
All apps & documentsBack to rekl0w
DISCOVER OUR PRODUCTSMade for your day.

Explore our applications and find the tools that fit your everyday life.

Product support

Support & privacy

Find help, privacy policies and terms for each application.

Company enquiries

[email protected]

Questions about REKL0W LTD or our products? Get in touch.

Company details

REKL0W LTD · Registered in England and Wales

Company number 17488283

Registered office · 8/A Greenwood Grove, Reklow Office, Marcham, Abingdon, England, OX13 6FR

REKL0W LTD · United Kingdom
Back to top
© 2026 REKL0W LTDSupport & privacy

Apple and the Apple logo are trademarks of Apple Inc. App Store is a service mark of Apple Inc. Google Play and the Google Play logo are trademarks of Google LLC.