The agreement
behind your account.

1. These Terms of Use (the “Terms”) form a binding agreement between the operator of Relay (“Relay”, “we”, “us”) and the person or organisation using the service (“you”). They govern your access to and use of the Relay website, application, APIs, and everything we provide through them (together, the “Service”).

   Relay is an independent product in beta and is not currently operated through an incorporated company. It is run by its individual operator, who is the counterparty to these Terms and is contactable at relayapphq@gmail.com. If Relay is later incorporated, we will update this clause and give notice under clause 19.

   In plain English There is no company behind Relay yet, and we are not going to pretend there is. One person operates it, and that person is who you are agreeing with.

2. You accept these Terms by creating a Relay account, joining a Relay workspace, or using the Service in any way. If you do not accept them, do not use the Service.

3. If you accept these Terms on behalf of a company or other organisation, you confirm you are authorised to bind that organisation, and “you” means that organisation.

4. Our Privacy Policy is incorporated into these Terms by reference and forms part of this agreement.

   In plain English Using Relay means you agree to this. The Privacy Policy is not a separate, optional document — it is part of the same deal.

Relay is an AI productivity hub. With your explicit authorisation, it connects to third-party tools you already use, reads the data those tools expose, and turns it into briefings, digests, timelines, tasks, and answers.

1. The Service currently provides:

   • A daily brief summarising your calendar, inbox, and connected tools.
   • An inbox digest that groups and prioritises email.
   • A calendar timeline and schedule view.
   • Task management, including tasks extracted from your connected data.
   • A chat assistant that can answer questions about your work and, subject to clause 8.5, prepare actions in connected tools.
   • Workspace summaries narrating activity across everything you have connected.

2. Relay is an aggregation and summarisation layer. It is not a system of record, a backup service, or an archive. It does not guarantee that data shown in Relay is complete or current relative to the third-party tool it came from, and it is not a substitute for that tool.

   In plain English If Relay and Gmail disagree, Gmail is right. Do not treat Relay as the only copy of anything, and do not treat “Relay didn't show it” as proof it doesn't exist.

3. The Service is provided on an evolving basis. Features, integrations, AI models, and interfaces may be added, changed, or removed as described in clause 13.

1. Access during beta may be limited, invitation-based, or subject to capacity limits, and may be revoked or changed at our discretion.

2. Known limitations at the effective date. These are current characteristics of the beta, not incidental bugs, and you should assume them when deciding what to use Relay for:

   • No uptime commitment. There is no service level agreement, no guaranteed availability, and no support response time.
   • AI capacity is shared and rate-limited. Relay runs primarily on free-tier AI models with provider-imposed rate limits. Under load, an AI feature may time out, return a partial result, or fail outright. This is expected, not exceptional.
   • AI output quality varies. Small free models can truncate or malform long summaries. Identical inputs may produce different results.
   • Integration coverage is uneven. Some connected providers are read only in practice because no Relay feature consumes them yet, and two providers offer no token-revocation endpoint (see clause 7.2).
   • No formal backup or recovery guarantee. Relay is not a system of record and you should not use it as the only copy of anything.
   • Data is not exportable in bulk. There is currently no one-click export; a copy of your data can be requested by email under clause 11.4.

3. Beta status does not reduce our obligations under applicable data protection law, and it does not excuse a security failure on our part. It describes the maturity of the product's features, not the standard of care we apply to your data.

   In plain English “It's a beta” is an honest warning about reliability. It is not a licence for us to be careless with your data, and we are not claiming it is.

1. You must be at least 16 years old, or the minimum age of digital consent in your country if that is higher. Relay is a workplace tool and is not directed at children.

2. You must not be barred from using the Service under the laws of your country, and you must not be subject to trade sanctions or export restrictions that would prohibit us from providing it to you.

3. You must have the authority to connect each third-party account you connect, and to allow Relay to access the data in it. See clause 7.3.

1. Relay accounts are authenticated through our identity provider. You are responsible for keeping your sign-in credentials secure, for any multi-factor settings on that account, and for all activity that occurs under it.

2. You must not share your account, sell access to it, or let another person use it. Each person using Relay needs their own account. Where you want a colleague to have access, invite them to your workspace instead (clause 6).

   In plain English Sharing one login between people is the fastest way to leak a whole workspace's connected accounts, and it makes it impossible for either of us to tell who did what.

3. You must provide accurate registration information and keep it current.

4. You must notify us at relayapphq@gmail.com without undue delay if you know or suspect that your account, or any account you have connected to Relay, has been compromised.

5. We may require you to re-authenticate, re-authorise an integration, or reset access where we reasonably believe it is necessary to protect your account or the Service.

Relay is organised around workspaces. A workspace is the shared container for a team's tasks, briefing settings, and connected tools, and it changes what other people can see.

1. When you join or create a workspace, workspace-level data — including tasks, briefing history, workspace settings, and the record of assistant actions — is visible to other members of that workspace.

2. Most integration credentials you connect belong to you, not to the workspace: another member cannot use your personal Google or Slack connection. A limited set of bot-style integrations are, by their nature, workspace-wide and are shared with all members. The Service indicates which is which at the point of connection.

   In plain English Connecting your Gmail does not hand your inbox to your teammates. But a Slack bot connection is installed into the Slack workspace itself, so it is shared by design.

3. If you invite others to a workspace, you are responsible for who you invite and for ensuring you are permitted to expose the connected data to them.

4. Leaving a workspace removes your access and your membership. It does not delete data belonging to the workspace or to its other members. See clause 17.5 for what deletion actually removes.

Relay's usefulness comes entirely from tools you connect — Google, Slack, Notion, ClickUp, HubSpot, Linear, GitHub, Jira, Zoom, Discord, Outlook, Todoist, Airtable, X, and others we may add. Each connection is made through that provider's own OAuth consent screen.

1. You grant every connection. Relay never accesses a third-party service until you complete that provider's authorisation flow and approve the permissions it displays. We request the narrowest scopes each feature actually needs; the current scope list for every provider is published in the Relay Handbook.

   Relay is not a read-only tool. Several of those scopes grant write access, because the assistant is designed to act, not only to report. Gmail is connected with permission to read, send, and draft; Google Calendar with permission to create and edit events; Google Docs and Sheets with permission to create and update; and Slack, X, Airtable and Jira with permission to post or create records. Every one of those write paths is gated behind the explicit confirmation described in clause 8.5, but the underlying permission is genuinely granted.

   In plain English If a page anywhere else says Relay is “read-only”, that page is wrong and this clause is right. Relay asks for write access on purpose, and then asks you before using it.

2. You can revoke any connection. Disconnecting an integration in Settings deletes Relay's stored credential and, for providers that offer a revocation endpoint, asks the provider to invalidate the token as well. A small number of providers offer no revocation endpoint; for those, disconnection removes our copy and the token expires under the provider's own schedule.

   In plain English Disconnect means disconnect, not just “hide it from the UI”. Where a provider lets us hand the key back, we hand it back.

3. You must be entitled to connect it. You represent that you have the right to grant Relay access to each account you connect and to the data in it, including where that data belongs to your employer, your clients, or third parties. If you need your organisation's permission, get it before connecting.

4. Third-party terms still apply. Your use of each connected service remains governed by that provider's own terms and privacy policy. Nothing in these Terms modifies your agreement with them.

5. We are not responsible for them. We are not liable for a connected provider's outages, rate limits, API changes, deprecations, pricing changes, data loss, or account suspensions. A provider changing or withdrawing its API may degrade or remove a Relay feature without notice.

6. Credentials can go stale. Tokens expire or are revoked outside Relay. Where we detect that a credential no longer works, we flag it for reconnection rather than silently presenting its absent data as an absence of data. Even so, you should treat a connection you have not used recently as unverified until it refreshes.

1. AI output is a draft for your judgement, not a finding of fact. This applies to every AI surface in the product: the daily brief, the inbox digest, workspace summaries, extracted tasks, prioritisation, and the chat assistant.

2. Omission is a failure mode too. An AI summary that does not mention something is not evidence that the thing does not exist. Missing or stale connections, provider rate limits, and model limits can all cause real items to be left out.

   In plain English “Relay said I had no meetings today” is not the same as “I had no meetings today.” Check the calendar before you skip the day.

3. Not professional advice. AI output is not legal, financial, investment, tax, medical, employment, or other professional advice, and must not be relied on as such. Relay is not a licensed adviser in any field.

4. Third-party models. AI features are delivered using third-party model providers. Content you submit to an AI feature — and the connected data needed to answer it — is transmitted to those providers for processing. As at the effective date of these Terms those providers are OpenRouter (which routes to a range of underlying model vendors) and Groq. We may change providers as the product develops; the current list is maintained in our Privacy Policy.

   If you supply your own model API key, requests made with it are sent to that provider under your own agreement with them, and that agreement — not this one — governs how they handle your content.

5. Actions require your confirmation. Where the assistant can change something outside Relay — sending or drafting a message, creating a record in a connected tool — it prepares the action and presents it for your explicit confirmation. It executes only after you confirm. You remain responsible for the content and consequences of any action you confirm, exactly as if you had performed it yourself.

6. Untrusted content. Relay reads content authored by third parties — email bodies, chat messages, documents, issue descriptions. That content can contain text crafted to manipulate an AI model (“prompt injection”). We isolate and mark such content and instruct the model to disregard instructions inside it, but no current defence is complete. Treat assistant output derived from untrusted content with the same suspicion you would apply to the content itself.

7. No output guarantee. We do not warrant that AI output will be accurate, complete, consistent between runs, available, or free of offensive or objectionable material. Identical inputs may produce different outputs.

8. You must not use Relay's AI features to generate unlawful content, to impersonate a person or organisation, to produce material misrepresented as human-authored where disclosure is legally required, or in any way that would breach clause 9.

1. You are responsible for all data you connect or submit, and for the lawful basis on which you do so. Do not connect accounts containing special-category personal data, regulated health or financial records, or data subject to contractual confidentiality you cannot extend to us, without first satisfying yourself that doing so is lawful.

2. Automated or excessive use that degrades the Service for others, or that generates disproportionate AI or third-party API cost, may be rate limited, throttled, or suspended without notice.

3. We may investigate suspected breaches of this clause, and may preserve and disclose information where we reasonably believe it is necessary to comply with law, enforce these Terms, or protect the rights and safety of users or the public.

4. Security research. We welcome good-faith vulnerability reports. Testing is permitted only against your own account and workspace, must not access other users' data, must not degrade the Service, and must be reported to relayapphq@gmail.com before public disclosure. Research meeting those conditions is not a breach of these Terms.

   In plain English Find a hole, tell us, don't touch anyone else's data, give us a chance to fix it. Do that and we will not come after you.

1. You keep your content. Connecting or creating content in Relay transfers no ownership to us.

2. The licence you grant us is narrow. You grant us a worldwide, non-exclusive, royalty-free licence to host, store, transmit, display, and process your content solely to provide, secure, and support the Service for you and your workspace. It lasts only as long as we hold the content, and it ends when the content is deleted.

   In plain English We need permission to put your email on your screen. That is all this licence is for. It is not a licence to publish, resell, or repurpose your data.

3. We do not train on your content. Relay does not use your content, or AI output generated from it, to train models, and we do not sell or rent it.

   We cannot make that promise on behalf of the third-party model providers described in clause 8.4. Your content is processed by them under their own published terms, which we accept as a customer rather than negotiate. Some models we use are offered on free tiers whose terms permit the provider to retain or use prompts, including for model improvement. If that is unacceptable for particular data, do not put that data through Relay's AI features.

   In plain English We don't train on your data and we never will. But we are a small product using other companies' models on their standard terms — we are not in a position to bind them, and we are not going to claim otherwise.

4. AI output is not exclusive. Given how generative models work, other users may receive output that is identical or similar to yours. We make no representation that AI output is original or that it does not infringe third-party rights, and you are responsible for checking before you publish or rely on it.

5. Our licence to you. Subject to these Terms, we grant you a limited, revocable, non-exclusive, non-transferable right to use the Service. All rights not expressly granted are reserved. The Relay name, logo, interface, and underlying software remain ours.

6. Copyright complaints. If you believe content on the Service infringes your rights, contact relayapphq@gmail.com with enough detail to identify the work and the material. We will investigate and may remove content and terminate repeat infringers.

How we collect, use, store, and delete data is set out in full in the Privacy Policy. This clause states the parts that are contractual commitments rather than disclosures.

1. Integration credentials are encrypted at rest using AES-256-GCM, and are decrypted only inside our server-side functions at the moment a request needs them. They are never sent to your browser and are never exposed to other members of your workspace, except for the workspace-wide bot integrations described in clause 6.2.

2. Access is scoped to your workspace. Every request that touches your data is authenticated against your verified identity and checked against your workspace membership before any data is returned.

3. Deletion. You may delete your account data from Settings. Where you are the only member of your workspace, this removes the workspace and its associated records, including our stored integration credentials, and we ask providers to revoke those credentials where they support it. Where the workspace has other members, we remove your membership and your personal usage history and leave the shared workspace intact for them. Residual copies in encrypted backups are purged on our normal backup cycle.

   In plain English Deleting your account cannot delete your teammates' workspace out from under them. If you are the last one out, the whole thing goes.

4. Statutory rights are unaffected. Nothing in these Terms limits any right you have under applicable data protection law, including rights of access, correction, deletion, portability, and objection. Where we act as a processor of personal data on your behalf, that processing is subject to a separate data processing agreement available on request.

5. Security incidents. We maintain technical and organisational measures appropriate to the risk, and will notify affected users of a personal data breach without undue delay, as required by applicable law.

1. The Service is currently provided free of charge during beta. Free access is not a permanent entitlement.

2. If we introduce paid plans, we will present pricing, billing period, renewal terms, and refund terms clearly before you are charged, and we will not charge you without your express prior agreement. We will give reasonable advance notice before a free tier you are using becomes paid.

3. You are responsible for any costs you incur with third parties through your use of Relay — including charges from a connected provider, or usage billed to an AI provider API key you supply yourself.

4. Where you supply your own AI provider key, we make no commitment about the cost, availability, or rate limits of that provider, and you remain solely responsible for spend on that account.

1. We aim for high availability but do not guarantee it. The Service may be unavailable for maintenance, deployments, provider outages, or reasons outside our control. We offer no service level agreement or uptime commitment during beta.

2. We may add, change, suspend, or discontinue any feature or integration at any time. Where a change materially reduces core functionality you rely on, we will give reasonable notice where practicable.

3. We may impose or adjust usage limits — request rates, AI call volume, storage — to keep the Service stable and affordable to run.

4. We may discontinue the Service entirely. If we do, we will give you reasonable notice and a reasonable opportunity to export your content before access ends.

   In plain English We are a small beta product. If we ever have to shut down, you will get warning and a chance to get your data out — not a dead login screen one morning.

1. To the fullest extent permitted by law, the Service is provided “as is” and “as available”, without warranties of any kind, express or implied, including implied warranties of merchantability, fitness for a particular purpose, non-infringement, and any warranty arising from course of dealing or usage of trade.

2. We do not warrant that the Service will be uninterrupted, timely, secure, or error-free; that defects will be corrected; or that data or AI output obtained through the Service will be accurate, complete, or reliable.

3. We are not responsible for failures, delays, data loss, or inaccuracies caused by connected third-party services, AI model providers, or infrastructure providers outside our control.

4. Nothing here is professional advice. The Service does not provide legal, financial, investment, tax, medical, or other professional advice, and no relationship of that kind is created by using it.

5. Some jurisdictions do not allow the exclusion of certain warranties. Where that is the case, the exclusions above apply only to the extent permitted, and you may have rights that these Terms cannot remove.

1. To the maximum extent permitted by law, neither party is liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for loss of profits, revenue, goodwill, business opportunity, or anticipated savings, however caused and on any theory of liability.

2. To the maximum extent permitted by law, we are not liable for loss or corruption of data, for decisions you take in reliance on AI output, or for actions you confirm the assistant should take under clause 8.5.

3. Cap. To the maximum extent permitted by law, our total aggregate liability arising out of or relating to these Terms or the Service is limited to the total amount you have paid us for the Service in the twelve months before the event giving rise to the claim.

   The Service is currently provided free of charge, so that amount is presently nil. We state this plainly rather than hiding it: if you need a contractual remedy backed by a monetary cap, Relay in its current free beta form does not offer one, and you should take that into account before relying on it for anything of consequence.

   In plain English You are not paying, and in exchange we are not underwriting your losses. That is the trade. If that is not acceptable for how you plan to use Relay, do not use it for that.

4. What is never excluded. Nothing in these Terms limits or excludes liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, or for any other liability that cannot lawfully be limited or excluded. Some jurisdictions do not allow certain limitations, so parts of this clause may not apply to you.

5. The limitations in this clause apply even if a limited remedy fails of its essential purpose, and reflect a reasonable allocation of risk given that the Service is provided free of charge during beta.

1. You agree to indemnify, defend, and hold harmless Relay and its officers, employees, contractors, and agents from and against any third-party claim, demand, loss, damage, liability, cost, or expense (including reasonable legal fees) arising out of or relating to:

   • your breach of these Terms or of applicable law;
   • your connection of an account, or submission of data, you were not authorised to connect or submit;
   • your infringement of a third party's intellectual property, privacy, or other rights;
   • content you send, publish, or cause to be sent through a connected integration, including any action you confirmed under clause 8.5;
   • your use of AI output in a way that harms a third party.

2. We will notify you of any claim we seek indemnification for, allow you to control the defence with counsel of your choosing (subject to our reasonable approval), and cooperate at your expense. You may not settle a claim in a way that imposes an obligation or admission on us without our prior written consent.

   In plain English If your use of Relay gets us sued by somebody else, that is on you — but we owe you prompt notice and cooperation, not a surprise invoice after the fact.

3. This clause does not apply to the extent the claim arises from our own breach of these Terms, our negligence, or our wilful misconduct.

1. You may leave at any time. You can stop using the Service, disconnect your integrations, or delete your account data from Settings. There is no lock-in and no notice period.

2. We may suspend. We may suspend your access, or a specific integration, where we reasonably believe it is necessary to protect the Service, other users, or a third party — for example on suspected compromise, abuse, or a breach of clause 9. We will tell you why unless doing so would be unlawful or would compromise an investigation.

3. We may terminate your account for a material breach of these Terms that you do not cure within a reasonable period after notice, for repeated breaches, for unlawful use, or where required by law. We may terminate immediately and without notice for serious abuse, fraud, or conduct endangering the Service or its users.

4. We may terminate for convenience on reasonable notice while the Service is free of charge, including if we discontinue the Service under clause 13.4.

5. On termination, your right to access the Service ends immediately. Deletion of data follows clause 11.3. Where practicable and lawful, we will give you an opportunity to export your content before deletion. Terminating your Relay account does not by itself revoke access you granted at a third-party provider; check that provider's own connected-apps settings.

   In plain English Deleting Relay removes our copy of the key and, where the provider supports it, asks them to cancel it. It is still worth checking your Google and Slack app settings yourself — belt and braces.

6. Survival. Clauses 10 (content and IP), 14 (disclaimers), 15 (liability), 16 (indemnification), 18 (governing law), and 20 (general) survive termination, along with any other provision that by its nature should survive.

1. These Terms and any dispute arising out of them are governed by the laws of the Islamic Republic of Pakistan, without regard to its conflict-of-law rules.

2. The parties submit to the exclusive jurisdiction of the courts of Pakistan, except that either party may seek injunctive relief in any court of competent jurisdiction to protect its intellectual property or confidential information.

   In plain English Relay is operated from Pakistan, so that is the law and the forum. Clause 18.4 means this does not strip you of protections your own country gives you.

3. Talk first. Before starting formal proceedings, the parties will attempt in good faith to resolve the dispute by negotiation, beginning with written notice to relayapphq@gmail.com describing the dispute and the relief sought, and allowing 30 days to resolve it.

4. Nothing in this clause limits any mandatory right you have to bring proceedings in the courts of your country of residence, or to rely on the consumer protection law of that country, where such rights cannot be excluded by agreement.

1. We may update these Terms to reflect changes in the Service, our practices, or the law. The version and effective date at the top of this document always identify the current version.

2. For material changes — anything that meaningfully reduces your rights or increases your obligations — we will give notice by email or in the app at least 30 days before the change takes effect.

3. Continued use of the Service after a change takes effect constitutes acceptance. If you do not accept a change, your remedy is to stop using the Service and delete your account before the effective date.

4. We will keep previous versions of these Terms available on request so you can see what changed.

1. Entire agreement. These Terms and the Privacy Policy are the entire agreement between you and us about the Service, and supersede any prior understanding on the subject.

2. Severability. If a provision is held unenforceable, it is modified to the minimum extent necessary to make it enforceable, or severed if it cannot be. The rest remains in force.

3. No waiver. Our failure to enforce a provision is not a waiver of it, and does not prevent us enforcing it later.

4. Assignment. You may not assign or transfer these Terms without our written consent. We may assign them to an affiliate or in connection with a merger, acquisition, or sale of assets, on notice to you.

5. Force majeure. Neither party is liable for a failure to perform caused by events beyond its reasonable control, including infrastructure and provider outages, network failures, natural events, and government action. This does not excuse payment obligations.

6. Relationship. These Terms create no partnership, agency, employment, or joint venture between us.

7. No third-party beneficiaries. No one other than you and us has any right to enforce these Terms.

8. Notices. We may give you notice by email to your account address or by a prominent notice in the Service. You give us notice, including formal legal notice, by email to relayapphq@gmail.com. Relay has no registered postal address while it operates without an incorporated entity.

9. Language. These Terms are drafted in English. Any translation is provided for convenience; the English version governs.