ARNSTEINGROUP

Last updated: 7 October 2026

Application-specific notice

Privacy notice

How Zlero AI OS handles Gmail data.

This notice concerns the private Zlero AI OS Gmail integration. It is separate from the Arnstein Group website and Garmin privacy notice. Hosting this information on the Arnstein Group domain does not make every connected mailbox or project an Arnstein asset.

1. Operation and contact

The application operator is Arnstein s.r.o., Company ID 07451032, Revoluční 1044/23, Staré Město, 110 00 Prague 1, Czech Republic. Access to each connected mailbox requires authorisation from its account holder or the relevant organisation. Operating the application does not transfer ownership of mailbox contents or merge separate businesses and projects. Application and privacy contact: novotnyjan@arnsteingroup.cz.

2. Information accessed

With account authorisation, the integration reads the account email address, message and thread identifiers, sender and recipient details, dates, subjects, message bodies, labels, read/unread metadata, and attachments. Original messages are retained with their full email headers. Complete collection includes historical mail, spam, trash and drafts.

OAuth access and refresh tokens are stored locally to maintain the authorised connection. Passwords are not requested by the collector.

3. Purpose and permissions

The data is used to preserve an email archive, retrieve correspondence and documents, and support owner-requested review of selected records. Local full-text search and document attachment extraction are in development. Only the Gmail read-only scope is requested; the integration does not change mailbox contents or read/unread state.

4. Storage and access

Original messages and attachments are stored in compressed email files on the operator-controlled computer, together with a local database index. OAuth tokens use owner-only file permissions. The local archive is included in encrypted backups held with Backblaze B2. Backup access is controlled by the operator.

The public website is hosted on Netlify. The collector does not upload Gmail messages, attachments, indexes or OAuth tokens to Netlify. Website requests may produce technical hosting logs.

5. Sharing and AI-assisted use

The collector and planned local query tool do not automatically transmit message content to external AI providers. If the owner requests analysis of selected material with an external assistant, that is a separate transfer to the selected provider. The owner must check that provider's applicable privacy, retention and training settings and disclose and authorise the intended data use before sharing.

Gmail data must not be sold, used for advertising, credit scoring or unrelated profiling, or used to train or improve general-purpose or non-personalised AI models. Any permitted transfer must be limited to the requested functionality or another exception allowed under Google's Limited Use requirements.

Zlero AI OS's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

6. Retention, revocation and deletion

The archive is retained for the owner's requested historical recordkeeping. No automatic expiry or deletion schedule is currently implemented. Revoking authorisation in Google Account settings prevents further authorised collection but does not automatically delete copies already archived.

To stop collection or request deletion of an archive, index, extracted files or credentials, contact novotnyjan@arnsteingroup.cz. Deletion is a separate, manual operation. Any legally required retention and the treatment of backup snapshots must be reviewed for the relevant account. No fixed deletion deadline or backup retention period is specified here; the applicable arrangements are confirmed when a request is handled.

7. Separate accounts and projects

Separate account archives and tokens are being added. Mailbox membership alone is not used to decide which business or project owns a document. Mixed personal and business correspondence must be handled according to its actual purpose and responsibility.

8. Changes and requests

Material changes to access, purpose or sharing must be disclosed before the changed use begins, with renewed authorisation where required. Questions and requests about personal data can be sent to the contact above.