Privacy Policy

Last updated: October 5, 2026

This site is run by Siarhei Rudak, a Product Engineer. I operate as an individual entrepreneur registered in Georgia. Rudax is the public name of that practice, not a separate company.

This page says, in plain words, what happens to your data here. I don't sell it, and there are no ads. The legal name, the registration number, and a postal address are not stated on this page.

What I collect

• Your name, email and message, when you use the contact form on the home page or on /services/.
• Emails you send me: if you write to info@rudax.pro, I keep the conversation so I can reply.
• Answers you type into the brief builder on /brief/. They are saved in this browser so you can leave and come back. They are not uploaded.
• Server logs. The host records technical data about visits, such as your IP address, to keep the site running and secure. The contact form also reads the IP address to slow down repeated submissions. That count stays in the memory of the running function. It is not written to a database.

Why I collect it

To reply when you write. To keep the site online, and to see which pages and buttons are used, as counts rather than as a profile of you. If we work together, to do the step you hired me for. That part is in "Your code" below. This site does not sign anyone up to a monthly letter. I do not send a regular newsletter.

The contact form

The form on the home page and the same form on /services/ send your name, email and message to me so I can reply. They are used only to reply to you. They are not added to a mailing list. The site does not delete them on a timer. If you ask, I delete the copy I hold.

The brief builder

The brief is built in your browser. The answers are saved in this browser's local storage, not in a cookie and not on my server. Downloading the brief saves a file on your device. Starting a new brief deletes the saved copy in the browser. I cannot delete that copy from here.

Who processes it

I don't run my own servers. These services handle data on my behalf, as a data processor:

• Resend (resend.com) delivers the contact form. The site sends your name, email and message to Resend, which sends a plain-text email to my inbox. The code does not turn on open or link tracking for that email. Resend publishes that stored message content is kept in the United States, and that email and log data is kept for 30 days on their Free, Pro and Scale plans. This page does not name which of those plans the site is on.
• Vercel (vercel.com) is the host. It serves the site and runs the contact-form function. That function is configured for Vercel's Frankfurt region. Vercel keeps server logs, including IP addresses. This page does not state a retention period for those logs, because the site's code does not set one.
• Plausible (plausible.io) provides visit counts. The script and the counts are requested from this site, at paths starting with /pv/, and the host forwards them to Plausible. Your browser does not load that script from plausible.io directly. Plausible's data policy says they do not use cookies, do not store the raw IP address, and keep visitor data in the European Union. I see aggregated counts: pages, referrers, countries, devices, and a few named clicks, such as sending the contact form or a click that leaves the site. Those clicks do not include your name, email or message. Links to social profiles and the share-card images do not add another collector.
• My email inbox stores the contact-form messages, after Resend delivers them, and any email you send to info@rudax.pro, so I can reply. This site's code does not name the company that hosts that inbox.

I don't sell your data, rent it, or share it with advertisers. Beyond these services, and the providers they themselves use, nobody gets your data, unless the law compels me.

Your code

If you hire me, this is the same promise the services page already gives, in the same words:

It stays yours. Access is the narrowest the step needs, read-only for a check, under a mutual NDA signed before anything is shared. I change nothing in your infrastructure and nothing in your accounts, keep a working copy only while the work runs, and delete it when the result is delivered. AI coding tools are part of how I work, and every tool that would touch your code is named in writing before anything is sent anywhere. You decide with that in front of you.

The services page states the same rules, and adds this line about where the product is run:

Anything I exercise actively runs on staging or on a copy, never on your production data.

Cookies

Opening these pages does not set a cookie, and the site does not load a third-party signup script. The brief builder uses local storage in this browser, which is not a cookie. Plausible's data policy says their script does not use cookies. The counts are described above.

Your rights

• Ask what I hold. Write to info@rudax.proand I'll tell you what I have.
• Ask for deletion. Write to info@rudax.pro. I delete what I hold, and I ask Resend to delete what they stored for you. The brief saved in your browser is on your device.

How long I keep it

• A contact-form message stays until I delete it. There is no automatic date in the site. Resend's own window is described above.
• A working copy of your code stays only while the work runs, and is deleted when the result is delivered.
• Brief answers stay in your browser until you start a new brief or clear the site's data there.

Changes

If what this page says changes, I update the page and the date at the top.

Contact

Questions about your data: info@rudax.pro