How we protect your invention
Handing an unprotected idea to software is a real act of trust. Here are the nine things worth knowing, each in a couple of sentences, and each linking straight to the clause that backs it so you can read the binding version whenever you want to.
Your uploads and every output generated for your project stay yours, in full. The licence you give us exists so the software can run and nothing else, and it ends when your material is deleted.
Terms of Service, clause 6 arrow_forwardEvery project has its own knowledge base, memory and vault, and access is decided per request by a policy engine that refuses when it cannot reach a decision. Nothing becomes public unless you publish it.
Privacy Policy, section 4 arrow_forwardSupport sees the shape of your account, not its contents. If you ask us to help with something specific, that access is granted explicitly, expires on its own, and appears in your activity log. No standing access, and none of it silent.
Terms of Service, clause 7 arrow_forwardYour uploads, your documents and your conversations are not used to train, fine-tune or improve any model, ours or anyone else's. Our model providers are contracted on terms that prohibit it.
Privacy Policy, section 2 arrow_forwardShare a project with named people and revoke any of them individually, whenever you like. An unlisted link works like a key rather than a secret: anyone holding it can open it, so you hand it out deliberately.
Privacy Policy, section 4 arrow_forwardWe keep your invention material confidential and use it only as the Terms allow. That obligation survives the end of the agreement, so closing your account does not release us from it.
Terms of Service, clause 7 arrow_forwardA handful of providers help run IPGuru, each doing one job, and all of them are listed publicly. One never receives your content at all. We publish changes before a new provider starts work, and you can object to any addition.
See the list, Privacy Policy section 5 arrow_forwardEncryption in transit and at rest, per-project isolation, authorisation that denies by default, an append-only audit ledger, malware scanning on every upload, and a fresh sign-in demanded for the actions that matter, such as exporting, transferring or publishing.
The full control list arrow_forwardA patent needs your invention to be new, and it is public disclosure that takes that away, whoever does it. Keeping your own side quiet until you file is the most valuable habit an inventor has, so the crew flags the moments that would put your idea in public. When an idea is worth more kept quiet than filed, we help you build the trade-secret record instead.
What we do, and what we do not arrow_forwardThose nine summaries are exactly that. The binding version is in the documents themselves, and confidentiality has a clause of its own in the Terms because it matters more than anything else in there to most of the people who use IPGuru.
Two things we would rather say here than have you discover later. Our infrastructure runs in the United States wherever you are, under Standard Contractual Clauses where a transfer restriction applies. And a SOC 2 programme, including third-party penetration testing, begins in November 2026: until it completes we describe our controls plainly rather than point at a certificate, and we will publish the position as it changes.
Work on a real invention, privately, before you tell anyone anything.
auto_awesome Start free