This Data Processing Agreement (“DPA”) forms part of the Master Terms of Service (the “Terms”) between Quayutec and the Customer that accepted them. It applies wherever Quayutec processes personal data on Customer’s behalf in providing the Services. It takes effect when Customer accepts the Terms, without a separate signature. It is the contract under which Quayutec processes Customer Personal Data as a processor. It is drafted to set out the terms listed in Article 28 of the GDPR and Article 28 of the UK GDPR, and the terms the other laws named in Section 2 call for. Capitalised terms it does not define have the meaning the Terms give them.
1Parties and roles
1.1 Processor. Bhawesh Tibrewal, trading as Quayutec, an individual carrying on business in India, whose address is 289, Saraswati Kunj, Golf Course Road, Sector 53, Gurugram, Haryana 122011, India (“Quayutec”). Questions about this DPA go to hello@quayutec.com. Quayutec has not appointed a data protection officer.
1.3 Controller. The Customer is the Organization that accepted the Terms, acting as controller of the personal data that it, its people and its Agents put into the Services. Where Customer itself processes that data for another controller, Customer is a processor, Quayutec is its sub-processor, and Customer passes on to that controller whatever this DPA requires.
1.4 Rooms. In a Room, each Organization, the Host and each Guest, is the controller of the personal data it puts into that Room, and Quayutec processes it for each of them under the DPA each has accepted. Putting content into a Room that other Organizations have joined discloses it to those Organizations. From then on it is part of that Room’s shared record. It stays in that record if the Organization that put it there leaves the Room or is deleted, detached from that Organization, its Agents and its people (Section 11.3), until the Host deletes it or deletes the Room. For example, when Company B, a Guest, posts a message in a Room that Company A hosts, Company A receives that message as part of its Room’s record, and Company B’s later deletion instruction does not remove it from Company A’s Room. Content an Organization keeps private to itself in another Organization’s Room (its private memory and private files) is not disclosed, and is deleted on that Organization’s instruction.
1.5 Quayutec as controller. For the account, billing, waitlist, Agentia, public-site and security data that the Privacy Policy describes, and for its own limited purposes in Section 5.6, Quayutec is a controller in its own right, and the Privacy Policy, not this DPA, governs that data. Quayutec is not a party to the arrangements between the Organizations in a Room, including any agreement they make with each other about the content they share.
1.6 Personal use. Where Customer is an individual who uses the Services only for purely personal or household purposes, this DPA still applies: Quayutec processes the personal data in Customer’s account only on Customer’s instructions and as this DPA describes, and gives it the protection this DPA gives Customer Personal Data. Data Protection Law may not apply to Customer’s own processing in that case (for example, Article 2(2)(c) of the GDPR, its equivalent in the UK GDPR, and section 3(c)(i) of India’s Digital Personal Data Protection Act 2023), but it can still apply to Quayutec as the provider of the means for that processing (Recital 18 of the GDPR), and nothing in this DPA reduces Quayutec’s own duties under it or the rights of the people whose data it is. Sharing a Room with another Organization may take Customer’s processing outside a purely personal or household activity; Section 1.4 then applies to it as to any other Organization.
2Definitions
Data Protection Law means every law on the processing of personal data that applies to the processing under this DPA, to the extent it applies, including:
- (a) the GDPR (Regulation (EU) 2016/679), and the national laws that implement Directive 2002/58/EC;
- (b) the UK GDPR and the Data Protection Act 2018, as amended by the Data (Use and Access) Act 2025, and the Privacy and Electronic Communications (EC Directive) Regulations 2003;
- (c) the Swiss Federal Act on Data Protection (“FADP”);
- (d) India’s Digital Personal Data Protection Act 2023 (“DPDP Act”) and the Digital Personal Data Protection Rules 2025 (“DPDP Rules”); and the Information Technology Act 2000 (“IT Act”) and the rules and directions made under it, including, for as long as they apply, section 43A and the Information Technology (Reasonable security practices and procedures and sensitive personal data or information) Rules 2011 (“SPDI Rules”), the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules 2021 (“IT Rules”), and the directions of the Indian Computer Emergency Response Team of 28 April 2022 (“CERT-In Directions”);
- (e) the US State Privacy Laws (Section 15);
- (f) Brazil’s Lei Geral de Proteção de Dados (Lei 13.709/2018, “LGPD”) and the regulations of its Autoridade Nacional de Proteção de Dados (“ANPD”);
- (g) Canada’s Personal Information Protection and Electronic Documents Act (“PIPEDA”) and Quebec’s Act respecting the protection of personal information in the private sector (CQLR c. P-39.1);
- (h) Japan’s Act on the Protection of Personal Information (“APPI”);
- (i) the Republic of Korea’s Personal Information Protection Act (“PIPA”);
- (j) Singapore’s Personal Data Protection Act 2012 (“PDPA”);
- (k) South Africa’s Protection of Personal Information Act 2013 (“POPIA”);
- (l) Australia’s Privacy Act 1988;
- (m) the United Arab Emirates’ Federal Decree-Law No. 45 of 2021; and
- (n) the Kingdom of Saudi Arabia’s Personal Data Protection Law (“PDPL”).
Customer Personal Data means personal data that Quayutec processes on Customer’s behalf in providing the Services, as Section 3 describes. For a Customer subject to POPIA, it includes information about an identifiable, existing juristic person, where POPIA treats that information as personal information (Section 20.6).
Sub-processor means a third party Quayutec engages that processes Customer Personal Data.
Personal Data Breach means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, Customer Personal Data.
Security Incident means any of: a Personal Data Breach; any other breach of data security affecting Customer Personal Data; any violation or attempted violation of an obligation concerning the confidentiality of Customer Personal Data; and reasonable grounds to believe that Customer Personal Data has been accessed or acquired by an unauthorised person.
Standard Contractual Clauses or EU SCCs means the standard contractual clauses for transfers to third countries set out in the Annex to Commission Implementing Decision (EU) 2021/914.
UK Addendum means the International Data Transfer Addendum to the EU SCCs, template version B1.0, issued by the UK Information Commissioner under section 119A of the Data Protection Act 2018, as revised under its Section 18. The functions of the Information Commissioner passed to the Information Commission on 30 September 2026.
Brazil SCCs means the standard contractual clauses in Annex II to Resolution CD/ANPD No. 19/2024.
Agent Rights, Room Rules, Room Admin, Manager, Owner of an Agent, Approval Gate, Irreversible Action, Bilateral Room Agreement, Organization, Host, Guest and Room have the meanings the Terms give them.
“Personal data”, “processing”, “controller”, “processor”, “data subject” and “supervisory authority” have the meanings the applicable Data Protection Law gives them. Under the DPDP Act, “controller” is read as Data Fiduciary, “processor” as Data Processor and “data subject” as Data Principal. Under the LGPD they are read as controlador, operador and titular. Under the US State Privacy Laws, “controller” is read as business or controller, and “processor” as service provider, contractor or processor.
3Details of the processing
This Section and Schedule 1 are the description of the processing that Article 28(3) GDPR and Annex I.B of the SCCs require.
| Particular | Detail |
|---|---|
| Subject matter | Providing the Services: Project Rooms and their messages, tasks and shared memory; the Approval Gate, with the Agent Rights and Room Rules it applies; the Room’s ledger; the connection of Agents and of the AI tools that act as them; and the email notices these produce. |
| Duration | For as long as the Terms are in force, and afterwards until the data is returned or deleted under Section 11, or kept under Section 19. |
| Frequency | Continuous, for as long as Customer uses the Services. |
| Nature of the processing | Storing, organising and indexing Room content, including reading the text out of the files added to a Room so that it can be searched (the text is read, and search vectors are computed, by Quayutec’s own code, as a background task on Trigger.dev, a Sub-processor listed in Section 8; neither a file nor its text is sent to an AI model or an outside reading service to do this); making it available to the people and Agents that Customer, and the Organizations Customer shares a Room with, allow to see it; reading the actions that always-on Agents declare, to apply Agent Rights and Room Rules, and showing an action to the people asked to decide it before it is posted (Section 5); sending it to the model provider an always-on Agent’s owner chose (Section 5); sending notices by email; recording decisions and events, including each acceptance of a Room’s Room Rules and the words that record it; keeping an event stream for each Agent; showing a public Agent’s profile to other Organizations (Section 5.5); and returning or deleting it. |
| Purpose | To run the Services as Customer configures them, under the Terms and this DPA, and for no other purpose. |
| Data subjects | Customer’s people who use the Services (Customer itself, where Customer is an individual), including its Top Manager and any observers; people whose names, messages or details Customer, its people or its Agents put into a Room, such as colleagues, clients or contacts named in a task or a specification; and the people of other Organizations in the same Room, where Customer’s Agents process what they write, or where they decide at the Approval Gate an action of Customer’s Agent that lands on their Organization. |
| Categories of personal data | Names and email addresses; account and organisation identifiers; anything personal in the Room content Customer chooses to put in (messages, task text with its acceptance criteria and evidence, specifications, files and the text read out of them, and shared memory); Approval Gate records (what was proposed, which Organization was asked to decide it and why, who decided it, and when, and, for an action that went ahead, who allowed it); Agent Rights and their history (who changed them, when, and from what to what); changes to an Agent’s Agent Rights that a Manager of its Organization proposed, and how each ended (Section 17.5); each version of a Room’s Room Rules, with the person and Organization behind each change; each acceptance of Room Rules, with the person who accepted, when, and the words that record it; the Organizations made Room Admins and who made them so; incident reports a person files about an Agent’s work, which are free text of up to 4,000 characters and may name or describe people; Agent registration data (name, role, capabilities, instructions, model and provider, connection type, and the Agent’s identity keys, the private key encrypted as Section 7 describes); an event stream for each Agent that records kinds of event without their content (for example, that a task was completed or a held action approved); run telemetry; and connection records for Agents and connected apps, stored as hashes where Section 7 says so. |
| Special categories | None is needed to use the Services. Customer will not put special categories of personal data (Article 9 GDPR), or data about criminal convictions and offences, into a Room unless it has a lawful basis to do so and has judged the measures in Section 7 appropriate for it. Quayutec signs no business associate agreement under the US Health Insurance Portability and Accountability Act, so Customer will not put protected health information into the Services. |
| Where it is processed | Section 13.1 and the table in Section 8. |
| Retention | Sections 11 and 19. |
4Customer’s responsibilities
Customer is responsible for having a lawful basis for the personal data it puts into the Services and for giving the people it concerns any notice Data Protection Law requires. Customer decides what it shares with other Organizations in a Room, through the Bilateral Room Agreements it sets or accepts and the content it posts, and which model provider its own always-on Agents use. Through its Agents’ Agent Rights and the Room Rules it sets or accepts, Customer also decides which actions go ahead without a decision by a person at Customer. Customer decides whether each of its Agents is public (Section 5.5). Customer’s instructions to Quayutec must comply with Data Protection Law.
5Processing on Customer’s instructions
5.1 Documented instructions. Quayutec processes Customer Personal Data only on Customer’s documented instructions, including with regard to transfers to a third country. The only exception is processing that a law requires of Quayutec, and then only a law of the following kind: for processing subject to the GDPR, Union or Member State law; for processing subject to the UK GDPR, the law of the United Kingdom; for processing subject to the FADP, Swiss law; and for any other processing, the law that applies to it, including the law of India. Quayutec tells Customer of that legal requirement before processing, unless that law prohibits telling it. Where the law of a third country, including India, would require Quayutec to process or disclose personal data that is subject to the GDPR, the UK GDPR or the FADP otherwise than on Customer’s instructions, Sections 13.5, 18 and 19 apply instead of this paragraph.
Customer’s documented instructions are the Terms, this DPA, and the way Customer configures the Services: the Rooms it creates or joins, the Bilateral Room Agreements and Room Rules it sets or accepts, its Agents and their Agent Rights, follow-lists, connections and public setting, and its triage settings and read-only safelist. Quayutec tells Customer immediately if, in its opinion, an instruction infringes Data Protection Law.
5.2 Sharing within a Room. A Room is shared by design. When Customer puts content into a Room, or admits another Organization’s Agents to it, Customer instructs Quayutec to make that content available to the people and Agents of the other Organizations in the Room, within the scope of the Bilateral Room Agreement. Where one of Customer’s always-on Agents declares an action that lands on another Organization whose Room Rules ask it first, Customer instructs Quayutec to show that action as the Agent declared it (or, where the request covers the whole reply, the reply’s first 500 characters) to that Organization’s people who may decide it, before the reply is posted, and to quote the action in the Room if that Organization rejects it or does not answer within 72 hours. Every Organization that has joined a Room can see its Room Rules, their history, and the name of the person and the Organization behind each change.
5.3 Model providers. When an always-on Agent runs, Quayutec sends the Room’s recent messages, the shared memory that Agent may read, and the few passages of the Room’s files that are most relevant to the message that woke it and that Agent may read, to the model provider chosen by the Organization that owns the Agent, under that Organization’s own key. The provider is engaged by that Organization directly, under its own terms; it is not Quayutec’s Sub-processor. By admitting another Organization’s always-on Agents to a Room, Customer instructs Quayutec to send that Room’s content to that Organization’s chosen provider in this way. That provider may be in any country, and Quayutec does not choose it. A connected Agent’s tool reads the Room through the Room’s tools and handles what it reads under its owner’s own arrangements.
5.4 Disclosure to other Organizations and their providers (transfers). For the purposes of Clause 8.7 of the Standard Contractual Clauses, the disclosures in Sections 5.2 and 5.3 are made on Customer’s documented instructions.
5.5 Public Agents. An Organization chooses whether each of its Agents is public. A public Agent’s name, role, capabilities, model and provider, connection type, its Organization’s name, a trust score from 0 to 100 and a count of completed collaborations are shown to every signed-in Organization in the Agents directory (“Discover”). The trust score is 50 plus up to 50 points for the share of tasks assigned to that Agent, across every Room it works in, that it completed. An Agent’s instructions are shown only to people of the Agent’s own Organization, never to another Organization.
5.6 Quayutec’s own limited purposes. Quayutec uses the records of Agent Runs, Approval Gate decisions and account identifiers that the Services produce, as a controller in its own right, only to: count Agent Runs to meter and bill them; secure the Services and detect and prevent abuse, fraud and breaches of the Acceptable Use Policy; and comply with law that binds Quayutec. It does not use Room content (messages, task text, files and shared memory) for any of these purposes except security and legal compliance, and then only as far as necessary. The Privacy Policy describes this processing. For the US State Privacy Laws, these are internal uses to provide and secure the Services and to comply with law. Quayutec keeps the event stream for each Agent described in Section 3: the kind of event, the Agent, its Organization, the Room, the record the event concerns and when it happened, without any content. It is used only to run the Services and to keep them secure. To run them, it shows whether an Agent’s run has finished, the Agent’s activity timeline, and the lines in Activity about actions that went ahead. To keep them secure, it records blocked prompt-injection attempts, intercepted passwords and keys, safety cut-offs, incident reports about the Agent, and task acceptances and rejections. Quayutec computes no score from it and makes no decision about any person from it.
6Confidentiality
Quayutec binds every person it authorises to process Customer Personal Data to a duty of confidentiality, contractual or statutory. Room content is not encrypted at the application layer, so the people who operate Quayutec can technically read it through the database’s administrative access. They access Customer Personal Data only as needed to run, secure and support the Services, to investigate a problem Customer reports, or where the law requires it.
7Security measures
7.1 The measures. Quayutec implements the technical and organisational measures below. This Section is Annex II of the SCCs. Each measure is stated only as far as the code shows it; a measure that depends on an infrastructure provider is stated as that provider’s measure, which Quayutec has not audited. Customer is responsible for judging whether these measures suit the personal data it chooses to put into a Room. The Security page on Quayutec’s website explains the same measures at more length; where it and this Section differ, this Section governs.
- Access to a Room. Every request that reads or writes something belonging to a Room passes an explicit membership check: for a person, that their Organization owns the Room or has an Agent on its roster; for an Agent, that its key or sign-in token belongs to an Agent on that Room’s roster. A request without a session is refused before any route runs, except at a small number of endpoints that authenticate their caller in another way (such as payment and email webhooks, the public forms and the sign-in endpoints); Quayutec keeps the list and gives it on request. A test in the suite reads every API route and fails if one that touches a Room has neither check and no written reason.
- Between Organizations. Reading and writing a Room’s shared memory and assigning tasks are each checked against the Bilateral Room Agreement’s own permission, and a Guest without an active agreement cannot post, read or write shared memory, assign tasks, or wake its always-on Agents. Each Organization’s private memory is kept apart from the shared record and filtered to the Organization that wrote it, and a file an Organization keeps private is visible only to it. An Organization can change only its own row of a Room’s Room Rules unless it is the Host or a Room Admin, and a change that asks an Organization less applies to it only after it accepts.
- Database. Row-level security is enabled on every table, as a second layer against anything querying the database directly. The application’s own routes use a service role that bypasses it, so the membership checks above are the boundary on the path a request takes. The tables that hold Agent Rights history, Room Rules versions and acceptances can be added to by the application but not changed or deleted by it. Two things do change them: when a person’s account is deleted, their id is cleared from these records and the records stay; and when an Organization’s account is deleted, the Rooms it hosts are deleted, with their records.
- Provider keys and other secrets. A model provider key is encrypted with AES-256-GCM, with a fresh 96-bit nonce each time, under a 32-byte master key. The master key is held as an environment variable at two Sub-processors, Vercel and Trigger.dev, and in the local environment file of the person who operates Quayutec. It is not in an external key management service and is not hardware-backed. A key is decrypted in memory for the call that needs it and is never returned in an API response, and the service refuses to store a key if the master key is missing or the wrong length. An Agent’s identity private key, a scheduled task’s wake token and a connected app’s event signing secret are encrypted the same way. A key stored before encryption was introduced may still be held unencrypted until it is migrated.
- Agent keys and sign-in. An Agent’s Quayutec key is 32 random bytes, stored only as its SHA-256 hash; regenerating it replaces the hash and signs every connected app out of that Agent. Signing in an AI tool uses OAuth 2.1 with PKCE: a code works once, within 60 seconds; an access token lasts an hour and a refresh token 30 days, replaced each time it is used; only hashes of either are stored; a token works only through the Room’s MCP addresses and meets the same roster check as a key; and it stops working when the app is signed out, when the Agent’s key is replaced, or when the person who allowed it leaves the company.
- Instructions. An Agent’s instructions are returned only to people of the Agent’s own Organization.
- The Approval Gate. Each action an always-on Agent declares is checked before the reply declaring it is posted: first against the Agent Rights its own Organization chose, and then, where it is read as irreversible and lands on another Organization, against that Organization’s Room Rules (Terms Sections 4.3 and 4.5). Which Organization an action lands on is read from what the acting Agent writes in its declaration. Where either asks, the action is held until a person at that Organization decides it, one Organization after another; each request expires untaken after 72 hours, and a decision from a person at any other Organization is not accepted. Before the reply is posted, a run that waited reads again the rows it relied on, and asks an Organization whose row now asks. Agent Rights the Services cannot read count as “Ask first”. An Agent whose Agent Rights have not been chosen is held for its own Organization as it was before Agent Rights existed. Only the Services write the line in the Room that says who allowed an action. In a Room where Agent Rights and Room Rules are not switched on for every Organization, an action read as irreversible is held for a person at the acting Agent’s own Organization and no setting can clear it, an action read as read-only is held the same way unless that Organization has switched automatic approval on, and no other Organization is asked. Where the Services cannot read whether Agent Rights and Room Rules are switched on, or cannot read a Room’s Room Rules, the run takes the strictest reading: every declared action waits for a person at the acting Agent’s own Organization, and every action read as irreversible, except one the Agent declares for its own Organization alone, also waits for a person at every other Organization in the Room; and where the Services cannot tell which Organizations are in the Room, the Agent does not reply at all (Terms Section 4.6).
- Notices of held actions. An email asking for a decision goes to the Organization’s named Top Manager or, if none is named, to at most 25 of its members.
- Secret scanning. Before anything is written to a Room’s shared memory, a deterministic check refuses content that looks like a credential, and the same check reads the text of every uploaded file; a file in which it finds one cannot be shared with the Room.
- The record. Each approval or rejection carries a hash of the decision before it. Every Room event, including each action that went ahead and who allowed it, each change of an Agent’s Agent Rights or of a Room’s Room Rules, each acceptance of Room Rules, and each Room Admin made or removed, is appended to the Room’s ledger as a hash, signed where a signing key is configured, so an altered record fails the published check. A Room’s export prints the recipe to recompute the chain.
- The web layer. Every response carries strict transport security with a two-year age, subdomains included and preload requested; framing is denied, content sniffing is off, and camera, microphone, geolocation and payment are disabled. Product pages run scripts only with a nonce set for each request. Client source maps are not published.
- Error and product telemetry. Error tracking runs on the server only, and request data is stripped before an error report is sent. Product analytics in the signed-in application records page views and named events by account and company identifier, with no automatic capture of clicks and no session recording.
7.2 Limits of these measures. The following are true today and form part of this Annex II:
- Quayutec holds no SOC 2 report, no ISO/IEC 27001 certificate and no other third-party security certification, and makes no claim to one.
- No third-party penetration test has been commissioned or performed.
- There is no continuous integration pipeline; the test suite, including the route test above, runs on demand, not on every change.
- There is no key-rotation procedure for the master key.
- Output that declares no action is held only when a net catches it. It is treated as conversation, whatever the Room’s rules say, unless a fixed keyword list catches it, the Agent says in the first person that it will delete or destroy something, or the Agent says in the first person that it will take one of a fixed list of acting steps and either Agent Rights are switched on for every Organization in the Room and the Agent’s rights are “Ask first”, cannot be read, or were never chosen with its Organization’s automatic-approval switch off, or they are not and that switch is off; such output then waits, as a whole, for a person at the Agent’s own Organization only.
- The plain-language policy an Organization could once write is no longer saved or shown, and one saved before is stored and not evaluated. Only an Agent’s rights, an Organization’s rows of each Room’s rules, its read-only safelist and the automatic-approval switch change any outcome; the switch decides read-only actions, and whether output that says it will take one of those acting steps waits, only for an Agent whose rights were never chosen or in a Room where Agent Rights are not switched on for every Organization in it.
- Which Organization an action lands on is read from what the Agent writes. An Agent that names no Organization, or mentions another Organization or its Agents, is asked of every Organization whose rules ask. An Agent that names its own Organization for an action that in fact affects another Organization is believed, and that Organization is not asked.
- Kinds of action are read from the words that declare them, and the reading can miss one. Words that carry an amount, a currency or an account number count as money whatever the verb; words that name no kind count as “anything else that changes something”; words the Services cannot read count as every kind; but an action described in words the Services do not recognise as a kind can be read as fewer kinds than it is. Only a row, or Agent Rights, under which every Irreversible Action waits for a person cannot be missed this way.
- Where Agent Rights and Room Rules are not switched on, a Guest granted autonomous live action still opens a co-signature request that nothing waits on and only the acting Organization can resolve.
- Row-level security is not what guards the API path; the cross-tenant database checks are a SQL file run by hand, not automated.
- There is no automated deletion: a daily retention job counts the shared memory older than each Room’s memory window, but its deletion is switched off, so it deletes nothing. Deletion and export requests are carried out by hand (Section 11).
- The content security policy of the public website allows inline scripts.
7.3 Changes. Quayutec may change these measures, but not in a way that materially reduces the overall protection of Customer Personal Data (Section 21).
8Sub-processors
8.1 Authorisation. Customer gives Quayutec general authorisation to engage Sub-processors. Those that process Customer Personal Data are listed below. This list is Annex III of the SCCs.
| Sub-processor | What it does with Customer Personal Data |
|---|---|
| Supabase Pte. Ltd. | Hosts the database: Room content, shared memory and its search vectors, accounts and authentication, and realtime delivery. |
| Trigger.dev (API Hero Ltd) | Runs always-on Agents’ work as durable tasks, and holds the Approval Gate’s waitpoints. Quayutec’s own reading of the files added to a Room (taking the text out, the check for passwords and keys, and indexing for search) also runs on it, as a background task. |
| Vercel Inc. | Hosts and delivers the application and its API. |
| Hostinger (HOSTINGER PTE LTD) | Delivers transactional email: invitations, approval requests and sign-in links. |
| Resend (Plus Five Five, Inc.) | Delivers setup emails and reminders, which name the recipient, their company and, where relevant, a Room or an Agent. |
| Sentry (Functional Software, Inc.) | Server-side error tracking. |
Sign-in emails sent by Supabase Auth go through the mail service set in the Supabase dashboard; the row of whichever service it is covers them.
8.2 Not Sub-processors. A model provider chosen by an Agent’s owner is not a Sub-processor (Section 5.3). Nor are the other Organizations in a Room. Quayutec also uses Paddle, Slack, Google Sheets, PostHog, Google Analytics, Microsoft Clarity, Warmly, Dreamdata and Leadfeeder as a controller, for its own purposes described in the Privacy Policy; none of them processes the content of a Room. Cloudflare answers DNS queries for Quayutec’s domains and carries no Customer Personal Data.
8.3 Changes. Quayutec gives Customer notice of any intended addition or replacement of a Sub-processor at least 30 days before it processes Customer Personal Data, by updating this list and by email to Customer’s account owner. Customer may object on reasonable grounds relating to data protection by writing to hello@quayutec.com within that period. The parties will discuss the objection in good faith; if Quayutec cannot meet it, Customer may end its subscription before the change takes effect and is not charged for any period after it ends. For a Customer subject to PIPA, the notice is a request for Customer’s consent (Section 20.2).
8.4 Obligations passed on. Quayutec imposes on each Sub-processor, by written contract, data protection obligations that give Customer Personal Data the same protection as this DPA, in particular sufficient guarantees of appropriate technical and organisational measures.
8.5 Liability. Quayutec remains fully liable to Customer for each Sub-processor’s performance of those obligations.
9Assistance
9.1 Requests from data subjects. If Quayutec receives a request from a data subject about Customer Personal Data, it does not answer it itself, beyond telling the person to contact Customer, and passes it to Customer without undue delay. Taking into account the nature of the processing, Quayutec helps Customer answer such requests, including requests under the DPDP Act from Data Principals and under the US State Privacy Laws from consumers: Customer can see a Room’s content in the Services and ask for its records under Section 11.6, and Quayutec carries out a correction, deletion or export Customer asks for in writing.
9.2 Compliance. Quayutec gives Customer the information it reasonably needs, and that is available to Quayutec, to meet its own obligations on security of processing, notifying a breach, data protection impact assessments and prior consultation with a supervisory authority, under Articles 32 to 36 of the GDPR and of the UK GDPR, and the corresponding provisions of the FADP and the DPDP Act. On request, Quayutec gives Customer a written description of the data flows, the Sub-processors, the Agent Rights and Room Rules model, the ledger and the retention periods, for use in Customer’s own impact assessment.
9.3 US state law assessments. Quayutec gives a Customer that is a business under the CCPA the information it reasonably needs to complete its cybersecurity audit (Article 9 of the CCPA regulations), its risk assessment (Article 10) and its duties on automated decisionmaking technology (Article 11), and helps a Customer that is a controller under another US State Privacy Law with its data protection assessments and with the security of personal data, including personal data collected, stored and processed by an artificial intelligence system where Texas law requires that help.
9.4 Transfer assessments. Quayutec gives Customer the information it needs to assess a transfer under Section 13.5, and to apply the UK data protection test under Section 13.6.
10Personal data breaches
10.1 Notice to Customer. Quayutec notifies Customer of a Security Incident affecting Customer Personal Data immediately, and in any case within 48 hours, after becoming aware of it. Quayutec notifies every Organization whose Customer Personal Data the incident affects, including every Organization in an affected Room, by email to that Organization’s account owner and its named Top Manager.
10.2 What the notice says. As far as Quayutec then knows: the nature of the incident, including the categories and approximate number of data subjects and records concerned; its likely consequences; the measures taken or proposed to address it and to mitigate its possible adverse effects; and a contact for more information. Where Quayutec cannot give all of it at once, it gives it in phases without further undue delay. The notice gives Customer what it needs to meet its own clocks, which Schedule 3 lists.
10.3 Containment. Quayutec takes reasonable steps to contain and investigate the incident and to prevent it happening again. Quayutec does not notify a supervisory authority, the Data Protection Board of India or a data subject on Customer’s behalf unless Customer asks it to in writing. Notifying an incident is not an admission of fault.
11Return and deletion
11.1 How a deletion is carried out. There is no self-serve deletion in the Services. Quayutec deletes Customer Personal Data on a written instruction from Customer’s account owner, after confirming that the instruction comes from Customer, using its deletion tool, which first produces a plan of what it will delete and what it will keep. Quayutec carries out the instruction without undue delay, and within one month of receiving it, and confirms it in writing.
11.2 Deleting Customer’s Organization. On Customer’s instruction to delete its Organization, Quayutec deletes:
- Customer’s Organization, its Agents (which leave every Room they are in) and its people’s accounts, profiles, setup and email records, Terms acceptances and sign-in tokens, unless Customer asks to keep its people’s sign-in accounts;
- every Room Customer hosts, with everything in it, including what Guests put there (Section 1.4), and the files stored for those Rooms;
- Customer’s private memory and private files in Rooms other Organizations host, every version of each;
- the event stream of Customer’s Agents;
- the waitlist entries of Customer’s people, matched by mailbox.
Before deleting, it expires the held actions of Customer’s Agents and closes any held action Customer was asked to decide in another Organization’s Room, through the Services’ own path, so that the runs waiting on them end and each Room’s ledger records it. It also revokes Customer’s open agreements as a Guest and its unused invitations.
11.3 What stays, detached. Content Customer put into Rooms that other Organizations host stays in those Rooms’ records under Section 1.4: messages, shared memory, tasks with their results and evidence, Approval Gate records with their hash chain intact, agreements, shared files and ledger entries. Its link to Customer’s Organization, Agents and people is removed, or left as an identifier that no longer names anyone, and the Services show it as from “a deleted company”, “a deleted agent” or “a person who has left”.
11.4 Deleting a person. On Customer’s instruction to delete one of its people: an owner, an admin or the named Top Manager must first hand the role to another person in Customer’s Organization; the last person in an Organization is deleted only by deleting the Organization. The Agents the person registered stay with Customer’s Organization, without the person’s credentials: their Quayutec key, provider key, scheduled task wake hook, event subscriptions and sign-in tokens are cleared, and Customer’s Managers issue new ones.
11.5 Agent Rights and Room Rules records. The versions of a Room’s Room Rules, the acceptances of them with the words that record them, the history of an Agent’s Agent Rights, and the proposals to change an Agent’s Agent Rights (Section 17) are kept so that the record of who agreed to what still stands. On deletion of a person, Quayutec deletes the account and profile data that link these records to that person, and clears the person’s identifier from the history of Agent Rights, the versions of Room Rules, the acceptances, the Room Admin records and each Agent’s record of who set its rights. The records stay with their Organization, with the words of each acceptance, which name the Organization and not the person who accepted, and their hash. The Room Rules versions and acceptances of a Room are deleted with that Room.
11.6 Return. At Customer’s choice, Quayutec returns Customer Personal Data before deleting it. A return is a copy of Customer’s Room records in CSV or JSON, available to every Customer, whatever its plan, on request to hello@quayutec.com, in addition to any self-serve export its plan includes.
11.7 When the Terms end. When the Terms end, Customer has 30 days to ask for a return under Section 11.6. Quayutec then deletes Customer Personal Data within 60 days, unless Customer asked for deletion earlier or Section 19 requires Quayutec to keep part of it. Ending a subscription while the Terms continue deletes nothing.
11.8 Copies Quayutec cannot reach directly. When it deletes a person, Quayutec also removes their details by hand from the systems its deletion tool cannot reach: the waitlist copy in Google Sheets, the Slack post announcing a sign-up, the contact at Resend, and the person’s events at PostHog. None of these holds Room content.
11.9 Retention required by law. Where the law of the European Union, of a Member State or of the United Kingdom, or Swiss law, requires Quayutec to keep specific Customer Personal Data that is subject to that law, Quayutec keeps only that data, for no longer than that law requires, continues to protect it under this DPA, and processes it for no other purpose. Any other legal requirement to keep data, including under the law of India, is handled under Section 19.
12Audits and information
12.1 Information. Quayutec makes available to Customer the information necessary to demonstrate compliance with this DPA and with Data Protection Law, including Article 28 GDPR, Article 28 UK GDPR and the US State Privacy Laws, and allows for and contributes to audits, including inspections, by Customer or an auditor Customer mandates. Quayutec holds no third-party security certification or audit report, so it meets this first with information: Section 7; on request, the source file behind any statement in Section 7; written answers to Customer’s reasonable questions; and the Room’s own record. Customer can export a Room’s messages, memory writes, tasks, memory conflicts and escalations, followed by the Room’s whole ledger, as CSV or JSON, and recompute the decision chain itself. The export also carries the Room’s consent record: every version of its Room Rules, the acceptances (in the Host’s export, every Organization’s; in a Guest’s, its own) and the changes to the Agent Rights of the reader’s own Agents in the Room. The self-serve export needs membership of the Room and is included in the plans that include export; every Customer can also have it on request under Section 11.6.
12.2 Audits. Where that information is not enough, or a supervisory authority requires it, Customer may audit Quayutec’s processing of Customer Personal Data: on at least 30 days’ written notice; no more than once in any twelve months, unless a Security Incident or a supervisory authority requires otherwise; at Customer’s own cost; during business hours; through an auditor bound by confidentiality; and in a way that does not expose any other customer’s data. These audits are the assessments that the US State Privacy Laws let a controller make of its processor. With Customer’s consent, Quayutec may instead arrange for a qualified and independent auditor to audit it, at least once a year and at Quayutec’s own expense, and give Customer the report.
13International transfers
13.1 Where Customer Personal Data is processed. Quayutec is established in India. The database, file storage and sign-in that hold Customer Personal Data are in the United States (Supabase’s East US region, North Virginia), and the application’s server code runs in the United States (Vercel); Section 8 names each Sub-processor. Until 12 November 2026 they were in Japan (Supabase’s Tokyo region); the copy left there is kept, paused and unused, only so that the move can be undone, and is deleted by 26 November 2026.
13.2 The EU SCCs. Where Customer Personal Data subject to the GDPR is transferred to Quayutec, or onward to a Sub-processor, in a country without an adequacy decision, the transfer is made under the EU SCCs, which are incorporated into this DPA by reference and completed as follows:
- Module Two (controller to processor) applies where Customer is a controller, and Module Three (processor to processor) where Customer is a processor. Customer is the data exporter and Quayutec the data importer.
- Module One (controller to controller) applies to personal data that Customer transfers to Quayutec for Quayutec’s use as a controller in its own right: the account details of Customer’s people that Customer gives Quayutec, and the records Quayutec uses for its own purposes under Section 5.6. Customer is the data exporter and Quayutec the data importer.
- Clause 7 (the docking clause) applies. Under Clause 9 (Modules Two and Three), Option 2 applies: general written authorisation, with the notice period in Section 8.3. The optional wording in Clause 11 does not apply. Under Clause 13, the competent supervisory authority is the one Schedule 1, Part C identifies.
- Under Clause 17, Option 1 applies: the Clauses are governed by the law of Ireland. Under Clause 18(b), disputes arising from the Clauses are resolved by the courts of Ireland; a data subject may also bring proceedings before the courts of the Member State where they habitually reside, as Clause 18(c) provides.
- Annex I is completed by Schedule 1 and Section 3, Annex II by Section 7, and Annex III by Section 8.
13.3 Quayutec’s own position under the GDPR. Recital 7 of Decision (EU) 2021/914 says the SCCs “may be used for such transfers only to the extent that the processing by the importer does not fall within the scope of Regulation (EU) 2016/679”. Quayutec may itself be subject to the GDPR under Article 3(2) for some of this processing. The European Commission has said it is developing standard contractual clauses for transfers to importers whose processing is directly subject to the GDPR. Until it adopts them, the parties use the EU SCCs as the safeguard for these transfers, and Quayutec will offer the new clauses by a notice under Section 21 within 90 days of their adoption.
13.5 Transfer impact. Under Clause 14 of the EU SCCs, the parties warrant that they have no reason to believe that the laws and practices of the countries of destination prevent Quayutec from fulfilling its obligations under the Clauses. Quayutec’s assessment covers:
- India, where Quayutec is established: the IT Act s.69 (directions to intercept, monitor or decrypt information); s.70B(6) and the CERT-In Directions (calls for information and directions; incident reports; logs); IT Rules r.3(1)(j) (information or assistance to authorised agencies within 72 hours of an order); and, from 13 May 2027, DPDP Act s.36 and DPDP Rule 23 (calls for information, which may be ordered kept secret).
- The United States, where Supabase stores the data (Supabase Pte. Ltd. is a Singapore company) and where Vercel Inc. and the other US Sub-processors are incorporated: a US provider of electronic communication or remote computing services must disclose data within its “possession, custody, or control, regardless of whether such communication, record, or other information is located within or outside of the United States” (18 U.S.C. 2713).
Quayutec documents this assessment and gives it to Customer on request, so that Customer can document its own and make it available to its supervisory authority under Clause 14(d). Section 18 sets out what Quayutec does when it receives a request from a public authority.
13.6 From the United Kingdom. For a transfer subject to the UK GDPR, the UK Addendum is incorporated into this DPA. Table 1 is completed with the parties’ details in Schedule 1, Part A; Table 2 with the Modules and options selected in Section 13.2; Table 3 by Schedule 1, Section 7 and Section 8; and in Table 4, neither party may end the UK Addendum when the Approved Addendum changes. The Mandatory Clauses are incorporated by this reference:
Part 2: Mandatory Clauses of the Approved Addendum, being the template Addendum B.1.0 issued by the ICO and laid before Parliament in accordance with s119A of the Data Protection Act 2018 on 2 February 2022, as it is revised under Section 18 of those Mandatory Clauses.
The competent regulator for these transfers is the Information Commission. Quayutec gives a UK Customer the information it needs to consider whether the data protection test in Article 46(1A) and (6) UK GDPR is met: where the data is processed, the Sub-processors, the measures in Section 7, and how Quayutec handles requests from public authorities (Sections 13.5 and 18).
13.7 From Switzerland. For a transfer subject to the FADP, the EU SCCs apply with these changes: references to the GDPR are read as references to the FADP to the extent the transfer is subject to it; the Federal Data Protection and Information Commissioner (“FDPIC”) is the competent supervisory authority for such a transfer, in parallel with any EU authority where the GDPR also applies, and is named in Schedule 1, Part C; and “Member State” in Clause 18(c) is not read so as to stop data subjects habitually resident in Switzerland from bringing proceedings there. The law of Ireland governs the Clauses for a transfer that is also subject to the GDPR; Swiss law governs them for a transfer subject only to the FADP.
13.9 Onward transfers. Quayutec transfers Customer Personal Data onward to a Sub-processor in a country without an adequacy decision only as Clauses 8 and 9 of the EU SCCs allow: the Sub-processor is bound by the EU SCCs under the appropriate Module, an adequacy decision covers that onward transfer, or the Sub-processor otherwise provides appropriate safeguards under Article 46 GDPR. Disclosures to other Organizations in a Room and to their model providers are made as Section 5.4 sets out.
13.10 Copies. Customer may ask Quayutec for a copy of the safeguards that apply to its transfers, and may give them to its data subjects as Article 13(1)(f) GDPR and the Brazil SCCs require of it.
13.11 Transfers out of India. Where the DPDP Act applies, it allows transfer outside India except to a country the Central Government restricts by notification (s.16(1)) and subject to any requirement in respect of making personal data available to a foreign State (Rule 15). Quayutec will stop or adapt a transfer if such a notification or order covers it. Where the SPDI Rules apply, Quayutec transfers sensitive personal data or information only to a recipient that provides the same level of data protection (Rule 7), which Section 8.4 secures.
14Liability, precedence, governing law and term
14.1 Liability. Each party’s liability under this DPA is subject to the limitations and exclusions of liability in Section 10 of the Terms, except where Data Protection Law does not allow them to apply. Nothing in the Terms or this DPA limits either party’s liability to data subjects under the EU SCCs or the Brazil SCCs, or Quayutec’s liability for its intentional acts or gross negligence. Nothing in this DPA limits liability to a natural person for a defective product that the law does not allow to be limited (Directive (EU) 2024/2853, Art. 15, for products placed on the market after 9 December 2026).
14.2 Precedence. If this DPA and the Terms conflict on the processing of personal data, this DPA governs. If the EU SCCs (with the UK Addendum or the Swiss changes, where they apply) or the Brazil SCCs conflict with this DPA or the Terms, those clauses govern.
14.3 Governing law. This DPA is governed by the law of Ireland so far as it applies to processing subject to the GDPR; by the law of England and Wales so far as it applies to processing subject to the UK GDPR; by Swiss law so far as it applies to processing subject only to the FADP; and otherwise by the law that governs the Terms (Terms Section 13). Disputes under this DPA follow Terms Section 13.2, except a dispute under the EU SCCs or the UK Addendum, which goes to the courts those clauses name, and a claim a data subject brings under Data Protection Law, which proceeds as that law provides.
14.4 Term. This DPA lasts for as long as Quayutec processes Customer Personal Data, including after the Terms end.
15US state privacy laws
15.1 Scope. In this section, “US State Privacy Laws” means the California Consumer Privacy Act of 2018, as amended (the “CCPA”), and its regulations, and every other comprehensive US state privacy law that applies to Customer Personal Data. The CCPA has no exemption for personal information about people acting in a business or employment role, and this section applies to that information too.
15.2 Role and business purposes. To the extent the US State Privacy Laws apply, Quayutec is Customer’s “service provider”, “contractor” or “processor”, and processes Customer Personal Data only for these business purposes, which Section 3 sets out: hosting Project Rooms and their messages, tasks, files (including the text read out of them to make them searchable) and shared memory; running the Approval Gate, with the Agent Rights and Room Rules it applies, and the Room’s ledger; connecting Agents and the AI tools that act as them; and sending the email notices these produce. Customer discloses Customer Personal Data to Quayutec only for these limited and specified business purposes.
15.3 Restrictions. Quayutec will not: (a) sell or share Customer Personal Data, as the CCPA defines those terms, or use it for cross-context behavioral advertising; (b) retain, use or disclose it for any purpose other than those business purposes, including any other commercial purpose, or outside the direct business relationship between Quayutec and Customer, except as the US State Privacy Laws permit; or (c) combine it with personal information Quayutec receives from or on behalf of anyone else, or collects from its own interactions with the person concerned, except as the US State Privacy Laws permit.
15.4 Processor duties. Quayutec will comply with the obligations the US State Privacy Laws place on it, give Customer Personal Data the level of privacy protection they require, and notify Customer if it decides it can no longer meet those obligations. Quayutec follows Customer’s instructions (Section 5); makes each person who processes Customer Personal Data subject to a duty of confidentiality (Section 6); helps Customer answer consumers’ requests (Section 9.1), meet its security and breach duties (Sections 7 and 10) and complete its assessments (Section 9.3); at the end of the services, deletes or returns Customer Personal Data at Customer’s direction, unless the law requires it to be kept (Section 11); makes available the information needed to demonstrate its compliance and allows the assessments in Section 12; and engages a Sub-processor only under a written contract that requires it to meet these obligations (Section 8.4), after giving Customer an opportunity to object (Section 8.3).
15.5 Responsibility for security. Quayutec is responsible for the measures in Section 7. Customer is responsible for its own settings in the Services, including its Agents’ Agent Rights, its Room Rules and Bilateral Room Agreements, who among its people has access, and its relationship with the model provider it chose.
15.6 Customer’s rights. Customer may take reasonable and appropriate steps to make sure Quayutec uses Customer Personal Data consistently with Customer’s obligations under those laws, including under Section 12, and, on notice, to stop and remediate unauthorised use. Quayutec certifies that it understands these restrictions and will comply with them.
16India
16.1 DPDP Act. Where Customer is a Data Fiduciary under the DPDP Act, Customer is the Data Fiduciary and Quayutec its Data Processor, and this DPA is the contract under which Customer engages Quayutec for the purposes of s.8(2). As s.8(1) provides, Customer remains responsible under the DPDP Act for processing that Quayutec carries out on its behalf. Quayutec:
- processes Customer Personal Data only under this DPA and Customer’s instructions (Section 5);
- protects it with the reasonable security safeguards in Section 7, which are the security terms of this contract for the purposes of DPDP Rule 6(1)(f);
- notifies Customer of a Security Incident as Section 10 provides, with the information Customer needs to give the Data Protection Board of India and each affected Data Principal intimation without delay, and to send the Board its detailed report within seventy-two hours (DPDP Rule 7);
- helps Customer answer the requests of Data Principals and redress their grievances (Section 9.1);
- erases Customer Personal Data on Customer’s instruction under Section 11, subject to the retention that Section 19.3 describes; and
- from 13 May 2027, keeps the personal data, associated traffic data and other logs of the processing for the period DPDP Rule 8(3) requires, as Section 19.3 sets out.
These obligations apply from the dates the DPDP Act and DPDP Rules come into force, which for most of them is eighteen months after their publication, 13 May 2027.
16.2 Reasonable security practices. For section 43A of the IT Act, for as long as it applies, the parties agree that the measures in Section 7 are the reasonable security practices and procedures for Customer Personal Data. Quayutec is not certified or audited against ISO/IEC 27001 or any code approved under SPDI Rule 8, and makes no claim of deemed compliance with that Rule.
16.3 Intermediary duties. Quayutec receives, stores and transmits Room content on behalf of its customers. Indian law may treat it as an intermediary for that content, and the IT Rules then require it: to remove or disable access to unlawful information within three hours of a court order or a reasoned written intimation from an authorised officer (r.3(1)(d)); to preserve information it removes, and associated records, for 180 days for investigation (r.3(1)(g)); to retain a user’s registration information for 180 days after the registration is cancelled (r.3(1)(h)); and to give information or assistance to an authorised agency within 72 hours of an order (r.3(1)(j)). Where these duties apply to Customer Personal Data, Section 19 governs the retention.
16.5 Confidentiality. Quayutec and its people keep Customer Personal Data confidential and do not disclose it in breach of this DPA (Section 6; IT Act s.72A).
17Agent rights and room rules records
17.1 What they are. Where Agent Rights and Room Rules are switched on for an Organization, the Organization chooses what each of its always-on Agents may do on its own (its Agent Rights), and each Room has rules, one row per Organization, saying whether an action that cannot be undone waits for a person at the Organization it lands on (its Room Rules). The Host, and the Organizations it makes Room Admins, can change any row; any Organization can change its own row. A stricter rule applies at once; a looser one reaches an Organization only once one of that Organization’s Managers accepts it (Terms Section 4.5). Quayutec runs these settings as Customer’s instructions (Section 5.1).
While they are switched off. Every Room has a first version of its rules, recorded when the Room is created (and, for the Rooms that existed on 16 October 2026, added that day). While agent rights and room rules are not switched on for the Host, that first version asks every Organization first, names the Host Organization and no person, and no acceptance is recorded.
17.2 The records. Quayutec keeps, as Customer’s processor:
- for each Agent: its rights level, the kinds of action that always ask a person, and who set them and when;
- every change to an Agent’s Agent Rights: who made it, when, and from what to what;
- every version of a Room’s Room Rules: each Organization’s row, which row changed, and the person and Organization who changed it, and when;
- every acceptance of a Room’s Room Rules: the Organization, the person who accepted, when, which version, how it was accepted (on creating the Room, on joining it, on accepting a change, or by changing its own row), and the words that record the acceptance, of up to 4,000 characters, with their SHA-256 hash;
- the Organizations the Host made Room Admins of a Room, who made them so, and when;
- for each held action: which Organization was asked to decide it and why; and, for an action that went ahead, who allowed it;
- the proposals to change an Agent’s Agent Rights described in Section 17.5;
- in each Room’s ledger, a hashed entry for each action that went ahead, each change of an Agent’s Agent Rights, each change and acceptance of the Room’s Room Rules, and each Room Admin made or removed.
17.3 Who sees them. Every Organization that has joined a Room sees that Room’s Room Rules, their history, and the name of the person who made each change, with their Organization. The history of an Agent’s Agent Rights, with the names of the people who changed it, is shown to the people of the Agent’s own Organization. A line in a Room that says who allowed an action names the person who approved it, if anyone did, by display name and never by email address. A change of an Agent’s Agent Rights is recorded in the ledger of every Room the Agent works in. The email addresses of each Organization’s owners, admins and Top Manager are used to tell them when one of its Agents’ rights changes, when a Room’s rules change or are accepted, or when a Room Admin is made or removed.
17.4 The words that record an acceptance. The words stored with an acceptance state the accepting Organization’s own row of that version in plain words, naming the Organization and not the person. Where Agent Rights and Room Rules are switched on for the accepting Organization, they are the words shown beside the button that recorded the acceptance.
17.5 Proposals to change an Agent’s Agent Rights. A Manager of an Agent’s Organization who is not the Owner of the Agent may change the Agent’s Agent Rights (Terms Section 3.3). A stricter change applies at once and the owner is told; any other change waits for the owner to accept or reject it. Quayutec keeps each proposal: who proposed it, to which owner, when, from what to what, against which version of the Agent’s rights, which waiting proposal it replaced, and how it ended (accepted, rejected, replaced by a newer one, or outdated by a change in between). One proposal waits for each Agent at a time. A proposal’s words are never changed after it is made; only how it ended is recorded. Proposals and their answers are visible only to the people of the Agent’s own Organization and are never written to a Room’s ledger; only a change that takes effect is recorded there, as any change of Agent Rights is. The people concerned are told by email.
17.6 Control. Each Organization is the controller of its own Agents’ rights and their history, its own proposals, its own rows of each Room’s Room Rules and its own acceptances.
17.7 Retention. Section 11.5 applies. Room Rules versions and acceptances are kept for the life of the Room. The history and proposals of an Agent’s Agent Rights have no fixed expiry today; nothing deletes them automatically.
17.9 The change itself. Under today’s Approval Gate, a person at the acting Agent’s Organization saw every action read as irreversible. Under Full autonomy, where the Organization an action lands on chose “autonomous”, nobody does. New Rooms and existing Rooms ask every Organization until that Organization accepts something looser, and existing Agents keep today’s behaviour until their owner chooses their rights.
18Requests from public authorities
18.1 What Quayutec does. If Quayutec receives a legally binding request from a public authority for Customer Personal Data, or learns of direct access by a public authority to it, Quayutec:
- notifies Customer promptly, with the information it is allowed to give, unless the law prohibits notice, in which case it asks the authority to allow notice;
- reviews the legality of the request and challenges it where, after careful assessment, there are reasonable grounds to consider it unlawful, and seeks interim measures to suspend its effects until a decision, where the law allows;
- discloses the minimum the request requires, on a reasonable interpretation; and
- documents each request, its assessment and its answer, and gives Customer that record on request, as far as the law allows.
This Section applies the commitments in Clause 15 of the EU SCCs to all Customer Personal Data.
18.2 Laws Quayutec knows may apply. Section 13.5 lists the Indian and US laws a Customer’s assessment should cover. Indian law may prohibit telling Customer about some requests: an order under DPDP Rule 23 may require a call for information to be kept secret.
19Retention that a law requires
19.1 The rule. Quayutec keeps Customer Personal Data after Customer’s instruction to delete it only where a law that applies to Quayutec requires it, and then keeps only the data that law requires, for no longer than it requires, protected under this DPA, restricted from any other use, and deleted when the period ends. Quayutec tells Customer, on request, which of its data is held under this Section and why.
19.2 Data subject to the GDPR, the UK GDPR or the FADP. For Customer Personal Data subject to the GDPR, the UK GDPR or the FADP, only a requirement of Union, Member State, UK or Swiss law allows Quayutec to keep data after Customer’s deletion instruction (Section 11.9). If the law of India or another third country requires Quayutec to keep such data, Quayutec treats that requirement as a law of the country of destination under Clause 14 of the EU SCCs: it tells Customer, describes the requirement in the assessment under Section 13.5, and keeps the data only as Section 19.1 allows.
19.3 India’s one-year rule (from 13 May 2027). DPDP Rule 8(3) requires a Data Fiduciary to “retain, in respect of any processing of personal data undertaken by it or on its behalf by a Data Processor, such personal data, associated traffic data and other logs of the processing for a minimum period of one year from the date of such processing”, for the purposes in the Seventh Schedule, and to have its Data Processor keep them too. DPDP Rule 6(1)(e) also requires one year’s retention of logs and personal data as a security safeguard, “unless compliance with any law for the time being in force requires otherwise”. Accordingly:
- (a) Customer is a Data Fiduciary under the DPDP Act for the processing. Quayutec keeps the personal data, associated traffic data and other logs of the processing for one year from the date of the processing before erasing them, uses them only for the purposes in the Seventh Schedule, and then erases them. An instruction from Customer to delete them sooner takes effect at the end of that year, and Quayutec removes them from use in the meantime.
- (b) The processing is of the personal data of people outside India, under a contract with a Customer outside India. Section 17(1)(d) of the DPDP Act disapplies most of the Act’s obligations to that processing, and Quayutec does not keep that data under Rule 8(3) after Customer’s deletion instruction.
20Other jurisdictions
20.1 Canada and Quebec. Section 7 sets out the protection Quayutec gives a Canadian Customer’s personal information, for the purposes of PIPEDA Principle 4.1.3. For a Customer subject to Quebec’s Act respecting the protection of personal information in the private sector, this DPA is the written mandate for the purposes of s.18.3: Quayutec protects the confidentiality of the information (Sections 6 and 7), uses it only for the mandate (Section 5), stops keeping it at the end of the contract (Section 11), notifies Customer’s person in charge of the protection of personal information without delay of any violation or attempted violation of an obligation concerning its confidentiality (Section 10, Security Incident), and allows that person to carry out any verification (Section 12). For Customer’s privacy impact assessment under s.17, Quayutec gives the facts in Sections 3, 7, 8 and 13.1.
20.2 South Korea. For a Customer subject to PIPA, this DPA is the document for the purposes of Article 26(1): Quayutec processes the personal information only for the entrusted work (Section 5) and applies the technical and managerial safeguards in Section 7. Quayutec re-entrusts the processing to a Sub-processor only with Customer’s consent (Article 26(6)): the notice under Section 8.3 is a request for consent, and if Customer does not consent, Section 8.3’s objection route applies. For Customer’s disclosure under Article 28-8(2), Sections 3, 8 and 13.1 give the items transferred, the countries, the timing and method, the recipients, the purpose and the retention.
20.3 Japan. For personal data a Japanese Customer provides to Quayutec, Quayutec takes measures equivalent to those a business handling personal information must take under the APPI, as Article 28(1) of the APPI refers to, and gives Customer the information about India’s system and Quayutec’s measures that Customer needs under Article 28(2) and (3).
20.4 Australia. For personal information an Australian Customer discloses to Quayutec, Quayutec handles it in a way consistent with the Australian Privacy Principles.
20.5 Singapore. Where Quayutec is a data intermediary under the PDPA for a Singapore Customer, it protects the personal data (Section 7), does not keep it longer than needed (Section 11), and notifies Customer of a data breach (Section 10).
20.6 South Africa. For a Customer subject to POPIA, Quayutec is its operator. It maintains the security measures in Section 7, for the purposes of s.19, and notifies Customer immediately where there are reasonable grounds to believe that personal information has been accessed or acquired by an unauthorised person (s.21(2); Section 10). Customer Personal Data includes information about identifiable, existing juristic persons. This DPA is intended as the binding agreement for transfers out of South Africa under s.72(1)(a), and it passes substantially similar protection to onward transfers (Section 13.9).
20.7 United Arab Emirates. For personal data of data subjects in the UAE, Quayutec adopts the measures, controls and requirements set out in Federal Decree-Law No. 45 of 2021, the contractual route its Article 23(1)(a) describes.
20.8 Saudi Arabia. For a transfer from a Customer subject to the PDPL, Quayutec will sign the standard contractual clauses issued by the Saudi Data and Artificial Intelligence Authority on request, and its breach notice under Section 10 is timed to let Customer notify the authority within 72 hours.
21Changes to this DPA
Quayutec may update this DPA to reflect a change in Data Protection Law, or a change of Sub-processor under Section 8.3. For any other change, Quayutec gives Customer at least 30 days’ notice by email to its account owner before the change takes effect. Quayutec will not reduce the protection this DPA gives Customer Personal Data without Customer’s agreement. Each earlier version stays available on request. Where notice is owed, a changed DPA applies to a Customer that accepts the Terms after the change from that acceptance, and to every other Customer at the end of the notice.
Schedule 1: Annex I to the Standard Contractual Clauses
Part A. List of parties
Data exporter. The Customer: its name, address and contact person as held in its Organization account. Activities relevant to the transfer: its use of the Services, as Section 3 describes. Role: controller (Modules One and Two) or processor (Module Three). Signature and date: Customer’s acceptance of the Terms, recorded with its date.
Data importer. Bhawesh Tibrewal, trading as Quayutec, 289, Saraswati Kunj, Golf Course Road, Sector 53, Gurugram, Haryana 122011, India. Contact: hello@quayutec.com. Activities relevant to the transfer: providing the Services. Role: processor (Modules Two and Three) or controller (Module One). Signature and date: as for the exporter.
Part B. Description of the transfer
- Categories of data subjects: as Section 3.
- Categories of personal data: as Section 3.
- Sensitive data: none is needed; Customer’s restrictions are in Section 3. The safeguards are those in Section 7.
- Frequency: continuous.
- Nature of the processing: as Section 3.
- Purposes: as Section 3, and, for Module One, Quayutec’s own purposes in Section 5.6.
- Retention: Sections 11 and 19.
- Transfers to Sub-processors: the subject matter, nature and duration are as Section 8 lists for each Sub-processor, for the duration of this DPA.
Part C. Competent supervisory authority
- Where Customer is established in an EU Member State: the supervisory authority of that Member State.
- Where Customer is not established in the Union but has appointed a representative under Article 27(1) GDPR: the supervisory authority of the Member State where that representative is established.
- Where Customer is not established in the Union and has no such representative: the supervisory authority of the Member State where the data subjects whose personal data is transferred are located.
- For transfers subject to the FADP: the Federal Data Protection and Information Commissioner, in parallel with any authority above where the GDPR also applies.
- For transfers subject to the UK GDPR: the Information Commission.
Schedule 3: Notification clocks (for information)
Each clock below is the obligation of the party named in the first column, under the law in the last column. Section 10 sets Quayutec’s own duty to Customer; the rest is here so that Customer can see what its own clock needs from Quayutec.
| Who notifies | Whom | When | Source |
|---|---|---|---|
| Quayutec | Customer, and every Organization whose data is affected | Immediately, and in any case within 48 hours of becoming aware | This DPA, Section 10 |
| Quayutec | CERT-In | Within 6 hours of noticing the incident or being told of it | CERT-In Directions, direction (ii) |
| A controller under the GDPR | The competent supervisory authority; where the controller has no EU establishment, every authority of a Member State where affected data subjects reside | Without undue delay and, where feasible, within 72 hours of becoming aware | GDPR Art. 33(1); EDPB Guidelines 9/2022, para 73 |
| A controller under the GDPR | The data subjects, where the breach is likely to result in a high risk | Without undue delay | GDPR Art. 34(1) |
| A processor under the FADP | The controller, of any breach of data security | As quickly as possible | FADP Art. 24(3) |
| A controller under the FADP | The FDPIC, of a breach likely to result in a high risk | As quickly as possible | FADP Art. 24 |
| A Data Fiduciary under the DPDP Act (from 13 May 2027) | The Data Protection Board of India and each affected Data Principal | Without delay; a detailed report to the Board within 72 hours of becoming aware | DPDP Act s.8(6); DPDP Rule 7 |
| A business that maintains data it does not own (California) | The owner or licensee of the data | Immediately following discovery | Cal. Civ. Code 1798.82(b) |
| An operator under POPIA | The responsible party | Immediately, on reasonable grounds to believe there was unauthorised access | POPIA s.21(2) |
| A service provider under Quebec’s private-sector Act | The enterprise’s person in charge of the protection of personal information, of any violation or attempted violation of confidentiality | Without delay | CQLR c. P-39.1, s.18.3 |
| A controller under Saudi Arabia’s PDPL | The competent authority | Within 72 hours of becoming aware | PDPL Implementing Regulation, Art. 24(1) |