Privacy

This describes what the site actually stores, checked against the code rather than written from a template. Where something is kept, it says why and for how long.

Updated October 2026

Who is responsible

The data controller is The Institute for Smart Applications, Kfar Saba, Israel, registration number 032445678. For anything on this page, including a request to see or delete what is held about you, write to hello@yellow.domains.

Browsing and using the tools

There is no analytics script, no advertising script and no third-party tracker on any page, and no placeholder pretending otherwise. The site sets one cookie, and only if you sign in: it carries the session identifier described below, scripts cannot read it, it expires 30 days after you sign in, and signing out deletes it. There is no cookie banner because there is nothing to consent to. If that ever changes, this page changes first and anything that profiles you will sit behind a consent choice you actually make.

There is no advertising on this site today, and the paragraph above says so plainly. This one says what would be true if that changed, because the page promises to change before it does rather than after.

If advertising is introduced here it will be Google's, and third parties including Google use cookies to serve ads based on your visits to this site and to others. You would be told on this page before a single advertisement loaded, anything that profiles you would sit behind a consent choice rather than a notice, and you can switch personalised advertising off at any time — for every site, not only this one — at Google's Ads Settings, or opt out of third-party vendors at aboutads.info.

Domains you add to the cart are held in your own browser using localStorage. We do not sync it or read it from the server. It leaves your browser only when you go to checkout, because the order has to say what you are buying.

To stop the free tools being used as an anonymous scanner, we count requests per caller. That counter is keyed on your IP address, kept in our database, and deleted an hour after the window it covers — so roughly two hours at the outside. It is not linked to anything else about you.

Our host and our database also keep ordinary request logs, as any server does — the address a request came from, what was asked for, when, and whether it failed. They exist so that a fault can be traced, and nothing is built on top of them. They sit on those providers' systems and rotate out on their schedule rather than on one we set.

Where lookups go

Searches and tool queries are processed on our server, which then contacts public infrastructure on your behalf. Availability and WHOIS lookups query the registry's public RDAP service, found through IANA's bootstrap directory, and our registrar where a registry publishes no RDAP. DNS lookups query the public resolvers at 1.1.1.1 and 8.8.8.8. Certificate checks open a TLS connection to the hostname you entered.

Those services receive the name being looked up and our server's network address, not yours, because your browser never contacts them directly. Each operates under its own privacy policy. Availability answers are held in memory for up to two minutes and contain domain names only.

When you buy a domain

We store your email address, your name if you gave one, the names and terms you bought, what each cost, the status of every registration and refund, and which version of the terms you accepted and when.

ICANN requires registrant contact details for every registration, so we also store the name, street address, city, state or province, postcode, country and phone number you give at checkout, and pass them to our registrar and the relevant registry. WHOIS privacy is applied wherever the registry permits it, which keeps those details out of the public record — but not away from the registry, the registrar, or a valid legal request.

Payment is taken on Cardcom's hosted page and card numbers never reach our servers. We keep Cardcom's transaction reference, which is what lets us issue a refund, and for a period we also keep the full confirmation message Cardcom sends us. That message describes the payment, not the card, and it exists so an order that failed to complete can be replayed from what the provider actually said rather than from what we assumed. It is emptied 90 days after the order settles.

Signing in

There is an account area, and it has no password. Signing in sends a single-use link to your email; we store a hash of that link, never the link itself, and a session identifier once you use it. A domain here is owned by an email address rather than by a profile, so there is no separate account record to hold. Used and expired links are deleted within a day, and expired sessions within a week.

Email we send you

Receipts, registration results and renewal reminders are sent through Resend, on their European infrastructure. We log the recipient, the subject, whether it was accepted and any error — not the body — so that a receipt which never arrived can be traced. Those records are kept for two years.

We do not send marketing email and there is no mailing list to leave. Everything we send is about something you bought.

Why we are allowed to hold it

• To perform the contract. Your order, your email, your registrant details, the domain record. Without these there is no way to sell you a domain or let you manage it.
• Because the law requires it. Registrant accuracy is an ICANN obligation. Records of what was sold and what was paid are a bookkeeping obligation under Israeli law.
• Because we have a legitimate interest. Rate-limit counters and send logs, which exist to keep the site working and to prove a receipt was or was not delivered. Both are narrow and short-lived.

Nothing here is used for profiling, and no decision about you is made automatically. Nothing is sold, and nothing is shared for anyone else's marketing.

Who else sees it

• Atak Domain Bilgi Teknolojileri A.Ş. (IANA 1601), the registrar we file through, and through it the registry for your ending — registrant details, because a registration cannot be filed without them.
• Cardcom — the payment itself. They are the ones who see your card; we never do.
• Resend — the email address we write to, and what we write.
• Supabase and Vercel — the database and the hosting the site runs on.

These are service providers acting on our instructions, except the registrar and registry, which have their own obligations to ICANN. Some of them operate outside your country, and a registration in particular is filed with whichever registry runs your ending, wherever that is. If you want the current list of where each one processes data, ask and we will tell you.

Keeping it safe, and what happens if we do not

What protects the data here is mostly structural rather than clever. Card numbers never arrive. There are no passwords to steal, because there are none. The database is reachable only from our server and never from your browser, and traffic to the site and to the database is encrypted in transit. Access to the live data is one person's.

That is an honest list and also a short one. There is no security team here and no overnight monitoring, and that is worth weighing the same way you weigh the price.

If data here is lost or taken, you will hear it from us. Within 72 hours of knowing, we will tell the Israeli Privacy Protection Authority and, where the EU or UK rules apply, the relevant supervisory authority — one timetable rather than two, because one person cannot keep two. We will write to you directly wherever the loss could actually cause you harm, and we will do it before we have finished working out how it happened, in plain words: what was taken, and what to do about it.

How long

• Rate-limit counters: about two hours.
• Sign-in links: one day after use or expiry.
• Sessions: one week after expiry.
• Payment confirmation messages: emptied 90 days after the order settles.
• Email send records: two years.
• Request logs at our host and database: on their retention schedule, not one we set.
• Orders, refunds and domain records: kept while you hold the domain and then for as long as bookkeeping law requires, which in Israel is years rather than months. These are the evidence of what you bought and what you were owed, and we will not delete them on request while that obligation runs.

What you can ask for

Write to hello@yellow.domains and ask for a copy of what is held about you, a correction, a deletion, a restriction on what we do with it, or a copy in a portable form. You can object to processing we do on a legitimate-interest basis. We will answer within 30 days.

Two honest limits. We cannot delete a registrant record that ICANN requires the registrar to hold, and we cannot delete the record of a sale while bookkeeping law says to keep it — in both cases we will say which applies rather than refuse without a reason. If you want your registrant details corrected, ask: they have to be accurate, and an inaccurate one is grounds for the registry to suspend the domain.

If you are in the EU or the UK and think we have handled your data badly, you can complain to your national data protection authority. We would rather you told us first, but it is your right either way.

Changes

This page carries the month it was last changed. If we start collecting something new, it appears here before it starts, not after. The terms cover what happens to the domain itself.