Legal information
Security and data control
Last updated: 21 October 2026
1. Connections and credentials
The public website and app use HTTPS. IMAP uses TLS on port 993; SMTP supports TLS on 465 or mandatory STARTTLS on 587, with certificate checks. Saved OAuth tokens, IMAP/SMTP credentials and private-catalog credentials are encrypted by the server with AES-256-GCM.
Credential protection does not mean end-to-end encryption of all email. The server must process content and AI features transmit the necessary context to the provider. Infrastructure administrators may have technical data access capabilities: changing a password does not remove those privileges.
2. Access and company separation
Archive pages and operations require authentication and membership of a company with active access. Authentication cookies are HttpOnly, SameSite=Lax and Secure in the HTTPS environment. Mutation requests are subject to origin checks. This is not a guarantee that vulnerabilities cannot exist.
Users can change their password, and accounts marked as having a temporary password require a change. An administrator can suspend company access without knowing the new password. Use unique credentials and do not share accounts.
3. AI, documents and sending
AI classifications and drafts can be wrong. Check recipients, text, catalogue matches, quantities, prices, tax and attachments before sending. Automatic quote generation creates a draft for review, not an automatic send.
Gmail and Outlook can receive a draft with an attachment when authorised. SMTP replies require explicit confirmation. IMAP is not a sending protocol and an SMTP reply is not necessarily copied to Outlook's Sent folder. Check operation outcomes in your email client.
4. Revocation and reporting issues
To stop a connection, disconnect the mailbox in Trattiva and revoke tokens or app passwords with the provider. If you suspect unwanted access, change the affected credentials and contact support. Disconnection does not delete the previously imported archive.
Report issues to filippo.bertoli09@gmail.com with the feature, time and steps to reproduce them. Do not include passwords, API keys, tokens or complete mailboxes; redact customer data in screenshots. Continuous 24/7 support is not claimed.
5. Limits and shared responsibilities
This page describes measures in the code and service, not ISO certification, an independent audit or a guarantee of invulnerability. Guaranteed recovery times and verified backup coverage for every item are not claimed. Agree continuity and export requirements before relying on the service for critical processes.
Customers must lawfully authorise access to mailboxes and catalogues, inform users and correspondents and check that the service is suitable for the data processed. Technical measures do not replace privacy agreements, provider checks and organisational incident management.