Terms and Privacy

1. Who you are contracting with

Alyx is sold by Space Alyx S.A.C., registered at [[ REGISTERED ADDRESS ]], tax identification [[ TAX ID ]].

These terms apply from the moment you buy, download or install Alyx. If you do not accept them, do not install it.

Questions about this agreement go to megasent.go@gmail.com.

2. What the licence gives you

• You are buying a licence to use the software — not the software itself, and not its source code.
• Pro and Max are yearly subscriptions, charged for a year at a time. The 7 free days at the start are part of that subscription, not a separate tier: you sign up with a card, the first week costs nothing, and you can cancel within it.
• If a subscription lapses, Alyx cannot be used until you activate it again, but it never locks your files. Your conversations and everything Alyx generated — spreadsheets, charts, exports — stay in your folders and you can open, export and delete them, paid or not. Your model is yours and Alyx holds nothing back.
• One licence covers Alyx itself, in every host application it supports. A licence bought while using Revit also runs Alyx in the other hosts as they arrive, on the same seat — there is nothing extra to buy. Moving to a newer version of a host application is free and needs no new licence.
• One licence runs Alyx on one computer at a time. Activating a machine takes the licence seat; reactivating that same machine, after a reinstall for instance, does not take a second one.
• Moving to another computer is self-service and unlimited: release the seat on the old machine from Settings, then activate the new one.
• Alyx works offline. It renews its signed licence in the background every few days whenever it has a connection — and if you are offline for longer, it keeps working for as long as the plan you paid for is still live. The end date of that plan travels inside the signed licence, so your own computer knows it without asking us. Come back online and it renews itself, without asking for your key.
• What your licence permits — which product it covers, and whether the software may write to your model, run the local AI, compile custom code or run composed flows — travels inside that signed licence file on your own computer. Alyx reads it there, offline, and does not ask a server for permission before letting you do anything.
• That is also why a lapse takes effect on its own: when the plan behind the last signed licence has ended and no new licence is issued, Alyx stops working by itself, wherever it is, with or without a connection, until you activate it again. Your conversations and the files it made for you stay open to you either way.
• The AI model runs on your own computer. There is no per-prompt fee, no token budget and no usage meter.
• The licence is personal and non-transferable unless we agree otherwise in writing.

3. Your licence key

Your key is a credential. Keep it as private as a password: anyone holding it can install the product against your licence.

We store only a hash of your key, never the key itself, so we cannot read it back to you if you lose it. Keep your purchase email.

A key can be revoked if the payment behind it is reversed or charged back, or if it is used in a way clause 4 forbids. Every revocation is recorded with a reason, and we will tell you which one applies.

4. What you may not do

• Share, resell, sublicense, rent or publish your licence key.
• Redistribute the installer, the AI model or the bundled knowledge base, whole or in part.
• Work around the licence check, or run a modified build.
• Reverse-engineer the product, except where the law of your country grants you that right and does not allow us to take it away.

5. Updates and support

[[ WHICH UPDATES THE LICENCE INCLUDES, AND FOR HOW LONG ]]

[[ SUPPORT CHANNEL, AND WHAT RESPONSE TIME IS PROMISED — IF ANY IS ]]

Features may be added, changed or retired between releases. Nothing in this agreement promises a specific future feature.

6. Payment, taxes and refunds

Payment is taken by our store, [[ PAYMENT PROVIDER ]], under its own terms. We never see or store your card details.

[[ REFUND WINDOW AND CONDITIONS — how many days, and what disqualifies a refund ]]

[[ HOW TAX OR VAT IS HANDLED, AND WHO IS RESPONSIBLE FOR IT ]]

A refunded or charged-back order disables the licence key it created.

7. What you need to run it

• Windows 10 or 11, and Autodesk Revit 2027.
• Your own valid Autodesk Revit licence. It is not included in this price and we do not sell it.
• Alyx is an independent product. It is not affiliated with, endorsed by or sponsored by Autodesk. Autodesk and Revit are trademarks of Autodesk, Inc.
• The AI runs locally, so how fast it answers depends on your hardware. [[ MINIMUM HARDWARE THE SELLER COMMITS TO SUPPORTING ]]

8. Warranty and liability

[[ WARRANTY, LIABILITY LIMIT AND EXCLUSIONS — the clause that most needs a lawyer in the seller jurisdiction, and the one that must not be copied from another product terms ]]

In plain language, pending that review: Alyx assists you, it does not certify your model. You stay responsible for checking the drawings, the quantities and the code compliance it produces, exactly as you would check the work of a colleague.

9. Ending the licence

There are two different endings here and they do not have the same consequence. A subscription that you cancel or that simply lapses is the ordinary one; a licence that we end because it breached this agreement is the other.

If your subscription ends, you do not have to uninstall anything: your conversations and files stay where they are and stay open to you. In practice a paid computer that is already running keeps renewing for about a week past the date, so a renewal that has not reached us yet does not stop you mid-project. That grace is for paid subscriptions only — a free trial ends on its own date, exactly.

If we end a licence for breaching this agreement, we will say which clause and why, and in that case you must stop using the product and uninstall it.

Either way, the files you created with it are yours and stay yours.

10. Changes to these terms

If these terms change, the new version appears on this page with a new date. Changes do not apply retroactively to a purchase already made.

11. Governing law

[[ GOVERNING LAW, AND THE COURTS THAT DECIDE A DISPUTE ]]

[[ CONSUMER-RIGHTS CARVE-OUT FOR BUYERS IN OTHER COUNTRIES, IF THERE IS ONE ]]

1. The three identifiers we hold

• A hash of your licence key (SHA-256). It identifies the licence without our ever holding the key, and it cannot be turned back into it.
• A hash of a device fingerprint, computed on your own computer. It only tells the same machine again apart from a different machine, which is what keeps a reinstall from costing you a seat. It is not a hardware serial number, and not the name of your computer.
• A country code: two letters, ISO-3166 alpha-2, such as PE, ES or US. Our host derives it from the connection; we keep the two letters and nothing else.

2. The support details we hold, when we have them

Added in August 2026, and this page was updated in the same change. The three identifiers above are enough to run a licence and not enough to help a person: an email arriving from a customer whose only trace here is a hash cannot be answered without asking them to prove which hash is theirs. So a licence can now carry the following, and this is the complete list.

• Your name and your email address, when the store that took your payment passes them to us, or when you give them to us yourself by writing for support. The product never asks you for either one, and a licence with both fields empty works exactly the same.
• A reference for your case, and a private note we write about it: what went wrong, what we checked, what we did. We write it, not you. You may ask what it says about you and we will tell you.
• The date your licence runs until, when it has one.
• That is the whole of it. There is no record of what you do inside Alyx — no usage history, no feature counts, no profile. The support screen is built out of the licence, seat and event rows described further down, and nothing else exists to build it out of.

3. What we never store

• IP addresses. Not in the licence ledger, not in the download log, not in the support record, nowhere. Like any website, your connection has to reach a hosting provider that sees an address in order to answer it — but no address is ever written into our database.
• Raw licence keys. Only hashes, everywhere, including the audit trail and the support screen — which is why we cannot read your key back to you, not even to help you.
• Anything from your work: no models, drawings, families, schedules, prompts or chat history. The AI runs on your computer, and none of that is sent anywhere.
• Your payment details. The card number, the billing address and the invoice stay with the store that took the payment; we never see them and we could not produce them if asked.
• A password. There is no account to sign into: your licence key is the credential, and the only place it exists in readable form is your own copy of it.
• Cookies and third-party analytics on this website: there are none, and there are no external fonts or trackers either. The only thing this site keeps in your browser is your language choice, stored locally under the name slx_lang.

4. When your computer talks to our server

Six occasions, listed here with what each one actually sends. The first three concern your licence and happen only if you have one. The other three — the trial check, the update check and the download — are made by any installation, including one that has never bought anything and holds no licence at all.

• Activation, once per computer: your licence key and the fingerprint hash go out, and a signed licence for that machine comes back. The key is hashed the instant it arrives and the raw key is never written down. Your copy may also send the version of Alyx it is running, which helps us read the record later. The call is recorded: the key hash, the fingerprint hash, the seat, the country code and whether it succeeded.
• Renewal, roughly every few days in the background: the current signed licence and the fingerprint hash, and a fresh signed licence comes back. Your copy may also send its own clock reading, which we compare with ours to notice a clock that has been turned back and never trust for anything else. Recorded like an activation.
• Release, when you free the seat yourself: the current signed licence and the fingerprint hash, so another computer can take the seat. Recorded like the other two.
• The trial check, sent when Alyx first runs and periodically after that while a trial is running — at most one check a day is ever recorded, however often your copy asks. The trial lasts seven days. It sends the hash of your device fingerprint and, if your copy chooses to, the version of Alyx it is running — no licence key, no licence file, no name and no email address, because a computer on trial has none of those. The answer says when the trial started, when it ends, how much of it is left, and what time our own clock says so your computer can check its own against it. It is the one call in this list that identifies your computer with no licence behind it, and it writes a record: the device trial row set out in clause 5.
• The update check, once every time Alyx starts — so this is the call that happens most often. It sends no key, no licence, no fingerprint and no identifier of any kind: it asks which product and which version of Revit you have, and receives a signed note saying what the current release is. Nothing about it is written to our database, and the answer is the same for everyone, so it is cached and often never reaches us at all.
• Downloading the installer: the request itself and, when downloads require a key, one extra call that exchanges your key for a link that works for ten minutes. Each download attempt is recorded — the time, the key hash if a key was used, the country code, which file and which build was asked for, and whether it succeeded.
• Without a licence, none of the first three calls happens — no key, no seat and no signed licence exist, so there is nothing to activate, renew or release. This page used to say a copy with no licence makes no licence call at all, and that was too broad: the install check still goes out — a copy that has bought nothing announcing that it exists — and it leaves a row behind. The accurate statement: a copy with no licence makes the install check, the update check and the download, and nothing else.
• Using the AI sends nothing at all. There is no request to make: the model is on your own disk.

5. The records we keep, field by field

• Licence: the key hash, which Alyx product it is for, the plan, how many machines it allows, its status, the date it runs until if it has one, the order and customer identifiers the store gives us, your name and email address if we have them, our reference and note for your case, a random identifier for the licence itself, and when it was created or last changed.
• Seat, meaning one computer: the fingerprint hash, when it was first and last seen, the country code last seen, how many times it has renewed, whether it is active or released, and the identifier of the signed licence it is currently holding — which is how we can tell the current copy of a licence from an older copy of the same one.
• Licence events: one row per activation, renewal, release, refusal or revocation. Each row holds the outcome and the reason, the key hash, the seat, the fingerprint hash, the identifier of the licence file involved, the country code, the time on that licence file, the clock reading your computer reported, and a short note that can include which version of Alyx you were running. This trail is append-only — it cannot be edited or deleted by anyone, including us. It carries no name and no email address, on purpose: a record nobody can correct must not hold anything that identifies a person.
• Download events: one row per download attempt, with the time, the licence key hash when a key was used, the country code, which of the two installer files was asked for, which product and which Revit year it was for, the version served, and whether it succeeded. Refusals are recorded as well as successes.
• Device trial — and this is the only record on this page that is not about a customer, which is why it is stated at length rather than in a line. A computer that starts the free trial gets one row, kept under the same device fingerprint hash described in clause 1. It holds when that computer was first seen, the date its trial ends, when it was last seen, how many times it has checked in, and the two-letter country code of the most recent check. There is no key, no seat, no name, no email address and no IP address in it, because a computer on trial has given us none of those — we cannot tell you whose machine a given row is, and neither can anybody else.
• One row per computer, not one per check: it is rewritten at most once a day, and the two dates that decide the trial are written once, when the computer first appears, and never moved afterwards. That is the whole point of it — it is what keeps a trial from starting over on the same machine, which is what used to happen when somebody created a second Windows user account.

6. What is inside your signed licence file

Activation and renewal put a small signed file on your own computer. It is what the software reads to decide what it may do, and it is listed here because it is made out of your data and it decides things about you — so you are entitled to know what is in it. It is not a record we keep; it lives on your disk and we cannot read yours.

• The hash of your licence key and the hash of your device fingerprint — never the key itself, so a licence file that leaks does not leak the key that made it, and cannot be used on a different computer.
• Which product it entitles. The licence file names Alyx, and one licence covers Alyx in every host application it supports — your computer reads that offline, without asking us. Software that is not Alyx refuses the file outright.
• What the software may do: a short list of capabilities — writing to your model, running the local AI, compiling custom code, running composed flows. The software checks that list and nothing else. Because the list is inside a file that expires, capabilities change on their own the moment a subscription lapses, with no uninstall, no message from us and no need for your computer to be online.
• The seat it belongs to, the dates it is valid between, a random identifier for that particular file, and the random identifier of your licence described in clause 5.
• About that last identifier, stated plainly because an earlier version of this page overstated it: it is a random number generated when your licence is created, and today it appears in two places only — this signed file, and our own admin screen. It is NOT embedded in the installer, the AI model or the knowledge base you download. Everyone receives byte-identical files. Its only effect today is that a licence file which leaks says which licence it was issued for, and if that ever changes this page changes with it.
• It contains nothing else. No name, no email address, no IP address, and nothing at all about your work.

7. Why we keep it

To know that a licence is genuine, to keep one licence from quietly becoming twenty, to keep our own hosting inside a free tier that abuse would otherwise burn through, and to be able to answer you when something goes wrong.

That last reason is the whole purpose of the name, the email address and the note. They are used to find your licence when you write to us and to answer you about it. They are not used to market anything to you, they are not combined with anything from any other source, and they are not the basis of any decision made about you automatically.

None of it bans anyone automatically. Unusual activity ranks a list that a human reads, because a wrong ban on a studio that is working costs far more than a copied key.

8. How long we keep it

• Licence and seat records: for as long as the licence exists.
• Licence events: kept as the record of what was sold and activated, which is the question asked years later when someone needs to establish that a licence was genuine.
• Download events: kept for at least 180 days, and may be pruned after that.
• Device trial rows: nothing deletes them today, and the reason is worth saying rather than hiding. The row is the only thing that remembers a computer has already had its free trial, so deleting it hands that machine a fresh one. [[ HOW LONG AFTER A TRIAL ENDS THE ROW IS KEPT, AND WHETHER IT IS EVER PRUNED — the seller must decide a real period and write it here; no number is invented on this page ]]
• Support details — your name, your email address, our reference and our note: [[ HOW LONG AFTER A LICENCE ENDS THESE ARE KEPT, AND WHEN THEY ARE DELETED — the seller must decide a real period and write it here; no number is invented on this page ]]

9. Who can see it

• One person: the owner of Alyx. There are no staff accounts and no roles in the admin screen — it is reached with a single secret that only he holds, and every revocation it can perform is recorded with a reason.
• Our hosting provider necessarily runs the database that holds it. See the next clause.
• [[ WHETHER ANYONE ELSE WILL EVER HAVE ACCESS — a contractor, an employee, a support tool — AND UNDER WHAT WRITTEN AGREEMENT. If the answer is nobody, say nobody. ]]
• Nobody else at all. This is never sold, never shared, never handed to an advertiser or a data broker, and never used to train anything.

10. Who else is involved

• Hosting: Cloudflare runs this website, the licence server, the database and the installer storage. [[ DATA-RESIDENCY WORDING THE SELLER IS WILLING TO COMMIT TO ]]
• Payments: [[ PAYMENT PROVIDER, AND A LINK TO ITS PRIVACY POLICY ]]. It takes the money and holds your card details. It hands us the order identifiers and, so that we can support you afterwards, your name and email address.
• Nobody else. No advertising networks, no analytics vendors, no data brokers — and none of this is ever sold or shared.

11. Your rights

[[ THE DATA-PROTECTION LAW THAT APPLIES TO THE SELLER, AND THE RIGHTS IT GIVES — to be confirmed before selling ]]

In practice: present your licence key, and we can tell you exactly which rows relate to it, tell you what our note about you says, correct your name or email address, empty those fields entirely, revoke the licence, or release its seats.

Emptying those fields costs you nothing: your licence keeps working, because it has never depended on them. What it costs is our ability to recognise you the next time you write, and we will have to ask you for your key again.

One honest limit: the licence event trail is append-only by design and cannot be rewritten, not even by us. That is exactly why it holds no name, no email address and no IP address — hashes, country codes and timestamps only. Your name and email live on the licence record instead, which we can correct or empty on request.

Requests and questions: megasent.go@gmail.com.

12. Changes to this notice

If what we store changes, this page changes with it and the date at the top moves. We will not start collecting something new and quietly leave this text as it was.

That has already happened once, and it is written down rather than smoothed over: in August 2026 we added the support details in clause 2 — a name, an email address, a reference and a note — and this notice was rewritten in the same change. Before that it said we held none of them, which was true then and would have been false the day after.

In the same month we also corrected three things this page had got wrong about itself, and they are named rather than quietly edited. It said a watermark identifier was embedded in your copy of the product: it is not, everyone receives identical files, and clause 6 now says what that identifier actually is. It said your computer contacted us on four occasions and left out the update check, which is in fact the most frequent one: clause 4 now lists five and says what each sends. And it described our audit rows as holding only an outcome and a reason, when they hold more than that: clause 5 now lists the fields.

And it happened again days later, in the same month, with the change that matters most so far. We began keeping a record about people who are not customers. Until then every row this system held belonged to somebody who had bought something; from now on a computer that starts the free trial is recorded too — its device fingerprint hash, the dates its trial runs between, when it last checked in, how many times, and a two-letter country code. Nothing new is collected to do it: that fingerprint hash is the one clause 1 has always described and has always been kept for the computers on a licence, and no IP address is stored, before or after. What genuinely widened is who has a record here at all, and that is too large a thing to leave to a quiet edit. Clause 5 now sets out the trial row, clause 4 lists six network calls instead of five — the sixth being the trial check, which is made by software that holds no licence — and clause 8 says plainly that nothing deletes those rows today.