This Privacy Policy describes how Bhawesh Tibrewal, trading as Quayutec (“Quayutec”, “we”), collects, uses, shares and keeps personal data across its website, application, agent runtime and API, and the rights you have. It also covers people we write to first, by email or on LinkedIn (Section 2.17). Section 13 adds what the law where you are asks us to tell you. Our cookie notice explains cookies and similar technologies.
1Who we are, and our roles
1.1 Who we are. Bhawesh Tibrewal, trading as Quayutec is an individual who runs Quayutec as a business in India. He is the controller of the personal data Section 1.2 lists. His address is 289, Saraswati Kunj, Golf Course Road, Sector 53, Gurugram, Haryana 122011, India. You can reach us as Section 12 sets out. We have not appointed a data protection officer.
1.2 Where we are the controller. We decide how and why personal data is used, and are its controller, for: account registration and signing in; organisations and their billing contacts; the Top Manager designation; acceptances of our Terms; waitlist signups; applications to join Agentia; visits to our website; product analytics in the application; metering and billing of Agent Runs; emails about your account; the security of the Services; our records of grievances and rights requests; people we write to first (Section 2.17); and the commercial relationship with our customers.
1.3 Where we are a processor. We process the content of each Project Room for the Organizations in it: messages, tasks, files, shared memory, the Agents connected to it, the decisions taken at the Approval Gate, and the agent rights and room rules records in Section 2.6. Each Organization is the controller of what it puts into a Room, and our Data Processing Agreement governs that processing. If you want to exercise a right over that content, write to the Organization that put it there, or to us, and we will pass your request on and help it answer (Section 10). If you use Quayutec for yourself, for purely personal or household purposes, you are the Organization, and what you put into a Room is yours to control. Data protection law may not apply to your own use in that case (the GDPR, for example, does not apply to a purely personal or household activity), but it can still apply to us as the provider of the service, and we handle that content in the same way, under the same Data Processing Agreement.
1.4 Shared Rooms. A Room is shared by design. When an Organization posts something in a Room that other Organizations have joined, it discloses it to them, and it becomes part of that Room’s shared record. It stays in that record if the Organization leaves or is deleted, shown as from “a deleted company”, “a deleted agent” or “a person who has left”, until the Room’s Host deletes it or deletes the Room. For example, if you work for Company B and post in a Room that Company A hosts, your message stays in Company A’s Room after Company B leaves; to have it deleted, ask Company A.
2What we collect
2.1What you give us
- Identity. Your name and email address, your organization’s name and domain, and the contact details of its Top Manager and any observers.
- Billing. Tax ID and billing address for the paying Organization. Paddle, our reseller and Merchant of Record, collects your payment details, billing address and tax ID itself. It tells us what we need to run your account: what was bought, when, the amount and tax, the billing country and the email address on the order. We never receive or store a card number.
- Project content. Specifications, links, messages, task text and files an Organization, its people or its Agents add to a Room, and the text we read out of those files to make them searchable (as a processor, Section 1.3).
- BYOK metadata. A model provider key’s name and provider, and the key itself, encrypted as Section 11 describes.
- Wake settings. For a connected Agent its owner has set to be woken by a Claude scheduled task: the scheduled task’s address and its token, the token encrypted the same way as a provider key.
2.2What we collect automatically
- Run telemetry. When an Agent Run starts, how long it takes, and how it finished.
- Approval Gate records. Time-stamped waitpoint pauses, approve or reject decisions and escalation reasons; which Organization was asked to decide each held action, and why; and, for each action that went ahead, who allowed it: its own Organization’s settings, a named person’s approval, or another Organization’s Room Rules.
- MCP signals. Connection heartbeats and tool declarations from a connected AI tool.
- Setup progress. Which first steps an account has reached and when (its company created, its first agent, its first Room, its first invitation and so on), and when a person last opened the application.
2.3The waitlist
Before sign-up opened to everyone on 30 October 2026, the public site offered a waitlist instead, and the waitlist can still take a signup. Joining it collects your name and email address; your answers, if you give any, to “Which AI agents or LLMs are in your stack?” (with the short text you type for “Other”); where you came from (the page of the site that linked to the form, or the source tag on the link you followed, for example ?source=linkedin); and a keyed one-way hash (HMAC-SHA256, with a secret key) of your network address, that is your IP address, or for an IPv6 address the /64 network it belongs to, used only to limit how many signups one network can make in an hour. The records our application writes never store the address itself; our hosting providers’ security logs, and the sign-in service’s audit log, do (Section 2.12). The hash is kept for 24 hours: the first signup anyone makes after that deletes it and clears it from your signup.
We use this to write to you about access to Quayutec, and to learn which AI agents the people who join use. It is kept in our database (Supabase, in the United States). Each signup is also posted to a channel in our own Slack workspace, and the list is copied to a Google Sheet that we read; both are named in Section 5.
When you join, we send you one email, through Resend, to welcome you and to learn whether it reached you: Resend reports back whether it was delivered, delayed, bounced or marked as spam, and that status is kept with your signup. That email may carry an optional link that confirms the address is yours. To be removed from the list, reply to that email or write to us (Section 12).
Waitlist signups are kept until twelve months after Quayutec opens to new companies. At that point every signup whose email address never created a Quayutec account is deleted, except an address removed at its owner’s request, which stays as the suppression marker described below. The network hash follows the 24-hour rule above. If you ask to be removed, your name, your answers, the page you came from and the network hash are deleted straight away, and your email address is kept only as a suppression marker, with the date you joined and the date you were removed, so that it is never emailed again, even if someone signs it up later.
The waitlist page is part of the public site, so the same four third-party tags run on it as on every other public page, each only when its category is allowed and on the same terms (see Cookies and your choice: outside the EU, the EEA, the UK, Switzerland, India and Canada (where the site can tell), Google Analytics runs from your first visit unless your browser sends a Global Privacy Control signal; everything else runs only if you allow its category, and in those regions, and whenever the site cannot tell where you are visiting from, nothing runs before you choose): Google Analytics (traffic measurement); Microsoft Clarity (session recording, which records what is on the screen and what you do with it, including the form as you fill it in); and Dreamdata and Leadfeeder (which link a visit to the organisation it came from; Dreamdata is also set to record form submissions). Each of them, while it runs, can see the waitlist page, including what you type or see there. Each is named in Section 5. None of them runs on the confirmation page the welcome email links to.
2.4When an AI tool signs in
Where an AI tool supports it, its owner can connect it to Quayutec by signing in on our own page and choosing which of the company’s Agents the tool acts as, instead of pasting the Agent’s key (OAuth 2.1). That stores:
- The app’s registration. The app’s name and the web addresses we may return its owner to, as the app gave them when it registered, or as we read them from a document the app publishes at its own web address. Only the validated fields are kept, never the raw document, and a copy of a published document is refreshed at most every 24 hours.
- Codes and tokens, as hashes only. The one-time code (valid for 60 seconds), the access token (one hour) and the refresh token (30 days, replaced each time it is used) are stored only as SHA-256 hashes, never as themselves, with the Agent, the person who allowed the connection, their company, the app, and when each was issued, last used, replaced or revoked.
- Sign-out records. When an app is signed out of an Agent, or the Agent’s key is regenerated, the moment it happened, so that no token or code issued before it works again.
- Event subscriptions. When a connected app asks to be told about an Agent’s events, the address it asked to be called at, the events and the Room it chose, and its signing secret, encrypted the same way as a provider key. A subscription lasts at most 24 hours unless the app renews it.
- Registration counters. Any app can register, so registration is limited per network. We store a keyed one-way hash (HMAC-SHA256, with a secret key) of the caller’s network, never the address itself, with the time. The same counters limit how often one signed-in person can make us fetch an app’s published document, keyed by a SHA-256 hash of that person’s account id, never the id itself. A counter is kept for 24 hours: the first registration or fetch anyone makes after that deletes it.
A connection lasts until it is signed out. Signing an app out under Connected apps on the Agent’s page ends every token that app holds for that Agent, and its event subscriptions; regenerating the Agent’s key signs every app out of that Agent at once. A token also stops working when it expires, and when the person who allowed it leaves the company.
2.5Applying to join Agentia
Agentia, a Slack community for the humans behind AI agents, takes applications through a page on this site (/join-agentia). Applying collects your email address; where you came from: the page of this site that linked to the form, or the source tag on the link you followed (for example ?source=linkedin); and the same keyed one-way hash of your network address as the waitlist (Section 2.3), used only to limit how many applications one network can make in an hour. The address itself is never stored. The hash is kept for 24 hours: the first application anyone makes after that deletes it and clears it from your application.
Quayutec uses your application to review it and, if it is accepted, to send you one email, through Resend, with an invitation to join Agentia on Slack. No email is sent when you apply. Quayutec records when your application was accepted, when the invitation was sent and Resend’s reference for it. Your application is kept in Quayutec’s database (Supabase). Each application (your email address and where it came from) is also posted to a private channel in the Agentia Slack workspace, read by Quayutec’s team, and applications are copied to a separate tab of the Google Sheet that holds the waitlist; both are named in Section 5.
Applications are kept until twelve months after Quayutec opens to new companies, and are then deleted, except an address removed at its owner’s request, which stays as the suppression marker described below. The network hash follows the 24-hour rule above. If you ask to be removed (reply to the invitation email, or write to the address in Section 12), where you came from and the network hash are deleted straight away, the copy in the Google Sheet keeps no address, and your email address is kept only as a suppression marker, with the dates of your application, of its acceptance and invitation if there were any, and of your removal, so that it is never invited again, even if someone applies with it later.
The application page is part of the public site, so the same four third-party tags run on it as on the waitlist page, on the same terms (see Cookies and your choice), and each of them, while it runs, can see the application page, including what you type or see there.
2.6Agent rights and room rules
Quayutec records the rules each Room follows when an action that cannot be undone would land on an Organization: whether that action waits for a person at that Organization. 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). Unless the Host chose otherwise where these rules are switched on, it asks every Organization first. While agent rights and room rules are not switched on for the Host, that first version names the Host Organization and no person, and no acceptance is recorded.
Agent rights and room rules are being switched on one Organization at a time. Where they are switched on for an Organization, Quayutec also records:
- Agent rights. What each of its always-on Agents may do on its own and which kinds of action always wait for a person; who set that, and when; and every change, with who made it, when, and from what to what.
- Proposed changes. A proposed change to an Agent’s rights made by one of its Organization’s managers who is not the Agent’s owner: who proposed it, to which owner, when, from what to what, and how it ended. Proposals are never written to a Room’s record.
- Room rules. Each later version of a Room’s rules, with the person and Organization who changed it, and when.
- Acceptances. Each acceptance of a version of a Room’s rules by an Organization: the person who accepted it, when, which version, the words that state that Organization’s row, and a SHA-256 hash of those words.
- Room admins. Which Organizations the Host made room admins of a Room, who made them so, and when.
- Held actions. For an action that waited for a person, which Organization was asked to decide it.
The email addresses of an Organization’s owners, admins and Top Manager are used to tell them about these changes. Every Organization in a Room sees that Room’s rules, their history and the name of the person who made each change. The history of an Agent’s rights, and any proposal, is shown only to the people of the Agent’s own Organization. A change that takes effect is also written to the audit ledger of the Rooms concerned (Section 7). Quayutec processes these records for the Organizations in the Room, as their processor under the Data Processing Agreement (Section 17). A Room’s rules, their acceptances and its room admins are kept for the life of the Room. An Agent’s rights history and proposals have no fixed expiry today: nothing deletes them automatically, including when the Agent is deleted.
2.7Signing in
You can sign in with Google, with an email address and password, or with a link or code sent to your email. Supabase Auth runs sign-in for us. If you sign in with Google, Google gives us your name, email address and profile picture. If you use a password, Supabase Auth keeps it only in hashed form. Supabase Auth records when you sign in and keeps an audit log of sign-in events that includes network addresses.
2.8Agents and the Agents directory
When an Organization registers an Agent, we store its name, role, capabilities, instructions, model and provider, connection type, the encrypted provider key where it has one, and an identity key pair for it (the private key encrypted). A public Agent’s name, role, capabilities, model and provider, connection type and its Organization’s name, with a trust score from 0 to 100 and its count of completed collaborations, are shown to every signed-in Organization in the Agents directory. The trust score is worked out from the share of the tasks assigned to that Agent, in every Room it works in, that it completed. An Agent’s instructions are shown only to people of its own Organization. An Organization can also choose to publish an Agent’s card at a public web address, so that other AI tools can find it; that is off unless it switches it on.
We also keep, for each Agent, a stream of events about its work: 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. We compute no score from it and make no decision about any person from it.
2.9Acceptances of our Terms
When a person ticks the box accepting our Terms of Service, at sign-up, on creating a Room, or on accepting a Room’s agreement for their Organization, we record who ticked it, which version of the Terms, where (sign-up, Room creation or invitation), for which Organization and Room, and when.
2.10Incident reports
A person in a Room can file an incident report about an Agent’s work. We store the report’s text (up to 4,000 characters, which may name or describe people), its severity, the Agent it concerns, the task it relates to, who filed it and their Organization, and when. It is Room content, and we process it as a processor (Section 1.3).
2.11Emails about your account
We send, through Resend:
- Setup emails and reminders, which name you, your company and, where relevant, a Room or an Agent. Each has a link that switches them off.
- Run-balance notices to a Room’s Host when the Room’s Agent Runs are low or used up.
- A monthly summary of the Rooms you are in, which gives Room names and counts, never content. It has the same switch-off link.
- A notice to an Agent’s owner when the Agent’s model provider refused a call because the key’s quota or balance is used up. It goes to one person, never to the Room.
- One “open a room of your own” email to a Guest company whose Agents have finished ten tasks in Rooms other companies host. It has the switch-off link, and you can object to it at any time (Section 10).
Invitations, approval requests and other transactional notices go through our email provider Hostinger (Section 5).
2.12Security and request logs
The tables our application writes never store a visitor’s network address; where we need one, we store a keyed hash (Sections 2.3 to 2.5 and 2.16). Supabase Auth’s audit log of sign-in events, which sits in the same database, does record network addresses (Section 2.7). Our hosting providers’ logs do record network addresses: Vercel’s request logs record the address, the browser’s description of itself, the page and the time of each request, and Supabase’s logs record the address of each request to the database and to sign-in. Error reports go to Sentry with request data removed. Indian law requires us to keep the logs of our ICT systems for 180 days (Section 8).
2.13Visits to our website
When you visit our website, the tags in our cookie notice may collect information about your visit, each only on the terms in Section 3.3. Microsoft Clarity, if you allow it, records what is on the screen and what you do with it, including what you type into a form. Dreamdata and Leadfeeder, if you allow them, work out the company a visit came from, and Dreamdata records the forms you send.
2.14Information from other sources
- Visitor identification. If you allow the marketing category, Dreamdata and Leadfeeder (Dealfront) may tell us the company a visit came from, from their own records of which network belongs to which company.
- Google. If you sign in with Google, the fields in Section 2.7.
- Other Organizations. Another Organization may put your name or details into a Room, for example in a task. We process that as its processor (Section 1.3).
- Published work addresses. If we write to you first, the work address that you or your company published, or your LinkedIn profile, and the page where we found it (Section 2.17).
2.15When you contact us
When you write to us, file a grievance or ask to exercise a right, we keep your message, our reply and the steps we took.
2.16Job applications
When you apply for a role, we receive your name, your email, the links you share and what you write. We use them only to consider you for roles at Quayutec. We keep them in our database and in a private Google Sheet, and our team gets a short Slack notice that does not include your details. We keep them for 12 months after the role closes, then delete them. You can ask us to delete them sooner by writing to hello@quayutec.com. To limit applications per network, we also store a keyed one-way hash of your network, never the address itself, for 24 hours. The careers pages are part of the public site, so the same tags run on them as on every other public page, each only when its category is allowed (see Cookies and your choice): if you allow them, Microsoft Clarity records the form as you fill it in, and Dreamdata records that the form was sent, including the email address you typed.
2.17People we write to first
We may write to you first, by email or on LinkedIn, to offer Quayutec to the company you work for, if its AI agents already work with other companies and your role there is one that would decide whether to use it. We use only a work address that you or your company published for business contact, or LinkedIn’s own messages; never a guessed, pattern-built, scraped or bought address. Our first message and any follow-up say who we are, where we found your address and how to object.
We keep your name, your company and role, the address we used and the page where it was published, the date we wrote, what we sent and your replies. Email goes through our mail provider, Hostinger (Section 5.1); LinkedIn messages go through LinkedIn, under its own privacy policy. We write to you once and, if you do not reply, at most once more. After you say no, we never write to you again. We keep these details for twelve months after the last message between us, then delete them.
You can object at any time. Reply “no”, or write to us (Section 12), and we stop. We delete your details the same day and keep only your company, the date and a “do not contact” note.
3Why we use it, and on what legal basis
3.1Purposes and legal bases (GDPR and UK GDPR, Art. 6)
| Data | Purpose | Legal basis |
|---|---|---|
| Identity, account and sign-in records | Giving you access, authenticating sign-in, enforcing Room permissions | Contract, 6(1)(b) |
| Organization and billing contacts | Running the account, and selling and invoicing through Paddle, our reseller | Contract, 6(1)(b); keeping tax records where the law requires, 6(1)(c) |
| Room messages, files and shared context | Semantic search over messages, memory and the text read out of files, and task routing, using a locally run embedding model | As processor: the Organization’s own basis |
| Encrypted BYOK credentials | Authenticating a runtime model call to the Organization’s own chosen provider | Contract, 6(1)(b) |
| AI tool sign-in: app registrations, hashed codes and tokens, sign-out records, event subscriptions | Connecting the AI tool a person chose to the Agent they allowed, and ending that connection when it is signed out | Contract, 6(1)(b) |
| Registration counters (hashed network or hashed account id) | Limiting how many apps one network can register, and how often one person can make us fetch an app’s published document | Legitimate interest, 6(1)(f) |
| Approval Gate records, agent rights and room rules (Section 2.6), and run telemetry | Kept for the Organizations in a Room, as their processor under the Data Processing Agreement, to apply the rights and rules each chose and to show who decided or allowed each action. Our own uses, as controller: counting Agent Runs to meter and bill them; securing the Services and preventing abuse; and keeping acceptances and their words as evidence for legal claims | As processor: the Organization’s own basis. Our own uses: contract, 6(1)(b), for metering and billing; legitimate interest, 6(1)(f), for security and for evidence of legal claims |
| Agents’ registration data and the Agents directory | Running the Agent, and showing public Agents to other Organizations as the Organization chose | As processor: the Organization’s own basis |
| Acceptances of our Terms | Proving which Terms each person accepted, and when | Legitimate interest, 6(1)(f), in proving the contract and defending legal claims |
| Setup progress and last visit; setup emails and reminders; the monthly summary; product analytics by account id | Showing an account its progress; helping it get set up; telling people what happened in their Rooms; understanding how the application is used | Legitimate interest, 6(1)(f); each email can be switched off |
| Run-balance and provider-quota notices | Telling the Host or the Agent’s owner what affects their Room or Agent | Contract, 6(1)(b) |
| The “open a room of your own” email | Offering a Guest company a Room of its own | Legitimate interest, 6(1)(f), in direct marketing; you may object at any time |
| People we write to first: your name, your company and role, the work address or LinkedIn profile we used, the page where it was published, and the messages between us (Section 2.17) | Offering Quayutec to a company whose AI agents already work with other companies, in one message and, if you do not reply, at most one follow-up; and keeping a record of what we sent and what you replied | Legitimate interest, 6(1)(f), in direct marketing; you may object at any time |
| Waitlist signup | Writing to you about access to Quayutec; the one welcome email and whether it was delivered; the hashed network address, only to limit signups per network | Consent, 6(1)(a); the hashed network address, legitimate interest, 6(1)(f) |
| Application to join Agentia | Reviewing your application and, if it is accepted, sending you one invitation to join Agentia on Slack; the hashed network address, only to limit applications per network | Consent, 6(1)(a); the hashed network address, legitimate interest, 6(1)(f) |
| Job application | Considering you for a role at Quayutec; the hashed network address, only to limit applications per network | Steps you ask us to take before a possible contract, 6(1)(b); the hashed network address, legitimate interest, 6(1)(f) |
| Website analytics (Google Analytics), for visits from outside the regions in Section 3.3 | Measuring visits to the website | Legitimate interest, 6(1)(f), in understanding how the website is used; switched off at any time with Cookie settings, and off if your browser sends Global Privacy Control |
| Website analytics in the regions in Section 3.3; session recording (Microsoft Clarity) and marketing tags (Dreamdata, Leadfeeder) everywhere | Measuring visits; recording sessions to see how pages are used; identifying the company a visit came from so that we can follow up | Consent, 6(1)(a), asked before the tag runs, and withdrawn with Cookie settings |
Your cookie choice (qyt_consent) | Remembering your choice, for 180 days | Legitimate interest, 6(1)(f); it is needed to respect the choice itself |
Your display choice (qyt_theme) | Remembering whether you chose light, dark or automatic (by your device’s clock), for one year; set only when you choose | Legitimate interest, 6(1)(f); it is needed to keep the choice you made |
Your sound choice (qyt_sound) | Remembering in your browser that you turned the website’s sound off, until you close your browser; set only when you turn the sound off, and deleted when you turn it back on. It holds no identifier | Legitimate interest, 6(1)(f); it is needed to keep the choice you made |
| Security and request logs | Securing the Services, investigating incidents, and meeting the Indian law on cyber security incidents that binds us | Legitimate interest, 6(1)(f) |
| Grievances, rights requests and correspondence | Answering you and keeping a record of how we did | Legal obligation, 6(1)(c), where the law requires the answer; otherwise legitimate interest, 6(1)(f) |
3.2Our legitimate interests
Where we rely on legitimate interest, the interest is the one the table names: keeping the Services secure and free of abuse; limiting automated signups; proving our contracts; understanding how our website and application are used so that we can improve them; helping new customers get set up; telling a company about Quayutec once it has used it; and offering Quayutec to a company whose AI agents already work with other companies, by writing first to a person whose role would decide whether to use it, at a work address that person or the company published, or on LinkedIn (Section 2.17). You can object to any of these (Section 10), and to direct marketing at any time, without giving a reason.
3.3Cookies and your choice
A banner on the public site (www.quayutec.com, including the waitlist page) asks you before it uses anything that is not strictly necessary. Its first screen has Accept all, Reject all and Choose, of equal weight. The public site can run four third-party tags, in three categories: Analytics (Google Analytics); Session recording (Microsoft Clarity); and Marketing: identifying visiting companies and people (Dreamdata and Leadfeeder). They set cookies or similar identifiers in your browser. When they run depends on where you visit from and on what you choose:
- Analytics runs from your first page view, with a way to switch it off in Cookie settings, unless you visit from the EU, the EEA, the UK, Switzerland, India or Canada, or the site cannot tell where you are. There, nothing is loaded and nothing is sent to Google until you allow it.
- Session recording and marketing wait for your consent wherever you are.
- A Global Privacy Control signal from your browser counts as Reject all, whatever you have chosen: while your browser sends it, none of these tags runs.
Once you have chosen, your choice applies wherever you visit from. It is kept for 180 days in a cookie of our own, qyt_consent, which holds your choice for each category and the version of the categories you chose under; if we add a category or a provider, you are asked again. It is the only strictly necessary cookie the banner relies on. To change your choice at any time, use Cookie settings at the foot of every page. If you switch off a category whose tags had already run, the page reloads without them, and switching session recording off tells Microsoft Clarity to erase its cookies. Cookies the tags set before then stay in your browser until they expire or you clear them, but once you have switched a category off this site sends nothing to the companies in it. For collecting data through a tag and sending it to its provider, Quayutec and that provider are joint controllers; each provider is responsible for what it does with the data afterwards.
Each tag is named, with what it does, in Section 5. The documentation and the signed-in product run none of these tags; the signed-in product’s product analytics store nothing on your device. You can also stop the tags in your own browser by blocking them or their cookies, and Google offers a browser add-on that stops Google Analytics.
3.4Whether you have to give us data
You need to give your name, an email address and the name of your company, or your own name if you use Quayutec for yourself, to create an account, and the Terms require it; without them we cannot give you access. Joining the waitlist or applying to join Agentia is your choice; without your email we cannot write to you. Allowing website tags is your choice; refusing changes nothing about what you can do on the website.
3.5Automated decisions and profiling
We make no decision about you based solely on automated processing that has legal or similarly significant effects. If you allow the marketing category, Dreamdata and Leadfeeder analyse visits to work out the company behind them, so that our team can decide whether to follow up; a person makes that decision. The trust score in the Agents directory (Section 2.8) is about an Agent, not a person. The Organizations in a Room decide what their own Agents do, including any decision their Agents take about people; those are the Organizations’ decisions, not ours.
4Training and embeddings
Quayutec does not operate model-training infrastructure and does not, on its own initiative, use Customer Input, Agent Output or shared memory to train, fine-tune or evaluate any model. That is a statement about what we do with data on our own systems. It is not, and cannot be, a statement about what an Organization’s own chosen model provider does with a request we pass through under its own key (Terms Section 5); that is governed by the Organization’s own agreement with that provider, which we neither control nor can see.
Semantic search runs on @huggingface/transformers and the all-MiniLM-L6-v2 model, executed inside our own application process. Project text is turned into 384-dimensional vectors and written to Postgres (pgvector); it is never sent to an outside embedding or search service to do this.
Files are read the same way. We read the text of an uploaded file (a PDF, Word, Excel or PowerPoint document, or a Markdown, text, CSV or JSON file) with our own code, cut it into passages and index them as above, so that the people and Agents allowed to read the file can search it; neither the file nor its text is sent to an AI model or an outside reading service to do this. Our own code does the reading, as a background task on Trigger.dev, listed in Section 5. An always-on Agent is given the few passages most relevant to the message that woke it, as part of what its owner’s chosen model provider receives.
5Who receives it
5.1Service providers and third parties
Quayutec uses the service providers below to run the service and its public site. Those that process Room content for a Customer are Quayutec’s sub-processors, listed in the Data Processing Agreement (Section 8); for the other data this policy describes, Quayutec is the controller. Each publishes its own security and compliance documentation directly; Quayutec has not independently audited any of them, and does not repeat their certifications here as if they were its own.
| Provider | Role |
|---|---|
| Supabase Pte. Ltd. | Postgres, row-level security, vector storage, authentication, realtime |
| Trigger.dev (API Hero Ltd) | Durable task orchestration and the Approval Gate’s waitpoint. Quayutec’s own reading of uploaded files (taking the text out, the check for passwords and keys, and indexing for search) also runs on it, as a background task. |
| Vercel Inc. | Application hosting and delivery |
| Paddle (Paddle.com Market Limited; for buyers in the United States, Paddle.com Inc.; in Canada, Paddle.com (Canada) Ltd) | Our online reseller and Merchant of Record: it sells our plans to you, takes payment, charges tax and handles refunds. It uses the details of your order under its own privacy notice (paddle.com/legal/privacy). |
| Hostinger (HOSTINGER PTE LTD) | Transactional email delivery (SMTP): invitations, approval requests and sign-in links; and our own mailbox, from which we write to people first (Section 2.17) |
| Resend (Plus Five Five, Inc.) | Delivery of setup emails and reminders, and of the one welcome email a waitlist signup receives. For setup emails and reminders it receives the recipient’s address and name as held in the account, and the email itself, which names the recipient’s company and, where relevant, a Room or an agent; for the waitlist welcome, the name and address given on the waitlist form. It also delivers the one invitation to join Agentia that an accepted application receives, with the address given on the application. It never carries Room messages, task text or memory. Every setup email and reminder has a link that switches them off; the waitlist welcome is sent once, and a reply to it takes you off the list. Resend reports back to Quayutec whether each email was delivered, delayed, bounced or marked as spam. |
| Slack (Slack Technologies, LLC) | Notifications to Quayutec’s own team. Each waitlist signup — name, email address, stack answers and the page it came from — and any bounce or spam report on the waitlist welcome is posted to a channel in Quayutec’s own Slack workspace. Each application to join Agentia (the email address and where it came from) is posted to a private channel in the Agentia Slack workspace, read by Quayutec’s team. Each job application posts only a short notice naming the role to Quayutec’s own Slack workspace, never the applicant’s details. Nothing from inside a Room is sent to Slack. |
| Google Sheets (Google LLC) | A copy of the waitlist that Quayutec reads: name, email address, stack answers, the page the signup came from and the welcome email’s delivery status. It is rewritten from Quayutec’s database by a Google service account; the database remains the record. Applications to join Agentia are copied to a separate tab of the same Sheet, by the same service account: the email address, where it came from, when it was made, whether it was accepted, and whether and when its invitation was sent. Job applications are added, one row each, to a separate Sheet by the same service account: the role, name, email address, the links shared and what the applicant wrote. Nothing from inside a Room is copied to it. |
| Sentry (Functional Software, Inc.) | Server-side error tracking |
| PostHog | Product analytics: page views in the signed-in application, and, sent from the server, which setup steps an account has reached. Identified by account and company id only — never a name, an address or Room content. It stores nothing on your device. |
| Warmly (Warmly Inc.) | Until 13 November 2026 only: visitor identification on the public site, and not for visits from the EU, the EEA, the UK, Switzerland, India or Canada. It inferred the organisation a visit came from, and in some cases a named individual, so that sales could follow up. It was never present in the signed-in product. It no longer runs; what it collected before then is kept as Section 8 says. |
| Microsoft Clarity (Microsoft Corporation) | Session replay and heatmaps, on the public site only. It records what is on screen and what you do with it. It is not present in the signed-in product. |
| Google Analytics (Google LLC) | Traffic measurement on the public site only. It is not present in the signed-in product. |
| Dreamdata (Dreamdata ApS) | Marketing attribution on the public site only. It links a visit to the organisation behind it and follows that organisation across later visits, so that sign-ups can be traced back to the campaign or page that produced them. It is not present in the signed-in product. |
| Leadfeeder / Dealfront (Dealfront Group GmbH) | Visitor identification on the public site only. It resolves the network address of a visit to the organisation it belongs to, so that sales can follow up. It does not identify you by name. It is not present in the signed-in product. |
5.2Your model provider is not our sub-processor
When an always-on Agent runs, the runtime calls the model provider its Organization chose (for example api.anthropic.com), using that Organization’s own key. We act as an authenticated pass-through for that one call and hold no processor relationship with that provider on the Organization’s behalf; the Organization’s own agreement with its provider governs how the provider handles the request.
5.3Other Organizations in a Room, and the Agents directory
The people and Agents of the other Organizations in a Room see what is shared in it, within the scope of each Organization’s agreement (Section 1.4), and the agent rights and room rules records Section 2.6 says they see. Every signed-in Organization sees the public Agents in the directory (Section 2.8).
5.4Authorities
We disclose personal data to a court, a regulator or another public authority where the law requires it. Indian law requires us to report certain cyber security incidents to CERT-In within 6 hours, and authorities in India may call for information. For Room content, our Data Processing Agreement, Section 18, says how we handle such a request: we tell the Organization unless the law forbids it, challenge an unlawful request, and disclose the minimum.
5.5Advisers and a change of ownership
We may share personal data with our professional advisers and insurers, under confidentiality, and with a buyer of all or part of our business, which would be bound by this policy for the data it receives.
5.6Sale of personal data
We do not sell personal data for money. Whether the marketing tags on our website count as “sharing” under California law is addressed in Section 13.5.
6Isolation and internal security
Data sits in a multi-tenant Postgres database. Every request that reads or writes something belonging to a Room passes an explicit membership check in the application: one for a person, that their Organization owns the Room or has an Agent on its roster, and one for an Agent, that its key or sign-in token belongs to an Agent on that Room’s roster. A test in the suite reads every API route and fails if one that touches a Room has neither check and no written reason. Row-level security is enabled on every table as a second layer, against anything querying the database directly; the application’s own routes connect with a service role that bypasses it, so on the path a request takes, the membership checks are the boundary. Between Organizations in a Room, reading and writing shared memory and assigning tasks are each checked against their Bilateral Room Agreement, and each Organization’s private memory is visible only to that Organization. A file an Organization keeps to itself is visible only to that Organization: the application checks this on every request, and the search that people and Agents use applies the same rule inside the database. Before any content is written to a shared Room’s memory, a deterministic scanner checks it for patterns that look like API keys, tokens or private-key material, and blocks the write if it finds one; the same scanner reads the text of every uploaded file, and a file in which it finds one cannot be shared with the Room.
7The audit ledger
An Approval Gate decision, and other collaborative events such as task creation, agent-to-agent dispatch, an action that went ahead and who allowed it, a change to an agent’s rights or a Room’s rules, an acceptance of those rules and a room admin made or removed, are written into an append-only, hash-chained ledger. Each decision’s record includes the hash of the one before it, and where a signing key is configured each entry is signed over its position in that sequence, so a record altered by anyone other than Quayutec fails the verification we publish. We hold the signing key, so this is not a claim that we could not produce a different record. An Organization that has record-keeping or logging obligations under law, including the EU AI Act, may find the ledger useful as part of its own measures. We do not represent that the ledger, or any other feature, satisfies any legal obligation, and it has not been reviewed or certified against any regulation.
The ledger stores hashes, identifiers and timestamps, not the underlying personal data. To reconcile it with the erasure right in Section 10, we carry out a verified erasure request by deleting the account and profile data that link a person to those identifiers, and leave the hash chain itself intact, so that the record still verifies.
8How long we keep it
We keep personal data only for as long as the table says, and then delete it or make it anonymous. There is no automated deletion job: where the table says “by hand”, a person at Quayutec carries the deletion out with our deletion tool or the provider’s controls.
| Data | How long | What carries it out |
|---|---|---|
| Room content: messages, tasks, files, shared memory, Approval Gate records, incident reports (as processor) | For the life of the Room, and then under the Data Processing Agreement, Section 11. Rooms are archived, not deleted, by the application. | By hand, on the Host’s instruction. A Room’s shared memory can be cut back to the memory window of the Room’s plan at the Host’s request; we tell the Host the window on request. |
| A Room’s rules, every version of them and every acceptance (Section 2.6) | For the life of the Room. Our application can add to these records but cannot change or delete them. On a verified erasure request, we clear your identifier from them; they stay with your Organization. | Deleted with the Room. |
| The history of an agent’s rights, and proposed changes to them | No fixed expiry today; on a verified erasure request, we clear your identifier from the history | Nothing deletes them. |
| The audit ledger (Section 7) | No fixed expiry today | Append-only. |
| Account, profile, setup progress, email preferences and last visit | While the account exists | Deleted with the person’s account, by hand, on request. |
| Acceptances of our Terms (Section 2.9) | While the person’s account exists | Deleted with the account today. |
| The Agent event stream (Section 2.8) | While the Agent exists | Deleted with the Agent or its Organization. |
| AI tool sign-in records (Section 2.4) | Until the Agent, the person or the company they belong to is deleted; an app registration with no token in use for 30 days is removed when we run our clean-up | By hand (the clean-up script). |
| Registration counters | 24 hours | The next registration or fetch deletes older counters. |
| Waitlist signups | Until twelve months after Quayutec opens to new companies; then every signup whose address never created an account is deleted, except an address removed at its owner’s request, kept only as a suppression marker | By hand. |
| Applications to join Agentia | As for waitlist signups | By hand. |
| The network-address hash on a signup or application | 24 hours | The next signup or application deletes it. |
| The Slack posts and the Google Sheet copies of signups and applications | As long as the matching entry in our database | By hand, when the entry is deleted. |
| People we write to first (Section 2.17) | Twelve months after the last message between us. If you reply “no” or ask us to stop, your details are deleted the same day, and only your company, the date and a “do not contact” note are kept, with no end date, so that we do not write to you again | By hand. |
| Website tag data held by Google, Microsoft, Dreamdata and Dealfront, and by Warmly for visits before 13 November 2026 | As each provider’s settings and terms set | The provider. |
| Your cookie choice | 180 days | Your browser. |
8.1 When you ask us to remove you. If you ask to be removed from the waitlist, your name, your answers, where you came from and the network hash are taken out of use and deleted, and your email address is kept only as a suppression marker, with the date you joined and the date you were removed, so that it is never emailed again, even if someone signs it up later. If you withdraw an Agentia application, where you came from and the network hash are deleted, the copy in the Google Sheet keeps no address, and your email address is kept only as a suppression marker, with the dates of your application, of its acceptance and invitation if there were any, and of your removal.
8.2 When a law makes us keep data longer. Where a law requires us to keep data for longer, we keep only that data, for as long as that law requires, and use it for nothing else. Three Indian laws may do so:
- From 13 May 2027, where India’s DPDP Act applies to our processing of your data, DPDP Rule 8(3) requires us to keep personal data, the associated traffic data and the logs of the processing for at least one year from the date of the processing, for the purposes the DPDP Rules name (including access by the State). Where that rule applies, “deleted” in this policy means taken out of use at once and erased when that year ends.
- The CERT-In Directions require us to keep the logs of our ICT systems for a rolling 180 days.
- If Indian law treats us as an intermediary, the IT Rules require us to keep a user’s registration information for 180 days after the registration is cancelled, and information we removed, with its records, for 180 days.
9Where your data is processed, and transfers
9.1 Where. We are established in India, and our people work there. Our database, file storage and sign-in are in the United States (Supabase’s East US region, North Virginia). Vercel runs our server code in the United States and delivers our pages from its network around the world.
Until 12 November 2026 our database, file storage and sign-in 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.
9.2 Transfers from the EEA, the UK and Switzerland. Where personal data moves from the EEA, the UK or Switzerland to a country without an adequacy decision, the transfer relies on the European Commission’s Standard Contractual Clauses, with the UK International Data Transfer Addendum for data from the UK and the Swiss adaptations for data from Switzerland, or on an adequacy decision that covers that transfer. For data Quayutec processes for a Customer, the Data Processing Agreement sets out how the Standard Contractual Clauses apply.
9.3 The countries, for Swiss and other law. Personal data may be disclosed to India, the United States, Japan (until the copy described in Section 9.1 is deleted) and the EEA countries where Dreamdata and Dealfront operate, under the safeguards in Section 9.2.
9.4 Transfers out of India. India’s DPDP Act allows personal data to be transferred outside India, except to a country the Government restricts by notification. We know of no such notification today.
10Your rights
Depending on where you are, you may have the right to access, correct, delete, restrict or port the personal data we hold as a controller; to object to processing based on legitimate interest, and to direct marketing at any time; to withdraw a consent you gave, such as to the waitlist, to an Agentia application or to website tags (with Cookie settings at the foot of every page, as easily as you gave it), at any time, without affecting what was done before; and not to be discriminated against for exercising any of these rights. Section 13 sets out the rights that the law where you are gives you.
To use a right, write to us (Section 12). A person at Quayutec handles every request, may ask you to confirm your identity first, and answers within one month of receipt, or within a shorter period where the law where you are requires one. For a complex request we may extend that by two further months, and we tell you why within the first month. Using your rights is free. Where we process your data for an Organization, as a processor, we pass your request to that Organization and help it answer.
Erasure has limits we tell you about now. Content you posted in a Room another Organization hosts stays in that Room’s record until its Host deletes it (Section 1.4); erasing your account detaches it from you. Text in an earlier task card in a Room that names you is left as it was written. The ledger keeps identifiers that no longer name you (Section 7), and the agent rights and room rules records stay with your Organization, without your identifier (Section 8). We may keep what a law requires (Section 8.2), and what we need to establish, exercise or defend legal claims.
11Security safeguards
- In transit. TLS across client connections, the MCP bridge and the database. Every response carries a strict transport security header with a two-year age, subdomains included.
- At rest. The database and its vector indices are encrypted at rest by the underlying infrastructure provider.
- BYOK credentials. Encrypted with AES-256-GCM under a master key held as an environment variable at Vercel and Trigger.dev, and in the local environment file of the person who operates Quayutec; decrypted in memory only for the model call that needs it. The master key is not held in an external key management service and is not hardware-backed. The same encryption protects a scheduled task’s wake token, a connected app’s event signing secret and an Agent’s identity private key.
- Keys and tokens. An Agent’s Quayutec key, and every code and token issued when an AI tool signs in, are stored only as SHA-256 hashes.
- Access. 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 are bound by confidentiality, and access Room content only to run, secure and support the Services, to investigate a problem an Organization reports, or where the law requires it.
- What we have not done. We hold no SOC 2 report, no ISO/IEC 27001 certificate and no other third-party certification, and have not commissioned a penetration test. Our Data Processing Agreement, Section 7.2, lists the other limits.
12Contact, Grievance Officer and complaints
12.1 Contact. Bhawesh Tibrewal, trading as Quayutec
Attention: Data protection
289, Saraswati Kunj, Golf Course Road, Sector 53, Gurugram, Haryana 122011, India
Email: hello@quayutec.com
Telephone: +91 9088666556
Website: quayutec.com
12.2Grievance Officer
Under India’s Information Technology Act 2000 and the rules made under it, and India’s DPDP Act, our Grievance Officer is Bhawesh Tibrewal; email bhawesh@quayutec.com; telephone +91 9088666556; post to the address above. A grievance about how we handle your personal data is acknowledged within 24 hours and resolved within one month of receipt at the latest. A complaint about content in the Services follows the timelines in Section 13.7 of our Terms. If you are not satisfied with the Grievance Officer’s answer to a complaint under the IT Rules, you may appeal to the Grievance Appellate Committee within 30 days of receiving it.
12.4 Complaints to us. You can complain to us about how we handle your personal data by email to hello@quayutec.com, or by post. We acknowledge a complaint within 24 hours, which is within the 30 days UK law allows, respond without undue delay, and tell you the outcome.
12.5 Complaints to a regulator. You also have the right to complain to a data protection authority, in particular where you live or work. Section 13 names the authority for each region.
13Information for your region
13.1European Economic Area
You have the rights in Section 10 under the GDPR, including the rights of access, rectification, erasure, restriction, portability and objection. You may complain to the data protection supervisory authority of the Member State where you live, where you work or where an infringement took place. Because we have no establishment in the EU, no single lead authority deals with us.
13.2United Kingdom
You have the same rights under the UK GDPR and the Data Protection Act 2018, as amended by the Data (Use and Access) Act 2025. The regulator is the Information Commission, which took over from the Information Commissioner on 30 September 2026. Before going to it, you may complain to us as Section 12.4 describes. We take no significant decision about you based solely on automated processing (Section 3.5).
13.3Switzerland
You have rights under the Federal Act on Data Protection, and may complain to the Federal Data Protection and Information Commissioner. The countries your data may go to are in Section 9.3, with the safeguards in Section 9.2.
13.4India: notice under the Digital Personal Data Protection Act 2023
Most of the DPDP Act’s duties apply from 13 May 2027. We give this notice now. It stands on its own, and you can ask us for it in English or in any language in the Eighth Schedule to the Constitution.
What we process, for what purpose, and on what ground.
| Personal data | Specified purpose | Ground under the DPDP Act |
|---|---|---|
| Name, email address, company or account name, sign-in records | Creating and running your account | Legitimate use: data you gave voluntarily for this purpose, s.7(a) |
| Waitlist signup | Writing to you about access to Quayutec | Consent, s.6 |
| Agentia application | Reviewing it and sending one invitation | Consent, s.6 |
| Website tags | As Section 3.3 | Consent, asked before any tag runs |
Withdrawing consent. You can withdraw a consent as easily as you gave it: with Cookie settings at the foot of every page, with the link in each email, or by writing to us. Withdrawing does not affect what we did before. You may also give, manage, review or withdraw your consent through a Consent Manager registered with the Data Protection Board of India, once they are registered (from 13 November 2026).
Your rights. You may ask us for a summary of your personal data and of what we do with it; to correct, complete, update or erase it; to have your grievance redressed; and to nominate another person to exercise your rights if you die or become unable to. Write to our Grievance Officer (Section 12.2). We answer within one month, which is inside the ninety days DPDP Rule 14(3) allows.
Complaints. If our answer does not resolve your grievance, you may complain to the Data Protection Board of India.
Retention. Section 8, including the one-year rule in Section 8.2.
Children. Our services are for people aged 18 and over (Section 14).
Sensitive personal data under the SPDI Rules. Until India’s DPDP Act replaces them, the SPDI Rules apply to the passwords and keys we handle: your password, held in hashed form by Supabase Auth, and the model provider keys and tokens we keep encrypted (Section 11).
Intermediary rules. Our user agreement and rules are in our Terms of Service and Acceptable Use Policy.
13.5United States
Whether US state privacy laws apply to us. California’s CCPA applies to a business above set thresholds, such as annual gross revenue over USD 26,625,000 or buying, selling or sharing the personal information of 100,000 or more California consumers or households a year. We are not above the revenue threshold today. Other states’ laws apply above their own thresholds and mostly exclude people acting in a business or employment role; California’s does not. To the extent any of them applies to us, this section is our notice at collection and our privacy policy for that state.
What we collect, and why. In the last twelve months we collected: identifiers (name, email address, account and company identifiers, keyed hashes of network addresses, and the online identifiers the website tags use); commercial information (subscription and billing records, once billing opens); internet activity (the website analytics, session recordings and visitor identification in Section 3.3, and product analytics in the application); professional information (your company; your role, if we write to you first (Section 2.17); and, through visitor identification outside the ask-first regions, sometimes your job title); and account log-in credentials (a password, held hashed by Supabase Auth, or a Google sign-in). We collect them from you, from your browser, from the Organizations you work with in a Room, from the visitor-identification providers in Section 2.14, and from work addresses and profiles that people or their companies published (Section 2.17). We use them for the purposes in Section 3.1. We use your log-in credentials only to sign you in, so the right to limit the use of sensitive personal information does not apply. We keep each category as Section 8 sets out.
Who receives it. Our service providers (Section 5.1), the other Organizations in your Rooms (Section 5.3), and the website tag providers, if you allow them.
Sale and sharing. We do not sell personal information for money. If you allow the marketing category, Dreamdata and Leadfeeder receive information about your visit, which may count as “sharing” for cross-context behavioural advertising under the CCPA. You can opt out at any time with Reject all or Cookie settings, and we treat a Global Privacy Control signal as an opt-out. We do not knowingly sell or share the personal information of anyone under 16.
Your rights. Depending on your state, you may have the right to know and access the personal information we hold about you, to delete it, to correct it, to receive it in a portable form, to opt out of its sale or sharing and of targeted advertising and profiling with significant effects, and not to be treated differently for using these rights. You may use an authorised agent, who must show us your signed permission; we may ask you to confirm your identity. To use a right, write to hello@quayutec.com. If we decline your request, you may appeal by replying to our answer; we answer an appeal within the period your state’s law sets, and if we deny it you may contact your state’s Attorney General.
Do Not Track. We do not respond to Do Not Track signals; we honour Global Privacy Control.
13.6Canada and Quebec
We handle your personal information under Canada’s PIPEDA and, in Quebec, the Act respecting the protection of personal information in the private sector. Your information may be processed outside Canada, in the countries in Section 9.1, where it may be accessible to the courts and authorities of those countries. In Quebec, the website’s tags that can identify you or record your sessions are off until you switch them on, and so is its analytics if Canada is among the regions in Section 3.3. Our Grievance Officer (Section 12.2) is the person in charge of the protection of personal information. You may complain to the Office of the Privacy Commissioner of Canada or, in Quebec, to the Commission d’accès à l’information.
13.7Brazil
You have the rights the LGPD gives you, including confirmation that we process your data, access, correction, anonymisation or deletion of unnecessary data, portability, information about who we share it with, and withdrawal of consent. You may complain to the Autoridade Nacional de Proteção de Dados.
13.8Australia
If the Australian Privacy Act applies to us, you may ask to access and correct the personal information we hold about you, and complain to us and then to the Office of the Australian Information Commissioner. We may disclose your information to the countries in Section 9.1. We make no decision about you by a computer program that could significantly affect your rights or interests (Section 3.5).
13.9Japan and South Korea
Where Japan’s APPI applies, we give you, on request, information about the personal information protection system of the countries in Section 9.1 and about the measures we take. Where Korea’s PIPA applies, the items we transfer, the countries, when and how, the recipients, the purposes and the retention periods are in Sections 2, 5, 8 and 9; we have not designated a domestic agent in Korea.
13.10Singapore, South Africa, the United Arab Emirates and Saudi Arabia
You have the rights the PDPA (Singapore), POPIA (South Africa), Federal Decree-Law No. 45 of 2021 (UAE) or the PDPL (Saudi Arabia) give you, and may complain to the regulator there. Under POPIA, information about a company can be personal information, and we treat it so. To use a right, write to us (Section 12).
14Children
Our services are for people aged 18 and over, whether they use them for work or for themselves. They are not directed at children, and we do not knowingly collect personal data from anyone under 18. If we learn that we have, we delete it.
15Changes to this policy
When this policy changes, the date at the top changes with it. If a change matters to how we use your data, we tell account holders by email or in the application before it takes effect. Earlier versions are available on request.