Translazor — Privacy & Data Policy
Last updated: May 2, 2026
Plain-English summary (not a substitute for the full policy): Translazor is designed so your application content stays under your control. We do not store your translated page content on Translazor servers. If you use Translazor in your Blazor application, translations are performed through the translation provider you configure, such as Azure Translator, using your own provider credentials. We may store basic account, billing, license, and support data needed to sell, deliver, validate, and support your license. Payments are handled by Stripe.
1) Who we are
Provider (“we”, “us”): Ahmed Elshorbagy, operating under Individual Activity (Individuali veikla) in Lithuania (“Translazor”).
Address: Vilnius, Lithuania
Business registration: Individual Activity (Individuali veikla) — certificate/ID available upon request.
Contact: Contact us
This Privacy & Data Policy explains how we collect, use, store, and protect personal data when you visit our website, purchase or use Translazor, create an account, use the customer dashboard, contact support, or otherwise interact with us.
2) Important product privacy note
Translazor is a software component/library that runs inside your own Blazor application. In normal use, your application content, page text, translated values, and cache data remain in your own environment.
- We do not host your Blazor application.
- We do not receive or store your page content for translation.
- We do not store your translated page content on Translazor servers.
- We do not sell your data.
- We do not use your application content to train AI models.
When translation is requested, your application may send text to the translation provider you configure, such as Azure Translator. That processing is controlled by your own configuration, provider account, and provider terms.
3) Data we may collect
Depending on how you use Translazor, we may collect the following categories of data:
- Account data: name, email address, company name, billing email, dashboard account information, and login-related identifiers.
- Billing and payment data: plan, subscription status, billing address, tax information, VAT ID if provided, payment status, invoices, receipts, Stripe customer ID, Stripe subscription ID, and Stripe checkout/session references.
- License data: license key, license status, plan, expiry date, activation date, domain/website associated with the license, and license validation history where needed for fraud prevention, abuse prevention, or support.
- Technical data: IP address, browser type, device information, request metadata, logs, error messages, and timestamps when you use the website, dashboard, checkout flow, license validation API, or support services.
- Support data: messages you send us, support requests, diagnostic information you choose to share, screenshots, logs, and attachments.
- Website usage data: pages visited, referring pages, approximate location derived from IP address, and interaction data if analytics or similar tools are enabled.
4) Data we do not intentionally collect from your application
Translazor is designed to avoid sending your application content to Translazor servers. Unless you intentionally provide it to us, for example in a support request, we do not intentionally collect:
- Your Blazor page content.
- Your translated page content.
- Your users’ translated messages or UI text.
- Your Redis or MemoryCache translation values.
- Your Azure Translator API key or other translation provider secrets.
- Your application database content.
If you send logs, screenshots, configuration files, or code samples to support, you are responsible for removing secrets, personal data, or confidential customer data before sending them.
5) How we use your data
We use personal data for the following purposes:
- To provide, deliver, activate, and validate Translazor licenses.
- To create and manage your customer dashboard account.
- To process payments, subscriptions, cancellations, receipts, taxes, and invoices.
- To provide support and respond to your requests.
- To prevent license abuse, fraud, unauthorized sharing, and misuse of the Product.
- To maintain security, debug issues, monitor service reliability, and improve the website and customer portal.
- To send service-related emails, such as license delivery, payment confirmation, renewal notices, subscription updates, and important product or legal notices.
- To comply with legal, tax, accounting, and regulatory obligations.
6) Legal bases for processing
Where the GDPR applies, we rely on one or more of the following legal bases:
- Contract: to sell, deliver, manage, support, and validate your Translazor license or subscription.
- Legal obligation: to comply with tax, accounting, invoicing, consumer protection, and regulatory requirements.
- Legitimate interests: to secure our systems, prevent abuse, detect fraud, improve the website, support customers, and protect our business.
- Consent: where required, for example for certain optional cookies, analytics, or marketing communications.
7) Translation providers and application content
Translazor may help your application send text to a third-party translation provider that you configure, such as Azure Translator.
In that case, the translation request is made from your application environment using your configured provider credentials. You are responsible for your provider account, provider configuration, provider fees, and compliance with the provider’s terms and privacy notices.
We are not responsible for how third-party translation providers process text sent by your application. You should review the privacy and data processing terms of any translation provider you choose.
8) Caching and stored translations
Translazor may support caching using your application’s configured cache, such as MemoryCache or Redis. Cached translations are stored in your environment, not on Translazor servers, unless you separately choose to send them to us.
- MemoryCache: stored in your application memory.
- Redis: stored in the Redis instance you configure.
- Cache keys: generated by your application/Translazor configuration.
- Cache lifetime: controlled by your application and configuration.
You are responsible for securing your cache infrastructure and ensuring that cached translations do not contain sensitive personal data unless appropriate safeguards are in place.
9) Payments, billing, and Stripe
Payments are processed by Stripe. We do not store your full card number on our servers. Stripe may process payment information, billing details, tax information, fraud prevention data, and transaction metadata according to its own terms and privacy notices.
We may store Stripe identifiers, such as customer ID, subscription ID, checkout session ID, invoice ID, and payment status, so we can manage your subscription, license, renewals, cancellations, refunds, and support requests.
Stripe may act as a controller and/or processor depending on the payment activity and applicable law.
10) License validation and abuse prevention
Translazor may use online license validation to check whether a license key is valid, active, expired, suspended, or associated with a permitted domain.
For this purpose, we may process:
- License key or license key hash.
- Domain or website associated with the license.
- Plan, expiry date, and subscription status.
- Basic request metadata, such as timestamp, IP address, and validation result.
- Error or abuse indicators, such as unusually high validation attempts.
We use this data to protect paid licenses, prevent unauthorized sharing, troubleshoot customer issues, and keep the Product commercially viable.
13) International data transfers
Some providers we use may process data outside Lithuania or the European Economic Area. Where required, we rely on appropriate safeguards, such as adequacy decisions, Standard Contractual Clauses, data processing agreements, or other lawful transfer mechanisms.
Third-party providers, such as Stripe or hosting/email providers, may have their own international transfer arrangements described in their own privacy documentation.
14) How long we keep data
We keep personal data only as long as reasonably necessary for the purposes described in this Policy, unless a longer retention period is required by law.
- Account and license data: kept while your account/license is active and for a reasonable period afterward for support, audit, and anti-abuse purposes.
- Billing, invoice, and tax records: kept for the period required by applicable tax and accounting laws.
- Support messages: kept as long as needed to resolve your request and maintain support history.
- Security and technical logs: kept for a limited period unless needed to investigate abuse, fraud, security incidents, or legal claims.
- Marketing data: kept until you unsubscribe or withdraw consent, where applicable.
15) Security
We use reasonable technical and organizational measures to protect personal data against unauthorized access, loss, misuse, alteration, or disclosure.
- Access control for systems containing customer/license data.
- HTTPS/TLS for website and API communication where applicable.
- Limited access to production systems.
- Use of established third-party providers for payment processing.
- Monitoring and logging for security and abuse prevention.
No system is perfectly secure. You are responsible for securing your own application, hosting environment, translation provider keys, Redis/cache infrastructure, and production secrets.
16) Your GDPR rights
Where the GDPR applies, you may have the following rights, subject to legal conditions and limitations:
- The right to be informed about how your data is processed.
- The right of access to your personal data.
- The right to rectification of inaccurate or incomplete data.
- The right to erasure, also known as the right to be forgotten.
- The right to restriction of processing.
- The right to data portability.
- The right to object to certain processing.
- The right to withdraw consent where processing is based on consent.
- The right to lodge a complaint with a supervisory authority.
To exercise your rights, contact us at support@translazor.com. We may need to verify your identity before responding.
18) Children
Translazor is a developer/business software product and is not intended for children. We do not knowingly collect personal data from children. If you believe a child has provided us personal data, contact us and we will take appropriate action.
19) Your responsibilities when using Translazor
If you use Translazor in your own application, you are responsible for your own privacy compliance, including:
- Informing your users if their text or page content is sent to a translation provider.
- Choosing and configuring your translation provider lawfully.
- Protecting API keys, connection strings, Redis instances, and production secrets.
- Avoiding translation or caching of sensitive personal data unless legally appropriate and secured.
- Maintaining your own Privacy Policy, cookie notices, and data processing agreements where required.
- Reviewing machine translation output before relying on it in sensitive or regulated contexts.
20) Changes to this Policy
We may update this Privacy & Data Policy from time to time. The latest version will be posted on this page with an updated “Last updated” date.
If changes are material, we may notify you by email or through the website/dashboard where appropriate. Your continued use of Translazor after the effective date means the updated Policy applies.
21) Contact us
For privacy questions, data requests, or security concerns, contact:
Email: support@translazor.com
Provider: Ahmed Elshorbagy, operating under Individual Activity (Individuali veikla), Vilnius, Lithuania.
Developer summary
- Translazor servers: do not store your translated page content.
- Translation requests: sent from your application to your configured translation provider.
- Provider credentials: your Azure/translation provider keys remain in your application configuration.
- Cache: MemoryCache/Redis translation cache is stored in your environment.
- Billing: Stripe handles payments, receipts, subscriptions, tax, and payment processing.
- License validation: may process license key, domain, plan, expiry date, and basic request metadata.
- Support: do not send secrets, production keys, personal data, or confidential customer data unless necessary.