Privacy Policy

This policy explains how AgileWorx collects, uses, stores, and shares information when you use Agile Translate. It applies to the Agile Translate web application, the presentations, glossaries, and fonts you upload to it, and the messages and screenshots you send to support.

AgileWorx is the data controller for the information described here. We operate in Saudi Arabia, Egypt, and Qatar. Company information is published at theagileworx.com.

For any question about this policy, write to info@theagileworx.com.

Account information. Authentication is handled by Google Firebase, which holds your credentials. From the sign-in method you use we receive your email address, your display name, your profile photo URL, whether your email address has been verified, and an account identifier. We also record the time of your most recent sign-in, the organisation or team you belong to, and your role. We do not store passwords.

Content you upload. The presentations you upload, the translated presentations we produce, a PDF preview and first-slide thumbnail of each, the glossaries and terminology you create or approve, and any font files you upload.

Support communications. Messages you send through the in-app support form or by email, any screenshots you choose to attach, and the account and app-page context included with the message.

Service records. For each translation we record its status, its timing, the volume of text processed, and the resulting credit charge. These records support your project history and your credit balance.

Technical records. Our servers keep standard access logs, which include IP addresses and browser information. We use them to keep the service secure and to investigate faults, and we keep them for a limited period.

We collect no payment card details and no location data, and we use no tracking or advertising technology.

We use the information above to translate your presentations and return the result, to maintain your project history, to authenticate you and enforce access to presentations, glossaries, and teams, to meter credits and storage against your plan, to scan every upload for malware before it is made available, to answer support requests, and to diagnose failures so that they can be corrected.

We do not use your content to train AI models. We do not sell or rent personal data.

Where a legal basis is required, we rely on the following.

Performance of a contract. Processing your account information and your uploaded content is necessary to provide the service you have asked us to provide.

Legitimate interests. Malware scanning, abuse prevention, diagnosing failures, and securing the service are necessary for the reliable operation of a business product, and we consider these interests balanced against your rights.

Legal obligation. We retain records where the law requires it, and disclose information where we are legally compelled to do so.

This policy follows the data protection laws that apply where we operate.

We use a deliberately small number of providers. This is the complete list.

Google Cloud provides hosting, storage, the database, and authentication through Firebase. Your files and account records are stored in Google Cloud's me-central1 region in Doha, Qatar.

OpenAI provides the translation itself.

Resend delivers messages submitted through the in-app support form to our support mailbox.

Microsoft 365 hosts our support mailbox and stores support correspondence and screenshots while our team handles them.

What the translation provider receives. Only the text extracted from your slides and the glossary terminology that applies to it. The PowerPoint file is never uploaded to the translation provider. Images, embedded media, and file metadata from the presentation never leave our infrastructure.

We also disclose information where the law requires it, and to an acquirer in the event the business is sold, in which case this policy continues to apply until you are notified otherwise.

Translation requires sending slide text to OpenAI, outside our infrastructure, so the terms under which OpenAI holds that text matter.

Training. OpenAI does not use data submitted through its API to train its models unless a customer explicitly opts in. We have not opted in.

Retention. OpenAI retains API content for a limited period for abuse monitoring, after which it is deleted.

Storage and processing. Your files, previews, and account records are held in Google Cloud's me-central1 region in Doha, Qatar. Our application servers run in the same region.

Translation. Slide text is sent to the OpenAI API, an external service that processes it outside the region. No other presentation content leaves our infrastructure.

Support. Messages and screenshots you submit for support are delivered through Resend and stored in our Microsoft 365 support mailbox outside the Google Cloud region.

If you need details of the safeguards applied to that transfer, write to info@theagileworx.com.

Your files are retained until you delete them. A presentation you upload remains available in your account until you remove it or your account is closed.

Files that fail a malware scan are moved to a quarantine location and deleted automatically within 24 hours.

Uploads that are started but never completed are released after six hours.

Account records and translation history are retained for as long as your account remains open.

Resolved support correspondence and screenshots are retained in our support mailbox for 12 months, then deleted.

You can delete a project at any time. Deleting it removes it from the service: the presentation you uploaded, the translation we produced, and the PDF preview and thumbnail generated from them.

When your account is closed we delete the presentations, previews, thumbnails, and glossaries held under it. Records we are required to keep, such as those supporting our own accounting, are retained separately from your content.

To close your account, write to info@theagileworx.com.

Traffic between your browser and the service is encrypted in transit. Files and database records are encrypted at rest. The database is not reachable from the public internet. Every upload is scanned for malware before it becomes available. Access to a presentation is authorised on the server for every request, against your identity and your team membership.

The Security page describes these measures in full.

If personal data we hold is exposed, altered, or accessed without authorisation, we investigate it promptly and notify the relevant authorities where we are required to.

Where the incident is likely to affect your rights or interests, we notify you directly and without undue delay, in plain language, describing what happened and what we are doing about it.

We set four cookies, all of them necessary for the service to work. We use no analytics cookies and no advertising cookies.

`__session` maintains your signed-in session. It cannot be read by JavaScript and expires after five days.

`aw_workspace` records whether you are working in your personal account or in a team. It cannot be read by JavaScript and expires after one year.

`insights_tz` records your browser timezone so Insights groups and displays activity on your local calendar days. It can be read by JavaScript and expires after one year.

`NEXT_LOCALE` records whether you are viewing the site in English or Arabic.

Your interface theme preference is stored in your browser's local storage rather than in a cookie, and is never transmitted to us.

You have the right to be informed of how your personal data is used, to obtain a copy of it, to request that it be corrected, and to request that it be destroyed. You may also ask us to restrict how we use it, object to that use, or transfer your data to another provider.

Write to info@theagileworx.com from the email address on your account. We may ask you to verify your identity before we act on a request, because a request to release or destroy personal data is not something we will take on an unverified email alone.

We aim to acknowledge requests within one business day and complete them within one month. If you are not satisfied with our response, you may lodge a complaint with the data protection authority responsible for you.

When this policy changes we update the date shown at the top of the page. Where a change materially affects how we handle your data, we notify account holders directly before it takes effect.