Privacy Policy

Your privacy is important to us. It is UNIO's policy to respect your privacy regarding any information we may collect from you across our website, https://unio.ai, and other sites we own and operate.

We only ask for personal information when we truly need it to provide a service to you. We collect it by fair and lawful means, with your knowledge and consent. We also let you know why we’re collecting it and how it will be used.

We only retain collected information for as long as necessary to provide you with your requested service. What data we store, we’ll protect within commercially acceptable means to prevent loss and theft, as well as unauthorized access, disclosure, copying, use or modification.

For ordinary website use, we don’t share personally identifying information publicly or with third parties, except when required by law. AI-agent use involves the service-provider processing described in the AI Agents and Google integrations section below.

Our website may link to external sites that are not operated by us. Please be aware that we have no control over the content and practices of these sites, and cannot accept responsibility or liability for their respective privacy policies.

You are free to refuse our request for your personal information, with the understanding that we may be unable to provide you with some of your desired services.

Your continued use of our website will be regarded as acceptance of our practices around privacy and personal information. If you have any questions about how we handle user data and personal information, feel free to contact us.

This policy is effective as of 1 January 2021.

AI Agents and Google integrations

This section covers the AI assistant, a private deployment operated by the owner of unio.ai for their own personal use. For privacy questions, requests to disconnect the integration or requests to delete retained copies, contact max@unio.ai.

Data and purposes

The Google Calendar integration accesses calendar identifiers and metadata, event titles and descriptions, times, locations, organizers and attendees returned by its calendar operations. OAuth tokens authorize access to the connected account. Relevant conversations and operational records may also contain calendar information.

This information is used for requested scheduling, agenda summaries, user-directed event creation and deletion, and personal-assistant workflows you expressly configure. Authorizing Calendar access does not give blanket permission for unrelated collection or arbitrary external actions.

Requested Google permissions

The authorization request includes the following permissions. You choose which permissions to approve:

  • Calendar: view and manage calendars and events.
  • Gmail: read email messages and settings, and send email on your behalf.
  • Drive: read and download all your Drive files, and create or manage files created by, opened with or shared with the assistant.
  • YouTube: view YouTube account data available through the YouTube Data API. This permission does not provide watch history.

Granting a permission does not authorize unrelated collection or arbitrary actions. Sending messages or changing files must follow your instructions and applicable confirmation rules.

Processing and retained copies

The assistant is hosted on Amazon Web Services (AWS) in Frankfurt, Germany. It sends the information needed to process requests to the OpenAI API for AI inference, and uses connected messaging channels to receive requests and deliver responses. The server location does not mean that all service-provider processing takes place in that region. AI inference means processing information to generate a response; it is distinct from training a general-purpose AI model.

OAuth credentials, fetched calendar data, conversation history, summaries and persistent memory, operational logs and backups are distinct kinds of data. Calendar results and derived summaries can remain in conversations, logs and memory after a request has finished. Disconnecting does not by itself remove retained copies.

Your control

You can stop using the integration and revoke its Google permissions through your Google Account connections. Revocation stops authorized API access; it does not automatically erase stored conversations, memories, logs or backups. Deleting retained copies is a separate step from revoking access.

Each Google integration requires your approval of the requested permissions. Neither continued website use nor an update to this policy is OAuth consent.