Privacy policy
What this website collects, what happens to it, and what you can ask us to do about it. It is short because the site does very little.
- Last updated
- 6 August 2026
01
Who we are
Kramiva is a founder-led software and digital-product studio. For information you submit through this website, we are the data controller. You can reach us at contact@kramiva.com, and a person reads that address.
02
What this website collects
The inquiry form is the only place this site asks you for personal information. There is no account, no login, no newsletter, and no comment field.
- Your name, work email, company, and (optionally) company website
- Your country, so we can propose sensible meeting times and the right contracting basis
- What you need, and — both optional — your approximate budget range and timeline
- Your project summary, and optionally how you heard about us
- Which page you started the inquiry from, so we know what prompted it
03
What happens to it
It becomes one email, sent to us. The site has no database and stores no copy of your inquiry: the submission is validated, passed to our email provider, and exists after that as a message in our inbox.
We use it to reply to you and, if the project proceeds, to scope and run the engagement. That is the whole purpose. We do not add you to a marketing list, we do not sell your information or disclose it for anyone else's marketing, and we do not put inquiry content into any AI model for training. The only other parties involved are the infrastructure providers named below, which process it so the form works and our reply reaches you.
04
Who else is involved
Two providers, and we can name both.
- Our hosting provider, which serves this website and runs the code that processes the form
- Resend, which delivers the inquiry to us as email
05
How long it is kept
Because the site stores nothing, retention is a question about our mailbox rather than about this application. Inquiries stay in it while they are useful — an active conversation, or a project we are delivering — and we delete on request without argument.
We are setting a fixed retention schedule with our advisers, and this page will state the period once it exists. We would rather tell you that than publish a number we have not committed to.
06
Your rights
Whichever country you are in, you can ask us for a copy of what we hold about you, ask us to correct it, ask us to delete it, or object to our holding it at all. Email us and we will action it — there is no form and no ticket queue.
For inquiries from the UK and EU, our basis for processing is legitimate interest: replying to a business inquiry you sent us. You can object at any time, and we will delete the record. If you are in the UK or EU you also have the right to complain to your supervisory authority.
07
Cookies, storage, and analytics
This site sets no cookies at all — none for advertising, none for analytics, none for sessions. It runs no analytics product and no tag manager: Kramiva does not currently use advertising pixels, behavioural analytics, or tracking cookies on this website, and there is no measurement script of any kind in the application.
Our hosting provider keeps ordinary server logs, as any web server does. That is infrastructure operation and error diagnosis — it is not behavioural analytics, it builds no profile of you, and we do not query it to study visitors.
It stores one item in your browser's local storage: your light or dark theme preference. It never leaves your device. See the cookie policy for detail.
08
Rate limiting and spam
To stop automated submissions, the form carries a hidden field that real people never fill in, and the server briefly counts submissions per connection. That count is held in memory for at most an hour, is never written to disk, and is never included in the email or sent anywhere.
09
Client data during an engagement
This policy covers the website. When we build software for you, any personal data inside that system is yours: we act as a processor, and the handling, the material service-provider dependencies, the hosting requirement, and what happens at the end are agreed in writing for that engagement before the build starts. A data-processing agreement can be included where the engagement requires one.