Privacy Policy

When you submit the reservation form we keep what you typed, a set of technical facts about the visit, and a record of what you did on the page. We use it to decide whether we can serve you, to reply to you, and to understand which pages and channels reach real buyers. We do not sell it, share it with advertising networks, or buy anything about you from a data broker.

Below is every field, grouped by where it comes from. The list is generated from the database schema, so it cannot be shorter than what we actually keep.

company; your name; work email; the domain part of your email; GPUs needed; target start date; workload type; and anything you chose to add.

This is the minimum we need to tell whether we can serve you. GPU count and start date decide that; email is how we answer.

Kept for 2 years, then deleted.

If you become a customer, the contact details you gave us become part of our business records, and we keep them for as long as we are working together and for as long as we are required to afterwards. The reservation itself still ages out on the schedule above.

After you reserve we may ask a second set of questions. Every one is optional. If you answer, we keep: your role; phone number, if you gave one; team size; who you use now; what you spend now; on-demand or committed interest; how long you expect to need capacity; storage requirements; how much data you need to move in and out; compliance requirements you named; when you expect to decide; how you heard of us; and anything that would rule us out.

A phone number is used only if you asked us to call. Compliance requirements are asked so we can tell you plainly, and early, if we cannot meet them.

Kept for 2 years, then deleted.

Without asking, we record: the page you submitted from; the site that sent you here, if any; the first page you arrived on; campaign tags in the link you clicked; your browser's identification string; a salted hash of your IP address — never the address itself; country, from your connection; region, from your connection; city, from your connection; your browser language; your timezone; browser window width; browser window height; screen width; screen height; display pixel density; phone, tablet or desktop, inferred from the browser string; whether you asked your OS for reduced motion; light or dark preference; whether JavaScript ran; and a random identifier for this browser session.

We do not store your IP address. We store a salted one-way hash of it, which lets us rate-limit and spot duplicate submissions and does not let us recover the address. Location is the country, region and city your connection resolves to, not a precise position.

Screen size, timezone, language and browser string are each ordinary on their own. Together they can distinguish one browser from another, so we treat this whole category as personal data and hold it to the same retention as the form.

Kept for 1 year, then deleted.

We also observe, during the visit: how long you were on the page; how long the form took you; how many times validation rejected a field; the GPU count you tried in the cost estimator; the hours you tried in the cost estimator; which sections of the page you scrolled to; which pages you visited this session; and how many source citations you clicked.

This is attached to your reservation so the person reading it knows which page you landed on, what you read, and whether you ran the numbers. It exists to make the reply better and the page clearer, and it is the part of this policy most sites leave out.

Kept for 1 year, then deleted.

Analytics is off unless an environment variable turns it on. When on, it is first-party: no third-party script, no cookie, no advertising identifier.

Each event records the event — a page view, a section scrolled into view, an estimator change, a citation clicked, a FAQ opened, an outbound link, and how long you spent before leaving; the page and referrer; your browser identification string, the salted IP hash, and country; a random session identifier that lives in your browser tab and is gone when you close it.

Events are keyed to a session identifier that lives in your browser tab and disappears when you close it. They carry no name or email. They only become about you if you submit the reservation form in the same session, because your reservation then carries the same identifier.

Kept for 1 year, then deleted.

Once a request is in, we add our own bookkeeping: a random record identifier; a short human-readable reference; when the request arrived; when we last touched the record; a key your browser generates on submit; when the follow-up arrived; where the request is in our process; a priority tier we assign; a priority score we compute; whether we flagged it as spam; why, if so; which of us is handling it; our notes to each other; when we emailed you a receipt; when we notified ourselves; the date we deleted what you typed, if that has happened; and when we pushed it to our own tooling.

The priority tier and score are a triage aid for whoever reads the inbox. They are opinions about which requests to answer first, not a judgement about you, and they are not shared outside the company.

Kept indefinitely, and no longer identifies you. Once everything above has been deleted, what remains is the reference, the date it arrived, and what became of it.

Hosting: the servers that run this site and the database that stores the request.

Email delivery: the service that sends your receipt and our internal notification — it sees your email address and the request.

Internal notifications: our own inbox and tooling receive a summary of each request, including the priority tier, where you connected from, and how long you spent on the page.

None of these is an advertising network, and none receives your data for any purpose except operating this site and answering your request.

Email hello@yottaify.com and we will tell you exactly what we hold on you — every field above, with its value.

We have not yet built the ability to delete a record on request. Until we have, we will not promise it here. When it exists, this sentence will change.

There is nothing to opt out of on the site itself: no cookie banner, because there is no cookie; no marketing list, because we do not add you to one.