Midway

Privacy Policy

Last updated November 15, 2026

This Privacy Policy explains what information Midway (“Midway”, “we”, “us”) collects when you use usemidway.com and the Midway app at app.usemidway.com (together, the “service”), how we use it, who we share it with, how long we keep it, and the choices you have. Midway lets you describe a business workflow in plain English and turns it into an automation that runs on its own, using the apps you connect.

Data we receive from Google is covered in its own section, How Midway handles Google user data. That section takes precedence over the rest of this policy for Google user data.

1. Information we collect

  • Account information. Your name, email address and organization, and, if you sign in with Google, the basic profile Google shares with us (name, email address and profile picture).
  • Content you provide. The automations you describe and build, your messages to Midway’s assistant, files you upload, data tables you create, approval decisions and comments, and the settings you choose.
  • Data from apps you connect. When you connect an app (for example Google Sheets, Google Calendar, Gmail or Slack) and your automations run, we access the data in that app that your automations read or change, and store the results as described below.
  • Websites your automations visit. If an automation uses a browser step, the pages it opens, and the sign-in you save for a website so the automation can use it.
  • Technical information. IP address, browser type, and logs and error reports that help us keep the service working and secure. Our application logs record identifiers and events, not the contents of your data.

2. How we use information

We use information only to:

  • provide the service: build, test and run the automations you set up, and show you their results;
  • keep your account and the service secure, and prevent abuse;
  • fix problems and keep the service working;
  • contact you about your account, your automations (for example a failed run) and important changes;
  • comply with the law.

We do not sell your personal information, share it for cross-context behavioral advertising, or use data from your connected apps for advertising. We do not use data from your connected apps to train AI models.

3. How Midway handles Google user data

This section describes how Midway accesses, uses, stores, shares, protects, retains and deletes data it receives from Google APIs (“Google user data”), including data from Google Workspace APIs.

Midway’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements, and to the Google Workspace API User Data and Developer Policy. This applies to raw and derived Google user data.

3.1 What Google user data Midway accesses

Midway asks for each kind of access separately, only when you choose to connect that Google app, and shows you what it will access before Google asks you to confirm. Midway can access:

  • Sign in with Google (optional, through our sign-in provider WorkOS): your name, email address and profile picture (openid, email, profile), used only to create and sign in to your Midway account.
  • Google Sheets (https://www.googleapis.com/auth/spreadsheets): see, edit, create and delete your spreadsheets. Midway opens only the spreadsheets your automations use (which you name by link or ID) and spreadsheets it creates for you. It cannot search or browse your Google Drive.
  • Google Docs (https://www.googleapis.com/auth/documents): see, edit, create and delete your documents. Midway opens only the documents your automations use (which you name by link or ID) and documents it creates for you. It cannot search or browse your Google Drive.
  • Google Forms (https://www.googleapis.com/auth/forms.body, https://www.googleapis.com/auth/forms.responses.readonly): see, edit, create and delete your forms, and see their responses. Midway opens only the forms your automations use and forms it creates for you.
  • Files you pick (https://www.googleapis.com/auth/drive.file): see, edit, create and delete only the specific Google Sheets, Docs and Forms files you choose in Google’s file picker inside Midway, and files Midway creates for you. Midway cannot see, search or browse any other file in your Google Drive.
  • Google Calendar (https://www.googleapis.com/auth/calendar): see, create, change, share and delete your calendars and their events, see when you are free or busy, and see your calendar settings (such as your time zone).
  • Google Contacts (https://www.googleapis.com/auth/contacts, https://www.googleapis.com/auth/contacts.other.readonly, https://www.googleapis.com/auth/directory.readonly): see, create, change and delete your contacts; see your “other contacts” (people Google saved because you interacted with them); and, for a Google Workspace account, look up people in your organization’s directory.
  • Every Google app connection (https://www.googleapis.com/auth/userinfo.email): your Google account’s email address, used only to label the connection so you can tell your accounts apart.

Midway reads or changes Google user data only when an automation you built and turned on runs, when you test-run an automation or one of its steps, or when, while building, you ask Midway’s assistant to look something up in a connected Google app. Changes (creating, updating, sharing or deleting rows, documents, forms, calendars, events or contacts) happen only as your automations specify.

3.2 How Midway uses Google user data

Midway uses Google user data only to provide and improve the user-facing features you use in Midway:

  • running the steps of your automations that read or change your Google apps;
  • passing data between the steps of your automations as you designed them (for example, adding a row to a spreadsheet for each new form response);
  • showing you your automations’ runs, inputs, outputs and errors, so you can check what happened;
  • helping you build and fix automations, when you ask Midway’s assistant to look something up or to test a step;
  • keeping the service secure and investigating problems you report.

Midway does not use Google user data for any other purpose. In particular, Midway never:

  • sells Google user data;
  • uses or transfers it for advertising, including personalized, retargeted or interest-based advertising;
  • transfers it to data brokers, information resellers or other third parties to resell;
  • uses it to determine creditworthiness or for lending purposes;
  • uses it to build databases or profiles unrelated to running your automations;
  • uses it to develop, improve or train generalized or non-personalized AI or machine-learning models, or transfers it to anyone for that purpose.

3.3 Artificial intelligence

Midway uses AI models from Anthropic (Claude) to build automations and to run the steps of automations that ask for AI (for example, summarizing a form response). When such a step runs, or when Midway’s assistant looks something up or tests a step for you, the data that step involves, which can include Google user data, is sent to Anthropic’s API to produce the answer and returned to Midway. Anthropic processes it as our service provider: under its commercial terms it does not use this data to train its models, and it deletes API inputs and outputs within 30 days, except where it must keep them longer to enforce its usage policy or comply with the law.

Midway does not use Google user data, including data obtained through Google Workspace APIs, to develop, improve or train generalized or non-personalized AI or machine-learning models, and does not transfer it to any third party for that purpose. Midway does not train or fine-tune any AI model on your data.

Data from connected apps is treated as untrusted when it is given to an AI model: Midway marks it as data, not instructions, removes hidden characters, and first screens it with a prompt-injection filter (Amazon Bedrock Guardrails, run by Amazon Web Services in the United States), so text in your apps that tries to give the AI instructions (a prompt injection) is not followed. Content the filter flags is not sent to the AI model.

3.4 Who Midway shares Google user data with

Midway shares Google user data only with these service providers, only to provide the features you use, and only under their terms of service and data processing agreements, which limit their use of it to providing their service to Midway and do not allow them to use it to train AI models:

  • Composio (app connection service): holds the access tokens Google issues to Midway when you connect a Google app, makes the calls to Google that your automations need, and passes the results back to Midway. It keeps a log of each call, including what was sent and returned, for up to one year, which Midway uses to confirm whether an action took effect.
  • Amazon Web Services (hosting and security): runs Midway and stores your automations and their run data in the United States (us-east-1), and screens data given to AI models for prompt injection (Amazon Bedrock Guardrails, in the United States).
  • Anthropic (AI models): processes the data of AI steps and assistant requests, as described in 3.3.
  • WorkOS (sign-in): receives your name, email address and profile picture when you sign in with Google.

Midway otherwise discloses Google user data only if you direct it to (for example, an automation you build that sends a spreadsheet row to another app you connected, or to people you choose), if necessary for security purposes (such as investigating abuse), to comply with applicable law or legal process, or as part of a merger, acquisition or sale of assets, after obtaining your explicit prior consent.

3.5 Who at Midway can see Google user data

Midway’s staff do not read Google user data unless: you give us explicit permission (for example, when you ask for help with a specific automation or run); it is necessary for security purposes, such as investigating a bug or abuse; it is necessary to comply with applicable law; or the data has been aggregated and anonymized and is used for internal operations. Staff access to production systems is restricted to a small number of people, requires individual authorization, and is logged.

3.6 How Midway stores and protects Google user data

  • Google’s access tokens for your connections are held by Composio, encrypted; Midway’s own database stores only a reference to the connection, not the tokens.
  • The inputs and outputs of your automations’ steps, which can include Google user data, are stored in Midway’s database and storage on Amazon Web Services in the United States, encrypted at rest (with keys managed by AWS Key Management Service) and in transit (TLS).
  • Each organization’s data is kept separate by database row-level security; automation code runs in isolated sandboxes with no access to other organizations’ data or to credentials.
  • Access to production systems is limited, individually authorized and logged.

3.7 How long Midway keeps Google user data

  • Run data (the inputs, outputs and logs of each step of a run): deleted 60 days after the run ends.
  • Run summaries (a short summary of each run, which can include some values the run received or returned, used to search your run history): deleted one year after the run ends.
  • Files an automation reads or creates: deleted 60 days after the run, unless you keep them in one of your data tables.
  • Data the assistant looked up in your apps while you built an automation: removed from the conversation 60 days after it was looked up.
  • Your automations, conversations with the assistant and data tables: kept until you delete them; deleted automations are erased 30 days after you delete them.
  • Access tokens: kept by Composio until you disconnect the app or delete your account.
  • Composio’s call logs: up to one year. Anthropic: within 30 days (see 3.3). Database backups: 7 days.

3.8 How to revoke access and delete Google user data

  • Disconnect a Google app on Midway’s Connections page at any time. Midway stops using the connection at once, and Composio deletes the connection and asks Google to revoke its access. Automations that use it can’t reach that app until you connect it again.
  • Revoke Midway’s access in your Google Account at myaccount.google.com/permissions. Midway can then no longer reach your Google data.
  • Delete automations and their runs in the app (Move to trash); they are erased 30 days later.
  • Delete your organization (owners, in Settings): within minutes its automations are switched off and every connection is disconnected and its access revoked; all its data is erased 30 days later (the window lets you restore an organization deleted by mistake), and from backups within 7 days after that.
  • Delete your account (on your Account page): you are signed out and your personal connections stop being used at once, and their access is revoked within 7 days (time for your organization to move automations that relied on them). Your account data is erased 30 days later. Connections you shared with your organization, and automations you built in it, stay with the organization.
  • Ask us at support@usemidway.com for a copy of your data or to delete it; we answer within 30 days.

Deleting data in Midway does not delete it from your Google apps. Step-by-step instructions: Managing and deleting your Google data in Midway.

3.9 Changes to how Midway uses Google user data

If Midway ever wants to use Google user data in a new way or for a different purpose than described here, we will update this policy, tell you, and ask for your consent before doing so.

4. Data from other apps you connect

Data from apps other than Google is handled the same way: accessed only as your automations and requests to the assistant require, used only to provide the service, shared only with the service providers below, kept for the periods in 3.7, and never sold, used for advertising or used to train AI models.

5. Service providers

We use these providers to run the service, only as needed to provide it:

  • Amazon Web Services: hosting, databases, storage, email delivery and logs, in the United States.
  • WorkOS: sign-in and organization membership.
  • Composio: connections to the apps you connect, and the calls to them.
  • Anthropic: AI models that build automations and run AI steps.
  • Browserbase: runs the browser for automations that use browser steps, and keeps the website sign-ins you save.

6. Cookies

We use cookies needed to keep you signed in and to protect sign-in. The app stores a few display preferences in your browser. We do not use advertising or analytics trackers.

7. Retention and deletion

We keep information while your account is active and for the periods in 3.7. When you delete your account or organization, we erase its data as described in 3.8. We keep a minimal audit log of account activity (who did what and when, without the contents of your data or contact details) for 12 months, and a record that the erasure happened (identifiers, times and counts only).

8. Your rights

Depending on where you live, including California and the European Economic Area, you may have the right to know what personal information we hold about you, to get a copy, to correct or delete it, to object to or restrict its processing, and not to be discriminated against for using these rights. Email support@usemidway.com to make a request; we answer within 30 days.

9. Security

We protect information with encryption in transit and at rest, isolation between organizations, limited and logged staff access, and the measures described in 3.6. No system is perfectly secure; if a breach affects your data, we will tell you as the law requires.

10. Children

Midway is not intended for anyone under 18, and we do not knowingly collect their information.

11. Where data is processed

Midway stores data in the United States. Our service providers may process it in other countries where they operate, under the same protections.

12. Changes to this policy

We may update this policy. We will post the new version here, update the date above, and tell you about significant changes before they take effect. Changes to how we use Google user data follow 3.9.

13. Contact

Questions, requests or complaints about privacy: support@usemidway.com.