Login Register interest

Acceptable Use and Data Responsibility Policy

Version 1.0 · Acuryln Bridge is operated by Acuryln Inc (not yet incorporated), Corner House, Holly Lane, Styal, Wilmslow, SK9 4JL, England ("Acuryln", "we", "us").

This Policy forms part of the Terms of Service. By creating an account, adding a connection, uploading API documentation, or enabling MCP tools, you ("the Customer") accept it on behalf of yourself and your organisation.

1. What Acuryln Bridge does Acuryln Bridge is a tool. It transfers, stores and exposes data only where and how you configure it to. We do not select the systems you connect, the data you retrieve, or the purposes for which you use it. You remain the controller of that data and the decision-maker for every connection, task, staging table, saved view and MCP tool you create.

2. Your responsibilities You confirm and warrant, for every connection and every dataset, that: 1. Right to access. You hold a valid licence, subscription, contract or other lawful authority to access the API or system you connect, and that using it through Acuryln Bridge does not breach that provider's terms of service, developer agreement, rate limits or acceptable use rules. 2. Ownership or permission. The data you retrieve, store or expose is either your organisation's own data, or you have documented permission from the owner of that data to retrieve, store, process and expose it in the way you have configured. 3. Lawful purpose. You will not use Acuryln Bridge to obtain, process, combine or distribute data in a way that is unlawful in the United Kingdom, in the country where you operate, in the country where the data subjects are located, or in the country where the connected system is hosted. This includes, without limitation, data protection and privacy law (including UK GDPR and the Data Protection Act 2018), computer misuse law, intellectual property law, competition law, export control and sanctions law, and contractual confidentiality obligations. 4. Data protection compliance. Where the data includes personal data, you have a lawful basis for processing it, have given any required notices to data subjects, have completed any required impact assessment, and have a lawful mechanism for any international transfer created by your choice of region or connected system. 5. AI and MCP use. Where you enable MCP tools or connect an AI assistant, you are responsible for what that assistant is permitted to query, for reviewing any tools it creates, for keeping write access disabled unless you intend it, and for the outputs generated from your data. 6. Credentials. The credentials you store are yours to use. You will rotate or revoke them if you believe they have been exposed and will not share account logins between individuals. 7. Users you invite. You are responsible for the actions of every user you invite to your instance, for assigning appropriate roles, and for removing users who leave your organisation.

3. Prohibited uses You must not use Acuryln Bridge to: access any system without authorisation; scrape or harvest personal data without a lawful basis; circumvent authentication, rate limits or access controls; process special category or criminal offence data without the additional safeguards the law requires; store payment card data outside a PCI DSS compliant arrangement; transmit malware; or infringe any third party's rights.

4. Data leaks and security incidents 1. Our responsibility. We are responsible for the security of the Acuryln Bridge platform itself: our hosting, our encryption of stored credentials and staged data, our access controls, our staff, and our sub-processors. If a security incident is caused directly by a failure of the platform, we will notify affected Customers without undue delay and in any case within 48 hours of becoming aware, and will cooperate with your regulatory obligations. 2. Your responsibility. You are responsible for any disclosure, loss or misuse of data that is not directly caused by a failure of the platform, including but not limited to: compromised or shared login credentials; users you invited or failed to remove; roles or permissions you assigned; connections, tasks, saved views or MCP tools you configured; AI assistants or third-party clients you connected; data you exported, downloaded or forwarded; and the security of the systems on the other side of any connection. 3. Shared incidents. Where an incident has more than one cause, responsibility is apportioned according to each party's contribution. Each party will preserve logs and cooperate in good faith to establish the facts. 4. Reporting. If you believe your instance or a connected system has been compromised, you must tell us immediately so that we can help contain it.

5. Monitoring and enforcement We may run automated security checks against your connections and staged data, including geolocation of endpoints, detection of personal data fields and checks against sanctions lists. These checks are provided to help you; they are not legal advice, not a guarantee of compliance, and do not transfer any of your responsibilities to us. We may suspend or restrict an instance, connection or tool where we reasonably believe this Policy is being breached, and will tell you why unless prevented by law.

6. Indemnity and liability You will indemnify Acuryln against claims, fines, losses and reasonable costs arising from your breach of this Policy, including claims by API providers, data owners, data subjects or regulators. Nothing in this Policy limits liability that cannot be limited by law, and our overall liability is as set out in the Terms of Service.

7. Changes We may update this Policy. Material changes take effect 30 days after we notify you in the app or by email, and you will be asked to accept the new version at your next login. Continued use after that date is acceptance.