Terms of Service and Data Processing Agreement
Version 1.0, effective 20 October 2026
These terms are accepted on a company’s behalf by one of its admins, using the acceptance box shown when the company first signs in to AllyPipe. A company that prefers a signed copy can ask us for a PDF of the same text.
Part A: Terms of Service
1. Who we are
1.1 AllyPipe is provided by Sigmatak Ltd, a company registered in [to be added] (company number [to be added]), registered office [to be added] (“AllyPipe”, “we”, “us”). Contact: [to be added].
1.2 These terms are an agreement between us and the organisation that uses AllyPipe (the “Customer”). They apply to the business use of AllyPipe only. AllyPipe is not offered to consumers.
2. Definitions
- Service: the AllyPipe customer relationship management platform, at the address linked from “Log in” on allypipe.com or any address we give.
- Workspace: the Customer’s own area of the Service, with its own database.
- Customer Data: all data the Customer or its Users put into the Workspace, including personal data about the Customer’s contacts and prospects.
- User: a person the Customer gives access to its Workspace: an admin, a staff member, or a partner user.
- Partner: an organisation the Customer adds as a partner in its Workspace, whose partner users see only what the Customer shares with them.
- Linked Company: another AllyPipe customer whose Workspace the Customer chooses to link with its own.
- Plan: the Customer’s plan (Evaluation, Linked partner, Team or Network) and its allowances, as described on allypipe.com.
- DPA: the Data Processing Agreement in Part B, which forms part of these terms.
3. Acceptance and authority
3.1 These terms are accepted when an admin of the Customer ticks the acceptance box in the Service, or signs a copy. The person accepting confirms they are authorised to bind the Customer.
3.2 We record who accepted, for which Customer, which version and when.
4. The Service
4.1 The Service lets the Customer record deals, contacts, companies, notes and campaigns; share chosen deals with Partners; link with Linked Companies; and record outreach its Users carry out themselves.
4.2 The Service does not send messages to anyone, does not sign in to LinkedIn or any other site on the Customer’s behalf, and does not collect data from other websites. Users carry out all outreach themselves.
4.3 The Service makes no calls to artificial intelligence services. An optional, read-only connector lets a User’s own Claude account read the Workspace. It is switched off until a Customer admin switches it on. The User’s Claude account is provided by Anthropic under the User’s or Customer’s own agreement with Anthropic, not by us.
4.4 We may change the Service to improve it, keep it secure or comply with law. We will not materially reduce its core functions during a paid period without notice under clause 18.
5. Users and access
5.1 The Customer’s admins decide who can use its Workspace, in what role, and which Partners see which deals. The Customer is responsible for its Users, including partner users it adds, and for disabling Users who should no longer have access.
5.2 Users sign in with a one-time code sent to their work email address. Users must keep access to that mailbox secure and must not share sign-in codes.
5.3 The Customer must tell us promptly at [to be added] if it believes a User’s account has been misused.
6. The Customer’s responsibilities
6.1 The Customer is the controller of Customer Data. It is responsible for having a lawful basis for holding and using it, for giving the people concerned the privacy information the law requires (its own privacy notice, which it can link in its Workspace settings), and for answering their requests. The Service provides tools for subject access, erasure and do-not-contact to help with this.
6.2 The Customer must comply with the law that applies to its marketing and outreach, including the UK GDPR, the Data Protection Act 2018 and the Privacy and Electronic Communications Regulations, and with the terms of any site it uses, including LinkedIn’s.
6.3 The Customer must not, and must make sure its Users do not:
- put into the Service data it has no right to hold, or special category or criminal offence data unless the law allows it and it is needed;
- use the Service to send unlawful marketing or to harass anyone;
- try to reach another customer’s data, test the Service’s security without our written permission, or interfere with the Service;
- copy, resell or reverse engineer the Service, except where the law allows this and cannot be excluded.
7. Customer Data
7.1 The Customer owns Customer Data. It gives us the right to host, copy and process Customer Data only to provide the Service, as set out in the DPA.
7.2 We do not look at Customer Data except (a) when the Customer asks us to for support, and only to the extent needed, or (b) when the law requires it. Our staff cannot see a Customer’s deals, contacts or campaigns through the platform’s own administration screens.
7.3 Customer admins can download all Customer Data at any time from the Service, as files that can be opened in a spreadsheet or imported into another system.
8. Partners and Linked Companies
8.1 The Customer decides, deal by deal, what each Partner sees. Partner users never receive contact email addresses or phone numbers, and see contact names only where the Customer allows it.
8.2 A link with a Linked Company is made at both companies’ request. Each sees only what the other chooses to share, and either can switch the link off. Overlap checks, if both companies switch them on, exchange only coded (salted hash) organisation names and a match status, never people’s details.
8.3 Once the Customer shares data with a Partner or Linked Company, what that organisation does with it is between the Customer and that organisation. The Customer should have its own agreement with each Partner.
9. Plans and fees
9.1 A new Workspace starts on the Evaluation plan, which is free of charge for 30 days. At the end of the Evaluation the Customer may move to a paid plan or end these terms, in which case clause 17.3 applies.
9.2 During early access the Service is provided free of charge. We will give at least 30 days’ notice before fees apply, and the Customer may end these terms before then.
9.3 Once fees apply, they are those of the Customer’s Plan as shown on allypipe.com at the time, invoiced monthly in advance (or yearly, if the Customer chooses yearly billing), payable within 30 days of the invoice, and exclusive of VAT.
9.4 We may change our prices on at least 30 days’ notice. A change takes effect from the Customer’s next billing period after the notice ends.
10. Availability and support
10.1 We will use reasonable care and skill to keep the Service available, but we do not promise it will be uninterrupted or error-free. The Service runs on Cloudflare’s infrastructure, and its availability depends partly on Cloudflare.
10.2 Support is by email at [to be added] on UK working days. We aim to reply within two UK working days.
11. Security
We protect the Service and Customer Data with the measures in Annex 2 and keep them under review.
12. Confidentiality
Each party will keep the other’s confidential information confidential and use it only for this agreement, except where it is already public, independently developed, or must be disclosed by law. Customer Data is the Customer’s confidential information.
13. Data protection
When we process personal data in Customer Data, we do so as the Customer’s processor under the DPA in Part B. When we process personal data about Users (for example sign-in records), we do so as controller, as described in the AllyPipe privacy notice.
14. Intellectual property
We and our licensors own the Service and all rights in it. The Customer gets a non-exclusive, non-transferable right for its Users to use the Service for its business during this agreement. If the Customer sends us feedback, we may use it freely.
15. Liability
15.1 Nothing in these terms limits liability for death or personal injury caused by negligence, for fraud, or for anything else that cannot be limited by law.
15.2 Neither party is liable for loss of profits, revenue, business, goodwill or anticipated savings, or for indirect or consequential loss.
15.3 Subject to 15.1, each party’s total liability under or in connection with these terms in any 12 months is limited to the greater of the fees paid in the previous 12 months and £5,000.
16. Suspension
We may suspend a Workspace or a User where needed to stop a security threat, a serious breach of these terms or unlawful use. We will tell the Customer, keep the suspension as short and narrow as we can, and not delete data because of a suspension.
17. Ending the agreement
17.1 The Customer may end these terms at any time by asking us to close its Workspace.
17.2 We may end these terms on 90 days’ notice, or immediately if the Customer seriously breaches them and does not put it right within 14 days of being asked.
17.3 When a Workspace is closing, it becomes read-only and only the Customer’s admins can sign in, so they can download all Customer Data. We delete the Workspace’s database no sooner than 30 days after closing starts, and record the date and what was deleted. Copies in Cloudflare’s point-in-time recovery are erased automatically within 7 days after that (30 days if AllyPipe uses a paid Cloudflare plan).
18. Changes to these terms
We may update these terms. We will give at least 30 days’ notice of a change that is not in the Customer’s favour, and admins will be asked to accept the new version. If the Customer does not accept, it may end these terms before the change takes effect.
19. General
19.1 Neither party may transfer these terms without the other’s consent, except that we may transfer them to a buyer of the Service who agrees to be bound by them.
19.2 These terms, the DPA and any signed order are the whole agreement between us about the Service.
19.3 Notices go to the email addresses each party gives.
19.4 Neither party is liable for delay caused by events outside its reasonable control.
19.5 These terms are governed by the law of England and Wales, and the courts of England and Wales have exclusive jurisdiction.
Part B: Data Processing Agreement
This agreement sets out how AllyPipe processes personal data on the Customer’s behalf, as required by Article 28 of the UK GDPR. It forms part of the Terms of Service in Part A. Where the Customer’s processing is subject to the EU GDPR, the same terms apply with references read accordingly.
1. Roles
1.1 The Customer is the controller of the personal data in Customer Data. AllyPipe is its processor.
1.2 Annex 1 describes the processing: its subject matter, duration, nature and purpose, the types of personal data and the people it concerns.
2. Instructions
2.1 AllyPipe processes Customer personal data only on the Customer’s documented instructions. These terms, and the Customer’s use and configuration of the Service, are those instructions.
2.2 If the law requires AllyPipe to process the data in another way, AllyPipe will tell the Customer first, unless the law forbids that.
2.3 AllyPipe will tell the Customer promptly if it believes an instruction breaks data protection law.
3. Confidentiality
AllyPipe makes sure that anyone it authorises to process Customer personal data is bound by a duty of confidentiality.
4. Security
AllyPipe takes the technical and organisational measures in Annex 2, appropriate to the risk, as required by Article 32 of the UK GDPR. It may update those measures provided the overall level of protection is not reduced.
5. Sub-processors
5.1 The Customer gives general authorisation for AllyPipe to use the sub-processors in Annex 3.
5.2 AllyPipe will give the Customer at least 30 days’ notice of any new sub-processor, by email to the Customer’s admins and by updating Annex 3. The Customer may object on reasonable data protection grounds. If the parties cannot resolve the objection, the Customer may end the agreement before the change takes effect.
5.3 AllyPipe imposes data protection obligations on each sub-processor equivalent in substance to this agreement, and remains responsible to the Customer for their performance.
6. International transfers
6.1 Customer databases are created in Cloudflare’s EU jurisdiction, so they are stored at rest in the European Union.
6.2 Cloudflare, Inc. is based in the United States and may access or process data outside the UK and EU to run its services, including when serving requests and sending sign-in codes. Such transfers are covered by Cloudflare’s Data Processing Addendum, which relies on the UK-US data bridge under the Data Privacy Framework and, where needed, the EU Standard Contractual Clauses with the UK Addendum.
6.3 AllyPipe will not otherwise transfer Customer personal data outside the UK or EU without a lawful transfer mechanism.
7. Helping the Customer
7.1 Data subjects’ rights: the Service gives the Customer tools to find, export and erase everything held about a person and to mark them do-not-contact. Where those tools are not enough, AllyPipe will give reasonable help on request.
7.2 AllyPipe will give reasonable help with the Customer’s security, breach notification, impact assessment and prior consultation duties under Articles 32 to 36 of the UK GDPR, taking into account the information available to it.
8. Personal data breaches
8.1 AllyPipe will notify the Customer without undue delay, and in any case within 48 hours, after becoming aware of a personal data breach affecting Customer personal data.
8.2 The notice will describe, as far as is known, what happened, the data and people affected, the likely consequences and what AllyPipe is doing about it, and will be updated as more is learnt.
8.3 The Customer decides whether to notify the Information Commissioner’s Office and the people affected.
9. Access to Customer Data
AllyPipe’s staff do not access Customer personal data except (a) to provide support the Customer asks for, limited to what is needed, or (b) where the law requires it. The platform’s administration screens do not show a Customer’s deals, contacts or campaigns.
10. End of processing
10.1 Customer admins can download all Customer Data at any time.
10.2 When the agreement ends, the Customer’s Workspace becomes read-only for 30 days so its admins can download everything. AllyPipe then deletes the Workspace’s database and records the deletion. Cloudflare’s point-in-time recovery copies expire within 7 days after deletion (30 days if AllyPipe uses a paid Cloudflare plan). AllyPipe keeps no other copy, unless the law requires it to.
11. Audits and information
11.1 AllyPipe will make available the information needed to show it meets Article 28, including this agreement, Annex 2 and the records of processing it keeps.
11.2 The Customer may audit AllyPipe’s compliance, on at least 30 days’ written notice, no more than once a year unless a breach has occurred or a regulator requires it. Audits will be carried out in a way that does not disrupt the Service or put other customers’ data at risk. Each party bears its own costs. AllyPipe may meet an audit request first by providing written answers and evidence.
12. Liability
Liability under this agreement is subject to the limits in clause 15 of Part A.
Annex 1: Details of processing
| Item | Details |
|---|---|
| Subject matter | Hosting and operating the Customer’s AllyPipe Workspace |
| Duration | For as long as the Terms of Service apply, then until deletion under clause 10 of Part B |
| Nature and purpose | Storing, organising, displaying, sharing (as the Customer chooses), exporting and deleting Customer Data so the Customer can manage its sales pipeline, contacts, partners and outreach records |
| People concerned | The Customer’s business contacts and prospects; contacts at its Partners and Linked Companies; its Users (staff and partner users) |
| Types of personal data | Names, job titles, employer, work email addresses, phone numbers, LinkedIn profile addresses, location and country, notes and activity records written by Users, outreach status and dates, lawful basis and source recorded for each contact, and sign-in email addresses and activity of Users |
| Special category data | None intended. The Customer must not enter it unless the law allows and it is needed (Part A, clause 6.3) |
| Where stored | Cloudflare D1 databases in the EU jurisdiction, one per Customer |
Annex 2: Security measures
| Area | Measure |
|---|---|
| Separation of customers | Each Customer has its own database. The code serving a Customer is given that database only, and automated tests check that it cannot reach another’s. |
| Sign-in | Cloudflare Access with a one-time code to the User’s work email; no passwords are stored. Every request is checked against the User’s membership of the Workspace and their being active. |
| Roles | Admin, staff with all records, staff with own records only, and partner users. What each role sees is enforced on the server and covered by automated tests. |
| Partner view | Partner users receive only deals shared with them, never contact email addresses or phone numbers, and contact names only where allowed. The data sent to partners is limited to a fixed list checked by automated tests. |
| Encryption | TLS for all traffic; data encrypted at rest by Cloudflare (AES-256). |
| Platform administration | The platform console is limited to one named AllyPipe administrator and does not display Customer deals, contacts or campaigns. |
| Links between companies | Requests between linked Workspaces require a service credential, a configured client id and a fresh, signed, single-use request. |
| Claude connector | Off by default; read-only; personal keys stored only as SHA-256 hashes, expiring after 90 days, checked on every request; never returns contact names, emails, phone numbers or LinkedIn addresses. |
| Audit trail | Changes to deals, sharing, users, settings, downloads and connector use are recorded in each Workspace’s activity log. |
| Web protections | Security headers and a content security policy; changes accepted only from the Service’s own pages; uploaded logos accepted only as checked PNG or JPEG files. |
| Recovery | Cloudflare point-in-time recovery of each database for 7 days (30 days on a paid plan). |
| Change control | Every change runs an automated test suite before release, and is tested on a separate staging copy with fictional data before it reaches production. |
| People | Access to production systems limited to Sigmatak’s named administrators, with multi-factor authentication on the Cloudflare account. |
Annex 3: Sub-processors
AllyPipe uses one sub-processor for Customer personal data.
| Sub-processor | What it does | Location | Safeguard |
|---|---|---|---|
| Cloudflare, Inc., 101 Townsend Street, San Francisco, CA 94107, USA | Hosts the Service and the Customer databases (Pages, Workers, D1); runs sign-in and sends one-time codes (Access) | Databases stored in the EU; service operated globally | Cloudflare Data Processing Addendum v6.4 (3 April 2026); Data Privacy Framework with UK extension; EU SCCs with UK Addendum. Cloudflare’s own sub-processors: list |
Not sub-processors of AllyPipe:
- Anthropic (Claude). The optional connector lets a User’s own Claude account read the Workspace. Anthropic acts under the User’s or Customer’s agreement with Anthropic, so the Customer decides whether to switch the connector on and covers that use in its own records.
- LinkedIn. AllyPipe never connects to LinkedIn. Users import their own exported connection files and record what they do on LinkedIn themselves.