Skip to content

Partner FAQ

Answers for companies working with Entatan: terms, pricing, ownership, AI tooling, data, and security.

Effective: Aug 20, 2026

Which terms apply to my engagement?

Your statement of work, the Partner terms of service, the Data Processing Addendum where we handle personal data, and the Acceptable Use Policy. If you have a master services agreement with us, it sits on top. The general Terms of Service cover the website and portal only.

How does pricing work?

Three shapes: fixed-scope sprints, monthly retainers, and venture structures. Pricing on our site is indicative; the SOW sets the number. Third-party costs such as ad spend, hosting, and model usage are passed through at cost or paid directly by you, and never committed without your approval.

Who owns the deliverables?

You do, on payment. Code written for you, brand assets, creative, and content transfer to you. We keep our reusable tooling, agent templates, and playbooks, and license you to use what is embedded in the deliverables. Open-source components keep their licences.

Which AI tools do you use, and where does our data go?

We use commercial AI model APIs and coding agents under terms that prohibit providers from training on our inputs. Your code and data are used only to deliver your engagement. Categories of provider are on the subprocessor page; specific vendors for your engagement are in the SOW or available in the portal.

Do you sign NDAs and DPAs?

Yes. Our Partner terms include mutual confidentiality, and our DPA is available for any engagement involving personal data. We will review your paper if you prefer, though our templates are faster.

Where is data stored, and is it segregated?

In the United States, with providers listed by category on the subprocessor page. Each engagement gets its own environments, repositories, and credentials. Production data is not copied into shared tooling.

What are your security practices?

Least-privilege access with multi-factor authentication, encryption in transit and at rest, secret and dependency scanning, code review on every change, logging and monitoring, and tested backups. Agents we deploy run with scoped credentials, approval gates, and audit logs. The security page has the full list.

How do you handle subprocessor changes?

We update the subprocessor page at least 15 days before a new provider touches partner data and notify portal users. You can object on data protection grounds; if we cannot resolve it you can end the affected SOW without penalty.

What happens when the engagement ends?

You get everything: repositories transferred, credentials rotated to you, assets handed over, and documentation in the portal. Within 30 days we delete or return partner personal data at your choice, except what the law requires us to keep. Retainers can be cancelled with 30 days' notice.

How do we raise a concern or dispute?

Start in the portal or with your engagement lead. Formal notices go to the contacts in the SOW. Security issues use the disclosure process on the security page. Both sides commit to 30 days of informal resolution before filing a claim.

Last updated: Aug 20, 2026