1. Product identity
Editor Ultra is a web editor for paginated documents, HTML, code and PDFs. The commercial description specifies included features, formats, limits and supported requirements. It includes spreadsheets (Grid and Board) and tools for connecting an AI assistant chosen by the user; it is not a modification of the free Editor HTML app. Shared sign-in does not merge product entitlements.
Preparing professional documents is a possible use, not advice, certification, filing or legally compliant preservation. The following warnings explain operation and do not exclude ONMAKE's conformity, care, security or mandatory liability duties.
2. Import, conversion and export
Moving between supported Word, ODT, RTF, Markdown, HTML, PDF and other formats may change fonts, styles, numbering, breaks, layout, tables, links, comments, fields, attachments and properties. Identical reproduction of every original file is not guaranteed. Results must be checked before sending, printing, publishing or filing.
Keep an original copy and separately check text, pages, images, data and metadata. Local autosave is a recovery aid, not a guaranteed archive or independent backup. Correct display does not prove every object, signature or structural feature remains unchanged.
3. Local engine and transfers
PDF processing may occur in the browser. Some features and fallback after an error or unsupported operation use the server and may upload the file. Where confidentiality requires no transfer, stop operations requiring the server and use only a verified local path. Server-side processing runs on ONMAKE's machines; conversions use the ExactDOC engine installed on the same machine.
Forms, comparisons, PDF/A and document conversions may follow different paths. Applicable limits must be stated in the offer and operation. Processing every document, font, standard or corrupted file is not promised.
5. Signatures and certificates
Signing in Editor Ultra inserts a graphical signature drawn or uploaded as an image. It is not advanced or qualified electronic signing, does not itself establish the signer's identity or authority and issues no ONMAKE seal or timestamp. An OnFirma email signature does not become a digital signature when inserted into a PDF.
PAdES, CAdES or .p7m verification is a technical check against the data, certificates, trust lists and revocation information available at that time. Indeterminate results, unreachable services, unknown revocation status or merely declared signing times must not be treated as positive validation. The check is not legal advice on effectiveness, authority, consent or admissibility. Editing a signed document may invalidate or alter its signature: retain the original and apply the appropriate external signing process to the new file.
7. Passwords and confidentiality
Opening protection and PDF permissions serve different purposes. Copy, print and editing restrictions depend on reader compliance with specifications and may be ignored by non-compliant software; they are not absolute extraction protection. Weak or shared passwords reduce protection. Server operations may require access to decrypted content: file encryption is not end-to-end encryption of the whole workflow.
Do not send passwords or confidential documents in ordinary support reports unless necessary and through an agreed channel. ONMAKE does not guarantee recovery of an unknown password.
8. Publishing and external content
FTP/FTPS/SFTP publishing is available through enabled paths. Customers must be authorised on the destination and check directories, permissions and files to be made accessible. Publishing may make content public and overwrite files, requiring specific confirmation and an appropriate recovery copy.
Do not use unencrypted FTP for personal documents or credentials. In the service, the certificate of an FTPS server and the identity of an SFTP server are not verified: encryption without server-identity verification does not provide the protection of an authenticated connection. Use these connections only with trusted servers and not for personal or confidential documents or sensitive credentials.
Opening HTML or content with remote resources may request third-party resources unless blocked or isolated. The offer does not promise anonymous browsing or untested security isolation. Preview functions must apply safeguards appropriate to untrusted content.
9. Final review and support
Before consequential use, check outputs using suitable tools and procedures, especially for pleadings, contracts, redacted data and signed files. After an anomaly, where lawful retain original and output, record version and steps and send a minimised report to info@onmake.it. Support and defect remedies are not conditional on waiving ONMAKE's liability.
10. AI assistants and agent tools
An AI assistant, in the browser or external, can read, create, edit, export and delete the user's documents and spreadsheets with the tools provided. With the in-browser assistant, deleting and exporting ask for confirmation on the page. Model responses may be wrong, incomplete or invented: the user checks every change and keeps copies of important documents.
Documents may contain text written to deceive an assistant (prompt injection). The service tells the assistant that document content is data to read, not instructions, but this does not remove the risk: users should not connect an assistant to documents they are unwilling to expose to its provider, and should review the actions taken.
The in-browser assistant remembers the user's provider, model and key in their browser, with the key encrypted; anyone using a shared device should disconnect it afterwards. With MCP or REST API the external AI acts with the user's key or authorisation, which can be revoked.