Skip to content
ELVYA
The appHow it worksThemesJournalAbout
Join the waitlistJoin
The appHow it worksThemesJournalAbout
Join the waitlist

Legal

Privacy Notice

What Elvya collects, why it is used, where it goes, how long it is kept, and the controls available to you.

Version
2026-10-13
Effective
13 October 2026

On this page

  1. Scope
  2. Controller and contact
  3. The public website
  4. Data and sources
  5. Purposes and legal bases
  6. Required and optional data
  7. Photos, likeness, and AI
  8. Recommendations and profiling
  9. Optional analytics
  10. Optional App Store refund assistance
  11. Essential telemetry and local device data
  12. Recipients and processors
  13. International transfers
  14. Retention and deletion
  15. Export and erasure coverage
  16. Your rights
  17. Security, complaints, and changes

Scope

This notice explains how Elvya handles personal data in the mobile app, the public website, and related backend services.

Controller and contact

Elvya is the service name used by the controller for account, profile, wardrobe, recommendation, purchase, and privacy-settings data. Contact privacy@updates.elvya.live to exercise privacy rights or ask for the controller, DPO, or representative details applicable to your location.

The public website

The public website does not create app accounts or accept wardrobe uploads. If you join the waitlist, it sends your email address, selected language, and signup location on the website to Resend so Elvya can record your request and send launch or product updates. The site also stores the app theme you preview on the Themes page in your browser's local storage. It does not configure analytics, advertising, or cross-site tracking. See the Cookie Notice for the website-specific storage summary.

Data and sources

Elvya receives data you provide, including account details, optional style and sizing fields, city or coarse location, wardrobe and likeness photos, product links, outfit plans, feedback, and privacy choices. Elvya also generates garment metadata, recommendations, style memory, body-measurement estimates, avatars, try-on outputs, operation records, and security logs. Apple or Google supplies verified purchase, subscription, refund, and opaque transaction identifiers. The app and backend create session, device, local-cache, diagnostic, and optional analytics data.

Purposes and legal bases

Account, wardrobe, planner, store-purchase, and requested recommendation processing is necessary to provide the service or take steps you request. Waitlist and related launch or product emails rely on the consent you give when submitting the website form; you can withdraw it through the unsubscribe link in any update. In this version, face, body, likeness, avatar, and try-on AI processing starts only after separate optional consent. Optional product analytics relies on consent. Security, fraud and abuse prevention, essential debugging, minimized operational telemetry, and pseudonymous measurement of recommendation quality and provider cost rely on legitimate interests, subject to documented balancing assessments. You may object through Privacy Settings. Elvya may also keep records where a legal obligation applies.

Required and optional data

An email, password, Terms acceptance, and 18+ confirmation are required to create an account. Profile presentation, height, sizing, location, wardrobe, likeness, notifications, and analytics are optional. The app asks for camera, photo-library, location, or notification permission only when you choose a feature that needs it. You can revoke operating-system permissions, but the related feature may stop working.

Photos, likeness, and AI

Wardrobe photos may be analyzed to isolate garments and infer descriptive metadata. If you separately consent to likeness features, selected face or full-body references, height, measurements, garment images, and generated outputs may be sent to AI image or body-processing providers. Uploaded images are normalized and metadata such as EXIF is removed before storage. Original face and full-body references are kept until you delete them or your account so Elvya can reuse them for avatar, garment-preview, and try-on generation. Elvya does not use this workflow for face recognition, identity verification, cross-user matching, or health diagnosis. AI-generated measurements, avatars, recommendations, and try-on images are estimates, not guarantees of fit, availability, or exact likeness.

Recommendations and profiling

Elvya uses wardrobe metadata, profile preferences, feedback, dismissals, impressions, weather context, and style memory to rank outfit and styling suggestions. Shop uses your stated department, sizes, styles, favourite colours and your closet's colours and fit to choose and order products from live Shopify results inside Elvya. These recommendations do not make legal or similarly significant decisions about you.

Optional analytics

Optional analytics is off until you choose to enable it. When enabled, Elvya sends allowlisted product events to PostHog: the app sends navigation and user-intent events, while the backend sends confirmed purchase and generation outcomes for current clients. Each event has one owner. PostHog does not receive crash reports, replay, raw logs, trace or request identifiers, wardrobe or likeness images, prompts, shopping links, filenames, measurements, precise location, arbitrary error messages, or stack traces. Autocapture, error capture, performance capture, GeoIP enrichment, advertising, and cross-app tracking are disabled. Withdrawal stops PostHog capture and removes obsolete queued compatibility analytics without disabling the service.

Optional App Store refund assistance

This choice is off by default and separate from analytics. If you enable it and Apple asks Elvya to assist with an App Store refund request, Elvya may send Apple the transaction identifier, whether the purchase was delivered, and the percentage of the purchase already consumed. Apple uses this information to inform its refund decision under its own terms. You can withdraw this permission at any time in Privacy Settings without losing app access or paid features; withdrawal does not affect information already shared while permission was active.

Essential telemetry and local device data

Elvya keeps minimized operational logs and traces needed to secure and operate the service. Production telemetry is designed to use route templates, request or operation correlation, status class, duration, exception type, and a sanitized error slug rather than raw user identifiers, URLs, messages, or stack traces. On your device, authentication tokens use protected storage; recreatable read models and media use cache storage; durable offline changes use app-support storage; and app-owned upload or export copies use managed temporary storage that is cleaned after the action and on sign-out or deletion. Sign out and clear device removes the signed-in session, local caches, queued data, and analytics identity but does not delete the server account.

Recipients and processors

Depending on the feature you use, recipients include Supabase for authentication, database, private storage, and an isolated aggregate-vector foundation; Google Cloud, including BigQuery in the EU, for pseudonymous recommendation-quality and provider-cost analysis; Resend for email delivery; OpenAI for image, metadata, body-estimate, and recommendation tasks; fal.ai for garment segmentation or configured body processing; PostHog for optional product analytics; Sentry for mobile crash diagnostics; Honeycomb through OpenTelemetry for minimized backend traces and aggregate metrics; WeatherAPI.com for weather requests; Shopify for Shop, which receives your search words or Elvya's words for a category or a garment, a department, size, price limit and delivery country, and, when Shop looks for pieces like a garment, one cut-out image of that garment (never a photo of a person): one of your own pieces, or a garment you can see in Explore in someone's look or closet, including automatically while you browse Community, so the pieces you publish in looks or show in your closet can be sent too; Shopify never receives your name, email or account identifier, and the shop you buy from receives what you enter at its own checkout; and Apple or Google for store billing. The aggregate-vector foundation is empty and disabled and does not receive personal or per-user vectors. With separate optional permission, Elvya may also send Apple purchase delivery and consumption information to assist with an App Store refund decision. Apple and Google process billing under their own terms and privacy notices. Elvya also uses TypeSafe to detect and describe garments in photos you add, describe looks, read product pages you add by link, and interpret the styling briefs you type in Studio and the planner; Google Vertex AI to create garment image embeddings; Firebase Cloud Messaging and Apple Push Notification service to deliver notifications; Google Cloud to host the backend, including Memorystore Redis; and Cloudflare to host the public website and rate-limit waitlist requests.

International transfers

Some providers may process data outside your country or the EEA. The provider region and transfer safeguard depend on the configured service and applicable contract. Contact privacy@updates.elvya.live for the safeguard relevant to your processing and how to obtain a copy. Elvya must verify the applicable vendor and transfer assessment before offering the affected processing in a new market.

Retention and deletion

Account, profile, wardrobe, outfit, planner, likeness, purchase, and style-memory records are generally kept for the account lifetime unless you delete them earlier or law requires a limited record. Recommendation candidate facts are kept 90 days; candidate diagnostic traces and detailed snapshot traces 7 days; impressions 30 days; feedback 365 days; and pseudonymous recommendation-quality and provider-cost warehouse facts 365 days. Backend usage events and daily aggregates are kept 365 days; current weather contexts one hour; weather forecast caches up to 24 hours; terminal operations and processing jobs 30 days; processed outbox records 14 days; failed or dead-letter records 7 days; expired or revoked sessions 90 days; password-reset tokens 7 days; and privacy export ZIPs 7 days. Release targets are 12 months for optional PostHog product analytics and 30 days for Honeycomb telemetry and Google Cloud application logs; those live vendor settings require authenticated verification before release. Crash diagnostics follow the period enforced by the active Sentry plan; no fixed period is claimed until it is verified. Consent and rights IP address and user-agent fields are removed after 30 days; minimized legal records remain only as long as needed to demonstrate compliance or handle legal claims.

Waitlist email addresses are kept until you unsubscribe or the waitlist closes, subject to any limited record required for compliance.

Export and erasure coverage

A complete export is prepared as a ZIP containing classified account records, owned media, PostHog subject data, subject-linked pseudonymous BigQuery rows, checksums, exclusions, and a processor-coverage manifest. The server bundle expires after 7 days, each download link after 15 minutes, and the app deletes its temporary local copy after sharing. Delete Likeness Data removes likeness references, inferred measurements and body type, avatars, likeness assets, and user-specific try-on outputs while keeping unrelated wardrobe originals, outfits, user-supplied height, and sizing. Account deletion deactivates access and queues deletion from PostHog, BigQuery, Redis, Supabase Auth, account rows, and private storage. Required cloud logs, backups, and retention-only telemetry may remain until their fixed lifecycle expires.

Your rights

Depending on your location, you may have rights to be informed, access data, correct it, erase it, restrict processing, receive portable data, object to certain processing, and withdraw consent without affecting earlier lawful processing. In Privacy Settings you can correct your profile details directly in Profile, export your personal data as a ZIP, delete likeness data, withdraw optional analytics, and request account deletion, which revokes access at once and starts server-side deletion. Requests for access details, for correcting data you cannot edit in Profile, for restriction, and for objection are submitted for review: the privacy team assesses each one, and processing is not paused or stopped until the request is assessed and applied. Elvya does not use the described recommendations to make legal or similarly significant decisions about you.

Email privacy@updates.elvya.live if you cannot use the in-app controls. For the external account-deletion path, see Request account deletion.

Security, complaints, and changes

Elvya uses access controls, private storage, short-lived signed URLs, transport encryption, redaction, and scoped service access to protect personal data. Elvya aims to respond to verified privacy requests within one month unless a lawful extension applies. You may complain to the data-protection authority where you live, work, or believe a violation occurred. Material notice changes will receive a new version and, where required, an in-app notice or renewed choice.

ELVYA
The appHow it worksThemesJournalAboutJoin the waitlist
SupportPrivacyTermsCookies

Elvya may earn a commission when you buy through links in Shop. Products are sold by the retailer, which sets prices and availability.