PRIVACY POLICY
RaynerCodes Cloud Solutions
Plain-language summary of how RaynerCodes Cloud Solutions handles your information. Last updated October 2026.
Who this applies to
This policy covers this website (raynercodes.dev) and the custom website services of RaynerCodes Cloud Solutions, run by Leonardo Rayner as an independent contractor in Georgia, USA. It explains what information I handle, why, and the promises I make about protecting it. Questions go to raynercodes@gmail.com.
Information I collect
Details you send me: when you use the booking or contact form, your name, email address, phone number, preferred contact method and call times, a description of your business and requirements, any existing website, and a record that you agreed to the Terms of Service and this policy. Project information: content, branding, and business details you give me to build and run your site, and any access I need to your accounts. Technical information: your IP address and basic request details, used for security, spam prevention, and troubleshooting. On your device: your light/dark and motion preferences are saved in your browser, and a signed-in site admin has a temporary session in their browser tab. I do not use advertising or cross-site tracking cookies on this site.
How I use it
Only to respond to you, scope and quote your project, build and maintain your website, keep it secure, and meet legal obligations. I do not use personal information for advertising, and I never sell, rent, or trade it.
Personal information is protected
Personal information belonging to you, your customers, or your business — names, emails, phone numbers, bookings, messages, and anything else that identifies a person — is never leaked, published, sold, or handed to anyone. I only release it when (a) the business owner asks me to, or (b) a verified customer asks for their own information. The only other cases are narrow and necessary: the trusted services needed to run your site (see “Services I rely on”), and where the law genuinely requires it through valid legal process. In that last case I will limit what I share to what is required and, where the law allows, tell you first.
Passwords, secret keys & credentials
Your passwords, access keys, API keys, and other secrets are never shared with anyone outside the RaynerCodes Cloud Solutions team, and are never put in emails, chats, code repositories, public pages, or a visitor's browser. They are kept in an encrypted secrets store in your own cloud account, and access is limited to what the work requires. Passwords for sign-in areas I build are never stored in readable form: they are stored only as salted, one-way hashes (with an additional secret “pepper” kept separately), so even I cannot read them. If a secret may have been exposed, I will rotate it promptly.
How I protect information
Connections use HTTPS encryption. Sign-in areas have brute-force protection that locks out repeated wrong guesses, and forms have rate limiting and spam traps to stop abuse. Access is restricted to what is needed, systems are monitored through logging, and logs are kept free of passwords and secret keys. Updates go out through an automated, tested process. No system is perfectly secure, so I cannot promise absolute protection, but I do promise to take these measures seriously and keep improving them.
If something goes wrong
If I confirm that personal information in a system I manage was exposed, I will tell the affected business owner without undue delay (and within 72 hours of confirming it), explain what happened, and help fix it and notify anyone who needs to be told.
Your customers’ information
For a website I build for your business, you own your business and customer data and decide how it is used. I handle it only to build, run, and secure your site, and only on your instructions. Customers who want their information accessed, corrected, or deleted should contact the business, and I will help the business carry that out.
AI features
If your site includes AI features, I send an AI service only what a task truly needs, keep AI calls on the secure backend, and avoid sending sensitive personal details unless the task requires it. I choose providers and settings that do not use your data to train their models wherever that option exists, and I do not use your or your customers’ information to train AI models myself.
Services I rely on
Running a site takes a few trusted providers: Amazon Web Services for hosting and storage, an email delivery service to send messages from the site, your domain registrar, and Google Fonts, which supplies this site’s typefaces (so Google can see your IP address and browser details when a page loads). They receive only what they need to do their job and are bound by their own privacy and security commitments. Links to other sites, such as LinkedIn, GitHub, X, Instagram, and Facebook, are covered by those sites’ own policies.
How long I keep information
Form submissions are kept while we are talking and working together, and afterward for a reasonable period, or until you ask me to delete them. For client sites, the data lives in your account, and when we part ways I remove my access. Security records, such as sign-in lockout entries, are short-lived, except that records of blocked abusers are kept so they stay blocked.
Your choices
You can ask me to show you the personal information I hold about you, correct it, or delete it. To protect you, I will verify who you are before sharing or changing anything, and I aim to respond within 30 days. Email raynercodes@gmail.com.
Children
This site and my services are for businesses and adults. I do not knowingly collect information from children under 13. If you believe a child has sent me information, contact me and I will delete it.
Changes to this policy
I may update this policy as my services change, and I will change the date at the top when I do. The agreement we sign for your project is what applies to your project.
This policy is a plain-language summary and may be updated; the agreement we sign for your project is what applies.