Filip Dilevski, trading as Dilevski Digital
Privacy policy
What we hold, why we hold it, who else sees it, and how to make us delete it.
In force from 15 October 2026
The short version
- We hold your email address, whatever you type into your site, and the pictures you upload. That is nearly all of it.
- We count page views on this site to see how many people visit and which ads brought them, without cookies and without knowing who you are. We do not follow you anywhere else, and there is no advertising tag here. Sites built here carry no analytics, unless their owner switches on a visitor count that records only which page was opened and on what day, or adds a tracking code of their own. There is no cookie banner here because there is nothing to consent to.
- We never sell personal data. We have never done it and the business does not depend on it.
- Ask us to delete your data and we will, except for the record of what we sold you, which we have to keep.
That is a summary, written to be understood rather than to be relied on. Where it and the document below disagree, the document below is the agreement.
1 · Who is responsible
Filip Dilevski, trading as Dilevski Digital is the data controller for the personal data described in this policy, except where section 4 says otherwise. Write to support@youbuiltit.com about anything in it, including to exercise any of the rights in section 8.
We are small enough not to be required to appoint a data protection officer, and we have not appointed one. The address above reaches a person.
2 · What we hold
Only what the service needs. In full:
| What | Where it comes from | Why |
|---|---|---|
| Your email address | You, when you sign up | It is how you sign in, and how we reach you about your order |
| Your business details — name, phone, address, email, social handles | You, in the intake form | They are printed on your website; that is the whole point of them |
| The words on your site | You, or drafted for you and then edited by you | To build and preview your site, and to freeze into what we deliver |
| Photographs and logos you upload | You | To put on your site. They may contain images of people, which is your responsibility under the terms |
| Your orders and their status | Created when you buy | To deliver what you bought, to prove we did, and for accounting |
| A copy of every site we deliver | Generated at the moment of purchase | So we can send it to you again if you lose it, and so we can show what was delivered if that is ever disputed |
| Questions you send us from the Help panel, and our answers | You, when you press “Send it to us” | To answer you, in the panel and by email |
| A problem report — what you wrote, the page you were on, your screen size, browser and device type, any errors the page had just hit, and a screenshot if you add one | You, when you press “Send report”; everything but your words and the screenshot is read by the page itself | To find and fix what went wrong, and to answer you by email |
| An application to test the builder — name, email, optional phone and city, what you wrote, and your CV | You, on the testers page | To choose testers. Nobody outside our team sees it |
| Your site offered as an example on /built-here — that you agreed, the words you agreed to and when, and what the page shows: your site's name, address, trade, town, colours and facts about how it is built | You, when you offer it from the publish page | To show it, if you ask us to and we approve it, until you withdraw it |
| Whether a site you host yourself is working — what we found at the address you gave, day by day | Our daily look at that address, once you have bought the site and given its address | To tell you, once, if it stops working; you can switch it off on the publish page |
| The address typed into the free website check, and what that website's front page shows | Anybody using the check on /check | To measure that page and show the result. The result is kept in our server's memory for up to ten minutes, so pressing again does not fetch it again, and is not stored |
| A scrambled form of your internet address, for rate limits on public forms | Your browser, when you use the free check | To stop the check being used by robots. Scrambled with a secret key so it cannot be read back, and deleted within a day |
We do not receive your card details. Paddle.com Market Ltd takes the payment as merchant of record and we never see the number. What comes back to us is that an order was paid.
We count visits with Vercel Web Analytics, so we know how many people come, which pages they open, from which country and kind of device, and which campaign or site sent them. It sets no cookie and is not linked to your account: what reaches us are counts, which say how many people came, not who you are. How Vercel tells one visit from another is described in its own analytics privacy notice (vercel.com/docs/analytics/privacy-policy). Before a page view is sent we strip the address down to the page itself: no project names or ids, no links' secret codes and nothing typed into a form or search, only the campaign tags an advertisement adds. There is no tracking pixel, no session recorder and no advertising tag on this site.
Sites built with it carry none of those by default. Two things are the site owner's choice. A visitor count, which comes with the contact form: each page view adds one to a number for that page and that day, and nothing else is kept — no cookie is set, and no address, browser or referrer is stored. And a tracking code the owner pastes in themselves, which is theirs to run and theirs to answer for, not ours.
3 · Why we are allowed to hold it
| Purpose | Lawful basis |
|---|---|
| Running your account and building your site | Performance of a contract with you |
| Taking payment and delivering what you bought | Performance of a contract with you |
| Keeping the delivery archive and order records | Legal obligation (accounting), and our legitimate interest in being able to re-deliver and to defend a dispute |
| Preventing abuse of the contact form | Our legitimate interest in not having our service used to send spam |
| Checking sites against our content rules before they can be bought, keeping the owner's confirmations, and handling reports about sites | Our legitimate interest, and our obligation as a hosting provider, in not publishing scams or illegal content; for a report, the reporter's address is kept only to tell them the outcome |
| Emailing you about a change to these terms or to the service | Performance of a contract, and legal obligation |
| Looking once a day at a site you host yourself, and telling you if it stops working | Our legitimate interest in the sites we sold working, and yours; you can switch it off at any time |
| The free website check, and the rate limits on public forms | Our legitimate interest in offering the check and in stopping it being abused |
| Showing your site on /built-here | Your consent, which you can withdraw at any time from the publish page; it is then taken off |
Showing your site on /built-here is the one thing above that rests on your consent, and you can withdraw it from the publish page at any time. Nothing else here relies on consent, which is why there is no banner asking for it. If we ever want to send you marketing, we will ask separately and you will be able to say no without losing anything.
4 · When the data is not yours and not ours
If you buy the contact-form add-on, people who visit your site can send you a message or book an appointment. That message or booking — the name, email address and, where they give one, the telephone number and note attached to it — is personal data belonging to your visitor, not to you and not to us.
For that data you are the controller and we act only as your processor: we receive it, store it, and show it to you, and we do nothing else with it. The written terms governing that are section 15 of the terms of service.
We also record the sender's IP address with each message and booking, and their browser identification with each message. That is used to stop the form being abused to send spam or to fill your diary, and for nothing else. It is not shown to you and it is deleted with the message or booking.
If one of your visitors asks you to delete what they sent, tell us and we will delete it. If they write to us directly, we will point them at you, because it is your data to decide about.
The same applies to words your customers write about you through your collecting link (/w/…): their words, the name they give, an optional place or detail, and the consent they agreed to, with its wording and the time. You are the controller and we are your processor. They give their consent to you, on a page that names your business; it is kept with their words as your record of it. The page tells them they can ask you, or us, to take their words down at any time — when they do, delete them on your "What customers say" screen and remove them from your site, or tell us and we will.
With each of those we also keep a scrambled form of the sender's internet address, scrambled with a secret key, used only to stop the link being flooded. It is not shown to you and it is deleted with the words.
6 · Where it goes
Our providers operate internationally, so your data may be processed outside your country and outside the European Economic Area — in practice, in the United States.
Where that happens we rely on the European Commission's Standard Contractual Clauses, or on an adequacy decision where one covers the provider. You may ask us for a copy of the relevant terms.
7 · How long we keep it
| What | How long |
|---|---|
| Your account and your unfinished projects | Until you delete them, or 24 months after you last sign in |
| Uploaded photographs and logos | With the project they belong to |
| Contact-form messages | 24 months, or until you delete the site or your plan ends, whichever is first |
| Appointment bookings | 24 months, or until you delete the site or your plan ends, whichever is first |
| Earlier versions of your site (history) | The newest few dozen per site; older ones are deleted as new ones arrive, and all of them go with the site |
| Your profile — name, username, picture, bio | With your account. The username you choose at sign-up is how you can sign in, so it can be changed but not cleared; the rest is optional and can be cleared at any time |
| Page view counts | With the site. They are numbers per page per day and describe nobody |
| Words your customers wrote through your collecting link, and their consent | Until you delete them, or with the site |
| Your site's place on /built-here | Until you withdraw it, or with the site |
| What our daily look found at your own address | With the site, or until you switch the look off |
| Free website check results | Not stored: kept in memory for up to ten minutes |
| Scrambled internet addresses kept for rate limits | One day |
| Questions sent from the Help panel, and our answers | With your account |
| Problem reports and their screenshots | With your account |
| A tester application and its CV | Until we have chosen testers, and never more than 12 months; sooner if you ask |
| Order records and invoices | As long as accounting law requires — assume ten years |
| The archived copy of a delivered site | 3 years from delivery |
| A fingerprint of a delivered site | Ten years, alongside the order it belongs to |
| Encrypted backups | Daily copies for 35 days and monthly copies for 400 days. Something you delete leaves the backups as they age out; we restore from them only to recover from a failure, never to bring back what you deleted |
The delivery archive is deliberate and we will not delete it on request while it is within the 3 years. It is how we can re-send a site you have lost, and how we could show what was actually delivered if you and we ever disagreed about it. It contains what you wrote and uploaded, and nothing else.
After 3 years we delete the file and keep only its fingerprint — a 64-character checksum that describes nobody and cannot be turned back into anything. We could have kept the files for the full ten years and the storage would have cost us very little; we do not, because holding your photographs and your words for a decade when we no longer need them is not something a low cost justifies.
You do not lose your site when that happens. We still hold the frozen record of what your site was, and the software that turns it into files produces the same result from the same input every time — so we can rebuild it and compare it against the fingerprint. If they match, what we send you is provably the same folder you were given. If they do not, our software has moved on in the meantime, and we will tell you that rather than let you assume otherwise.
8 · Your rights
Wherever you live, you may ask us to show you what we hold about you, correct it if it is wrong, delete it, give you a copy in a portable format, restrict what we do with it, or object to processing we are doing on the basis of legitimate interest. You may also withdraw consent where we relied on it, although as section 3 says, we generally do not.
Two of them you can use yourself, at any time, without asking: Account → Privacy & data downloads a copy of everything we hold about you, and deletes your account.
For anything else, write to support@youbuiltit.com. We will answer within 30 days and we will not charge you for it. We may ask you to confirm you are who you say you are, because handing somebody else's data to the wrong person is the failure this is all meant to prevent.
If you are in California: we do not sell or share personal information as those terms are defined by the CCPA, we have not done so in the preceding twelve months, and we do not knowingly collect the personal information of anyone under 16. You have the right to know, delete, correct and to non-discrimination for exercising any of them; the address above is how to exercise them.
The same applies if you are covered by one of the other US state privacy laws — Colorado, Connecticut, Virginia, Texas, Oregon and the rest. They differ in wording and the answer here does not: we do not sell your data, we do not use it for targeted advertising, we do not profile you, and you may ask us to show it to you, correct it or delete it.
We honour the Global Privacy Control and any equivalent browser signal. In practice there is nothing for it to turn off, because we do not sell or share personal information and run no advertising trackers — but a signal that is ignored where it would have mattered is worth nothing, so we act on it rather than explaining why we need not.
If you think we have got this wrong, please tell us first. You may also complain to a data protection authority: in North Macedonia that is the Agency for Personal Data Protection, and in the EU or UK it is the authority for the country you live in.
9 · Automated decisions
We do not make decisions about you by automated means that produce a legal effect or something similarly significant. Nothing here decides whether you may buy, what you are charged, or whether you keep your account — a person does that.
Before a site can be bought, an automated check reads its words and photographs and flags anything that looks against the rules. A flag is a question put to you, not a verdict: you settle each one yourself, and nothing is refused on the check's word alone.
The service does use an automated system to draft the words on your site. That is a suggestion made to you, not a decision made about you: you read it, change it, and choose whether to publish. Nobody's site is written and put live without a person in the middle.
If that ever changed we would say so here first, explain the logic in terms you could act on, and give you a way to ask for a human instead.
11 · Security
Everything is encrypted in transit. Every row of your data is protected by database-level access rules that scope it to your account, so a mistake in our own application code cannot show your project to somebody else. Uploaded files are stored privately and served through links that expire. Payment card details never reach us at all.
No system is perfect. If there is ever a breach affecting your personal data and it is likely to put you at risk, we will tell you and the relevant authority without undue delay.
12 · Children
You Built It is for businesses and is not directed at children. We do not knowingly collect data from anyone under 16. If you believe a child has given us data, tell us and we will delete it.
13 · Changes
If we change this policy materially — a new sub-processor, a new purpose, a longer retention period — we will email you before it takes effect. The date at the top of this page is always the version in force.
Questions about any of this: support@youbuiltit.com