POST to Reducto’s license server. In a browser, they go through the license proxy on your backend. No request contains document content, text, file names, paths, user names or email addresses.
What the requests contain
License checks (POST /-/license, before the first document opens and then about every hour) send the license id, the package name and version, a random id for the process or page, and usage counts since the last check, such as the number of documents opened.
Usage reports (POST /-/events, a few seconds after activity) send one event per Session start and per operation:
- The Session id, the file type (
docx), and whether it ran in a browser or a server. - For an operation: the command name, such as
insertText, whether it succeeded, the error class name (for exampleRangeError), and how long it took. Its arguments are not sent, so typed text is not sent. - A timestamp.
Headers and network data
On a server, both requests send your Reducto API key asAuthorization: Bearer. In a browser, the license proxy adds the key, so the browser never has it.
Like all web servers, Reducto’s license server sees the IP address and user agent of the caller. Reducto records the country with usage reports, and the IP address, country and user agent with license checks.
Encryption
Both requests use HTTPS (TLS), so they are encrypted in transit. With the license proxy, the browser connects to your backend over your TLS, and the proxy connects to Reducto over HTTPS. The request body has no other encryption. Reducto signs each license answer.The ReductoSession property
Each file that the package saves has a ReductoSession custom property (see Sessions and billing). The value is a random Session id and a start time, s_<random>@<timestamp>. It contains no data about the user, the machine or the document. It goes to Reducto only as the session_id above.