Privacy Policy
Short version: we only keep what you send us, we do not sell it, and you can ask us to delete it at any time.
What we collect
When you use the contact form we receive the name, the contact detail and the message you type. That is all — there are no hidden fields.
If you email us directly at info@ramstart.com we hold that correspondence in our mailbox in the normal way.
What we do with it
We use it to reply to you and, if we work together, to run the project. We do not sell it, rent it or pass it to anyone who is not working on your project.
We keep enquiries for as long as they are commercially useful and delete them on request.
Cookies and tracking
Nothing that tracks you runs before you allow it. On your first visit you get a banner with three options — accept all, reject all, or choose per category — and rejecting is exactly as easy as accepting.
Essential — needed for the site to work and never used to identify you. Analytics — anonymous page statistics with IP anonymisation. Marketing — Google and Meta advertising tags. Analytics and Marketing are off until you switch them on.
We use Google Consent Mode v2: Google tags are told "denied" before they load and are only upgraded if you consent. Your choice is stored in your own browser and can be changed any time from Cookie settings in the footer.
Fonts are served by Google Fonts, which receives your IP address as part of that request. This is required to display the page and cannot be switched off without self-hosting the fonts.
Your rights
You can ask what we hold about you, ask for it to be corrected, or ask us to delete it. Write to info@ramstart.com and we will act within 30 days.
If you are in the EU, the GDPR gives you these rights and you may also complain to your national data protection authority.
This is a plain-language policy, not legal advice.
It describes what the site actually does, and the consent mechanism described above is implemented and working. Even so, before RAMSTART handles client data at scale this page should be reviewed by a lawyer familiar with GDPR and local data protection law — a policy that is technically accurate can still be legally incomplete.