Privacy at Ugla

The short version

You choose whether to connect Google services. Your Ugla server holds the connection and uses the information needed for the tasks you authorise, including background work you enable.

Your choice of AI determines where task content is processed: on your machine, by an external provider you select, or through Ugla AI and its model provider. Connecting Google does not mean all processing stays on your phone.

We do not use Google connection data to train general-purpose AI models or for advertising. Disconnecting stops further use of the connection; deleting information already saved in chats, memory, files and backups is a separate step.

When you visit

Your browser sends technical information, including your IP address and the page requested, to our hosting infrastructure so it can deliver the website. The website is hosted on our Hetzner server. Cloudflare provides domain name resolution.

We do not add advertising, analytics trackers or cookies to this website. Fonts and the eye animation are served from the same website. Our web server is not configured to keep a visitor access log for this site.

When you contact us

If you email hello@ugla.ai, Cloudflare forwards your message to our Gmail inbox. Cloudflare and Google process the message, as does your own email provider. We receive your address, message and any information you include so we can respond. Please do not send passwords, access keys or sensitive account information.

When you request a beta invitation

To handle your beta request, we use your email address and your answers: the machine you would run Ugla on and the phone you use. If you choose “Something else,” we also keep the short description you type. We store the request in a protected list on our server. We do not subscribe you to marketing.

We also count the answers per day, without your email address or description, to see which setups people ask for. These counts cannot be linked to you and are kept after your request is deleted.

We process your request because you asked us to, as a step before providing the beta service. If we invite you, we share your email address with Apple for TestFlight. Apple processes tester information under its own privacy terms.

We delete the request after inviting you or when you withdraw. An automatic cleanup, at least once a day, removes requests older than 90 days. Server backups may retain a copy until they expire. Apple’s TestFlight record is separate; contact us to withdraw from the beta and ask us to remove your tester record.

To protect the form from spam and duplicate requests, our server temporarily holds scrambled fingerprints (salted hashes) of email and IP addresses in memory for up to one hour. We do not log form contents or store your IP address in the beta list.

To withdraw or request deletion, email hello@ugla.ai. You may also contact us to exercise your data protection rights, and you can lodge a complaint with Sweden’s privacy authority, IMY.

When you connect Google services

Google connections are optional. You choose a Google account and grant permission on Google's own sign-in page. Ugla receives your Google account identifier and email address to identify the connection. Ugla does not receive your Google password.

For Gmail, Ugla can read messages and their metadata to find mail, explain a thread or prepare a reply. With your permission it can save drafts, send messages, change labels and move messages to the trash. It does not request permission to permanently delete Gmail messages outside the trash.

For Google Calendar, Ugla reads your calendar list so you can choose calendars. It uses events and availability to answer scheduling questions and, with your permission, create, move or cancel events. Calendar information can include event titles, times, descriptions, locations and attendees.

For Google Drive, Ugla uses file metadata and content to find existing files, read or summarise documents and export supported Google documents as text. With your permission it can create documents, change file properties, move files to the trash and share files with people you specify.

Google's permission screen describes the access you grant. Ugla's own connection controls determine which operations it may perform and which must ask you first. Permission from Google does not let Ugla grant itself additional authority.

Where Google data goes

In this notice, Google information includes the raw information received from Google APIs and information derived from it, including summaries, extracted facts, and aggregated or anonymised information. The same restrictions on use, sharing and general-purpose AI training apply to all of these forms; removing identifiers does not remove those restrictions.

Your Ugla server exchanges the Google sign-in result for connection tokens and stores them in its encrypted vault. The server calls Google directly and can carry out work you have authorised while your phone is off. The connection tokens are not given to the AI model or stored in the ugla.ai website.

Google information used by a task may appear in conversations, saved results, memory, files or calendar information on your Ugla server. The website and Ugla's service-management system do not become a copy of your connected mailbox or Drive.

Where your server runs is a separate choice from which AI does the thinking. If you choose a server operated by someone else, that operator and its hosting provider are part of the processing environment. Operators of the hardware can have infrastructure access; owning your Ugla server is not a promise that a hosting provider cannot access the machine.

Google data and AI

An AI request can include Google information needed for the task, such as a message to summarise, calendar details or a document excerpt. With a model running on your own machine, that model processing stays there. With an external model, the selected information goes to the company that operates the model. With Ugla AI, the selected request passes through Ugla's separate inference service before reaching its approved model provider; Ugla does not store or log that request or response content in that service.

An external provider's processing location, retention and permitted human access depend on the service and plan used. Review those terms before permitting Google information to be sent there. Only use Google connections with a model service whose terms prohibit using that information to train or improve general-purpose AI models. This requirement also applies when you supply your own model account or API key.

Ugla uses Google information to provide the features you authorise. We do not sell it, transfer it to data brokers, use it for advertising or creditworthiness and lending decisions, or use it to train or improve general-purpose AI models. These restrictions also cover aggregated, anonymised and derived Google information. We do not permit transfers to a model service for general-purpose model training or improvement. Ugla follows the Google API Services User Data Policy, including its Limited Use requirements. A transfer to another service must be needed for an authorised feature and covered by your consent.

Disconnecting and deleting Google data

You can disable or disconnect a Google connection in Ugla's connection controls. Disconnecting stops new work through that connection and requests deletion of its connection key from your server's vault. If the vault is locked or deletion fails, the cleanup must finish before the key is reported as removed. Disconnecting in Ugla is separate from revoking permission in Google. Google may still show that you previously granted Ugla access. To revoke that permission, open your Google Account, go to third-party connections, select Ugla and remove its access. Disconnecting Ugla does not sign you out of Google in your browser.

Disconnecting does not delete your original Google messages, events or files. It also does not automatically erase information already saved in your Ugla conversations, memory, files or backups, including summaries, extracted facts and other derived copies. Remove those copies separately using the controls for that information and any backups you keep. Saved information on a server you operate remains under your storage and deletion choices; it has no automatic expiry merely because you disconnect Google.

If you need help removing information processed by a service operated by Ugla, contact hello@ugla.ai. Identify the service and request without sending passwords, connection tokens or recovery keys. An external model provider may retain a request under its own service terms; disconnecting Google does not revoke or erase a request already delivered to that provider.

Questions and requests

You can ask about information you have shared with us, request a correction or ask for deletion by contacting the Ugla team. Where applicable, you may also request access, portability or restriction, object to processing, or withdraw consent. You can complain to Sweden’s privacy authority, IMY. We may need to verify that a request is yours before acting on it.

hello@ugla.ai