A clear view of what we measure.

Analytics run automatically, with an opt-out.

For visitors in the United States and other regions outside the EEA, UK, and Switzerland, website analytics run automatically unless you have opted out or your browser sends Global Privacy Control. We do not show an automatic allow/deny banner. In the EEA, UK, and Switzerland, analytics stay off until you explicitly enable them. If we cannot determine the region, analytics stay off until you make a choice.

You can turn analytics off below at any time. Your preference is saved in this browser. Opting out removes our first-party visitor, session, and attribution identifiers. Explicit preference changes may be counted in anonymous date-level totals. Automatic regional defaults are not counted as someone accepting a consent prompt, and a decision count does not identify a person.

What our first-party analytics records.

When analytics are enabled, our first-party analytics can record:

• the page path you open, with URL queries and fragments removed;
• active time while the page is visible and the browser window is focused;
• navigation clicks and broad actions such as scheduling, calling, requesting directions, emailing, or opening reviews;
• FAQ opens, video progress milestones, and whether a quote or student-verification form was started or successfully submitted;
• device category, an external referring website’s hostname, a random persistent browser identifier, and a random per-tab session identifier that renews after 30 minutes of inactivity;
• original, latest, and last non-direct campaign attribution from approved UTM fields, referring hostnames, and advertising click identifiers; when optional analytics is allowed, approved campaign fields and an advertising click identifier may accompany the outbound Cents scheduler link so a resulting order can be attributed, while click-identifier values stored in our own analytics database are converted to a one-way keyed hash; and
• approximate city, region, and country supplied at Cloudflare’s network edge.

Our first-party analytics strips URL query strings and page fragments and does not record form field values, student IDs, names, email addresses, phone numbers, keystrokes, or exact GPS location. Only approved attribution fields are read from the landing-page query. Information you intentionally submit through a student or commercial form is processed separately as described under Form submissions. Third-party tags may process information according to their own configuration and notices; the first-party query-stripping rule does not describe or limit those providers.

Raw IP addresses are not stored in the analytics database.

Like any website host, Cloudflare receives the network address needed to deliver the site and protect it from abuse. For our analytics, Cloudflare’s edge can derive an approximate city or region; the raw address is also used transiently for abuse-rate limiting and is not written to our analytics database. When analytics are enabled, usage is measured with pseudonymous random browser and tab-session identifiers, not as a list of identified people. The private dashboard displays only a shortened browser-profile code, never the complete keyed hash or raw browser identifier.

A repeated browser-profile code usually means the same analytics-enabled browser storage, but it does not prove that the same person returned. Shared devices can use one code, while another device, browser, private window, cleared storage, or revoked consent can give one person several codes. IP addresses are not used as person identifiers.

Approximate location can be wrong, especially when a visitor uses a VPN, mobile network, corporate gateway, or privacy relay. It is intended for broad regional trends, not to identify a household or person.

To reduce re-identification risk, the owner dashboard shows an approximate town row only after that town has at least 3 tab sessions in the selected period.

Optional first- and third-party services.

When analytics are enabled under the regional policy and browser preferences above, the site may load:

• New Paltz Express Laundry first-party analytics for page, time, regional, journey, and action summaries;
• Cents website tracking connected to our laundry scheduling service;
• Google Tag Manager to manage approved Google Analytics or Google Ads measurement tags;
• PostHog for configured product analytics and, only when a public project key is enabled, heavily masked replay;
• Microsoft Clarity for configured interaction analytics and, only when a public project ID is enabled, masked replay; and
• Meta Pixel for configured standard advertising events.

Providers whose public ID is blank are not loaded. When replay is configured, all page text and inputs are masked and forms and owner-administration surfaces are blocked from replay capture. Those third parties process information under their own terms, privacy policies, and retention controls. Booking itself happens on Cents’ website and is governed by the notices shown there. Cloudflare also processes limited operational and security information as our website and database provider, independently of the optional analytics choice where necessary to operate and secure the site.

Cents order and customer reporting.

Cents can send our private owner tools updates about customer profiles and laundry orders. This operational reporting is separate from optional website browsing analytics. For business comparisons, we retain limited order status, service category, order amounts, source information when provided, and new-versus-repeat customer counts for up to 400 days. Customer and order identifiers in these records are converted to keyed one-way hashes. These limited records do not contain readable customer names or contact details.

We also keep a separate encrypted operational copy of customer names, email addresses, phone numbers, and order codes when Cents supplies them. These details support the signed-in owner's customer and order review, contact, and follow-up tools. Private name, contact, and order-code details expire after 30 days and are removed through regular cleanup; the private views are limited to that 30-day window. They are excluded from the analytics CSV and must not be sent to Google Analytics 4 or advertising tools. We do not retain street addresses, payment credentials, customer-access links, or the original webhook payload in this reporting copy.

Optional hosted-checkout steps are measured only when analytics consent permits them; detailed checkout events are retained for up to 30 days. A checkout click is not a confirmed order. When enabled, a limited report can match the same ad click identifier in website and Cents records, or show an unambiguous phone match as tentative. A matched order, order value, remaining balance, or completed service does not establish payment collected. Cents remains the system of record for your order and contact information.

The owner's delete control removes the active Cents reporting records, including the encrypted private details. Non-reversible delivery fingerprints may remain until their normal retention expiry to prevent repeated provider deliveries from restoring deleted data; these fingerprints contain no readable customer contact information or order details. Provider backups follow the separate backup limits described below.

Optional booking attribution.

When analytics are enabled under the regional policy and browser choice above, a Google ad click may offer a one-field phone step before opening Cents. You can continue without linking. If you submit the number, we store only a keyed one-way phone hash and temporarily retain an encrypted ad click identifier. The number is not added to the Cents booking URL. We only consider an order match within 14 days and do not treat a phone-only match as proven ad attribution.

Encrypted handoff identifiers expire after 90 days; limited matched order facts expire after 400 days and are removed by the owner analytics deletion control. This site does not send Cents-derived order conversions to Google Ads until a separate conversion connection and payment evidence are verified.

Student verification and commercial forms.

Form submission is separate from optional website analytics. Commercial quote requests are first stored encrypted in our private Cloudflare-hosted inbox, then we attempt an email copy through Web3Forms. Student verification first stores your details and ID attachment, encrypted, in that private inbox, then forwards an email copy through Web3Forms. Only the signed-in owner can review the inbox in our desktop application. We retain inbox records until the owner deletes them; deletion includes the stored attachment. Email copies and provider backups follow their separate retention policies. These records are excluded from analytics reports and exports.

• Student verification: full name, email, phone number, SUNY New Paltz student ID number, the uploaded student ID image or PDF, and the required eligibility-consent confirmation. We use it to review eligibility and apply the student discount. After setup, we may send a registration confirmation through Resend using your name and email address. That confirmation does not include your student ID number or attachment.
• Commercial quote: contact name, business name, email, optional phone number, business type, town, estimated weekly volume, and any message you enter. We use it to prepare and respond to the quote request.

Web3Forms’ current privacy policy describes Web3Creative as the form-data processor and says form submissions may be processed through providers including AWS, Cloudflare, and Hetzner; IP and email information may also be used by listed spam-prevention services. Its policy states that submission data is retained for a maximum of three years unless a shorter plan period applies or it is deleted earlier, and that server logs are deleted regularly. Review the Web3Forms privacy policy for its current terms and request channels.

New Paltz Express Laundry receives a copy of the submission for the stated purpose. To ask about, correct, or request deletion of the copy we received, email newpaltzlaundry@gmail.com or call (845) 255-7554. Some information may need to be retained where a legitimate business or legal requirement applies.

Retention, deletion, and limited backups.

Granular first-party analytics events and anonymous consent-event deduplication claims are kept for up to 30 days. Coarse aggregated daily totals, including consent-decision counts, are kept for up to 400 days so we can compare seasonal patterns. The random browser identifier and original/latest attribution remain in your browser until you decline, revoke consent, clear site data, or use a browser control that removes them; the tab-session identifier renews after 30 minutes of inactivity.

The owner can delete all active granular and aggregate first-party analytics at any time. That control does not delete Web3Forms submissions or records held separately by Cents, Google, PostHog, Microsoft, Meta, or other providers. Deletion removes records from the active analytics database. Cloudflare-managed backups or disaster-recovery copies may retain data temporarily and offer only limited recovery controls; those copies expire under Cloudflare’s backup lifecycle and are not used for routine analytics reporting.

Questions or privacy requests.

Contact New Paltz Express Laundry if you have a privacy question, want help resetting your analytics choice, or want to request access, correction, or deletion for information submitted to us.