Privacy Policy

Effective October 16, 2026

This policy explains what WORKWAE LLC ("workwae", "we", "us") collects when you use the workwae website, console, API and connect pages (the "Service"), why, who we share it with, how long we keep it, and the choices you have. It covers two groups of people:

• Customers: the businesses and developers who sign up for workwae and build on its API, and the people they invite to their workwae workspace.
• End users: the people who connect an email, calendar, contacts or meeting account to workwae, either on a workwae connect page or through a Customer's application.

When you connect an account through a Customer's application, workwae processes that account's data on the Customer's behalf and makes it available to that Customer, which is the purpose of the connection. The Customer's own privacy policy describes what it does with the data it receives; this policy describes what workwae does.

1. Information we collect

Customer account information

• Name, email address, password (stored only as a salted hash) and sign-in sessions.
• Workspace name, members, roles, invitations, API keys (stored hashed) and settings.
• An audit log of actions taken in the workspace, and usage counts used for plan limits and billing.
• Billing details. Payments are handled by Stripe; we receive the subscription and payment status, never your card number.
• Messages you send to our support address.

Connected account data

When an account is connected, workwae receives the permissions shown on the provider's consent screen and nothing more. Calendar, contacts and shared-mailbox permissions are requested only when the connection uses those features. The permissions and the data they cover are listed per provider in section 5. In summary, workwae may process:

• Identity: the account's email address, display name and provider user ID.
• Mail: message metadata (sender, recipients, subject, dates, folders and labels, flags, thread and header information), message bodies and attachments, drafts, and send-as identities. workwae also sends messages and changes labels, folders and read state when the Customer's application or the end user asks it to.
• Calendar: calendars, events (title, time, location, description, attendees, recurrence, response status, conferencing links), free/busy information and the mailbox time zone.
• Contacts: contacts and contact groups, including names, email addresses, phone numbers, addresses, organizations and photos.
• Meetings: for Zoom and Webex, the user ID, email address and name of the connected meeting account, and the ID, join link, topic, time, duration and recurrence of the meetings workwae creates for calendar events.
• Credentials: OAuth access and refresh tokens, or, for IMAP, SMTP, CalDAV and CardDAV accounts, the server address, username and password or app password.
• Organization directory: when a Google Workspace or Microsoft 365 administrator connects their organization, the list of users (names and email addresses) used to choose which mailboxes to connect.

Recipients of tracked messages

If a Customer turns on open or click tracking for messages it sends through workwae, we record when a recipient opens the message or follows a link: the time, IP address, browser user agent and request headers, and an approximate location (country, and where available region and city) provided by Cloudflare. Unsubscribe requests made through workwae links are recorded too, so the Customer can honor them.

Website and console

workwae.com sets no cookies and uses no analytics or advertising trackers. The console uses cookies only to keep you signed in and to protect sign-in flows. Our servers and Cloudflare, which delivers our sites, log requests (IP address, user agent, time, page) for security and reliability.

2. How we use information

We use information only to:

• provide the Service: sync, index, search, store and display mail, calendars and contacts; send mail; create, update and cancel meetings; and deliver webhooks and API responses to the Customer the account is connected to;
• run optional AI features a Customer has turned on (section 3);
• keep the Service secure, prevent abuse and fraud, and debug failures;
• provide support you ask for;
• bill Customers and enforce plan limits; and
• comply with the law.

We do not:

• sell or rent any personal information or connected account data;
• use connected account data for advertising, including retargeting or personalized ads;
• use connected account data to determine credit-worthiness or for lending;
• build profiles of end users for any purpose other than providing the Service; or
• use connected account data to develop, improve or train generalized or non-personalized artificial intelligence or machine learning models.

3. AI features

AI features are off until a Customer turns them on. When on, workwae sends only the text a feature needs to Gatewae, the AI gateway we use, which forwards it to a language model provider:

• Reply classification (to detect opt-out requests and automatic replies to messages the Customer sent): the reply's subject, the first 2,000 characters of its own text, and whether it carries standard auto-reply headers.
• Draft writing (when a person asks for a draft): their instructions, their draft so far and, when answering a message, that message's sender, subject and first 4,000 characters.

The results are returned to the Customer's workspace. We use only providers that do not use the data we send to train their models, and the data is never used by us to train any model.

4. How we share information

We share information only:

• With the Customer the account is connected to, through the API, webhooks and console, because that is what the end user connected the account for.
• With the provider you direct us to: for example, sending a message through Gmail, writing an event to Outlook, or creating a meeting in Zoom.
• With service providers that process data for us under contract and only on our instructions:

  Provider	Purpose
  Infrastructure providers in the United States	Servers, databases, object storage and encrypted backups
  Cloudflare, Inc.	Network delivery, DNS, DDoS protection and our own account emails
  Stripe, Inc.	Payments (Customer billing data only)
  Gatewae and its language model providers	AI features, only when a Customer turns them on

• For legal reasons: to comply with applicable law, a valid legal process, or to protect the rights, safety and security of our users, the public or workwae.
• In a business transfer: as part of a merger, acquisition or sale of assets, and for data received from Google APIs only after obtaining the end user's explicit prior consent.

workwae staff do not read connected account data except (a) with the explicit consent of the end user or Customer for specific messages or items, for example to resolve a support request; (b) when necessary for security purposes, such as investigating abuse; (c) to comply with applicable law; or (d) when the data is aggregated and anonymized for internal operations.

5. Provider-specific disclosures

Google (Gmail, Google Calendar, Google Contacts, Google Workspace)

workwae may request these Google permissions:

In line with the Limited Use requirements, data received from Google APIs is:

• used only to provide and improve the user-facing features described in this policy and visible in the Customer's application and the workwae console;
• transferred to others only to provide those features, to comply with applicable law, for security purposes, or as part of a merger, acquisition or sale of assets with the end user's explicit prior consent;
• never used or transferred for serving advertisements;
• never sold, and never used to determine credit-worthiness or for lending; and
• never read by humans except as described in section 4.

workwae does not use Google Workspace API data to develop, improve or train generalized or non-personalized AI or machine learning models. Customers that receive Google user data through workwae must also use it in line with the Google API Services User Data Policy (see our Terms of Service).

Deleting a Google account in workwae revokes workwae's access with Google, unless another connection of the same Google account through the same app still uses it. You can also remove workwae's access at any time at myaccount.google.com/permissions; Google Workspace administrators can remove domain-wide delegation in the Admin console under Security > API controls.

Microsoft (Microsoft 365, Outlook.com, Exchange Online)

workwae accesses Microsoft accounts through Microsoft Graph and, for accounts connected over IMAP and SMTP, Exchange Online, in accordance with the Microsoft APIs Terms of Use. workwae may request these permissions:

Data from Microsoft is used only to provide the Service as described in this policy, is never sold or used for advertising, and is not used to train AI models. You can remove workwae's access at myapps.microsoft.com (work or school accounts) or account.live.com/consent/Manage (personal accounts); administrators can remove organization-wide consent under Enterprise applications in the Microsoft Entra admin center.

Zoom

workwae connects to Zoom only to create, update and delete the Zoom meeting attached to a calendar event when the Customer's application or the user asks for one, in accordance with the Zoom API License and Terms of Use. workwae requests these Zoom permissions:

• meeting:write:meeting, meeting:update:meeting, meeting:delete:meeting: create a meeting for a calendar event, move it when the event changes, and delete it when the event is deleted or cancelled.
• user:read:user: read the connected Zoom user's ID, email address and name to identify the connection and the meeting host.
• For organizations that register their own Zoom Server-to-Server app, the corresponding :admin permissions, used to create meetings hosted by the organization's users whose email address matches the connected mailbox.

workwae stores the Zoom grant (encrypted), the Zoom user's ID, email address and name, and the ID and join link of each meeting it created. It sends Zoom the meeting's topic, start time, time zone, duration and recurrence, taken from the calendar event. workwae does not access meeting recordings, chat, transcripts, participant lists or any meeting content, and does not sell Zoom data or use it for advertising or AI training.

Disconnecting Zoom in workwae revokes the grant with Zoom and deletes the stored tokens immediately. You can also remove workwae from your Zoom account in the Zoom App Marketplace under Manage > Added Apps; Zoom notifies us and we delete the grant and your Zoom account details (user ID, email address and name) as soon as the notice arrives, and in any case within 10 days of being notified by Zoom or by you. Meetings already created stay in your Zoom account until you delete them there; the meeting ID, join link and host recorded with each one stay with its calendar event until the event or the connected calendar account is deleted.

Cisco Webex

workwae uses the Webex permissions meeting:schedules_write, meeting:schedules_read and spark:people_read (or their administrator equivalents for a Webex Service App) only to schedule, update and delete the Webex meeting attached to a calendar event and to identify the host. It handles Webex data the same way as Zoom data above.

6. How we store and protect information

• All traffic to and from workwae and the providers is encrypted with TLS.
• OAuth tokens, passwords, webhook signing secrets, stored message content and attachments are encrypted with keys managed in HashiCorp Vault, and each encrypted value is bound to the record it belongs to, so it cannot be opened anywhere else.
• Data is stored on servers in the United States. Access to production systems is limited to authorized personnel who need it to operate the Service.
• Each Customer's data is isolated from other Customers' data, and Customers control their own members' roles and API keys.

No system is perfectly secure. If we learn of a breach affecting your information, we will notify affected Customers and, where required, end users and authorities.

7. Retention and deletion

• Connected accounts: data is kept while the account stays connected. Synced calendar events cover 90 days back and 365 days ahead. Stored message content that has not been read for 30 days is deleted (Customers may keep less).
• Disconnected or deleted accounts: access stops immediately, the stored credentials can no longer be used, and a deleted Google account's grant is revoked with Google (see section 5). The account's data, including its credentials, synced mail, calendars, contacts and stored content, is deleted within 30 days, or at once if the Customer asks for an immediate purge.
• Tracking events: kept 90 days. Sent message records: kept 30 days after sending finishes. Data exports: downloadable for 7 days, then deleted.
• Audit log: kept 365 days. It records actions, not message content.
• Customer workspaces: the workspace owner can erase the workspace, which deletes all of its data and connected accounts.
• Backups: encrypted database backups are kept for up to 35 days, after which deleted data no longer exists in them.

8. Your choices and rights

• Disconnect: end users can revoke workwae's access at any time from the provider's settings (links in section 5) or by asking the Customer whose application they connected. Customers can disconnect accounts in the console or API.
• Access, correction, export and deletion: Customers can export or delete their data in the console and API. End users can contact the Customer whose application they connected, or us at privacy@workwae.com; if we process your data on a Customer's behalf, we will refer the request to that Customer or handle it on their instructions.
• Regional rights: depending on where you live (for example under the GDPR or the California Consumer Privacy Act), you may have the right to know, access, correct, delete or port your information, to object to or restrict processing, and to not be discriminated against for exercising these rights. We do not sell or share personal information for cross-context behavioral advertising. Contact us to exercise any right; we respond within 30 days and may need to verify your identity.

9. International transfers

workwae is based in the United States and processes data there. If you use the Service from elsewhere, your information is transferred to and processed in the United States.

10. Children

The Service is for businesses and is not directed to children under 16. We do not knowingly collect information from them; if you believe a child has provided us information, contact us and we will delete it.

11. Changes to this policy

We will post changes on this page and update the effective date. If a change materially affects how we use data from connected accounts, we will notify Customers in advance and, where required by a provider's policies, ask end users for consent again before the new use begins.

12. Contact

WORKWAE LLC
17350 State Highway 249, Suite 220 #38325
Houston, TX 77064-1142, United States
Privacy: privacy@workwae.com
Support: support@workwae.com