Privacy policy
Englang helps you work on projects with AI agents. This policy explains what data is used, who can receive it, and how you can ask for access or deletion.
Read about AI and project content, dictation, service providers, retention and your rights.
Who is responsible
Woatu GmbH, Switzerland, operates Englang and is the controller of the personal data described here. Contact legal@englang.ai for privacy questions or requests.
This policy covers englang.ai, the Englang mobile and web apps, hosted workspaces, website migration and hosting, and sharing and support. It also covers Englang pilot and TestFlight builds. A third-party service or a website you publish can have its own privacy policy. You are responsible for how you use other people’s data in your projects.
Account and service data
Sign-in. Your chosen sign-in provider, such as Apple, Google or X, gives us an account identifier and the profile details it makes available, such as an email address or name. We use these to create your account, sign you in and manage access. We do not receive your sign-in provider’s password.
Running the service. We store account and session identifiers, workspace details, device public keys, linked-account permissions and credentials where needed, invitation records, and setup and operation results. These let us connect your devices, run your workspace, deploy your website and recover from failures. We also process request and security data, such as IP addresses, request times and errors, to deliver the service and limit abuse.
Notifications. If you enable notifications, we process your device token or browser push subscription and the alert data needed to send them. You can turn notifications off in your device or browser settings.
Projects, conversations and AI
Your project files, agent conversations, prompts, attachments, tool results and credentials can be stored on the host where you work. A hosted workspace runs on infrastructure supplied through exe.dev. As its operator, Woatu can access the workspace and its contents to run, secure and repair the service, answer help requests, investigate abuse and meet legal duties. A hosted workspace is not storage that only you can read.
When you use an AI model, the agent sends your prompt and the context needed for the task to the model service. Context can include conversation history, files, images, code and tool output. Included AI uses OpenRouter, which routes requests to the provider serving the selected model. If you connect your own AI account or key, that provider receives the requests instead. Avoid giving an agent data you do not want that provider to process.
Woatu does not use workspace content to train models. This is not a promise about every external model provider. Its retention and training rules depend on the provider, model, account and settings you use. Check those rules before sending sensitive data.
On a host you add yourself, project content stays on that host unless you send it to a model, share it, publish it or use another connected service. Agents act with the permissions you grant on that host.
Voice dictation
Included dictation sends your recording through Englang to OpenRouter and the transcription provider. Optional spelling hints include project, website, app, agent and host names. You can turn these hints off in Voice Dictation settings. The dictation request does not include your source files, terminal contents or conversation history.
The Englang transcription endpoint does not save your recording or transcript. It keeps usage and rate-limit records, not the audio or text. The transcript is returned to your device; if you send it as a prompt, it becomes part of the agent conversation. OpenRouter and the transcription provider have their own data-handling rules. If you choose Apple Speech or another dictation provider, that provider handles the recording under its own rules.
Website migration and hosting
If you request a migration, we collect the website address and your email address to prepare the site and send you the result. We can also prepare an invitation from a business’s public website. In that case, the source is the public site, including any names, contact details, text and images it contains.
Migration copies, screenshots and checks are processed on the operator’s computer. A prepared site is stored in a private GitHub repository and served through Cloudflare. Draft and live addresses are separate. A draft address can be reached by anyone who has it: asking search engines not to index a page does not make it private.
When you publish, the published content is public. When you move a site to your own GitHub and Cloudflare accounts, those services process it under your account arrangements. Removing an Englang account does not remove copies held by other people or resources in your own accounts.
Sharing and support
Sharing gives the recipient access to the conversation and related content within the permissions you select. A recipient with control can also cause work to run on your host. The sharing relay can read the content it carries; shared conversations are not end-to-end encrypted through that relay.
A confirmed Get Help request gives the named helper the access shown in the app. We process the request, conversation access and support messages to help you. Revoking access stops future access through the service, but cannot recall content someone has copied or undo work already started.
Usage events
The app, backend and workspace send first-party usage events. Examples include sign-in, an invitation redeemed, a workspace ready, a screen opened, a message sent, an agent run, a preview, a publish and an error. Events contain identifiers, times, counts and status values. They do not contain message text, source code, file names or raw error messages.
We use these records to understand where the service fails, answer support questions and improve it. They can be linked to your account or invitation; they are not anonymous. The operator console shows activity and model usage. The app does not use a third-party analytics SDK for these events.
Payments
Where in-app purchases are available, Apple handles checkout and payment details. We do not receive your full payment card number. We process transaction and subscription identifiers, product, price, currency, dates, purchase status and credit grants to supply what you bought, prevent duplicate credits and keep accounts. TestFlight purchases are test transactions, not real payments.
Accounting records for real purchases are retained for 10 years to meet Swiss accounting duties. Account deletion does not erase records that must be kept by law. Test purchases must be distinguished from real revenue. This section does not mean that paid plans are available in every build.
Website visits and the waitlist
The public englang.ai website does not use advertising trackers or third-party analytics scripts. Fonts, images and videos are served from the website’s hosting. Cloudflare still processes network data, including your IP address and request details, to serve and protect the site.
The waitlist asks for your email address, an optional name and, if you want, the address of a website you want to move. We use them for the launch message you requested and to prepare for your website, not unrelated marketing. Sign-ups are stored in Cloudflare and included in an email digest to the operator’s mailbox, hosted by Google. Write to waitlist@englang.ai to leave the list.
The signed-in web app is separate from the public website. It uses essential cookies for sign-in and push, and browser storage for device keys, host settings and local app state. Clearing browser data removes local records, not your server account. The mobile app also keeps settings, keys and working data on your device.
Services that receive data
Providers receive the data needed for the features you use. Some act for Woatu; others also process data for their own accounts, security or legal duties. The main services are:
Cloudflare: website and API hosting, databases, website assets, relays, security and email routing. Cloudflare privacy policy.
exe.dev (Bold Software, Inc.): hosted workspace machines and the files and processes on them. exe.dev privacy notice.
GitHub: prepared website repositories and repositories you connect or create. GitHub privacy statement.
OpenRouter and the selected model provider: AI requests and included dictation, plus model usage records. OpenRouter privacy policy. Other AI providers you connect have their own policies.
Apple: Apple sign-in, app distribution, in-app purchases, push notifications and Apple Speech when selected. Apple privacy policy.
Google: Google sign-in when selected and the operator’s email. Google privacy policy. X: X sign-in when selected. X privacy policy.
Tailscale: network and device information if you link it. Tailscale privacy policy. Other services you connect receive data according to the permissions and tasks you choose.
We may also disclose data when required by law or when needed to address fraud, abuse or a security incident. Sharing and publishing disclose content to the recipients you choose or to the public, as described above.
Processing outside Switzerland
Woatu is based in Switzerland. The services above include providers in the United States and use infrastructure in other countries. Your data is not confined to Switzerland. Locations can depend on your host, selected model and connected services; the providers’ notices describe their international processing.
Cross-border transfers are subject to the Swiss Federal Act on Data Protection and, where applicable, the GDPR. These laws can require an adequate level of protection or other safeguards, such as recognised standard contractual clauses. Contact legal@englang.ai for information about the destinations and safeguards that apply to your use of Englang.
Why we process data
We use account, workspace, AI and support data to provide the service you request. We use operational and usage records for our legitimate interests in keeping it secure, reliable and useful. We use purchase records to fulfil orders and meet accounting and other legal duties. We rely on your consent where required, including for the launch email you request and optional features that ask for it.
Where the GDPR applies, these are respectively performance of a contract or steps you request before it, legitimate interests, legal obligations and consent. You may withdraw consent for future processing. This does not make earlier lawful processing unlawful. If you do not provide data needed for a feature, such as sign-in details or a website address for a migration, that feature cannot work.
How long data is kept
Account and workspace data: while needed to provide the service, until you delete it or the service ends, subject to legal and security needs. Workspace deletion removes the managed machine, not your account or external repositories. A workspace is not a backup; keep a copy in an account you control.
Usage events and migration request records: a 90-day retention window. Old database records are removed in batches during service activity, so physical deletion can take longer when the service is idle. A migration request’s expiry does not itself delete the prepared site, repository, migration evidence or email correspondence.
Waitlist and support correspondence: while needed to send the requested launch message, resolve your request or keep a necessary record of it. The waitlist has no automatic expiry. You can ask us to remove your entry and related correspondence.
Security, deletion and accounting evidence: we may keep limited records needed to prevent abuse, prove an operation or deletion, resolve a dispute or meet a legal duty. Purchase accounting records have the 10-year period described above. Provider backups and records have their own retention cycles; deletion from a live system need not erase every backup at once.
Your choices and rights
You can ask for access to your personal data, correction of inaccurate data, or deletion. Depending on the law that applies, you can also ask for a portable copy, restrict processing, object to processing based on legitimate interests, or withdraw consent. These rights can have limits where data is still needed for legal duties or claims.
Use Erase All Data in the app to start account deletion, or write to legal@englang.ai. We may need to verify that the request is yours. Deletion revokes account access and removes account data and the managed workspace through the service’s cleanup process; it is not always instant.
Prepared-site repositories, migration requests made before sign-in, waitlist entries and email correspondence are not all linked to your account. Tell us if your request also covers these. Deleting your account does not delete your original website, your GitHub repositories, domains, copies held by recipients, or records that must be retained. If you have an Apple subscription, manage or cancel it with Apple as well.
You can complain to the Swiss Federal Data Protection and Information Commissioner, or to the data protection authority in your country where applicable. You do not have to contact us first.
Children
Englang is intended for adults aged 18 and over. It is not directed at children. Contact us if you believe a child has provided personal data so that we can investigate and remove it where appropriate.
Changes to this policy
We will update this page when our data handling changes and show the effective date above. For material changes, we will also notify you in the app or by email where practical. This policy explains data handling; it does not replace the terms of service.