Most document tools ask a reviewer to trust a policy. This one gives them nothing to review: the file is opened and written inside the browser, and there is no server that ever receives it. Signing, merging, splitting, scanning a contract — all of it happens on the employee's own machine.
There is no self-serve team plan yet. The form reaches a person, and a licence is agreed in writing.
The first number is the one that ends the review. There is no document data held here to place in scope.
The tools open a file and write a new one in the browser tab. There is no endpoint on this site that accepts a document, so there is nothing for a network policy to block and nothing to intercept.
No document store, no object bucket, no temporary directory. A breach of this site cannot expose a customer file, because no customer file was ever sent to it.
Employees can use the suite today, before any contract exists. The free allowance needs no sign-up, so a pilot does not wait on identity-provider work.
It is a web page. There is no agent, no desktop client and no browser extension to package, sign and roll out.
An employee who already bought an individual pass keeps it. Nothing about a licence shortens it, and the 14-day refund policy applies to a first invoice the same way it applies to a $7 pass.
Written here rather than left to a call. A reviewer will find these anyway, and a page that hides them is a page that gets distrusted for the rest of the conversation.
There is no dashboard to add a person, see who is active or reclaim a seat. A licence is a commercial agreement; the tool itself still needs no login, so there is nothing to administer.
Single sign-on and directory sync do not exist, and are not claimed anywhere on this site. If they are a hard requirement, that is worth knowing before a trial.
Because files are never uploaded, usage cannot be measured from our side. A team licence is priced on a seat count, not on metered usage — there is no telemetry that would make metering possible.
Exports carry a Certificate of Execution that records the signers, the placement and a hash of the output. They are not qualified electronic signatures under eIDAS, and this site does not describe them as such.
The useful details are the ones a policy page cannot answer: which documents, who signs them, and whether procurement needs a DPA before a pilot.
If what you want is the engine inside your own product rather than this interface, that is a different licence and it has its own page. It is not packaged as an SDK yet — a licence would start as a conversation, not a download.