Your request information has a specific job.

Information this site handles

Repair details you provide

Your name, mobile phone number, email address, device and repair selections, preferred visit information, and any issue description you choose to submit.

Repair workflow records

A confirmation number, request and status history, and the operational information needed to review, communicate about, and coordinate the requested service.

Product and store inquiries

Your name, mobile phone number, email address, preferred reply method, selected product and configuration details, and any optional question you choose to submit, together with a reference number and processing status.

Website support conversations

The messages you send, store replies, the topic you select, message times, and any email address or phone number you provide for follow-up. A browser cookie connects you to your saved conversation.

First-party site counters

Cookieless daily totals for public page paths and a small allowlist of site actions and categories. Page views may also increment short-lived five-minute buckets containing approximate city, region and country, coarse device, browser and operating-system families, a referral category, and safe campaign labels. Raw event rows and persistent visitor identifiers are not stored.

Optional Google Analytics

Only after you opt in, Google Analytics 4 may use analytics storage and cookies to measure normalized page paths and page labels, limited repair, product inquiry and support chat actions, recognized public search or social referrer origins, and browser or device information collected by Google. Advertising storage, Google Signals, and ad personalization remain off.

Why request information is used

Request information is used for purposes connected to the repair or inquiry and store operation. It may move through the systems used to save the request, create a reference, communicate with you, and coordinate follow-up with the store team.

• Save and review a repair request or product inquiry.
• Create the reference and status information connected to that request.
• Let the Beltsville store communicate about the selected item or service and appropriate next steps.
• Send service text messages about a repair you requested, when you provided a mobile number.
• Route pending store inquiries through the authenticated KayLink/POS sync used by the store team.
• Let authorized store staff read and reply to website support conversations through KayLink/POS.
• Operate, maintain, and understand the request experience.

Contact about repairs and product inquiries

If you provide a phone number and email address with a repair request, Wireless Vision may use those details to respond to the request, coordinate an assessment, and share timing or next steps. The request form sends its confirmation and private status link to the email address you provide.

Text messages

When you give Wireless Vision a mobile number — on the repair request form on this site, or in person at the Beltsville store — you agree that the store may send you text messages about that repair. The consent language appears with the phone field on the request form and again on the review step before you confirm.

These are service messages tied to a repair you asked for: that the request was received, that the device is ready for pickup, that a device was picked up, and reminders about a balance owed. Wireless Vision does not send marketing, promotional, or advertising text messages, and does not text numbers that did not give the store a number for a repair.

Message frequency varies with the repair. Message and data rates may apply. Reply STOP to any message to stop future texts, or HELP for help. You can also call the Beltsville store at (301) 595-1877. Opting out stops the texts only — it does not cancel your repair, and the store will still reach you by phone or email.

Wireless Vision does not sell, rent, or share your mobile number or text-message consent with anyone for marketing purposes. Your mobile number is shared only with the messaging provider that delivers the message on the store's behalf.

Product inquiries and contact records

For a product inquiry, Wireless Vision uses the name, phone number, email address, and reply preference you provide to respond about the selected item or configuration. Choosing text as the reply method asks the store to reply by text; it is not enrollment in automated marketing messages. A product inquiry does not place an order, reserve an item, or charge you.

The website saves the inquiry in MongoDB with the selected product details, optional question, reference number, processing status, and operational anti-duplicate fields. Pending inquiries are available only through the authenticated KayLink/POS sync used by the store, and the POS can acknowledge an imported inquiry. An operational staff alert contains the product name, your name and phone number, and the reference number so the store can follow up.

Wireless Vision does not buy, rent, or import phone-number lists and does not sell, rent, or share repair or inquiry contact details for another party's marketing. To update the contact information on a request, call the Beltsville store at (301) 595-1877.

Website support chat

When website support is enabled, an essential cookie called wv_support_session connects this browser to its conversation. The cookie lasts up to 30 days unless you clear it sooner. It is HttpOnly, so page scripts cannot read it, and is separate from optional analytics cookies. Clearing it or using another browser may prevent you from reopening the same conversation.

Messages you send, staff replies, your selected topic, message times and read status, and any contact details you choose to provide are saved in the website database. Authorized store staff use the conversation through KayLink/POS to answer your question and follow up. You can start a chat without providing contact details. If no employee has taken the conversation after two minutes, you can choose email follow-up and provide an email address for the store to respond. Your question and email remain available to the store team in KayLink/POS; staff handle email follow-up manually. Please do not send passwords, payment details, or account PINs.

The conversation and its contact details are scheduled for automatic deletion 30 days after the latest message from you or the store. Each new message restarts that 30-day period. Expired conversations are no longer available through chat, although database cleanup can occur later than the scheduled expiration.

Chat does not send message text or contact details to Google Analytics or the site counters. Staff email and text alerts identify the conversation and may include its topic; they do not include the message text or your contact details. Short-lived request counters help limit misuse of the chat service.

During a live conversation, chat sends a temporary typing indicator so you and the store can see when the other person is writing. This indicator does not contain the draft text and expires after a few seconds without another typing update.

Text you have not sent stays only in this page's memory. Reloading the page clears an unsent draft. A message whose delivery is not yet confirmed may already have reached the store; chat checks the saved conversation before clearing that draft.

Embedded store map

The store page first shows a map preview hosted by Wireless Vision. That preview does not contact OpenStreetMap.

If you select Load interactive map, your browser requests the embedded map directly from OpenStreetMap. OpenStreetMap can receive technical request information such as your IP address and usual browser or network headers. The embed uses a no-referrer policy, so Wireless Vision instructs the browser not to send the store-page address as the referrer.

Wireless Vision does not remember your map-loading choice, and selecting the load button does not create a Wireless Vision analytics event. OpenStreetMap Foundation publishes the privacy policy for OpenStreetMap services.

Website measurement and your choices

First-party, cookieless counters

Wireless Vision uses basic counters by default to understand which public pages are useful, where repair, product inquiry and support flows need attention, and whether the site is working reliably. Each accepted event immediately increments a daily aggregate. The counter accepts only the UTC day, an allowlisted event name, a normalized public page path, and relevant safe categories such as repair step, brand, issue type, action location, or error category.

An accepted page view may also increment a five-minute context bucket. That bucket can contain the normalized page path, approximate city, region and country supplied by the site host, coarse device, browser and operating-system families derived from the request, a referral category, allowlisted campaign labels, and a count. Likely automated crawlers are excluded from visitor alerts. The bucket has no visitor or session identifier and cannot connect activity across buckets or visits.

These counters do not use analytics cookies and do not store raw event rows, IP addresses, exact coordinates, postal codes, full browser user-agent strings, persistent browser or device identifiers, full referrer URLs, full URLs, query strings, URL fragments, names, phone numbers, email addresses, repair notes, inquiry questions, chat messages or chat session, conversation and message identifiers, device serial or IMEI numbers, or confirmation and status codes.

Saved repair and product inquiry counters are created only after a new request is saved. Support counters measure deliberate widget opens, newly saved conversations, and the first saved choice of email follow-up. Replayed requests, continued or reopened chats, and repeated email choices do not create additional saved-action counts. Repair counters include only the canonical device brand and repair category; product inquiry and support saved-action counters have no additional parameters. Support saved-action totals use a sitewide page bucket. These signals do not establish a completed repair, sale, or delivered email. Your browser opt-out or supported privacy signal is carried with the request as a non-identifying instruction not to create that counter. Requests and support chat continue to work when analytics is off.

To limit automated abuse, the intake briefly converts the network address supplied by Vercel into a secret-keyed rate-limit token and stores it in a separate short-lived abuse-prevention record scoped to one short time window. The raw address is discarded. The token is used only to count requests from the same network address during that window, is never joined to the daily aggregate counters, and is scheduled to expire within two minutes.

You can opt out of future first-party measurement using Privacy & analytics in the footer. A browser Global Privacy Control or Do Not Track signal is also treated as an opt-out. Because accepted events are immediately combined into totals without a visitor identifier, Wireless Vision cannot locate or remove one person’s event from an existing daily aggregate.

Optional Google Analytics 4

Google Analytics 4 is off unless you choose to allow it. If enabled, GA4 may receive normalized page paths, normalized page labels, allowlisted repair, product inquiry, support chat and call actions, recognized public referrer information, and browser, device, or network information collected by Google. Same-site referrers are reduced to a normalized public path. A small explicit list of recognized public search and social referrers is reduced to a canonical origin; all other external referrers, including unknown, local, private, and reserved hosts, are omitted. Analytics storage is enabled only after that opt-in, so Google may create analytics cookies and visitor or session identifiers. Advertising storage, Google Signals, and ad personalization remain off. Wireless Vision does not send Google names, phone numbers, email addresses, repair notes, inquiry questions, chat messages or chat session, conversation and message identifiers, device serial or IMEI numbers, confirmation or status codes, product slugs, unknown raw paths, query strings, or URL fragments.

Your choice persists across visits only when browser storage is available and the preference can be saved or removed. If a preference cannot be saved or removed, the change is guaranteed only for the current page session; a later visit uses the last valid preference successfully stored in this browser, or the privacy-minimized default if none exists. That default keeps optional GA off while privacy-minimized first-party counters operate unless a supported browser privacy signal turns all measurement off. You can reopen this control at any time to allow or stop future measurement. An opt-out, Global Privacy Control, or Do Not Track signal sets Google's documented property-disable flag, returns analytics storage to denied, removes Google Analytics cookies created by this site, and stops this site from sending later GA4 events; a request already in flight may finish.

Who handles measurement

Wireless Vision controls the first-party counter and decides its limited purposes. MongoDB hosts the database containing the daily aggregate totals and short-lived five-minute context buckets. Vercel hosts this website and necessarily handles network delivery information needed to serve pages and counter requests. Wireless Vision writes only Vercel's coarse city, region and country labels into an enabled context bucket, not the raw network address or exact coordinates.

Google provides GA4 and receives analytics information only when optional GA4 is allowed in this browser. Google does not operate or receive the Wireless Vision first-party counter records.

Retention and requests

Raw first-party analytics events are retained for zero days because no raw event rows are created: an accepted event increments one or more aggregate buckets within the request and is not stored separately. Five-minute visitor-context buckets are scheduled for automatic deletion after seven days. Daily aggregate counters are scheduled for automatic deletion about 400 days after the UTC day they summarize; database cleanup can occur later than each scheduled expiration. Optional GA4 loads only after you allow it in this browser. The current GA4 property retains user- and event-level data for 14 months; information already combined into Google’s aggregate reports may persist longer.

Repair information follows a separate retention schedule and may be kept while needed to provide service, maintain business records, resolve a dispute, protect the request and status tools, or meet an applicable obligation.

The website's MongoDB copy of a product or store inquiry is assigned an expiration date under the configured service-request retention schedule and is scheduled for automatic deletion; database cleanup can occur later than the scheduled expiration. A request imported into KayLink/POS is a separate store business record and may be kept while needed to respond, maintain records, resolve a dispute, or meet an applicable obligation.

Depending on where you live and the law that applies, you may have rights to ask about, access, correct, or request deletion of personal information. This notice does not determine which rights apply to a particular request. The store can review the request and explain if some information must be retained.