The short version
RyanREAX does not run advertising trackers, analytics, or marketing pixels on this site. There are no visitor accounts. The enquiry forms open your own email app rather than sending anything to this server, so the details you type into them are never stored here.
Who is responsible
This site is operated by RyanREAX (Pittsburgh, Pennsylvania). For any question about this policy or the information described in it, contact ryan@ryanreax.com.
Information you choose to send
The coaching, photo, and video enquiry forms build a message and hand it to the email program on your own device. Nothing is submitted to this website, and no copy is kept here. Once you press send in your email app, the message reaches Ryan the same way any other email would, and it is kept in that mailbox for as long as it is useful to the conversation.
Mail sent to addresses at ryanreax.com is forwarded to a personal inbox by the domain registrar. If you would prefer not to email, nothing on this site requires it.
Payments
Optional support payments on the Reactions page are processed by Stripe. Card details are entered inside Stripe’s own checkout and are never seen by, or stored on, this website. Stripe handles that information under its own privacy policy.
Cookies
This site sets no advertising or analytics cookies. Two cookies exist and both relate only to the site owner signing in to the private admin area:
- A session cookie that keeps Ryan signed in to the admin, which expires after 30 days.
- A short-lived security cookie used while connecting the Instagram account, which expires after 10 minutes.
Ordinary visitors never receive either of these, and neither is used to profile anyone.
Server logs
Like almost every website, the web server records basic technical details of each request: IP address, the page requested, the time, and the browser’s user-agent string. These logs exist to keep the site running and secure. They are not combined with any other information, are not used to build a profile of you, and are not sold or shared.
Third-party content
Some parts of the site load content from other companies. When that happens, your browser contacts them directly and they can see your IP address:
- YouTube — video embeds use the youtube-nocookie.com privacy-enhanced player, and video thumbnails are served by ytimg.com.
- Google Fonts — typefaces are requested from fonts.googleapis.com.
- Stripe — the checkout component loads from Stripe when you choose to support the show.
- EpicSkiesPhotography.com — the preview window on the Photo + Video page frames that site.
Each of these operates under its own privacy policy, which governs what it does with that request.
The Feed page shows RyanREAX’s own public Instagram posts. The site connects to Instagram using Ryan’s account only, and the images and captions are copied to this server and served from here. Visiting that page does not connect you to Instagram, does not require you to log in, and collects nothing about your own Instagram account. No visitor data is ever sent to Meta by this site.
Children
This site is not directed at children under 13, and no information is knowingly collected from them. Coaching and photography enquiries involving a minor should come from a parent or guardian.
Your choices and removal requests
Because the site stores so little, most requests are simple. You can ask what has been kept about you, ask for any email correspondence to be deleted, or ask for a photograph of you to be removed from the site. Email ryan@ryanreax.com with the request and it will be handled promptly, and in any case within 30 days.
Photography and video clients are covered separately by whatever was agreed for that shoot. If you are unsure whether you agreed to your images being published, just ask and they will be taken down while it is sorted out.
Security
The site is served over HTTPS. The private admin area is protected by a password stored only as a salted hash, with rate-limited sign in. No system is perfect, but nothing sensitive about visitors is held here in the first place.
Changes
If this policy changes, the effective date at the top of the page changes with it. Material changes will be described here rather than slipped in quietly.