Privacy

Last updated 23 October 2026.

What we store

• Waitlist. When you join the waitlist we store your email address and the time you joined.
• Account. If you create an account we store your email address, a one-way scrambled version of your password (never the password itself), and the times you created the account and last signed in. Our sign-in provider, Supabase, also keeps technical records of sign-ups, sign-ins, sign-outs and session renewals, including the time, your IP address and your browser details. When you create an account, your password is also checked against a public list of leaked passwords (Pwned Passwords, api.pwnedpasswords.com): your password is never sent, only the first 5 characters of its one-way fingerprint, and a password found on the list is refused.
• Drafts. For each draft you save we store its name, the task text you typed, the preview steps, and the times it was saved and changed. Do not type passwords, card numbers or other people’s personal details into a task.
• AI plan counts. When AI plans are on, our server keeps a running count of how many AI plans each account has asked for, so that a daily limit can be applied. The count is saved in the database as a number only (how many times, in which minute or day), never what you asked, and counters older than two days are removed. Some other limits (for example for lookups in other apps) are still kept in the server’s memory only and start again when the server restarts.

Why

To tell you when early access opens, to sign you in, to keep the drafts you choose to save, and, when you ask for one, to have an AI write a preview plan.

Drafts do nothing

A draft is a saved plan. It is never sent or shared, and it is not connected to your email, Stripe or any other app. A run lists the steps of a workflow and saves a note of each one; a step that acts on one of your apps (reading it or adding to it) waits for your Approve click unless you chose Auto mode, and the saved run is private to your account. The one real action is a web call: if a workflow has a Call a web address step and you press Approve and call the address, Hushwork’s server asks that one address (a read-only request that only fetches) and keeps the start of the answer in your runs. It sends nothing from your account, refuses private or internal addresses, and does not follow redirects. Never put a password or key in a web address, because the address is saved in your workflow and run. If you press Connect Linear, Linear asks you to allow Hushwork to read your tasks and to add a new task (it cannot change or delete anything that already exists). Hushwork then keeps the permission Linear gives it, scrambled (encrypted), in your account until you press Disconnect, and a Look something up step set to Linear can, after you press Approve, ask Linear for your open tasks and keep the list in your runs; a Create a Linear task step adds ONE new task with the exact words you read on the Runs page, only after you press Approve (once per run), and keeps a note of it in your runs. If a workflow has an Ask the AI step and you press Approve and ask the AI, your request in that step, and anything the AI is allowed to read (your Linear task titles, or one web page you chose), is sent to Groq, the company that runs the AI, and its answer is kept in your runs. The AI can only read: it cannot change, send or delete anything. If you press Connect Google, Google asks you to allow Hushwork to read your calendar events (read-only: it cannot add, change or delete anything). Hushwork keeps the permission Google gives it, scrambled (encrypted), until you press Disconnect. After you press Approve on a step that looks at your calendar, Hushwork asks Google for your next events and keeps the list in your runs; if an Ask the AI step is allowed to look at your calendar, those event titles are also sent to Groq with your request. If an Ask the AI step is set to read a Slack channel (you write slackmessages:channelname in the step), Hushwork asks Composio for the latest 10 messages of that one channel and sends them to Groq with your request; only the AI’s answer is kept in your runs. A Notion page step writes the text you read on the approval card onto the new page. If you connect another app through Composio (composio.dev, for example Todoist or Notion), you sign in on Composio’s page and Composio, a separate company, keeps the permission; Hushwork never sees it. After you press Approve on a step that looks in that app, Hushwork asks Composio to read one fixed thing (for example your open tasks), the answer passes through Composio, and Hushwork keeps a short text of it in your runs (and sends it to Groq if an Ask the AI step may look at that app). After you press Approve on a Do something in another app step, Hushwork asks Composio to do that one thing (send one email from your Gmail, send one Slack message, create one GitHub issue, add one Todoist task, add one Google Calendar event, create one Notion page, save one Gmail draft that is not sent, or create one new Google Sheet, Slides presentation, Doc or Drive folder in your Google Drive) with the words you can read on the approval card; those words pass through Composio and the app, and nothing else is sent. Hushwork identifies you to Composio only by a random account id, never your email. Manual mode (the default) always waits for your Approve click. If you schedule a workflow, Hushwork runs it by itself at the time you chose, as you, in the same way as Auto mode: it uses the permissions you already gave and keeps the same results in your runs. A scheduled run adds a row or creates a task only if you ticked Let it write by itself for that schedule. To do this while you are away, the server uses a special all-access database key that is only ever used for scheduled runs; every query it makes names your account, and it is never shown to anyone. If you choose Auto mode on the Workflows page, pressing Run does every real step of that workflow straight away and in order, without asking, including adding a row to your Google Sheet and creating a Linear task; it stops at the first step that does not work, and you can switch back to Manual any time. If you connect Google, Google also asks you to allow Hushwork to add rows to Google Sheets, to read your Gmail inbox (read-only: it cannot send, change or delete mail) and to see the names of your recent Google Drive files (never what is inside them). When the AI is switched on, whatever a lookup step finds (your tasks, calendar events, inbox senders and subjects, Drive file names, or another app’s answer) is also sent to Groq, the company that runs the AI, so it can write a clear summary; the summary and the app’s own list are both kept in your runs. After you press Approve on a step that looks at your inbox, Hushwork asks Gmail for the sender, subject and time of your latest 10 messages (never the text inside an email) and keeps that list in your runs; if an Ask the AI step is allowed to look at your inbox, those senders and subjects are also sent to Groq with your request. Only if you choose the option “My Gmail inbox, with the text of each email” in an Ask the AI step, Hushwork’s server also reads the opening of the text (about the first 450 characters) of your 5 newest emails and sends it to Groq with your request; the email text itself is not kept, only the AI’s answer is kept in your runs. Likewise a step that looks at Drive keeps the name, kind and time of your 10 latest files in your runs (and sends them to Groq if an Ask the AI step may look at your Drive). A step can then, after you press Approve and add the row, add ONE row at the bottom of the sheet whose web address you wrote in that step, with exactly the boxes you saw on the approval card. Hushwork never reads or changes the other cells, and a record of the added row is kept in your runs. If an Ask the AI step is set to use an MCP server (a tool server whose web address you typed into the step), Hushwork connects to that server, lets the AI use only the server’s read-only tools, and sends that server the questions the AI asks it (made from your request). What the server answers goes to Groq to write the AI’s answer, and the answer is kept in your runs. Hushwork does not log in to MCP servers, so only servers that need no login can be used. Nothing else is sent anywhere.

AI plans

• AI planning is optional. It is off unless the person who runs Hushwork has switched it on, and the note under the task box always says which it is. When it is off, or when you turn the Write with AI switch off, the plan is made by simple keyword matching in your browser and your task text goes to no AI service. Your task text and the steps of the plan reach our server only when you press Save as draft or Save as new draft, and the steps you change in a draft you already saved reach it when you press Save changes.
• When AI planning is on and you press the arrow, only the task text you typed is sent, through our server, to Groq, a company that runs AI models. Groq runs an AI model (currently openai/gpt-oss-20b, an open-weight model from OpenAI) to write the plan. Your email address, name, account id and other drafts are not sent. Our server also refuses to send text that looks like a card number or a secret key.
• Groq says it does not keep inference requests by default. It may log inputs and outputs for up to 30 days, only to fix errors or investigate abuse, and it keeps any data it retains in the United States (Groq’s data page, read 17 October 2026).
• Groq’s Services Agreement says Groq may not use inputs or outputs to train or fine-tune models unless the customer allows it, and we do not allow it (Services Agreement, modified 22 June 2026). Groq handles your text under its own terms.
• An AI can get things wrong. A plan is shown as text for you to read; it is never sent or connected to anything, and a plan only does something when you run the workflow and approve its steps. Do not type passwords, card numbers or other people’s personal details into a task.

Where it lives

Your account and drafts live in a database and sign-in service run by Supabase, hosted in the Mumbai, India region. Supabase stores this data for us under its own terms. When AI plans are on, the task text of each AI plan goes to Groq, which says any data it retains is stored in the United States.

Who sees it

• Your drafts are visible to you when you are signed in. Other accounts cannot read them: the database itself enforces this.
• The people who run Hushwork can technically see the database. We do not sell your email or share it with advertisers.
• When AI plans are on, Groq receives the task text of every AI plan you ask for, and handles it under its own terms.

Cookies and your browser

• A sign-in cookie keeps you signed in. It exists only for that, and it is removed when you sign out.
• Your light or dark choice, your pause-motion choice and the position of the Write with AI switch are kept in your browser’s own storage. They never leave your device.
• This site has no analytics and no advertising trackers.
• Like any website, whoever serves it can see your IP address when your browser asks for a page.

Waitlist and accounts are separate

Joining the waitlist does not create an account, and creating an account does not add you to the waitlist.

Getting your data removed

To keep a copy first, open Settings and press Download my data (your workflows, newest runs and schedules as one file; saved app connections are never included). To delete your account, open Settings and press Delete my account. It removes your workflows, runs, schedules and saved connections together, and disconnects the apps you connected through Composio. To have a waitlist email removed, open an issue on the project’s GitHub issues page (please leave private details out of it: we will reply there). We keep waitlist emails until early access opens or you ask us to remove them, and accounts and drafts until you ask or the account is deleted.

Questions about this page: open an issue on the project’s GitHub issues page.