Terms of Service

The moment you install, sign up, log in, or otherwise use any DaxionTech product — our apps, our hardware, our websites, or anything we put out under the Daxion name (we'll just call all of it "the Services") — you're agreeing to this document. That's the deal.

If something here doesn't sit right with you, stop using the Services. Simple as that. If we update this document later and you keep using the Services anyway, you're agreeing to the new version.

Who can agree. You need to be old enough to enter into a contract where you live. If you're signing on behalf of a company, you need the authority to do so. Don't agree to this for someone else if you can't actually bind them.

Here's the honest version of what we do: we build software and (soon) hardware that makes it harder, slower, and more expensive for someone to break into your stuff. That's it. We don't make things "unhackable." Nobody does. Any vendor that tells you otherwise is selling marketing copy, not security.

When you use the Services, you're acknowledging that:

• Every piece of tech carries some level of risk, and that risk changes over time.
• New attacks and vulnerabilities get discovered all the time — sometimes in software that's been "safe" for years.
• Attackers keep getting better. Defenders have to keep up. That's a permanent arms race.
• No company — us included — can promise you'll never be hit.

So far as the law allows it, DaxionTech — that means us, the founders, the team, anyone working with us, and any companies attached to us — is not on the hook for any of the following, whether it comes from using the Services, misusing them, or not being able to use them at all:

• Someone hacking you, breaking in, or getting access they shouldn't have
• Data being stolen, leaked, copied, or exposed
• Files, accounts, credentials, or anything else getting lost, corrupted, or deleted
• Money going missing — wire fraud, account theft, crypto loss, any of it
• Someone else misusing our software, or someone compromising your account and acting as you
• Our stuff not playing nicely with someone else's stuff
• Bugs we didn't catch, zero-days, or weaknesses nobody knew about yet
• Hardware that fails, fries, or stops working
• Things you could have prevented — weak passwords, ignored update prompts, the usual
• Downtime, slow performance, or the Services being unavailable when you needed them

If something does go wrong and you have a claim against us, the most we'd ever owe you is whichever is bigger: (a) what you actually paid us for that specific product or service in the last 12 months, or (b) one hundred US dollars. Some places don't let companies cap liability this far — if you live somewhere like that, we'll go as low as the law lets us, and not lower.

DaxionTech is still being built. A lot of what we ship right now — Daxion Boost, the upcoming Vault, the Shield work, and whatever comes next — is early. MVPs, prototypes, betas. We don't hide it.

Beta builds break sometimes. They might do weird things, miss edge cases, or not protect against everything we want them to eventually protect against. Don't run anything critical on a beta of ours. Don't use a pre-release version to guard data you can't afford to lose. Use it to evaluate, give us feedback, help us make it production-grade — that's the right way to use early builds.

If you send us feedback, bug reports, ideas, or screenshots from a beta, we're allowed to use that to make the product better. We're not going to owe you anything for sending it, and we're not going to claim you sent something you didn't.

Security only works when both sides do their part. We bring the tools; you bring the judgment to use them well. By using the Services, you're agreeing to do your half:

• Use real passwords. Don't reuse them. Turn on two-factor wherever it's offered — including with us.
• Keep your stuff updated. Your OS, your phone firmware, your apps, and our software. Skipping updates is how people get hit.
• Don't try to reverse-engineer our code, pull it apart, or use it as a weapon against anyone else.
• Don't use the Services to break the law or attack other people. That should go without saying, but we're saying it.
• If you find a bug or a security flaw in something we make, tell us. Reach out through our support channel before you post it publicly.
• If you have Daxion hardware — a USB key, a Vault device, anything physical — keep track of it. Physical access undoes a lot of digital protection.

If you ignore the rules above, we can cut off your access without warning. We don't enjoy doing it, but we will.

The internet is a hostile place, and a lot of what happens out there is outside of anything we can control. You're agreeing that you know about, and accept the existence of, threats like:

• Phishing emails, fake text messages, fake phone calls, and people pretending to be someone they're not
• Ransomware that locks your files, and malware that just destroys them
• Zero-days — flaws in your OS, your drivers, your browser, your hardware — that nobody's patched yet
• Supply-chain attacks, where a library or vendor you trust gets compromised upstream
• Network attacks like DDoS floods, DNS hijacking, and traffic interception
• Cryptography that used to be safe and isn't anymore — including future quantum-era breaks
• Someone on the inside abusing their access, or stolen credentials being used against you

What we build helps reduce the impact of these things. It does not erase them. If you connect to the internet, you've accepted some level of risk by definition — that's not us, that's just how the network works.

Our rule on data is simple: we only ask for what we actually need. If we don't need it to run the Services, keep them secure, or improve them, we don't collect it.

Here's what we might handle:

• Your email and a name when you sign up or subscribe
• Anything you write to us in the chatbot, on a contact form, in a feedback submission, or in a support email
• Basic technical info about your device — OS, version, how the app is performing — so we can fix crashes and make things faster
• Diagnostic info you choose to send us if you're opening a support ticket

We don't sell your data. Not to advertisers, not to brokers, not to anyone. We don't knowingly take data from kids. And when Daxion Vault is live, anything you encrypt in it stays under your key — not ours. We literally won't be able to read it, even if a court asks us to. That's by design.

If you want the full version — what we keep, for how long, your rights under GDPR or CCPA, how to ask for a copy of your data or have it deleted — read our Privacy Notice or just email us. We'd rather you ask than guess.

This part is about the physical Daxion devices we're working on — Daxion Vault, the Shield modules, USB security keys, and any other hardware we ship later. We'll just call all of it "Daxion Hardware" so we don't have to keep listing them.

• You'll need to register it. When you receive a Daxion Hardware device, you'll likely need to tie it to a verified account. That's how firmware updates reach you, how warranty service works, and how we make sure a lost device can be flagged.
• Warranty. We may offer a limited warranty on manufacturing defects. It won't cover devices that were dropped in water, opened up, modified, or compromised because the computer you plugged them into was already infected.
• It's not magic. Hardware security makes you a much harder target. It doesn't make you untouchable. Someone with the physical device in their hands, the right lab gear, or a side-channel attack can still get past hardware-based protection. Anyone who tells you otherwise is lying.
• Take care of it. Treat a Daxion Hardware device like you'd treat a key to your house. If you lose it or it gets stolen, tell us immediately. We can revoke its access remotely. We can't always wipe it remotely — that depends on whether it can reach the network.
• Updates. We'll push signed firmware updates from time to time. Some will patch security issues, some will add features. If you refuse updates, you're going to fall behind on protection.
• End-of-life. At some point, older hardware revisions will stop getting support. We'll give you reasonable notice when that's coming. After that, you can keep using the device, but you're on your own.

Everything we make — the code, the designs, the names, the logo, the documentation, the methods we use behind the scenes — belongs to DaxionTech (or to the people who licensed it to us). When you use the Services, you're getting permission to use them the way they're meant to be used. That's it. You're not getting ownership of anything.

Don't copy our software, repackage it, rebrand it, sell it, sublicense it, or build something on top of it without asking us first. The names Daxion, DaxionTech, Daxion Boost, Daxion Vault, and Daxion Shield, along with the look and logo that go with them, are ours. Please don't use them in ways that confuse people about who made what.

We try to keep everything running smoothly, and most of the time we do. But we're not going to pretend we'll never have downtime, glitches, or stretches where something is broken. Servers need maintenance. Infrastructure gets migrated. A security incident sometimes means pulling things offline on purpose. Power goes out. Sometimes the internet itself has a bad day. Any of that can interrupt the Services.

We can also change, pause, or shut down parts of the Services when we have to — for security, for legal reasons, or because the product is heading in a different direction. We'll try to give you a heads-up when it makes sense. Sometimes we won't be able to.

Unless we've signed something separate with you that says otherwise, everything we put out is "as-is" and "as-available." That's the truth, and we're not going to dress it up with warranty language we can't actually back. We're not promising it's perfect, bug-free, fit for what you have in mind, or that it'll be there when you need it.

That said, we're not going to leave you hanging when things go sideways. Where we can, we'll help. On a best-effort basis, that usually looks like:

• Helping you figure out what happened and how bad it is
• Walking you through incident response and what to do next
• Sorting out configuration or integration issues so the product actually works for you
• Being straight with you about what you're exposed to and what your options are

None of that is a contract. We're doing it because we care about the people who use what we build — not because we have to. We can't promise we'll get your files back, get your account back, or undo what happened. Anyone who promises that without seeing the situation first is lying to you.

Hit confirm below and you're telling us you've actually read this — not skimmed it, not assumed — and that the disclaimers and risk acknowledgments above make sense to you. From that point on, this is a real contract between you and us.

We'll update this document as threats shift, laws change, and our products grow. When that happens, we'll publish the new version on this page. If you keep using the Services after that, you're agreeing to the new version. It's a fair deal — we keep the document honest, you stay current.

Got a question about any of this? Don't guess. Email us at daxiontech.com@gmail.com and we'll explain it like a human.