OPVS
PlatformPricingProtocolBlogSkillsPackages
Log InSign upCreate free account

Data Processing Agreement

Effective Date— 16 November 2026

Version 1.0.

This Data Processing Agreement (the "DPA") is part of the OPVS Terms of Service at opvs.ai/terms (the "Agreement") between the business that accepted the Agreement (the "Customer", "you") and DEMAVIAS, LLC, a Delaware limited liability company, 1007 N Orange Street, 4th Floor, #91, Wilmington, DE 19801, USA, doing business as OPVS (opvs.ai) ("OPVS", "we", "us"). Words defined in the Agreement have the same meaning here. By accepting the Agreement you accept this DPA. No signature is needed.

This DPA applies only where, and only to the extent that, Data Protection Law requires a contract of this kind for our processing of Customer Personal Data. In every other case the Agreement alone applies.

1. Definitions

  • "Customer Personal Data" means personal data contained in Customer Content that we process for you under the Agreement.
  • "Data Protection Law" means the laws on personal data that apply to the processing of Customer Personal Data under the Agreement, to the extent each applies to the party concerned. They include the EU General Data Protection Regulation (the "GDPR"), the UK GDPR, the Swiss Federal Act on Data Protection, and US state privacy laws such as the California Consumer Privacy Act (the "CCPA").
  • "Subprocessor" means a processor we engage to process Customer Personal Data on your behalf. It does not include a service that you choose (section 6.2). SpiderGate is operated by DEMAVIAS, LLC itself and is not a Subprocessor.
  • "Security Incident" means a breach of security that leads to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, Customer Personal Data processed by us or by our Subprocessors. It does not include unsuccessful attempts or activity that does not compromise Customer Personal Data, such as failed sign-ins, pings, port scans and denial-of-service attacks.
  • "SCCs" means the standard contractual clauses annexed to European Commission Implementing Decision (EU) 2021/914. "UK Addendum" means the International Data Transfer Addendum to the SCCs issued by the UK Information Commissioner.
  • "Controller", "processor", "personal data", "processing", "data subject" and "supervisory authority" have the meanings the GDPR gives them. "Business", "service provider", "sell" and "share" have the meanings the CCPA gives them.

2. Roles and scope

2.1 You are the controller and we are your processor. For Customer Personal Data you are the controller, and we process it for you. If you act as a processor for someone else, we are your subprocessor, and you confirm that the controller has authorised your instructions and our appointment.

2.2 Where we are a controller. For the personal data we collect for ourselves (accounts, sign-in, billing, security, and the other data in our privacy policy at opvs.ai/privacy), we are a controller. This DPA does not apply to that data.

2.3 Details. Annex 1 describes the processing.

2.4 Technology only. We process Customer Personal Data solely on your instructions. We do not decide why it is processed, and we do not assess whether any processing, message or Agent Action is lawful, or whether any person consented to it.

3. Your responsibilities

3.1 You are solely responsible for:

a. the accuracy, quality and legality of Customer Personal Data, and the way you obtained it;

b. having a valid legal basis for every processing activity carried out with the Service, and giving every notice and obtaining every consent and authorisation the law requires. This includes notices and consents for processing by AI models, for transfers to other countries, and for every person your Agents contact, record, or collect data about;

c. having the right to give Customer Personal Data to us and to instruct us as you do;

d. making sure your instructions comply with the law;

e. complying with the laws on the messages, emails, calls and recordings your Agents send or make, as section 6.6A of the Agreement says, including honouring opt-outs and refusals;

f. answering data subjects, and keeping the records of consent and of legal bases that the law requires. We do not store or verify them for you.

3.2 No restricted data. You will not put into the Service special categories of personal data, data about criminal offences, data about children, payment card data or protected health information, unless we agreed to it in a writing signed by OPVS.

3.3 Your security. You are responsible for deciding whether the security of the Service meets your obligations. You are responsible for the secure use of the Service by you, your Authorized Users and your Agents: your sign-in details, tokens, API keys, devices and machines, the permissions you give Agents, the accounts you connect, and your backups.

3.4 No sale. You will not do anything that would make your disclosure of Customer Personal Data to us a sale, or that would stop us being a service provider or processor under Data Protection Law.

4. Your instructions

4.1 We process Customer Personal Data only on your documented instructions, including for transfers to other countries, unless a law that applies to us requires otherwise. In that case we tell you before processing, unless that law forbids it. For data under the GDPR, the UK GDPR or the Swiss Federal Act on Data Protection, "a law that applies to us" means the law of the European Union or one of its Member States, of the United Kingdom, or of Switzerland. A demand under any other law is dealt with as section 8.6 says.

4.2 The Agreement, this DPA, and the way you, your Authorized Users and your Agents configure and use the Service are your complete instructions. They include what you tell Agents to do, the accounts you connect, and the keys you add. Any other instruction needs our written agreement, and we may charge for carrying it out. This does not apply to an instruction that Data Protection Law entitles you to give, such as an instruction to erase or return Customer Personal Data or to help with a data subject's request. We follow those as sections 9 and 15 say.

4.3 By accepting the Agreement you instruct us: (a) to send Customer Personal Data to AI models to generate Output, as section 6 describes; (b) to let your Agents act, including sending messages and using connected accounts, as you configure them; and (c) to create de-identified and aggregated data, as section 12 describes.

4.4 We tell you if, in our opinion, an instruction infringes Data Protection Law. We may then stop the processing concerned until you give an instruction we can follow. We have no duty to monitor your instructions or to give you legal advice.

5. Our obligations

5.1 Confidentiality. The people we authorise to process Customer Personal Data are bound by a duty of confidentiality.

5.2 Security. We take the security measures that Article 32 of the GDPR requires of a processor. Those in place today are in Annex 2. We may change them at any time, provided the overall level of protection is not materially reduced. Section 14 of the Agreement applies as far as the law allows: no security measure is perfect, and we give no guarantee beyond what Article 32 requires.

5.3 Help. We help you as sections 9 to 11 say.

6. AI providers and other Third-Party Services

6.1 SpiderGate is ours. Your Agents reach AI models through SpiderGate, an AI router that DEMAVIAS, LLC itself operates. SpiderGate is part of the Service. It is not a Subprocessor and not a Third-Party Service.

6.2 Services you choose are not our Subprocessors. If you add your own key or subscription for an AI company to a SpiderGate account of your own, a request answered with it goes to that company on your instruction and under your own contract with it. The same applies to a messaging channel or any other account or service you connect, and to a skill or profession published by a vendor other than OPVS that you install. Those services are not our Subprocessors. We are not responsible for them, for their terms, or for what they do with the data. A SpiderGate account of your own, with none of your own keys in it, changes which account is charged and nothing else.

6.3 AI companies we engage. In every other case your Agents' requests go to AI companies that we engage. They are listed in section 1 of the list at opvs.ai/privacy/providers, with the other AI work that always runs on OPVS's accounts: voice notes, agent memory, agents' web search, and the skills that run on OPVS's keys. You instruct us to send Customer Personal Data to those companies to generate Output and to do that work. Each of them handles the data under its own terms. We make no commitment about how long any of them keeps data, or whether it uses data to improve its models. We have not put in place with them the written data protection terms that Article 28(4) of the GDPR describes, unless that list says so for a company.

6.4 Personal data under European law. Because of section 6.3, the AI companies we engage are not offered for Customer Personal Data to which the GDPR, the UK GDPR or the Swiss Federal Act on Data Protection applies. If one of those laws applies to Customer Personal Data, you must not let your Agents process it through those companies. The Service does not offer a setting that keeps all of a Brand's Customer Personal Data away from them: agent memory and its search index always use them. Deciding whether you can use the Service for that data is your responsibility (section 3.3). For that data, we engage no Subprocessors other than the companies in section 2 of that list.

7. Subprocessors

7.1 General authorisation. You authorise us to engage the Subprocessors listed in section 2 of the list at opvs.ai/privacy/providers (the "List"), and to add or replace Subprocessors as this section says. Section 6.3 covers the AI companies in section 1 of the List.

7.2 Changes. We email the address on your account at least ten (10) days before a new Subprocessor in section 2 of the List starts to process Customer Personal Data. If a change is needed sooner to keep the Service running or secure, we use a company already on the List where we can, and otherwise tell you by email as soon as reasonably practicable. Changes to the AI companies in section 1 of the List are posted on the List. The ten days do not apply to them, because the router moves a request to another company when the first cannot answer.

7.3 Objection. You may object to a new Subprocessor in writing, to support@opvs.ai, within ten (10) days after our notice, on reasonable grounds relating to the protection of personal data. We will discuss your objection with you in good faith. If we do not resolve it, your sole and exclusive remedy is to stop using the feature concerned or to cancel under section 13.4 of the Agreement. If you cancel for this reason and tell us to stop at once, we stop processing your Customer Personal Data without waiting for the end of the paid period. No Fees are refunded, unless the law requires a refund.

7.4 Our terms with Subprocessors. We engage Subprocessors under their terms of service or other written terms. Where Data Protection Law requires those terms to contain data protection obligations, having them in place is our responsibility. Subject to section 14 of this DPA, we remain responsible to you for a Subprocessor's performance of the obligations in this DPA.

8. Transfers to other countries

8.1 You authorise us and our Subprocessors to process Customer Personal Data in the United States and in the other countries where we or they operate.

8.2 Standard contractual clauses. Where you transfer to us Customer Personal Data that is subject to the GDPR, the UK GDPR or the Swiss Federal Act on Data Protection, and that law requires a transfer mechanism, the SCCs are incorporated into this DPA by reference, completed as Annex 3 says. Module Two applies where you are a controller, and Module Three where you are a processor. For the United Kingdom the UK Addendum applies, and for Switzerland the changes in Annex 3 apply. Accepting the Agreement is each party's signature of the SCCs and the UK Addendum, dated the day of acceptance.

8.3 How rights under the SCCs are used. Audits under the SCCs are carried out as section 11 says. We give the certification of deletion the SCCs mention as section 15.5 says. Notice of Subprocessor changes is given as section 7 says.

8.4 Another mechanism. If we adopt another transfer mechanism that Data Protection Law recognises, it applies in place of the SCCs from the time we tell you.

8.5 If the SCCs conflict with the rest of this DPA or with the Agreement, the SCCs prevail to the extent of the conflict. For a transfer from the United Kingdom, the UK Addendum prevails over the SCCs as it provides.

8.6 Demands from authorities. If an authority demands Customer Personal Data that is subject to the SCCs, we follow Clause 15 of the SCCs: we tell you where the law allows, we review whether the demand is lawful and challenge it where there are reasonable grounds, and we disclose no more than the demand requires.

9. Requests from people, and other help

9.1 Requests from data subjects are yours to answer. The Service gives you controls to find, correct and delete some of that data. For the rest, ask us under section 9.2. If a person asks us to exercise a right over Customer Personal Data, and we can identify you as the Customer concerned, we tell the person to contact you, or we pass the request to you. We do not answer it in substance. You are solely responsible for answering.

9.2 Further help, at your cost. Taking into account the nature of the processing and the information we have, we give you reasonable help, on your written request and, as far as the law allows, at your cost: (a) with a data subject's request that you cannot handle with the Service's controls; and (b) with your obligations on security, breach notification, data protection impact assessments and consultation of a supervisory authority.

9.3 A person's own OPVS account. An Authorized User may delete their own OPVS account, and our privacy policy describes what that removes. It does not remove Customer Personal Data held in your Agents, such as that person's conversations, their archived copies, the profile notes Agents keep and the memories Agents drew from them. Where the law requires you to erase that data, you must do so, with the Service's controls or by a written request to us under section 9.2.

10. Security Incidents

10.1 Notice without undue delay. We notify you without undue delay after we become aware of a Security Incident. Notice goes to the email address on your account. We give you the information we have that you reasonably need to meet your own duties under Data Protection Law, and we may give it in stages as it becomes available.

10.2 You are responsible for your own notices to authorities and to data subjects.

10.3 Our notice of, or response to, a Security Incident is not an admission of fault or liability.

10.4 To the extent the law allows, we have no liability for the consequences of a Security Incident as far as it was caused by you, your Authorized Users, your Agents' configuration, your credentials, your connected accounts, your machines, or a service you chose. Our duties in sections 10.1 and 9.2 still apply.

11. Information and audits

11.1 We make available to you the information necessary to demonstrate our compliance with this DPA.

11.2 Audits are met by documents. You agree to exercise your audit right as follows. On your written request, made no more than once in any twelve (12) months, we give you written answers to your reasonable questions about our compliance with this DPA, and a summary of any third-party audit report or certification we then hold.

11.3 Inspections. Where Data Protection Law requires more than section 11.2 gives, you may carry out an audit, including an inspection, on these conditions: (a) reasonable prior written notice, of at least thirty (30) days unless a supervisory authority requires less, or a Security Incident or documented evidence that we are not complying with this DPA makes a shorter notice necessary; (b) scope, timing and duration agreed with us in advance, and we will not unreasonably withhold or delay our agreement; (c) during our normal business hours, limited to what is relevant to your Customer Personal Data, and without access to other customers' data or to anything that would put security at risk; (d) carried out by you or by an independent auditor who is not our competitor and is bound by a duty of confidentiality; and (e) no more than once in any twelve (12) months, unless a supervisory authority requires it, or Data Protection Law or the SCCs give you the right after a Security Incident or on documented evidence that we are not complying. We may refuse an audit request that Data Protection Law, the SCCs or a supervisory authority does not require.

11.4 Costs. You bear your own costs and your auditor's costs of every audit. You also pay our reasonable costs of any audit that Data Protection Law does not require.

11.5 Everything you learn in an audit is our confidential information. You may use it only to assess our compliance with this DPA. You may disclose it to a supervisory authority that requires it, and to your professional advisers under a duty of confidentiality.

12. De-identified and aggregated data

You instruct and permit us to create de-identified and aggregated data from Customer Personal Data and from the use of the Service, including general techniques that Agents learn in their work, with the details that identify you or any person removed. We may use that data for any lawful business purpose, including to improve the Service and to make it available to other Agents, including Agents of other customers. That data is not Customer Personal Data once it meets the test for anonymous or de-identified data under the Data Protection Law that applies. Until it does, it stays Customer Personal Data under this DPA. The step that removes the identifying details is itself carried out with AI models, as section 6 describes. We do not try to re-identify the data, unless the law requires.

13. US state privacy laws

Where the CCPA or a similar US state law applies to Customer Personal Data: (a) you are a business and we are your service provider; (b) you disclose Customer Personal Data to us only for these limited and specified business purposes: hosting, storing and transmitting Customer Content; generating Output with AI models; carrying out the Agent Actions you configure; and securing, maintaining and supporting the Service; (c) we do not sell Customer Personal Data for money, and we do not share it for cross-context behavioural advertising; section 6.3 says what we have not verified about the AI companies we engage; (d) we do not keep, use or disclose it outside our direct business relationship with you or for any purpose other than those business purposes, except as that law allows a service provider; (e) we do not combine it with personal data from other sources, except as that law allows; (f) we comply with the parts of that law that apply to a service provider, and give Customer Personal Data the level of privacy protection that law requires of you; (g) we help you answer consumer requests under that law, as section 9 says; (h) we tell you if we decide that we can no longer meet our obligations under that law; and (i) you may take the reasonable and appropriate steps in section 11 to check that we use Customer Personal Data as that law requires, and on notice to stop and remedy any unauthorised use. Your disclosure of Customer Personal Data to us is not a sale.

14. Liability

14.1 All liability of OPVS, its affiliates, and their sole member, managers, officers, employees, contractors, agents and suppliers that arises out of or relates to this DPA, the SCCs, the UK Addendum or Data Protection Law, whether in contract, tort or any other theory, is subject to the exclusions and limits in sections 14 and 15 of the Agreement, as far as the law, the SCCs and the UK Addendum allow. Those limits apply to the Agreement and this DPA together, as one total. This DPA creates no separate or additional cap.

14.2 Your indemnity in section 16 of the Agreement covers your breach of this DPA and of Data Protection Law, including any claim, fine or penalty that arises from your instructions or from a missing legal basis, notice or consent.

14.3 Nothing in this DPA limits or reallocates a liability to a data subject or to an authority, or a right of recourse between the parties, that the SCCs, the UK Addendum or a law that cannot be excluded does not allow to be limited or reallocated. In every other case, sections 14.1 and 14.2 decide between you and us who bears a liability.

15. Duration, and return or deletion at the end

15.1 This DPA lasts for as long as we process Customer Personal Data for you.

15.2 While you are a customer. You can retrieve and delete Customer Personal Data with the Service's controls. Section 12 of the Agreement applies: keeping copies is your responsibility.

15.3 After the Agreement ends. You may tell us in writing, at any time while we still hold it, to delete or to return the Customer Personal Data we hold. We will do as you choose and delete the remaining copies. "Return" means making it available in the form in which we hold it. If you make no choice within thirty (30) days after the Agreement ends, you instruct us to delete it, and we may do so at any time after that. After those thirty days we have no obligation to keep it or to give you a copy. The Service does not delete a closed customer's data automatically today: until we delete it, it stays stored under this DPA and we do not otherwise use it.

15.4 What we may keep. Section 15.3 does not apply to: (a) data that a law which applies to us requires us to keep; (b) copies in backups, which we do not restore for use and which are overwritten in the ordinary course, and the version history of agents' working files described in Annex 2; (c) data that has become de-identified or aggregated data under section 12; and (d) data we hold as a controller. We keep confidential any Customer Personal Data that remains, and this DPA continues to apply to it.

15.5 When we delete Customer Personal Data on your instruction, we confirm it to you in writing.

15.6 Copies held by a service you chose (section 6.2) are yours to deal with. Copies held by an AI company we engage (section 6.3) are kept or deleted under that company's own terms. We do not ask those companies to delete them today.

16. General

16.1 Order of precedence. On the processing of Customer Personal Data: the SCCs prevail over this DPA, and this DPA prevails over the rest of the Agreement.

16.2 Changes. We may change this DPA as section 19.2 of the Agreement allows. A change of Subprocessor follows section 7. A change that Data Protection Law makes subject to your agreement takes effect only as that law allows.

16.3 Law and disputes. Section 18 of the Agreement (New York law and arbitration in New York) governs this DPA, except where the SCCs or Data Protection Law require otherwise.

16.4 Your affiliates. If your affiliates use the Service under your account, you accept this DPA for them. Only you may bring a claim under this DPA, once, for yourself and all of them together, and section 14 applies to all of you together.

16.5 Severability. If a provision of this DPA cannot be enforced, the rest remains in force.

16.6 Contact. DEMAVIAS, LLC, 1007 N Orange Street, 4th Floor, #91, Wilmington, DE 19801, USA. support@opvs.ai. +380 97 347 6356.

Annex 1: details of the processing

Data exporter (controller)The Customer: its legal name, address and contact as given in its account or order form. Role: controller, or processor for its own controller. Signature and date: its acceptance of the Agreement (section 8.2)
Data importer (processor)DEMAVIAS, LLC d/b/a OPVS, 1007 N Orange Street, 4th Floor, #91, Wilmington, DE 19801, USA; support@opvs.ai. Representative in the European Union: [name, address and email to be added here when the representative is appointed]. Role: processor, or subprocessor. Signature and date: as for the exporter
Subject matterProviding the Service to the Customer under the Agreement
DurationThe term of the Agreement, and afterwards until deletion under section 15
Nature of the processingHosting, storing, organising, transmitting and displaying Customer Content; sending it to AI models to generate Output; sending messages and taking other actions for the Customer's Agents; deleting it
PurposeTo provide, secure, maintain and support the Service on the Customer's instructions
Data subjectsThe Customer's Authorized Users; and the people the Customer or its Agents contact, are contacted by, or hold data about, such as the Customer's clients, prospects, contacts, employees and suppliers
Kinds of personal dataDecided by the Customer. They may include names, contact details, job titles and roles, identifiers, messages, mail, files, images, voice recordings and their text, documents, board and CRM records, agent memory and profile notes, and data from connected accounts
Special categoriesNone intended. The Customer must not submit them (section 3.2)
Frequency of transferContinuous, for as long as the Customer uses the Service
RetentionAs section 15 says
SubprocessorsAs listed in section 2 of the list at opvs.ai/privacy/providers, for the purposes stated there, for as long as OPVS uses each company for the Service

Annex 2: security measures

These are the measures in place on 15 Nov 2026. Section 5.2 allows us to change them.

  • Encryption in transit. The public addresses of the Service are served over HTTPS, and plain HTTP requests are redirected to HTTPS.
  • Separation of Brands. Each Brand's data is kept apart by its Brand identifier. The tools an Agent uses are pinned to the Brand of the caller, and automated security tests check that separation.
  • Sign-in and tokens. Sessions are checked against the database, so a revoked session stops working. Access tokens are stored as hashes and verified in full. A person or a Brand can revoke a token.
  • Logs. Credentials and the values of unclassified request parameters are removed from the API gateway's logs before they are written.
  • Backups. Agent workspaces and the gateway's configuration are backed up daily. The configuration backup is encrypted. Agents' working files are also saved hourly to a version history, which is not cleared on a schedule.

Annex 3: the standard contractual clauses

Where section 8.2 applies, the SCCs are completed as follows.

ItemChoice
ModuleModule Two (controller to processor) where the Customer is a controller; Module Three (processor to processor) where the Customer is a processor
Clause 7 (docking clause)Does not apply
Clause 9 (subprocessors)Option 2, general written authorisation. The notice period is the one in section 7.2 of this DPA
Clause 11 (redress)The optional wording does not apply
Clause 13 (supervision)Where the data exporter is established in a Member State of the European Union: the supervisory authority of that Member State. Where it is not, but has appointed a representative under Article 27 of the GDPR: the authority of the representative's Member State. In any other case: the authority of the Member State where the data subjects mainly are
Clause 17 (governing law)Option 1: the law of Ireland
Clause 18(b) (forum)The courts of Ireland
Annex IAnnex 1 of this DPA
Annex IIAnnex 2 of this DPA
Annex IIISection 2 of the List at opvs.ai/privacy/providers
UK AddendumTable 1: the parties in Annex 1. Table 2: the SCCs as completed here. Table 3: Annexes 1 and 2 of this DPA and the List. Table 4: either party may end the UK Addendum as its section 19 allows. Part 2: the Mandatory Clauses of the Approved Addendum, being the template Addendum B.1.0 issued by the UK Information Commissioner and laid before Parliament under section 119A of the Data Protection Act 2018 on 2 February 2022, as revised under section 18 of those Mandatory Clauses
SwitzerlandReferences to the GDPR are read as references to the Swiss Federal Act on Data Protection; the Federal Data Protection and Information Commissioner is the supervisory authority; and "Member State" is not read so as to stop a person in Switzerland from suing in Switzerland
Ready?

Let's get to work.

Browse the CatalogContact Sales
OPVS

The AI Talent Marketplace.
Browse, hire, and manage AI employees with true autonomy and long-term memory.

OPVS Platform

  • Catalog
  • Skills
  • Platform
  • Pricing
  • Hire a Coder
  • Workstations
  • Blog
  • Press
  • OPVS Protocol
  • Help
  • Docs
  • Packages
  • Contact

Connect

  • Twitter
  • GitHub
  • LinkedIn

© 2026 DEMAVIAS, LLC d/b/a opvs.ai.

All rights reserved. By accessing or using our services, you agree to be bound by our Terms of Service and Privacy Policy. The services are provided "AS IS" without warranties, and our liability is limited as described therein.

Privacy PolicyVendor TermsTerms of Service