Security & Trust
Building trust into global growth. How GlotEO protects your content, your account, and your customers’ information.
At GlotEO, we recognize the importance of protecting your content, your account, and your customers’ information.
We aim to make our security and data-handling practices transparent so you can make informed decisions about using our platform. This page describes the safeguards we maintain today and the limits of what we claim. The binding rules are in our Terms, Privacy Policy, and Data Processing Addendum.
Your content stays yours
You retain ownership of the content you provide to GlotEO and of the translations and localized assets generated from it, subject to our Terms.
GlotEO processes website content, images, videos, and related information to provide translation, localization, and publishing services. Our license to that content is limited to providing, maintaining, securing, and supporting the service you asked for. We do not use it to train AI models unless you give separate, explicit permission.
AI processing and transparency
GlotEO uses AI and third-party technology providers to deliver translation and localization. Sending content to a model so it can produce a translation is not the same thing as allowing that provider to train on it.
Customer content may be processed by these providers to generate the result you requested. The Privacy Policy explains that distinction, and the subprocessor register names the providers, what they process, and where to read their terms.
Video and audio localization is provided by Verbalate. The same rule applies: we do not use that content to train AI models, and we do not authorize Verbalate to do so, unless you give separate, explicit permission.
We may analyze operational information to keep the service secure, troubleshoot problems, and improve performance. That is not a license to train models on your content.
AI providers and data privacy
Trusted AI infrastructure. GlotEO uses established AI providers, including OpenAI and Google Gemini, through their commercial APIs for translation and localization. Those APIs come with the providers’ own contractual privacy terms. Using them does not certify GlotEO, and it is not a zero-retention setup.
No AI training by default. OpenAI states that it does not use API data to train its models unless you explicitly opt in. Google states that the paid Gemini API does not use submitted prompts and responses to improve its products. We do not submit customer content on unpaid Gemini quota, because that quota may be used to improve Google’s products. Sending content so a model can produce a translation is inference, not the same thing as training.
Commercial data protection. Both providers publish data processing terms that describe their security and privacy obligations. Read OpenAI’s business data privacy page and OpenAI’s Data Processing Addendum, and Google’s Gemini API terms.
Encryption and security. OpenAI states that business data is encrypted in transit and at rest on its side. Google describes safeguards for the paid Gemini API, including processing under its data processing addendum. Those are the providers’ controls. GlotEO is not independently ISO 27001 or SOC 2 certified.
Data retention. A response does not mean the provider has already deleted the prompt. Providers may keep certain data for a limited time for security, abuse monitoring, or service operation, depending on the API and the account settings. Google’s paid Gemini API logs prompts and responses for abuse monitoring. Zero data retention is a separate option and is not how these calls are described here. See Google’s Gemini data retention notes.
GlotEO’s responsibility. GlotEO remains responsible for securing its application, controlling access, and protecting customer information. Provider certifications are not GlotEO certifications. Details of who processes what are in the subprocessor register and the Data Processing Addendum.
Protecting your information
GlotEO uses access controls and administrative and technical safeguards designed to reduce unauthorized access to customer information.
The GlotEO website and application are served over HTTPS. Account passwords are stored as hashes rather than plaintext. Security measures are reviewed as the platform develops.
No method of transmission or storage is completely secure. We do not claim that these safeguards make loss, outage, or unauthorized access impossible.
Data storage and privacy
GlotEO uses third-party hosting and technology providers. Information may be processed or stored in Australia and other countries, including the United States.
We retain information according to the schedule in the Privacy Policy, the purpose of the information, and applicable requirements. Customers can contact us to request access, correction, or deletion of personal information, subject to those requirements.
Deleting a project from GlotEO removes it from our active systems on that schedule. It does not erase copies that search engines or other independent sites may already have made of pages you published.
Security standards and compliance
We are building our security practices as our platform develops.
GlotEO does not currently hold an independent security certification. Information about certifications, assessments, and related security documentation will be published here when it applies. Until then, this page, the Privacy Policy, and the subprocessor register are the documents to use when you assess the service.
If something goes wrong
If we confirm a security incident that affects your customer data, we will notify the account holder without undue delay and reasonably cooperate with their investigation. That notice is separate from any obligation to report to a regulator or to notify individuals, which depends on the incident and the law that applies.
Security enquiries
Have questions about how GlotEO handles your data?
We are happy to discuss your organization’s security and privacy requirements before you connect your website or submit content.
Contact us: gloteo.com/contact
Related: Privacy Policy · Terms · Subprocessors · Data Processing Addendum · Contact