Privacy Policy

Version of October 29, 2026 · Versión en español · Terms and Conditions

Degú is an artificial intelligence assistant for companies, operated by Prohack SpA (Chilean tax ID 78.041.671-8), with its address at Carmencita 25, Office 72, Las Condes, Santiago, Chile.

Degú is purchased by an organization or, in the mobile app, by a person with a personal account. Prohack does not become the owner of what it processes: the content remains that of whoever purchases the service and of the people it refers to. This policy explains what we process, why, on what basis and for how long. The Spanish version prevails if the two differ.

For the content that an organization connects or uploads, the organization is the controller and Prohack processes it on its behalf, under Annex A of the Terms and Conditions. For account, usage and billing data, Prohack is the controller.

With a personal account, you are the one who purchases: your content is yours, you manage it, and you ask us directly for access, a copy or deletion, within the deadlines in section 6. Prohack processes it only to provide the service to you.

1. What data we process

• Account data: name, work email and role within the organization.
• Usage data: technical information about how the service is used (features, consumption, errors and performance), for billing, security, support, improving the service and producing aggregate statistics that do not identify the organization or any person. The activity log that the organization's administrator sees (who did what) is the organization's content: we process it on its behalf, for auditing and support.
• Billing data: the organization's legal name, tax ID, line of business, address, commune and billing email. Payment data is handled by the payment processor; Prohack does not store card numbers or bank credentials.
• Connected content: the documents and data from the sources the organization decides to connect (Google Drive, OneDrive, SharePoint, network folders, databases, email, WhatsApp and files its users upload), and what each person connects for themselves in "My connectors" (Gmail, Google Chat, Google Drive, Outlook and OneDrive), which stays available only to that person. The Google part is detailed in section 2.
• Content created in the Studio: the images, videos and narrations that users create or edit, with the descriptions they wrote to create them.
• Mobile app data: if the voice features are used, the audio needed to transcribe and respond; and if notifications are enabled, the device identifier needed to deliver them.

The basis for each processing: account and billing data, to perform the contract and meet our legal (tax) obligations; usage data, for our legitimate interest in security and in improving the service, and to bill consumption; and content, on behalf of whoever purchases the service, who must have a legal basis to connect it.

2. Google user data

Degú connects to Google in three ways: the organization's Google Drive and the organization's Firestore, which an administrator connects for the whole company, and "My connectors", where each person connects their own Gmail, Google Chat or Google Drive, for themselves only. In every case Degú requests only the permissions it needs and uses the data only for what this section describes.

The organization's Google Drive

When an organization connects its Google Drive, Degú requests the drive.readonly permission. It is a read-only permission: Degú cannot create, modify or delete files in the organization's Drive.

We use it exclusively to:

• Show the folder tree so the organization can choose what to share with Degú.
• Read the content of the files in the chosen folders in order to index them.
• Answer users' questions, citing the source documents.

The organization chooses which folders it shares and can exclude folders or cut off the connection at any time from the application. There are two actions, with different effects:

• Disconnect revokes the access token. Degú stops reading the Drive immediately, and what was already indexed is kept, so that earlier answers keep their sources.
• Delete with all its data revokes the token and also erases the indexed content of that source: documents, summaries, derived data and the folder selection.

The organization's Firestore

An administrator can connect a Firestore database (Firebase) from the organization's Google Cloud project by signing in with Google. Degú requests the datastore permission, the narrowest one Google offers for Firestore. Google has no read-only Firestore permission, so this one would allow writing, but Degú only reads. We ask that it be connected with an account that only has the Viewer role on the project, so that Google itself rejects any write.

We use it exclusively to:

• List the collections, so the organization can choose which ones to share with Degú.
• Read the chosen collections and keep them in Degú as tables, so the organization's users can query them in the chat.

Deleting the connection erases those tables, everything indexed from them and the stored credentials. To also remove the permission from the Google account, do it at myaccount.google.com/permissions.

My connectors: your Gmail, your Google Chat and your Google Drive

What you connect in "My connectors" (in Settings) is for you only: no one else in the organization, neither an administrator nor a colleague, can use it from their chat, because each request is made with your permission and no one else's. Degú uses it only when you ask it to in the chat.

• Gmail. With gmail.readonly, Degú searches and reads your emails, threads and attachments to answer your questions. With gmail.compose, it writes drafts in your mailbox and sends them. No email is sent in the same message in which it is drafted: Degú shows you the draft, and it can only be sent in a later message of yours, when you ask for it. If you also choose "Allow sorting your email", with gmail.modify Degú adds and removes labels and moves emails out of the inbox (archiving), and with gmail.settings.basic it creates filters for incoming email; each filter is created only when you confirm it in your next message. Degú never deletes emails or empties the trash.
• Google Chat (Google Workspace accounts only). With chat.spaces.readonly and chat.messages.readonly, Degú lists the spaces, group chats and direct messages you take part in, and reads their messages, with the name of who wrote them, to summarize them or find what is still pending. With chat.messages.create, which you may choose not to grant, it posts a message in your name: Degú shows you the exact text and only posts it if you confirm it in your next message, exactly as it was shown to you. If you also grant “Allow messaging people”, with directory.readonly Degú looks up in your company directory the email of the person you want to read or write to, and with chat.spaces.create it opens the direct message with them if it does not exist yet, only when posting a message you confirmed. It only writes to someone outside your company if you type their email.
• Google Drive. With drive.readonly, Degú searches and reads your files to answer, or to attach them to an email it drafts for you. It is read-only: it does not create, modify or delete files.

What we store. We do not copy or index your email, your Chat messages or your files: Degú reads them in Google at the moment you ask. We store only:

• the connection: the connected account, the permissions you granted and the access credentials Google issues, encrypted;
• what is needed for a confirmation to work, which stops being usable after 24 hours: the identifier of each draft Degú wrote (not its content, which stays in your mailbox), the criteria of a proposed filter, and the text of a proposed Chat message with the space it would go to, which is deleted once it is posted.

The conversation with Degú (your question and its answer, which may quote or summarize what it read) stays in your history like any other, and is kept and deleted as described in section 5.

Disconnecting. You can disconnect each service at any time in Settings → My connectors. Degú immediately deletes the connection and its credentials and, for Google Chat, also the messages it had proposed that you did not confirm. It also revokes the permission in your Google account, unless you still have another Google service connected in Degú: Google revokes the application's whole permission, which would also cut off that other service. In that case, or if you want to be sure, you can remove it yourself at myaccount.google.com/permissions.

Limited Use

Degú's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Specifically, for all Google data and without exception:

• We use it only to provide the Degú features described in this section, at your or your organization's request.
• We do not sell it. We only transfer it when needed to provide those features (to the providers in section 4 that run the service), to comply with the law, or for security.
• We do not use it for advertising of any kind, for profiling, or to determine creditworthiness or for lending.
• We do not use it to develop, improve or train artificial intelligence models, whether generalized, our own or third parties'. The Amazon Bedrock models process it only to generate the answer you asked for.
• No person reads it, unless it is essential to resolve a security issue, comply with the law, or provide support with express authorization: from the organization, in writing, or from the account owner, in "My connectors".

3. Where and how it is stored

The infrastructure runs on Amazon Web Services in the United States: region us-east-1, and requests to the models may be processed in other regions of that country. Documents are stored encrypted, and metadata in a database with row-level isolation per organization, so that no organization can reach another's data.

Within each organization, Degú respects the permissions of the original source: a user only gets answers based on documents they already had access to.

Access to production is restricted to authorized Prohack personnel and is logged.

4. Who we share it with

We do not sell data. Only the providers needed to operate the service are involved:

• Amazon Web Services: hosting, storage, database, transactional email, web search and the voice that narrates Studio videos (Amazon Polly), only where the organization has voice enabled.
• Amazon Bedrock: the language models that generate the answers, from developers such as Anthropic, Amazon, Cohere and OpenAI, and the ones that create images and videos, from Stability AI and Luma AI, all running within AWS. Content sent to Bedrock is not shared with those developers or used to train models, as stated in the Amazon Bedrock FAQ and its data protection documentation.
• ElevenLabs: voice in the mobile app, only if its voice features are used.
• Apple: delivery of notifications on iOS, only if they are enabled.
• Fintoc and Paddle: collecting payment for plans, depending on the country. When paying through Paddle, Paddle acts as the Merchant of Record and processes purchase data under its own policy.
• Haulmer: issuing electronic invoices in Chile, with the billing data.

The sources the organization connects (for example, Google, Microsoft or WhatsApp) are governed by their own relationship with the organization. We may also disclose data if a competent authority requires it through legal process.

5. How long we keep it

For as long as the organization (or the person, with a personal account) keeps the service. When it ends (including when a trial expires without a purchase), there are 30 days to request a copy of the content; after that, we delete it (uploaded files, indexed content, derived data and the activity log) and connection credentials within the following 60 days. If deletion is requested at any time, we do it within 30 days of the request. Encrypted backups are erased in their normal rotation cycle. Account data is deleted with the content; usage data is kept for up to 12 months and after that only remains in aggregate statistics that identify no one.

Our security logs (system access and operations) are kept for up to 12 months, and tax documents for the period required by law. The record of the acceptance of the Terms and of this policy (which version, when, and with which account and email) is kept for the limitation period of any claims that may arise from the contract, so that it can be proven.

6. Rights

Users may request access to, rectification, erasure, objection to, portability or restriction of their personal data, and not to be subject to decisions based solely on automated processing, by writing to us or through their organization's administrator. We respond within the legal deadlines. Until November 30, 2026, Chilean Law No. 19,628 applies: we respond within two business days to requests for access, rectification, erasure or blocking (art. 16). From December 1, 2026, Law No. 21,719 applies, adding objection, portability and automated decisions: we acknowledge receipt and respond within 30 calendar days, extendable once by another 30. When the data is an organization's content, that organization resolves the request, with our help; with a personal account, we resolve it.

If the answer is not satisfactory, a complaint may be filed with the competent data protection authority; in Chile, from December 1, 2026, the Personal Data Protection Agency (Agencia de Protección de Datos Personales).

7. Changes

If this policy changes materially, we will notify active organizations and people with a personal account by email before the change takes effect.

8. Contact

Prohack SpA · Carmencita 25, Office 72, Las Condes, Santiago, Chile
soporte@prohack.cl