Partner terms

Last updated 7 November 2026 · Version 2026-11-07

These terms apply between [COMPANY NAME] Ltd ("Tensil Fit", "we") and a brand that uses Tensil Fit on its store ("the Partner", "you"). They include our data processing terms (Annex A) and security measures (Annex B).

1. Agreement

These terms apply when you accept them in writing, sign an order form that refers to them, or first use a Tensil Fit live key issued to you, whichever comes first. If an order form signed by both of us says something different, the order form wins for that point. The person accepting must have authority to bind the Partner.

2. The service

• Size widget: a script and secure frame on your product pages that recommends sizes to shoppers.
• Brand Console: size-chart upload and mapping, catalogue coverage, calibration suggestions for your approval, and reports on recommendations and fit returns.
• APIs and integrations: for sending orders and returns (including Shopify webhooks).

The service is currently a preview. We may change or improve features; if a change materially reduces what you use, we'll tell you in advance.

3. Fees

During the preview the service is free unless an order form says otherwise. We'll give you at least 60 days' notice before charging, and you can end these terms instead.

4. Your responsibilities

• Accurate information: keep your size charts, product details and fabric information accurate. Recommendations can only be as good as this data.
• Keys: keep your secret console key confidential. Use only your publishable widget key on your website. Tell us straight away if a key may have leaked, and revoke or rotate it.
• Installation: install the widget as documented, and list the websites allowed to show it.
• Your notices: your privacy notice must tell your customers that you use Tensil Fit for sizing and that you share order and return information with us. Your cookie notice and consent tool must cover the widget's browser storage (listed on our cookies page). Where the law requires consent for that storage, load the widget only after consent.
• Lawful data: only send us data you're allowed to share. Don't put names, postal addresses, payment details or other unnecessary personal data into fields you send us (for example order notes), and never send special category data.
• Respect shoppers: don't try to identify shoppers from Tensil Fit data, combine it to build profiles beyond your own store's relationship with them, or present our recommendations as guaranteed.
• Fair use: don't scrape, resell or reverse-engineer the service, or use it to build a competing service.
• Brand presentation: keep the small Tensil Fit mark and name in the widget, and follow our brand guidelines when you mention Tensil Fit.

5. Shopper data and roles

• Fit profiles (Tensil Fit is controller). Shoppers' Tensil Fit accounts, measurements and Wallets are ours to protect under our privacy notice. You never receive measurements, height, weight, age band or shoppers' other brands.
• Linked shoppers (each of us is a separate controller). When a shopper links your store, with their consent you receive a pseudonymous ID for them, the recommended size and confidence, coarse fit notes per body zone, and whether their purchases fit. Each of us is responsible for our own use of what we hold.
• Your store data (Tensil Fit is your processor). For the orders, returns, recommendation records and visitor data we handle to run the widget for you and report to you, we act on your instructions under Annex A.
• Learning across brands. With the shopper's consent, a linked shopper's purchases and returns at your store improve their own profile. Separately, we may use your store data in aggregated or de-identified form to improve our sizing model and to show cross-brand benchmarks, which are only shown when at least 3 brands contribute and never identify you or a shopper.
• Deletion requests. You can ask us to delete a customer's data by email or through Shopify's privacy webhooks. We delete the matching order and return records and tell you when it's done.

6. Measuring results

To show the real effect on fit returns, a random share of your visitors (the "comparison group", 10% unless you change it, between 0% and 50%) don't see a recommendation; we still calculate it and compare outcomes. The group is chosen at random from the widget's browser ID. You can change the share in the Brand Console. Setting it to 0% means we can't measure the effect.

7. Content and data rights

• You keep all rights in your brand, products, size charts and store data. You give us a non-exclusive licence to use them to provide and improve the service for you, and to show your name and logo in the widget on your store.
• We keep all rights in the service, the sizing model and anything we create from aggregated or de-identified data.
• With your permission, we may name you as a partner on our website.

8. Confidentiality

Each of us keeps the other's non-public information confidential and uses it only for these terms, except where it is already public, independently developed, or must be disclosed by law. This lasts for 3 years after these terms end (indefinitely for keys and personal data).

9. Availability and support

During the preview we aim for high availability but give no service level. If Tensil Fit is unavailable or your account is suspended, the widget hides itself or shows your own size chart, so shoppers can still buy. Support: [email protected], on UK working days.

10. Liability

• Recommendations are estimates. We don't promise any particular reduction in returns, and you remain responsible for your products, prices, sales and returns policy.
• Neither of us is liable for indirect or consequential loss, or for loss of profit, revenue, goodwill or data (except our obligations to protect personal data).
• Each party's total liability in each year is limited to the greater of the fees paid or payable in the previous 12 months and £1,000.
• Nothing limits liability for death or personal injury caused by negligence, fraud, or anything else that can't be limited by law.

11. Suspension and ending

• Either of us can end these terms with 30 days' written notice, or straight away if the other seriously breaches them and doesn't fix it within 14 days of being asked.
• We may suspend your keys straight away to protect shoppers or the service (for example after a key leak or misuse), and will tell you why.
• When these terms end, your keys stop working. Within 30 days we delete or anonymise your store data, unless you ask for an export first or we must keep it by law. Shoppers' own Tensil Fit profiles stay theirs.

12. General

• We may update these terms with 30 days' notice by email. If you don't agree, you can end them before the change takes effect.
• Neither of us may transfer these terms without the other's consent, except to a buyer of all or most of the business who agrees to them.
• These terms are the whole agreement about their subject. If part is unenforceable, the rest still applies.
• These terms are governed by the law of England and Wales, and the courts of England and Wales have exclusive jurisdiction.

Annex A: Data processing terms

This annex applies where Tensil Fit processes personal data on the Partner's behalf (section 5, "Your store data") and meets Article 28 of the UK GDPR and the EU GDPR.

Tensil Fit will:

1. process the data only on the Partner's documented instructions (these terms and the Brand Console settings), unless the law requires otherwise, in which case we'll tell the Partner first where allowed;
2. make sure everyone who processes the data is bound by confidentiality;
3. apply the security measures in Annex B;
4. use only the subprocessors listed on our subprocessors page, give 30 days' notice of a new one, and let the Partner object (and end these terms if we can't resolve the objection); we remain responsible for our subprocessors;
5. help the Partner respond to people exercising their rights, and with security, breach notification, impact assessments and consultations with regulators, taking into account the information available to us;
6. notify the Partner without undue delay, and within 48 hours where possible, after becoming aware of a personal data breach affecting the Partner's data, with the information the Partner needs;
7. at the end of the service, delete or return the data as described in section 11, unless the law requires us to keep it;
8. make available the information needed to show compliance with this annex, and allow reasonable audits (first by questionnaire and documents, and on-site only where those aren't enough, at the Partner's cost, with 30 days' notice, no more than once a year unless a regulator requires it or after a breach);
9. only transfer the data outside the UK or EEA with appropriate safeguards (an adequacy decision, or the UK International Data Transfer Addendum or EU Standard Contractual Clauses).

The Partner authorises the subprocessors listed on the subprocessors page on the date the Partner accepts these terms.

Annex B: Security measures

• Encryption: all traffic over HTTPS (TLS 1.2 or higher). Shoppers' measurements encrypted at rest with AES-256-GCM, using a separate key per shopper.
• Separation: each Partner's data is isolated with database row-level security that the application cannot bypass; the service refuses to start if that protection is weakened.
• Access: staff access through a console behind an access gateway, with two-step sign-in, roles with least privilege, fresh verification for sensitive actions, and an audit log that can't be edited. No staff access to shoppers' measurements.
• Keys: API keys stored only as keyed hashes and shown once; Partners can revoke and rotate them at any time.
• Data minimisation: Partners receive pseudonymous IDs only; free-text return comments are deleted after 30 days; records are deleted on a fixed schedule.
• Resilience: nightly backups kept 14 days, with a monthly restore test.
• Hosting: servers in the United Kingdom with no open inbound ports; traffic arrives only through Cloudflare's network.
• Monitoring and response: rate limits on sign-in and APIs, request IDs in logs (which exclude IP addresses and secrets), and a documented incident process.