Privacy policy

This Privacy Policy explains how Encode ("Encode", "we", "our") collects, uses, and shares information when you visit or use our website and services. Encode is a product of Endurer Technologies ("Endurer").

Who we are

Endurer Technologies, Koppelboerhoek 106, 7546 AV Enschede, the Netherlands, registered with the Netherlands Chamber of Commerce (KvK) under number 99176173, VAT number NL005374783B53. Email support@endurer.tech about your personal data, or encode@endurer.tech about anything else. We have not appointed a data protection officer: the law does not require one for the processing we do.

Our two roles

• For your account, billing, support and this website we decide why and how your personal data is processed: we are the controller, and this policy describes that processing.
• For your customer content (the repositories, issues and comments you connect, and what your Workers make from them: plans, commits, pull requests, walkthrough videos and screenshots of your app, and task logs) we process personal data only on behalf of, and on the instructions of, the customer who connected it. There the customer is the controller and we are its processor, under our data processing agreement (see the terms). If your name or other personal data is in such content, ask that customer about it; we pass on any request we receive.

Information we collect

• Contact and sign-in details (such as name, email address and the sign-in method you choose) when you create an account, request support, or contact us. Sign-in runs through Endurer's own sign-in service.
• Account and service data (such as your plan, your Workers, organisation settings, the repositories and issues you connect, and service logs) needed to deliver our services.
• Your email address and the details you give when you ask to hear when pre-orders open or when a plan becomes available, as described under Pre-order and launch notifications.
• Billing details when you pre-order or subscribe: the billing name and address, your business VAT number if you give one, and your payment method. Stripe stores the payment method; we receive only its type, brand, last four digits and expiry month, never the full card number.
• Technical data (IP address, browser type and diagnostic logs, including the pages visited) to secure and improve our services. Visitors who are not signed in get no identifier: their page visits are not linked to each other or to a person.

How we use your information, and on what legal basis

• Provide and maintain the services you signed up for, and process purchases and subscriptions: necessary for our contract with you or your organisation (Article 6(1)(b) GDPR).
• Run your pre-order: confirm it, tell you the launch date, start billing on launch day, and tell you if launch moves. These emails are part of the agreement, not marketing (Article 6(1)(b) GDPR).
• Respond to support requests, tell you about your account, and send the pre-order and launch notifications you asked for: our contract, or your consent for the notifications (Article 6(1)(a) GDPR).
• Detect, prevent, and address security incidents or abuse, and improve the service from usage figures that hold no customer content: our legitimate interest in a secure, working service (Article 6(1)(f) GDPR). You can object to this at any time.
• Keep invoices and billing records as tax law requires: a legal obligation (Article 6(1)(c) GDPR).
• Process your issues and code with the AI models that power Encode, solely to provide the service you requested, as your organisation's processor.

You do not have to give us your personal data, but without an email address we cannot create an account or take an order. We make no decisions about you by automated means alone that have legal or similarly significant effects.

Your code and repositories

Encode works on your code on Encode's own infrastructure, where your Workers run. To research, plan and write changes, parts of your issues and code are sent to the AI models that power Encode, which run on Endurer's own hardware or at the AI model providers we reach through OpenRouter, listed under Sub-processors.

We do not use your code to train models. We send it to a model provider only through OpenRouter with zero data retention required and data collection denied on every request, so the request goes only to providers that have told OpenRouter they do not store prompts or replies after processing and do not train on them. OpenRouter itself does not store prompts or replies, only metadata such as token counts. Two exceptions apply at OpenRouter and the providers: content flagged as potential child sexual abuse material may be kept for review and reporting where the law requires it, and a short-lived in-memory cache may hold a request while it is processed.

We keep task logs, model transcripts and walkthrough recordings for a limited time, listed under Data retention, to run the task, show you what happened and help you when you ask. We do not use them to train or fine-tune models. A Worker that researches on the public web sends short search queries to a public search engine (DuckDuckGo); a query can contain words from your issue, such as an error message or a library name.

Sub-processors

These companies process personal data for us, including customer content where the purpose says so.

AI model providers OpenRouter may route a Worker's request to. Each runs the model on the request and returns the reply under zero data retention. They are OpenRouter's sub-processors; the transfer to the United States is the one to OpenRouter above. Locations are as each provider states to OpenRouter.

Models that run on Endurer's own hardware involve no third party. We tell customers about a new or replaced sub-processor, model providers included, at least 30 days before it processes their customer content: we update this list and email the owners of every organisation. A customer can object within that time, as the data processing agreement describes.

Transfers outside the EEA

Where a sub-processor above is outside the European Economic Area, the transfer is covered by the safeguard named in its row: the EU-U.S. Data Privacy Framework (an adequacy decision of the European Commission) or the EU Standard Contractual Clauses, with the supplementary measures we assessed for the transfer. Write to support@endurer.tech for a copy of the clauses that apply.

Cookies and local storage

The public pages set no cookie. The dashboard sets a session cookie when you sign in there (and a short-lived one while the sign-in runs) that keeps you signed in. It is strictly necessary for the sign-in you asked for, so we do not ask for consent to it. Visitors who do not sign in get no cookie at all. Your choice of light or dark theme is stored in your browser's local storage and is not sent to us. We use no advertising cookies and no third-party analytics.

Sharing and disclosure

• The sub-processors listed above, which process data on our behalf and only on our instructions.
• Your own Git host (such as GitHub, GitLab or Forgejo): Encode reads issues and code from it and writes branches, comments, pull requests and walkthrough videos to it, as you set up.
• A public search engine, for the web searches described under Your code and repositories.
• The sign-in provider you choose (such as GitHub or Google), if you sign in with one.
• Authorities or third parties when required by law, or to protect our rights and users.

We do not sell your personal data.

Pre-order and launch notifications

Pre-orders open soon. When you leave your email address to hear when they do, we store your email address, optionally your company name, the number of Workers you expect to need, the time you signed up, that you agreed to be emailed when pre-orders open and when Encode launches (and which wording of that consent you saw), whether you also asked for product updates, and whether you asked to be told when the Autonomous Junior Software Engineer plan (without human verification, not sold at launch) becomes available. Once pre-orders are open, the form only takes addresses for that plan, with its own consent wording. If you later pre-order with the same email address, we note that on your entry so we do not invite you to pre-order again. The list is stored on Endurer's own servers.

We use it only to tell you when pre-orders open and when Encode becomes available. We send product updates only if you ticked that box, and tell you about the Autonomous Junior Software Engineer plan only if you asked for it, once it becomes available. We never sell or share the list. The legal basis is your consent, which you can withdraw at any time: write to support@endurer.tech and we remove you from the list. The notification list is deleted three months after subscriptions open, and no entry is kept longer than 12 months.

Data retention

We keep data only as long as the table below says, then delete it. When your organisation has no Workers and no pre-ordered Workers left, you can remove the saved payment method on Stripe's page from the dashboard, or ask us to. When a customer's contract ends we delete its customer content as the data processing agreement describes.

Your rights

You have the right to access, correct, delete, or restrict the processing of your personal data, to object to processing based on our legitimate interests, and to data portability. Where we rely on your consent, you can withdraw it at any time; that does not affect what we did before. Send any such request to support@endurer.tech; we answer within one month. You can also lodge a complaint with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens, autoriteitpersoonsgegevens.nl) or the authority where you live or work.

Changes to this policy

We post every change on this page with a new date. For a change that affects how we process customer content, we email the owners of every organisation before it takes effect.

Contact us

If you have questions about this Privacy Policy or our data practices, contact us at encode@endurer.tech, or write to Endurer Technologies, Koppelboerhoek 106, 7546 AV Enschede, the Netherlands.