This Customer Agreement (the "Agreement") is a contract between feat labs, inc. ("feat", "we", "us") and the organization identified during signup ("Customer", "you"). It governs Customer's use of feat's hosted feature flag platform and related services (the "Service"). By creating an organization on feat, the individual clicking accept ("Authorizing Individual") accepts this Agreement on Customer's behalf.
Plain-English summary: this is the org-binding contract. The individual who creates the org clicks accept on behalf of the organization. Individual users have a separate, much shorter User Terms of Service. The Data Processing Addendum and any sub-processor list are part of this Agreement by reference. This summary is informational; the sections below control.
1. Authority to bind
The Authorizing Individual represents and warrants that (a) they are at least 18 years old, (b) they have full authority to bind Customer to this Agreement, (c) they are entering into this Agreement in their capacity as an employee, officer, or duly-authorized agent of Customer, and (d) Customer accepts all obligations stated herein. If the Authorizing Individual lacks authority to bind Customer, Customer is nonetheless bound to the extent permitted by applicable apparent-authority or ratification doctrines.
2. The Service
feat hosts feature flag configuration, evaluates it through SDKs embedded in Customer's applications, and provides administrative tools. We may change non-material features at any time. We will give reasonable notice of changes that materially reduce the functionality of a paid plan Customer depends on.
3. Authorised Users
Customer's employees, contractors, and other individuals authorised by Customer to use the Service ("Authorised Users") access the Service under the User Terms of Service. Customer is responsible for the acts and omissions of its Authorised Users as if they were Customer's own. Customer remains the sole controller of all personal data processed about its Authorised Users and end users in connection with the Service.
4. Plans, fees, and billing
Plans, included usage, and overage rates are described on the Pricing page and incorporated here by reference. Subscription fees are charged in advance; usage overages in arrears. Amounts are exclusive of taxes; Customer is responsible for applicable taxes other than those on our net income.
5. Acceptable use
- No reverse engineering, scraping, or circumventing rate limits.
- No targeting that violates anti-discrimination or consumer-protection law.
- No malware distribution, illegal content, or violations of third-party rights.
- No use of the Service to attack or probe systems Customer does not own or lacks permission to test.
feat may suspend access to the Service for material breach of this section or to protect other customers or the Service itself.
6. Data protection
The Data Processing Addendum ("DPA") forms part of this Agreement and governs feat's processing of personal data on Customer's behalf. By accepting this Agreement, the Authorizing Individual also accepts the DPA on Customer's behalf. Customer is the controller; feat is the processor. Sub-processors are disclosed at /legal/subprocessors.
7. Confidentiality
Each party will protect the other's confidential information with at least the care it uses for its own and only use it to perform under this Agreement. Customer Data (defined below) is treated as Customer's confidential information.
8. Customer Data
"Customer Data" means data Customer submits to the Service, including flag configurations, audit-log entries, and context attributes routed through our APIs. Customer retains all rights to Customer Data. feat may use Customer Data only to provide the Service and as instructed under the DPA.
9. Intellectual property
feat retains all rights in the Service, including SDKs, documentation, trademarks, and any feedback or aggregated, de- identified analytics derived from Customer's use. Open-source components are governed by their respective licenses.
10. Warranty disclaimer
EXCEPT AS EXPRESSLY STATED, THE SERVICE IS PROVIDED "AS IS" WITHOUT WARRANTIES OF ANY KIND. FEAT DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT TO THE MAXIMUM EXTENT PERMITTED BY LAW.
11. Limitation of liability
TO THE MAXIMUM EXTENT PERMITTED BY LAW, NEITHER PARTY WILL BE LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES. EACH PARTY'S AGGREGATE LIABILITY IS CAPPED AT THE FEES PAID OR PAYABLE TO FEAT IN THE TWELVE MONTHS PRECEDING THE EVENT GIVING RISE TO LIABILITY, OR USD 100, WHICHEVER IS GREATER. THIS CAP DOES NOT APPLY TO EITHER PARTY'S BREACH OF CONFIDENTIALITY, WILLFUL MISCONDUCT, OR INDEMNIFICATION OBLIGATIONS.
12. Indemnification
feat will defend Customer against third-party claims that the Service, used as permitted, infringes a US patent, copyright, or trademark. Customer will defend feat against third-party claims arising from Customer Data, Authorised User conduct, or Customer's violation of Section 5.
13. Term and termination
This Agreement starts when accepted and continues for so long as Customer maintains an active organization. Either party may terminate for material breach not cured within 30 days of notice. On termination feat will make Customer Data available for export for 30 days, after which it is permanently deleted per the DPA.
14. Governing law and disputes
This Agreement is governed by the laws of Delaware, United States, without regard to conflicts-of-laws principles. The parties consent to the exclusive jurisdiction of the state and federal courts located there.
15. Changes
feat may update this Agreement from time to time. If a change is material we will notify organization Admins by email at least 30 days before the change takes effect and prompt them to re-accept the new version in-product. Continued use of the Service after the effective date constitutes acceptance.
16. Order of precedence
If a separately-signed Order Form, Master Subscription Agreement, or negotiated DPA conflicts with this Agreement, the separately- signed document controls.
17. Contact
Notices to feat must be sent to support@feat.so. Notices to Customer will be sent to the Admin email addresses on the organization's account.
Acceptance record
When the Authorizing Individual accepts this Agreement at org creation, we record the date and version, the user ID of the Authorizing Individual, their role at the time, and their IP address and user-agent string. Admins can review the current on-file version from organization settings.