Privacy — Voidix

.doc-page [class*='doc-'] { opacity: 1 !important; transform: none !important; clip-path: none !important; } .doc-role-panel { visibility: visible !important; grid-template-rows: 1fr !important; }

Last reviewed 2026-08-17

Who this is, and what it covers

This notice covers voidix.tech and every page on it. The studio operating this site is the party responsible for the information described below — in data-protection language, the controller: [Registered entity name and address — not yet incorporated].

Write to [privacy@voidix.tech — confirm this mailbox exists] about anything on this page, including any of the rights in section 07. A request costs you nothing and does not have to be in any particular form.

The bracketed details above are unfinished on purpose. The studio is not yet a registered company, and naming one before it exists would be the first thing on this site we could not back.

What the site collects

Six things, and the first two only happen because you chose to send them. The rest are counts about how the site was used rather than about you — no name, no address, and nothing that could pick you out of the people who visited the same day.

When you send an enquiryYour email address, which is the only required field, plus anything else you choose to add: a name, a phone number, what you are looking to build, and a note of which part of the site you opened the form from. It arrives in an inbox and stops there — it becomes a business contact only if someone at the studio decides it should.
When you apply for a roleYour name, your email address, why you are writing, and the work you want read — a link, a CV as a PDF of up to 5 MB, or both. Optionally a phone number, and a note of which role you applied to. Applications are kept apart from enquiries and cannot cross into the studio’s business contacts.
When you set a motion preferenceOne entry in your browser’s local storage recording whether you asked the site to reduce its animation. It contains no name, no identifier and nothing that could distinguish you from anyone else with the same setting, and it is never sent anywhere. Clearing your browser data removes it.
When you answer the cookie barYour answer is stored in this browser, with the date you gave it — that record is what lets us honour the choice and show when it was made. Saying yes also creates a random id on this device so a later visit is not read as a stranger; saying no, or never answering, creates nothing. You can change it at any time at the bottom of this page, and turning it off deletes the id straight away.
While you are using the siteWe count how far people get: whether the loading screen finished or you left during it, which sections you reached, which project or service you stopped on and for how long, whether you opened a question or a form, and whether the form was sent or abandoned. We also record what your device could handle — its rough performance class, screen size and whether you asked for reduced motion. None of this is attached to a name, an email or an address, and none of it is stored on your device.
Where your cursor goesOn a computer with a mouse, we record which parts of the screen the pointer rests in — as counts in a coarse grid, not as a trail — plus where you click, and whether a click landed on something that could not respond. It tells us which parts of a page people reach for. There is no grid on a phone or tablet, because there is no cursor.

Two things happen at the network layer that are worth naming even though the site does not choose them: our host records ordinary server logs, and the system receiving form submissions applies a rate limit based on the network address a submission came from, so that one sender cannot flood it.

The one thing we ask permission for

Everything in the previous section happens for everybody, because none of it can pick a person out of a crowd. This is the exception, and it is the only reason there is a bar at all.

If you allow it, we record the actual path your cursor takes across the page — not just where it rested, but the route it took to get there, several times a second. That is close to watching a recording of your visit, and we would rather say so in those words than describe it as “cursor data” and let you find out later. It is worth being blunt about why it needs asking: the way a person moves a mouse — the speed, the small corrections, the pauses — is distinctive enough to be a way of recognising them. Nothing else on this page has that property.

We use it to judge whether the site works: whether people find the controls, whether the long scrolling sequence reads or loses them, whether something is being reached for that does not respond. It is never sold, never shared, and never looked at alongside your name, because the two are not connected to each other anywhere in our systems.

Say no, or say nothing, and no path is recorded at all — not stored anonymously, not held briefly, not recorded. Turn it off later and every path we hold for you is deleted from our servers, not merely disconnected.

What the site never does

This section is the short one, and it is the reason the rest of the page is short.

No third-party analytics touches this site. No Google Analytics, no Tag Manager, no Plausible, no Vercel Analytics, no product-analytics service of any kind. Nothing you do here is sent to another company for them to hold, model or resell.
There are no cookies — nothing is written to a cookie, and nothing about you is sent along with every request. The bar that offers to remember you is asking about one entry in this browser’s local storage: a random id, created only if you agree, deleted the moment you change your mind. “Allow cookies” is what the button says because that is the phrase everyone knows, and the law treats the two the same.
There are no third-party tags, pixels, embeds, share widgets or advertising networks anywhere in the page.
The typefaces are served from this site’s own domain, not from a font network. Loading a page here does not tell anyone else that you did.
Nothing you send is ever sold, rented, brokered, or handed to anyone for their own marketing. There is no profiling and no automated decision-making about you.

Who else handles it

A form submission touches three systems on its way to a person, and each of them only ever sees what it needs to do its part.

The studio’s admin panelWhere enquiries and applications are read. It holds the text of what you sent and, for an application, a link to your CV rather than the file itself.
UploadThingWhere a CV file is stored, if you attach one. It is uploaded by our server rather than by your browser, and it is the only place the file itself lives.
Our hosting providerServes the pages and keeps ordinary server logs of requests, as every web host does. It never sees form contents as anything other than traffic in transit.

⚠ The exact companies behind the panel’s database and the hosting are still to be named here. Until they are, this section describes what each system does but not who runs it, and that gap should be closed before the studio is trading.

How long it is kept

The measurement described in sections 02 and 03 is deleted after 90 days. Not archived, not anonymised further — the individual records are removed, and what survives is a daily count of how many people did a thing, which no longer relates to any visit in particular. Cursor paths go on the same 90-day clock, and go immediately if you withdraw.

What you SEND us has no fixed number of months against it, because the studio does not yet run a deletion schedule for correspondence it could honestly promise to keep, and stating one we did not follow would be worse than stating none. What governs it instead: an enquiry is kept while the conversation it started is live, and for as long afterwards as we may reasonably need to remember it — a returning client picking up an old thread, or a record of what was agreed. An application is kept while the role is open and for a reasonable period after it closes, so that a strong candidate can be reconsidered for the next one. A CV is deleted when the application it belongs to is.

You do not have to wait for any of that. Ask us to delete what we hold and we will, on the terms in section 07.

Your rights

These are granted to everyone who writes to us, wherever you are. Drawing a line by country would mean sorting people by passport before answering a one-sentence request, and the request is easier to honour than the sorting.

Ask what we holdWe will send you everything associated with your address, in a readable form.
Correct itIf something is wrong, tell us what it should say and we will change it.
Have it deletedWe will remove it, including any CV file, unless there is a specific legal reason we must keep a record — in which case we will tell you what and why.
Take it with youWe will provide what you sent us in a common machine-readable format.
Object, or ask us to pauseYou can tell us to stop using what we hold, or to restrict it to storage only, while a question is resolved.
Complain to a regulatorIf we handle a request badly you can take it to the data-protection authority where you live. We would rather you told us first, but that is your choice and not a precondition.

Requests are answered within one month. We will not charge you, and we will not ask you to justify the request.

Where you stand in law

This notice is written to the standard of the EU and UK General Data Protection Regulation, which is the strictest of the regimes that could apply and the one that grants you the most. Where you are covered by it, the lawful bases are straightforward: we handle an enquiry or an application because you asked us to and because the studio has a legitimate interest in answering, and we keep a CV only for the purpose you sent it for.

Where the studio’s operations are established in Egypt, Law 151 of 2018 on the Protection of Personal Data applies alongside. Its rights — to be informed, to access, to correct, to erase, and to object — are materially the ones set out in section 07, and where the two regimes differ we will apply whichever gives you more.

⚠ Egyptian law also requires a controller to register with the Data Protection Centre once trading, and the executive regulations giving effect to Law 151 have not been issued at the time of writing. This page therefore states which law applies and what you are owed under it; it does not claim a registration the studio does not yet hold.

Changes to this notice

When this document changes, the review date at the top of the page changes with it. That date moves when the words move and at no other time — it is not a build stamp, so a deploy that changes nothing here will not make this page look freshly considered.

If a change ever means we start doing something this page currently says we do not — an analytics script, a cookie, a new recipient for what you send — we will say so plainly here rather than adjusting a sentence and hoping it reads the same.

Ask us anything about this.

Every right on this page is exercised by writing one email. [privacy@voidix.tech — confirm this mailbox exists]