1. Who operates this website

Ryan Angelo operates Ryan Angelo Photography as an individual. This policy describes information handling for the photography portfolio, inquiry form, sign-in features, and experimental tools at ryanangelophotography.com. For privacy questions, email ryangelo6818@gmail.com.

2. Contact inquiries

The contact form asks for your first name, last name, email address, subject, and message. When you submit it, your browser sends these details to Formspree to process and route your inquiry. Information you provide is used to respond to your questions and discuss requested photography services. Related replies and correspondence may also be held in email accounts. You continue to Formspree’s hosted verification and confirmation flow, which uses reCAPTCHA. Formshield spam protection and submission archiving are enabled. Formspree sends inquiry notifications to ryangelo6818@gmail.com.

You can contact Ryan directly by email instead. Emailing the listed Gmail address involves Google's email service as well as your own email provider. Please do not send payment-card details, passwords, identity documents, or other sensitive information through the form or in an initial inquiry.

3. Hosting, service providers, and technical data

The website uses Vercel for hosting and delivery, Formspree for contact submissions, Google Fonts for typography, and GitHub for optional sign-in. Requests to these services can disclose technical information such as an IP address, browser information, request time, and requested resource. Hosting logs can support website operation, troubleshooting, and security.

Google receives a connection request when your browser loads the externally hosted fonts and provides the reCAPTCHA service used in hosted form verification. Formspree receives the submitted form information and technical request information. Provider processing can take place outside your country. Additional recipients or integrations, storage locations, log access, and provider-specific retention and deletion arrangements remain subject to owner review; this policy does not promise a particular storage region.

Provider information is available in the Vercel Privacy Notice, Formspree Privacy Policy, Google Privacy Policy, and GitHub Privacy Statement. These describe the providers' practices, not a verification of this website's account configuration.

4. Sign-in and cookies

Browsing the public portfolio does not require a GitHub account. If you choose GitHub sign-in for restricted areas, the authentication flow requests profile and email information. It can receive your GitHub identifier, name or username, email address, and profile-image address. The website uses this information to establish a session and recognize you in the signed-in area.

NextAuth uses cookies for the session, sign-in security, and return navigation. You can manage or remove cookies through your browser; blocking them can prevent sign-in from working. There is no separate application account database or self-service account-deletion portal. Clearing website cookies does not delete your GitHub account or provider records.

The current application does not include an advertising pixel, newsletter signup, or visitor-analytics component. This does not mean that hosting logs or provider-side processing are absent. Hosting additions and the deployed cookie behavior still need owner verification.

5. Photographs and inactive features

Portfolio photographs, captions, and related information are public. People depicted may be identifiable. Image files can retain embedded information such as capture times, copyright information, and camera identifiers. Publicly accessible images may be copied or indexed by others; removing an image from this website cannot guarantee removal of independent copies.

Ryan plans to establish a documented permission process for publishing identifiable client photographs, including written photo or model releases where appropriate and consideration of parent or guardian authorization for minors. Existing published portraits still require a review of publication permissions; this policy does not represent that releases have already been collected for every photograph.

Private client galleries are currently disabled. The disabled gallery does not accept access-code submissions or request photographs from Amazon S3 or gallery rate-limit operations from Upstash. Disabling the feature does not delete previously stored photographs or historical provider records. Existing private storage and its retention/access settings still require review.

Online checkout and payment processing are not operational. This website does not currently collect payment-card details or complete photo orders. Any future client galleries, purchasing, Stripe Checkout, or digital delivery will need updated disclosures before activation.

6. Experimental tools

The image-provenance tool reads a selected file and computes its hash locally in your browser; selecting the file does not upload it. If an RPC service is configured and you choose Verify Provenance, the tool sends the hash and a blockchain read request to that service, which also receives connection information. A hash can link a request to a known file; it should not be treated as anonymous. This tool does not publish a blockchain transaction. Verification is unavailable without the required configuration.

The code-practice tool runs entered code locally in an isolated browser worker; it does not submit that code to a server. Loading either tool still generates ordinary website requests. Avoid using confidential material in experimental tools.

7. Retention and deletion

The owner-approved policy is to delete inactive inquiries that did not lead to photography services 12 months after the last meaningful exchange. Active client information may be retained for as long as reasonably necessary to provide photography services. Records needed for accounting, contractual obligations, dispute resolution, or applicable legal requirements may be kept longer for those purposes.

Ryan will periodically review stored information and manually delete records that are no longer needed. This is a manual business procedure, not an automated deletion system or a guarantee that every copy disappears on a particular day. Historical records still need to be reviewed under this policy.

Formspree and email services have their own storage, retention, backup, and deletion practices. The current Formspree plan provides access to 30 days of archived submission history. That access window is not a promise that Formspree automatically deletes all submission data after 30 days, and it does not delete notification emails or other copies. Provider-held records may remain under provider processes or applicable requirements. The owner still needs to confirm provider deletion options and handling of technical logs, authentication-related records, and backups.

8. Privacy and photograph-removal requests

Use the contact form or email ryangelo6818@gmail.com to ask about your information, request access or correction, request deletion, or raise a concern about a photograph. For an image request, include its page link and enough context to identify the image and explain your concern. Do not send identity documents unless an appropriate verification method has been arranged.

Requests may require reasonable identity or authority verification. Available rights, exceptions, and response requirements depend on applicable law and the circumstances. This policy does not restrict any rights you have under that law. Ryan will review requests and use reasonable identity or authority verification where necessary. Handling deletion across email, providers, and backups may require additional steps; immediate or universal erasure is not promised.

9. External links and policy updates

Links to Instagram and other external websites take you to services with their own privacy practices. Review their notices before providing information. This policy may be updated as the website or its data handling changes. An approved effective date and revision date will accompany the published version.