Privacy policy

Effective date: October 22, 2026
Operator: Megan Rustigian, doing business as VOÛTE
Mailing address: 528 SE Fascino Cir, Port Saint Lucie, FL 34984
Privacy contact: hello@voûte.com

1. Scope

VOÛTE is preparing to launch. This website currently provides product information and a launch-notification signup. The mobile-app sections below describe the pre-release app.

This policy explains information processed through VOÛTE’s website, mobile app, product searches, saved finds and support. The current app does not require a VOÛTE account. A search uses external services; processing does not take place entirely on your device.

2. Photos and product searches

When you submit a photo, the app sends the cropped image for analysis. Before transmission, the app redraws the image to remove embedded camera and location metadata. VOÛTE does not request device location permission. Removing metadata does not remove personal information visible in the photograph, such as faces, documents or an identifiable location. Avoid including unnecessary information about yourself or other people.

Search processing includes detecting bags, watches, clothing, jewelry, shoes and accessories, including visible pieces in a whole outfit, identifying and comparing likely products, conducting photo-assisted web searches, and finding listings. We also process the brand, model, visual attributes, typed references or other search terms needed for your request, together with candidate matches and results. Product descriptions and matches derived from an image may be inaccurate.

Viewing product listings or alternatives, including reopening a saved find, can send a smaller copy of the cropped photo to the backend again for matching. Product-history requests send product details without the photo. The app sends photo data inside requests and does not create a publicly accessible link to your uploaded photo. No photo is sent before you choose “Agree and continue” on “How your photo is used.” The consent-update TestFlight release asks holders of an older consent version to review the materially updated explanation before their next upload. This permission covers processing for your search; it does not authorize keeping your photos to develop or train VOÛTE’s systems. See Help improve VOÛTE below.

3. Where search information goes

VOÛTE uses third-party AI and search services to identify items and find relevant products. Our own catalog and curated recommendation service are being developed separately; they do not currently replace the search pipeline. This service does not make your submitted photo available through a public catalog or API.

The cropped photo passes through VOÛTE’s backend, hosted on Cloudflare through Rork, to Rork’s AI service and the Vercel AI Gateway. Depending on the task and fallback, OpenAI models perform category detection and photo-assisted web search; Anthropic models perform identification and visual comparisons; Google models provide a fallback. Not every request reaches every model or hosting provider.

Model-serving infrastructure may include OpenAI or Microsoft Azure for OpenAI models; Anthropic, Amazon Bedrock or Google Vertex for Anthropic models; and Google Vertex for Google models. These are possible processing routes, not a statement that every provider receives every photo. We are still confirming the routing and retention settings applied by Rork’s proxy.

For visual comparison, retailer images may be supplied alongside your crop to the relevant AI service. Experimental integrations such as SerpApi/Lens, Google Cloud Vision, SearchApi and eBay are not active recipients of customer photos in the current customer search routes.

Our AI requests ask the gateway to use zero-data-retention routing, and applicable OpenAI requests disable response storage. Public gateway endpoint information lists compatible routes. However, we have not verified that Rork’s proxy forwards every setting unchanged or what Rork itself logs or retains. These request settings are not a guarantee of end-to-end zero retention. Infrastructure logs, backups and provider handling are separate from the storage performed by VOÛTE’s application code. We do not claim a universal provider retention period or that all provider processing excludes training.

Provider references: Rork, Vercel, OpenAI, Anthropic, Google, Microsoft, Amazon Web Services, Google Cloud, Exa, wsrv.nl and Cloudflare. These references do not establish the contractual settings applying to VOÛTE.

4. Saved finds and information on your device

Saved finds and their photos are stored on your device. The app also stores search-access information, Terms acceptance, age statements and photo-processing choices on your device. Earlier builds may store only a yes/no consent flag or a local “Help improve VOÛTE” preview preference. That preview preference does not enroll you in photo contributions. In versions supporting contributions, fresh consent and an 18+ confirmation are required; contributed crops are associated with a verified installation on the server as described below. Terms acceptance, photo-processing consent and contribution consent are separate choices. The product-image cache is configured for up to 24 MB in memory and 160 MB on disk. Saved finds, their photos and device settings can be included in iCloud or computer backups according to your settings; the product-image cache is not backed up by the app. Local storage is not the same as an account-based VOÛTE cloud-sync service.

Removing a saved find deletes that find and its associated saved photo from the app’s local storage. A separately cached product image, server result or earlier device backup may remain. Uninstalling removes the app’s local data but does not delete server caches, AI-provider records or previous backups. Restoring a backup may restore information that the backup contains. Manage backups through the relevant Apple or computer settings.

5. Server caches, logs and retention

Photos are processed to perform your search. Separately, in app versions supporting “Help improve VOÛTE,” eligible item crops are saved to develop and train VOÛTE’s search only after you opt in and confirm you are 18 or older, as described below. Without that separate consent, the contribution program does not save your photos. Platform or provider logs and backups are separate from this application-level storage.

Recognition results are cached under a key derived from a fingerprint of the submitted photo, its category and any typed hint. Cached results may include inferred product details, candidates, detected-item regions and source pages, but not the uploaded photo image. A fingerprint is a technical reference, not a guarantee of anonymity.

Recognition-cache entries written since October 14, 2026 schedule deletion at expiry: 24 hours for a clear match and three hours for other cacheable recognition results. No-match results are not stored. Entries written before October 14, 2026 may have no deletion alarm and are removed only when the same item is requested again. Platform backups and point-in-time recovery retention have not been confirmed; cache expiry does not establish deletion from those systems.

Other caches are keyed by product rather than the submitted photo: pre-owned listings have a two-hour freshness window, new listings four hours, alternatives six hours and item details 30 days. Each product-cache entry written since October 14, 2026 also schedules deletion at its expiry. Older entries have no scheduled deletion and are removed when the same item is requested again. These schedules do not establish deletion from platform backups, logs or provider systems.

Photo fingerprints and access records: the backend stores shortened SHA-256 photo fingerprints, up to six per search, within an installation-specific access record. They tie follow-up requests to the original photo. The record is deleted after 180 days without use. It is separate from the shorter recognition-result cache. Although the install record does not require an account name or email, it can distinguish an installation and is not treated as guaranteed anonymous data.

Diagnostic logs include item names, search phrases, page URLs and timings. Application code does not deliberately log photo image data or IP addresses. Text or retrieved content may nevertheless contain personal information. Retention of these logs by Rork and Cloudflare, and separate infrastructure records and backups, has not been confirmed.

Help improve VOÛTE: optional photo contributions

This section describes the contribution feature in app versions that support it. With your separate permission, VOÛTE keeps small crops of searched items to develop, evaluate and train its own search, item-recognition and recommendation systems. Participation is voluntary and is not required to search. Accepting the Terms or allowing photo processing for an individual search does not enroll you.

What is saved: a small item crop, approximately 320 pixels, from eligible photo searches. Location and other embedded photo metadata are removed before saving. Visible personal information may still appear in a crop; avoid contributing faces, documents or other personal details. Each phone can contribute up to 500 photos. Currently, only clothing, shoes and jewelry photo searches contribute crops. Bags, watches and Get the Look do not contribute photos.

Your choice and age: new users must separately select “Help improve VOÛTE” and confirm “I’m 18 or older” during onboarding. Existing users are offered the choice once on the Home screen. Earlier preview preferences do not count as consent to this program, and earlier uploads are not automatically included. The 18+ requirement applies to contributions; ordinary use remains subject to the age requirements in section 10.

Storage and deletion: contributed crops are stored by VOÛTE’s backend and associated with a verified app installation so that they can be located and deleted. Contributions are accepted only when the server can verify the installation as the genuine VOÛTE app. In Settings, choose “Take part” to opt in or “Stop and delete my photos” to withdraw. Withdrawing stops new contributions and deletes all contributed photos associated with that phone’s verified installation. This is separate from deleting a locally saved find. Use this control on each contributing phone; uninstalling the app alone does not submit a contribution-deletion request. Contact us if you cannot access the contributing installation.

Contributed photos are kept for the development and training purposes above until you use “Stop and delete my photos” or VOÛTE removes them. Deleting stored contributions does not undo processing that has already occurred or guarantee removal of their influence from a model already trained on them. Platform backup and log retention remains unconfirmed; the deletion control does not establish deletion from those systems. We may pause new contributions while keeping the deletion control available.

You retain ownership rights you hold in your photos. Participation does not authorize public display, advertising use, sale of your photos or training third-party general-purpose models. Our catalog does not make your contributed photos publicly available. Provider processing for ordinary searches is described separately above.

Product catalog and aggregate listing activity

When product indexing is enabled, VOÛTE saves listings shown in search results to build its product catalog, including retailer, title, brand, price, retailer product photos, stock status and product details. It also records aggregate counts of how often each listing is shown and tapped. These catalog records do not store shopper identities or typed search queries. This describes the product index only; search processing, technical access records and diagnostic logs are described separately above.

Product indexing applies regardless of whether you opt into photo contributions. Retailer product photos in this catalog are separate from the photos you upload. Withdrawing photo-contribution consent deletes your contributed crops, but does not delete retailer listings or aggregate listing counts. The catalog is maintained over time and is separate from the short-lived search caches described above.

6. App services and provider records

Apple provides App Store services. App versions that include RevenueCat process an app-specific identifier, purchase history and receipts, and app, operating-system and locale information for app-access verification. An identifier described by the SDK as “anonymous” can still distinguish a particular app user or installation; it is not treated here as a guarantee of anonymization. In app versions that include RevenueCat, its SDK starts when the app launches, independently of photo consent. VOÛTE’s support inbox does not need your full payment-card information.

Relevant references include RevenueCat’s Privacy Policy and Apple’s Privacy Policy. RevenueCat customer records can be deleted through its dashboard when the relevant record can be identified and the request is appropriate. Provider, purchase and legal records may be subject to separate retention requirements. Removing a feature does not automatically delete previously collected provider records.

7. Retailer content and shopping links

Product images load from retailers or their image-delivery services. Those services receive network information needed to deliver the image, including your IP address. This can happen while viewing results, before you tap a shopping link. Opening a retailer page also connects your device to that retailer and its services. Their terms, privacy practices and choices apply to activity on their sites.

Retailers handle product checkout, delivery, returns and related personal information. VOÛTE does not process the physical-product order. A link or listing is not a promise that the retailer has the same privacy practices as VOÛTE.

8. Technical information, advertising and support

The app does not require an account and does not include analytics SDKs, advertising SDKs or tracking features. The website uses a small first-party script to count page views by UTC day, page and broad referral category (for example, Instagram, Google or direct/unknown). Only these aggregate counts are stored in the website’s Cloudflare D1 database. These first-party analytics records do not contain email addresses, IP addresses, full referring URLs, query strings or visitor identifiers. This first-party script does not use cookies, browser-storage identifiers, fingerprinting or advertising pixels. These counts measure page loads, not unique people, and are not linked to launch-signup records. Aggregate counts are retained to compare traffic over time.

The first-party analytics script skips collection when the browser signals Do Not Track or Global Privacy Control. JavaScript blocking also prevents collection. Hosting services still receive network information needed to serve requests and may separately retain technical logs. Other provider requests and records are described above.

The website also loads an impact.com script for our partner-program setup. The supplied integration requests link transformation and impression tracking. Loading this script connects your browser to impact.com’s infrastructure, which receives network information such as your IP address. This third-party integration is separate from the first-party aggregate counts described above; the cookie-free and browser-signal behavior of our own script does not describe the Impact script. The integration does not explicitly pass launch-signup email addresses to Impact.

When you contact us, we receive your email address, message, attachments and information needed to respond. We use correspondence to provide support, handle privacy or content concerns, investigate problems and meet applicable legal requirements. Relevant information may be shared with a service provider or an affected party where necessary to address the request. Do not send passwords, payment-card details or unnecessary identity documents.

Website launch notifications

If you sign up for a launch notification, we collect your email address, signup date, the signup source and a record of the notice you accepted. We store these records in the website’s Cloudflare D1 database so we can email you when VOÛTE launches. This signup is for the launch notification; it does not opt you into an ongoing newsletter. Email addresses are not displayed publicly.

We use temporary request counters to limit automated form abuse. Where the hosting service supplies an IP address, the form stores a time-windowed hash rather than the raw IP address in these counters. Counter records expire after 30 minutes and are removed during subsequent form activity. Hosting services may separately retain technical logs.

To withdraw your request or ask us to delete your signup, email hello@voûte.com with the subject “Remove from launch list.” We retain the signup until the launch notification has been sent or you request removal, subject to any records we must retain for applicable legal obligations. We may use an email-delivery provider for the launch message; we will update this notice to identify that provider before sending.

9. Choices and deletion requests

You can manage camera and photo-library permissions in your device settings, remove saved finds in the app, and manage device backups through Apple or your computer. Changing a permission does not delete information already transmitted.

You can decline initial photo processing by choosing “Not now.” App versions with the photo-processing withdrawal control in Privacy & Settings let you stop subsequent photo transmissions for searches until you allow processing again. That control does not undo earlier processing, delete cached results or remove provider records. Separately, in versions supporting contributions, choose “Stop and delete my photos” in Settings to withdraw contribution consent and delete the contributed crops associated with that phone’s verified installation. Earlier builds may not have these controls. Camera permission, photo-processing consent and contribution consent are separate. Contact us with questions about prior processing or deletion.

Contact hello@voûte.com to ask about access, correction or deletion. Rights and exceptions depend on applicable law. We may need proportionate information to identify the relevant record and verify a request. Do not send identification documents unless a secure and necessary verification process has been arranged.

Server caches are not indexed by a customer account or email address, and the Service has no email-based mechanism to locate and erase all of a person’s server records. Installation-specific access records and photo fingerprints are separate from product caches. An email address alone therefore cannot identify all relevant cached results or access records. We do not promise that removing a saved find, emailing us or uninstalling will delete every provider record.

Requests concerning information held by RevenueCat must be matched to the relevant provider record. Requests concerning a retailer’s own data may need to be directed to that retailer. Any information retained to meet a legal obligation or resolve a dispute remains subject to applicable limits.

10. Age, security and international processing

VOÛTE is intended for users aged 14 and older. Children under 14 may not use the Service. Users below the age of legal majority need a parent or legal guardian’s permission as described in our Terms; higher local age or consent requirements may apply. If you believe a child under 14 has provided personal information, contact us so we can investigate and take appropriate steps, subject to applicable legal obligations.

No transmission or storage system is perfectly secure. Processing by service providers may take place outside your location. The countries, safeguards and account-specific arrangements for the current service require confirmation; we do not claim that all information stays in the United States.

11. Changes and contact

We will identify policy changes with an updated effective date and provide additional notice or obtain new consent where required. Questions may be sent to hello@voûte.com or the mailing address above. We will update this policy to reflect material changes to our information practices.