Optional performance measurement
Vercel Speed Insights measures page loading speed and responsiveness. It starts only if you allow it. You can change your choice here at any time.
Performance measurement is off unless you allow it.
These controls save only your allow or decline choice in this browser. Turning measurement off stops future metrics from being sent; it does not recall metrics already sent.
Current status
Optional performance measurement is off until you allow it. Vercel Speed Insights measures page loading and responsiveness on reasonandrender.com. You can allow, deny or withdraw permission using the controls on this page. Contact sending, plan sharing and booking work independently of this choice. Advertising and marketing pixels remain inactive.
Your explicit choice is saved as one allow/deny value in localStorage. It has no automatic expiry; no choice is saved merely by visiting. The value contains no identifier, contact details or questionnaire answers. You can change it here or clear the website's data in your browser. Withdrawing permission stops further website performance requests, including from the already loaded script; it does not recall data already received by Vercel.
Performance reports use fixed public page names, loading and responsiveness measurements, browser/device and network information. Vercel documents country information and identifiers for page elements alongside those measurements. The website removes form content, answers, customer references, query strings and URL fragments from its performance reports. Reports exclude service endpoints, unrecognized pages and the access-protected website. Vercel describes its measurement data as not associated with an individual visitor or IP address; normal hosting requests still involve technical connection data.
Vercel serves this website. Performance permission does not control hosting or security requests, send an enquiry or create a saved plan. The separate access-protected website does not load optional measurement or save its preference.
Cookies, storage and technical records
The table explains how website features use page memory, browser storage and operational records. Sending an enquiry, requesting a plan copy or opening an external booking service are separate actions from visiting a page or setting a performance preference.
| Category | Details |
|---|---|
| Website application cookies | The website does not set application cookies. Vercel's separate access and security services can use provider-managed cookies. There is no application-cookie lifetime; provider-managed access cookies follow Vercel's settings. |
| Local storage, session storage and IndexedDB | Cookie Preferences saves one fixed allow/deny choice in localStorage when you choose a setting. It does not store an identifier, contact details or questionnaire answers. The choice has no automatic expiry. You can change it here or clear this website's data in your browser. |
| Project Plan page memory | Selections and a deterministic result stay in the current page's memory. Cleared by refreshing the page or confirming Start again. |
| Service workers and application Cache Storage | The website does not register a service worker or save data in application Cache Storage. Ordinary browser caching is separate. There are no website service-worker registrations or application cache stores to expire. |
| Page requests and ordinary browser caching | Same-origin pages, navigation resources, scripts, styles, fonts and images are requested; cache headers are present. Resource-specific cache headers and browser behavior; not a promise of server-log deletion. |
| Optional performance measurement, advertising and embeds | Vercel Speed Insights is off until you allow performance measurement on reasonandrender.com. It uses fixed public page names, including Contact and Project Plan. The website excludes form content, answers, customer references, query strings, fragments, service endpoints and unrecognized pages from its performance reports. Advertising, marketing pixels and embedded scheduling remain inactive. Denying or withdrawing permission stops further website performance requests. Previously received provider data follows Vercel's retention, separately from the saved choice. |
| Email My Plan address verification | Requesting or confirming verification sends your email, optional name and selected plan to the website server to tie verification to this email request. Resend sends an 8-digit code email containing no plan. Sending the plan and PDF requires the later final Email My Plan action after successful verification. The code lasts up to 15 minutes, within the request lifetime. Hashed verification and permission records last up to 23 hours, limited by the age of the plan and request; request-limit counters expire within 48 hours. The verification email follows mailbox and provider retention. |
| Unsent Contact messages and package interest | Name, email, message and package interest stay in page memory while editing; only an intentional Send Message action submits them. Refresh may clear the unsent message. Accepted submissions clear the personal fields; failed or uncertain submissions preserve them on screen. |
| Contact delivery and abuse prevention | Explicit submissions send enquiry details to the website server. Valid requests that pass its checks are passed to Resend for notification delivery to the owner's Gmail. Upstash holds limited retry and request-limit metadata; issued customer reference codes use the separate durable registry described below. Gmail messages and provider records outlast the form. Retry metadata has a 48-hour application expiry; customer reference reservations do not expire with it. Provider retention and the owner's deletion schedule remain separate. |
| Deliberate Project Plan email and call sharing | Email My Plan verification sends the selected plan and entered details to the server to bind the request, without emailing the plan. A deliberate final sharing submission then requests the email and PDF. The server recomputes and verifies the versioned plan before Resend delivery. Email/PDF copies outlast the page. Hashed per-action metadata expires after 48 hours; issued customer reference reservations remain. Shared aggregate budget counters follow UTC day/month windows. No plan bodies, PDFs or personal contact details are saved in Redis. |
| Server-side customer reference registry | After a deliberate submission passes validation and abuse checks, the server reserves a short customer reference. The shared Contact and plan registry holds pseudonymous metadata: the code, a hashed record identifier, the record type and service environment, and the information needed to identify its version. It holds no names, emails, answers, notes, PDFs or message bodies. No automatic expiry. Issued codes are not reassigned to another record and outlast the separate 48-hour operational retry records. This reservation behavior does not establish retention of email, PDFs or provider logs. |
| Direct Email and WhatsApp links | Choosing Email opens your email application; choosing WhatsApp opens Ryan's chat. These links do not load a widget, connect in advance or send an automatic message. Correspondence follows the chosen service's retention and your and the owner's account actions; the site does not clear it. |
Your Project Plan stays local
The planner uses page memory to hold your answers and calculate a recommendation. It does not save a profile, write your selections to browser storage or send them with network requests. Refresh the page or confirm Start again to clear the local answers and result. Keeping or editing answers on screen does not create a saved copy.
Email My Plan verification sends the selected plan and entered details to the website server to bind the request, without emailing the plan. A deliberate final sharing action requests the plan email and PDF. Opening a panel or editing its fields sends nothing. When call sharing is enabled, Zoom Scheduler opens after a separate click and a provider confirmation establishes the booking. Contact remains separate and never automatically receives questionnaire answers.
Browser and hosting limits
Ordinary browser caching may reuse local fonts, images and other downloaded files according to their cache headers and your browser settings. It is separate from cookies, application Cache Storage and saved preferences. Browser controls for site data and caches belong to your browser; this page does not change those settings or delete infrastructure logs.
Fonts and photographs are served from this website without contacting their original providers when you view them. Direct Email and WhatsApp links open external services after a click. Submitted Contact enquiries and deliberately shared plans are handled separately by the server and the services described in the Privacy Policy.
Browser site-data controls do not manage provider accounts, hosting and security records, email copies or booking details. The Privacy Policy explains those separate records, providers and retention periods. A performance choice on this page does not change your settings in Gmail, WhatsApp, Zoom or Google Calendar.
Questions about cookies and privacy
Ryan Wynn handles privacy and formal legal requests through ryan.james.wynn@gmail.com, with proportionate verification where needed. Do not send passwords or unnecessary sensitive information.
The Privacy Policy explains page requests, who receives information, retention and how to raise a privacy request. This page is updated when the website's storage or optional services change.