ReQueue is built for contractors who trust us with their inbox. Here is exactly what we do with that trust.
Last updated: October 2026
ReQueue connects to your Gmail account using Google OAuth. We hold exactly two permissions: read access to your mail, and permission to create a draft in your mailbox. ReQueue does not send email. Every follow-up is written into your Drafts folder and stays there: it leaves your account only when you open it and press send yourself. Nothing goes out automatically, and nothing goes out without you. We cannot delete or alter a message you already have.
To be precise about what that guarantee rests on, because the distinction is a real one: Google's draft permission is not a technically send-proof permission, so this is a commitment about what our software does rather than about what Google would allow. We hold ourselves to it in code. No part of ReQueue calls a send API, an automated test fails our build if anyone ever adds one, and a Gmail connection that came back carrying a broader permission than the two above is refused rather than stored.
We check your sent mail and your inbox every thirty minutes, around the clock, so a reply that arrives on a Friday evening is on your board before Monday. A check that finds nothing new does nothing and costs nothing.
We read subjects, participants, dates and attachment filenames across your mail to work out which messages are about a quote. Where a message belongs to a quote we are tracking, we also read its content, so the follow-up we write for you answers what your client actually said.
For those messages, and only those, we keep the content. A deal that runs for months is a conversation, and a system that remembers only a one-line summary of each message forgets the budget they named in April by the time it writes to them in July. Keeping it is what lets ReQueue answer a client rather than send a template.
That content is encrypted before it is stored, using a key held separately from the key that protects your Google credentials, and it is readable only by our servers - never by your browser, and never by another company. It is deleted 90 days after a deal is marked won, lost or removed, 18 months after the last activity on one still open, and within 24 hours of you disconnecting Gmail, whichever comes first.
Everything else in your mailbox is read in passing and not kept, with the one exception below. Newsletters, internal mail, vendor threads and personal messages are not stored, and neither are the contents of attachments - we extract the figures a quote needs and discard the file.
Your own writing. So that the drafts we write sound like you, we keep up to 12 emails you sent yourself from your connected mailbox. Before one is stored, the names, email addresses, phone numbers, street addresses, dollar figures and quote numbers in it are replaced with placeholders, and an email that cannot be cleaned that way is not kept at all. They are encrypted, replaced rather than added to when we refresh them, never shown to anyone else in your company, and deleted when you disconnect.
If your business email is on Microsoft 365, ReQueue connects to it through Microsoft's own sign-in instead of Google's. Everything in the section above about what we read, what we keep, how it is encrypted and when it is deleted applies in the same way, with “disconnecting Gmail” read as disconnecting your Microsoft 365 mailbox. Only work and school accounts can be connected; a personal Outlook.com or Hotmail account cannot.
We ask Microsoft for these permissions: to read and write your mail, to read your mailbox settings (we use this to confirm the mailbox is active and to read its time zone), to sign you in and read your basic profile, and to keep that access between your visits so we can check your mail on schedule. We do not ask for permission to send mail, and a Microsoft connection that came back carrying it would be refused rather than stored.
Why “write”, and what we do with it. Microsoft has no permission that allows creating a draft without also allowing other changes to mail, so the write permission is broader than what we use. We use it for one thing: placing a follow-up in your Drafts folder, and removing or updating a draft that ReQueue itself placed there. Before we change or remove one, we check with Microsoft that it is still an unsent draft. We do not change, move or delete any other message. As with Google, this is a commitment about what our software does, enforced in code, rather than a limit Microsoft imposes.
Your company's administrator. Many organizations let only an IT administrator approve apps that read mail. If yours does, your administrator approves ReQueue once for your organization. That approval does not give ReQueue access to anyone's mailbox: each person still chooses whether to connect their own, and nothing is read until they do.
From your email: subject lines, sender and recipient addresses, dates, attachment filenames, and threading identifiers (Message-ID, In-Reply-To, References). For messages that belong to a quote we are tracking, the message content as well, encrypted and time-limited as described above, and the redacted examples of your own writing described there.
From a Microsoft 365 connection: the mailbox's other addresses (its aliases), your Microsoft organization and user identifiers, and a marker of how far we have read your Sent Items, so each check reads only what is new.
From your activity: notes, call logs, and meeting records you enter manually.
Never stored: the content of mail that is not about a tracked quote (apart from those redacted examples of your own writing), the files attached to any message, your password, and payment details beyond what Stripe processes on our behalf.
ReQueue’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. In plain terms, that means four commitments:
If you revoke ReQueue’s access from your Google account permissions page, or disconnect from Settings, we stop reading your mailbox immediately and delete the stored message content described above.
ReQueue’s use of information received from Microsoft APIs follows the Microsoft APIs Terms of Use. We hold Microsoft 365 data to the same four commitments:
If you disconnect from Settings, or remove ReQueue at My Apps, we stop reading your mailbox and delete the stored message content described above.
OAuth tokens are encrypted at rest with AES-256-GCM and stored in your workspace only. Each workspace is isolated by row-level security policies. No workspace can access another.
All data is transmitted over HTTPS. The application runs on Vercel, your data is stored in Supabase, and scheduled work such as reading new replies runs on Trigger.dev. Vercel and Supabase each hold their own SOC 2 Type II reports.
ReQueue is built and operated by ClearOak & Co., LLC.
Disconnect Gmail: to stop ReQueue from accessing your email, disconnect Gmail at any time from Settings or revoke access from your Google account. Disconnecting stops all access immediately.
Disconnect Microsoft 365: disconnect your mailbox at any time from Settings. That deletes our copy of your access immediately and stops all reading. To remove ReQueue from your Microsoft account as well, use My Apps; your organization's administrator can also remove it for everyone.
Delete contacts: remove all imported contacts from Settings. Your next scan will repopulate them from email metadata.
Delete account: permanently delete your account and all associated data from Settings. This cannot be undone.
We use the following third-party services to operate ReQueue:
We do not sell, rent, or trade your data. We do not run advertising. Our business model is subscriptions.
Reach us at privacy@requeue.io. We respond within 2 business days.