Who this notice covers
Ryan Wynn contracts personally under the name Reason & Render and operates from California, United States. This notice covers reasonandrender.com and its access-protected website. Websites built for clients have their own privacy arrangements.
Correspondence locality: Al Bahya, Abu Dhabi, United Arab Emirates. This is separate from Ryan's operating location.
Ryan handles privacy and formal legal requests through ryan.james.wynn@gmail.com. The request process is described under Privacy questions and rights below.
Information involved in page requests
Loading a page makes requests for the page and its supporting resources. The serving system receives technical connection and request information, such as the connecting IP address, requested URL and browser headers. A referrer may be included when the browser sends one. Navigation can also request resources in advance.
The application uses these requests to deliver pages, navigation, images, fonts, styles and scripts. Connection information can identify or relate to a visitor even without a form submission. Application delivery logs contain a reference, provider message ID where available, outcome and timestamp. They exclude message content, names and raw email or IP addresses; hosting logs are separate.
Optional performance measurement is off until you allow it in Cookie Preferences. It measures loading and responsiveness using fixed public page names, including Contact and Project Plan. The website excludes form content, questionnaire answers, customer references, query strings and URL fragments from its performance reports.
Vercel serves this website and processes hosting and security requests separately from the Contact form and questionnaire.
Your local Project Plan
The questionnaire asks about project type, goals, requirements, timing and budget preferences. It does not ask for your name, email address or other personal contact details. Your selections are held in the current page's memory to calculate and explain a deterministic recommendation in your browser.
Ordinary questionnaire answers and results are not sent to a server, placed in URLs, written to browser storage or transmitted to analytics. Opening a sharing panel and typing its fields sends nothing. Refreshing the page or confirming Start again clears local progress; cancelling reset keeps it. There is no saved-plan account, reference lookup or recovery service.
When you deliberately submit Email My Plan, your email address, optional name and selected answers are sent to the website server. It checks the plan against current rules and prices and asks you to review any change. Resend then sends that version of the plan and its PDF to your requested email address only; this action sends no owner copy. Replies to that email go to Ryan's enquiry Gmail.
Before Email My Plan can send to your requested address, you request and enter an 8-digit code. Requesting and confirming it sends your email, optional name and selected plan to the website server to tie verification to that exact request. Resend sends the code to that address; the verification email contains no plan. 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. Redis stores no readable code, email address or plan content. You still choose the final action to send the plan. Inbox access does not establish legal identity, verify an address supplied for call sharing or subscribe you to marketing.
When you deliberately share your plan for a call, your name, email, selected answers and any optional notes go to the server. Resend sends Ryan the saved plan and PDF with your email as Reply-To. After provider acceptance you may open Zoom Scheduler, using the same email and required saved-plan reference. It checks the connected Google Calendar and creates the Zoom meeting for a confirmed booking. Sharing alone books no time. The provider's confirmed event is authoritative. Google Calendar and Zoom handle their own account and meeting information.
The recommendation is planning guidance. It is not a credit decision, binding quote, contract acceptance or reserved start date. Email copies freeze that plan revision; later edits do not change a previously shared plan or appointment.
Contact and delivery features
You can prepare a Contact enquiry using your name, email address, message and optional package interest. Your unsent message stays in the current page's memory while you type. Choosing a pricing package puts only its package ID in the Contact URL and can suggest an editable message; it does not transmit that message or transfer Project Plan answers.
When you intentionally press Send Message, the form sends those enquiry details to this website's server. The server validates the request and uses Resend to send a notification to Ryan's Gmail inbox. Your validated email is used as Reply-To so Ryan can reply manually. Information is used to respond to this enquiry, not to subscribe you to marketing.
Email opens your chosen email application. WhatsApp opens Ryan's chat only after a deliberate click; the website does not send a WhatsApp message or put your unsent message or questionnaire answers in the chat link. Communication through either channel is handled by that service.
The questionnaire can be completed without contact details. Its optional sharing panels explain what is sent and who receives it. This website does not take payments or enrol you in marketing subscriptions.
Cookies, storage and external resources
The website does not set application cookies, embed third-party calendars or use advertising pixels. Unsent Contact messages and Project Plan answers stay in page memory, rather than localStorage, sessionStorage or IndexedDB. The website does not install a service worker or save data in application Cache Storage. Vercel's access and security services are separate from these website features.
The current optional performance control saves one allow/deny choice in localStorage after you choose. No choice is written merely by visiting, and no contact details, plan answers or identifier are stored with it. You can withdraw permission in Cookie Preferences. The choice has no automatic expiry and can also be removed with your browser's site-data controls.
Pages and supporting resources have ordinary cache headers, so your browser may reuse downloaded files. This is separate from saving answers or cookie preferences. Cache behavior depends on the resource headers and your browser; it does not establish how long server logs are kept.
Fonts and stock photographs are served from this website. Viewing them does not contact a font or stock-photo provider. The website does not save unsent Contact messages or planner answers in browser storage.
Providers and data locations
Vercel provides hosting; Resend sends requested emails when the relevant action is enabled. Upstash holds the limited operational records described below. Google/Gmail stores correspondence. WhatsApp handles chat activity when you choose that external channel.
Vercel provides this website's hosting infrastructure. The separate access-protected website uses Vercel account-based access; that authentication is not a Contact submission or a customer account.
Resend processes submitted notification content and delivery records; Google/Gmail receives and stores the notification and later correspondence. Upstash stores limited hashed request and retry metadata for duplicate prevention and sending limits, plus a separate durable customer reference registry. It is not a database of enquiry messages. No browser-side provider key or direct browser email transport is used.
Ryan uses a consumer Gmail account for enquiries and formal requests. Google's consumer terms and privacy policy apply; Google does not offer a data processing addendum for consumer Gmail. This mailbox is not described as a Google Workspace processor account.
Vercel publishes a data processing addendum for its Pro service. Resend states that its data processing addendum applies to every account, and Upstash publishes a data processing agreement. These provider documents describe their handling and do not replace this notice or the separate terms of consumer Gmail and other services you choose to use.
The dedicated Upstash store is hosted in AWS North Virginia, United States, and uses encrypted TLS connections. It stores operational hashes and reference reservations, not enquiry messages or plan PDFs. Selecting a storage region does not confine all provider account, support or security records to that region.
Zoom Scheduler receives the booking details you enter, including your name, email and saved plan reference. Its connected Google Calendar supplies availability and holds confirmed events; Zoom supplies the meeting. These providers also handle technical and account information under their own terms. Opening scheduling follows a deliberate click; there is no embedded calendar or automatic reservation.
Resend states that email data is stored in the United States; the region used to send an email does not determine where it is stored. Hosting, email, storage and booking providers can process data through infrastructure and subprocessors in other countries. This website does not promise that all information remains in your country or a single region. The linked provider documents give further information about their locations and handling.
Retention and security
Project Plan answers remain in page memory until cleared by refresh or confirmed reset. Deliberately emailed snapshots and PDFs remain in the requested mailbox and provider records under their separate handling processes. The application provides no public archive or recovery by reference. Names, emails, notes, full answers and PDFs are not saved in Redis. Operational hashed identifiers, immutable version metadata, delivery status and provider IDs support limits and retries, separately from the durable customer reference registry. Aggregate shared sending counters use day/month windows. Those technical expiries are separate from Ryan's correspondence-retention policy below.
The Vercel hosting account has a 30-day runtime-log retention setting. Other infrastructure and security records are handled separately, as is Ryan's correspondence. This does not mean all data held by every provider is deleted after 30 days. Browser cache controls do not delete server records.
Unsent Contact messages stay in page memory; refresh may clear them. Failed or uncertain submissions preserve the message for you to check or retry. After confirmed provider acceptance, the form clears the personal fields. Browser autocomplete and account-managed email or chat history are separate from an unsent message on this website.
Submitted messages and replies remain in Gmail under Ryan's correspondence policy below. Resend also retains content and delivery logs. Its published Free-plan policy reports 30-day email and log retention, 7-day backups and deletion of remaining customer data within 90 days after account termination. Those provider periods do not delete the Gmail copy.
Ryan reviews inactive enquiry correspondence quarterly. At the next quarterly review after 12 months without meaningful contact, he deletes inactive website enquiries, direct email and WhatsApp enquiry correspondence, and received Project Plans under his control, except where a documented legal requirement or legal hold requires retention. This enquiry schedule does not apply to client, contract, tax or financial records. It does not delete visitors' own copies or override provider retention and backups.
The configured request-limit store uses hashed identifiers and limited reference, status, time and provider-ID metadata. Retry metadata has a 48-hour application expiry; request counters have their own configured windows. These are operational expiry settings, not a promise that all provider backups or logs disappear at that time. No enquiry message database is added.
Issued short customer references are reserved in Upstash so a code is not assigned to another enquiry or plan. These records contain only pseudonymous metadata: the code, a hashed record identifier, the record type and service environment, and the information needed to identify its version. They contain no names, emails, answers, notes, PDFs or message bodies. Reference reservations have no automatic expiry and outlast the separate 48-hour retry records. There is no public lookup, and quoting a reference grants no access to private plans or authority to change them. Keeping a reference reservation is separate from keeping correspondence.
Ordinary planner answers stay local, and operational records contain only the information needed for sending limits, duplicate prevention and references. Provider credentials stay on the server. Optional performance measurement requires your permission where it is available. These measures reduce collection and exposure but cannot guarantee perfect security.
Privacy questions and rights
Ryan handles privacy questions and requests personally. You can ask about information held about you, request a correction or ask for deletion. The rights, deadlines and exceptions that apply depend on your location and the applicable law. Nothing in this notice limits mandatory rights that apply to you.
Send privacy questions and formal requests to ryan.james.wynn@gmail.com. Please describe the information or request concerned. Ryan may ask for proportionate information to verify the request and identify the relevant records. Do not send passwords or unnecessary sensitive information.
Changes to this policy
This policy is updated when the website's information handling changes. Material policy changes will be described in a dated notice on the website, with affected correspondents notified where legally required. The Effective date and Last updated date appear at the top of this page.