This notice says what Workgraph, Inc (“we”) collects, why, who can read it, and how to reach us. Last updated 30 September 2026.
Account. Your work email address, a display name, and the company you register or join. We verify email ownership with a sign-in link. Room accounts have no password.
Content you contribute. Files, links and text you provide, any access you give us to them, selected records you import from connected tools, your needs and offers, generated briefs and claims, introduction decisions, and shared chat messages. We also retain content and records for existing Room workflows. Content is associated with its owning account and the permissions recorded for its use.
Records. Who approved what and when, provider calls, and disclosure and delivery events. Records are how the product works; they are retained with the Room.
Technical data. Server logs with IP addresses and request metadata, kept for security and operations.
Feedback and usage. Ratings and feedback you give on drafts, matches and introductions, and records of how the service is used. We use them, and aggregated or de-identified data that does not identify you or your company, to operate and improve the service.
Product analytics. Our server records these steps with PostHog, a product analytics processor, in the United States: arriving from a campaign link, requesting a sign-in link, signing in, starting and completing a tool connection, saving a document or link, and submitting a brief. Each record holds the step name, the time, the campaign tag from the link, the sign-in method or tool name, whether a saved item was a document or a link, whether the account was new, the profile type, and either a random browser identifier or a one-way hash of your account identifier. It holds no email address, name, file, link address, title, brief text, tool content or IP address from your browser, and no page content or recordings. Two first-party cookies carry this: room_a holds the random identifier for up to 180 days, and room_c holds the campaign tag for up to 30 days. Signing out clears both. We set neither and record nothing when your browser sends Do Not Track or Global Privacy Control. Turning analytics off here stores off in room_a for 180 days, which signing out keeps.
Connecting a tool, selecting an import or otherwise providing content authorizes us to obtain and store it. When Room offers saving alone, that action grants no model processing, staff review or matching permission. Those uses require a separately recorded processing agreement; existing agreements keep their original scope. Background discovery can use admitted context before you create or approve a brief. You separately approve outward wording. Counterparties receive only authorized representations before acceptance; identities and a shared chat are released after both sides accept. Existing Room workflows retain their recorded permissions. We do not sell content or use it to train models.
Model providers. The recorded processing agreement names the provider, model, purpose and reviewers. Connected-context processing sends bounded evidence and derived company context to OpenRouter and Microsoft Azure for the selected GPT-6 Astra model. Room staff review drafts before releasing them to you; a separate review checks proposed outward content. Existing Room prompts use their declared provider and approved inputs. An external provider reads whatever is sent to it and processes it under its own terms.
Hosted execution. Ordinary Runs execute on infrastructure we operate. We do not claim operator blindness for those Runs: the service operator can technically read data processed there. Each record states the execution venue.
Connected tools. You authorize a provider connection, then a specific import scope. Some provider permissions cover more than the selection room imports; the selection screen explains this. Credentials are encrypted in the connector vault and are not included in evidence or model prompts. Google Drive’s file picker receives a short-lived access token in your browser. The recorded connected-context agreement includes staff review of processed context and drafts.
Google data. Room's use and transfer of Google API data complies with the Google API Services User Data Policy, including its Limited Use requirements. These commitments also apply to information derived from Google data. We use this information to provide the features you authorize in Room. We do not use it for advertising, sell it, or use it to train models. Transfers are limited to delivering authorized features, security needs, legal requirements, or a business transfer with your prior consent. Human access requires your affirmative agreement for the specific data, a security need, a legal requirement, or an applicable aggregate-data exception under that policy. Disconnecting Google stops new imports and leaves saved records in your account; contact us to request deletion. Where the Google-specific limitations in this section conflict with broader data-use permissions elsewhere in this notice or the terms, these Google-specific limitations take precedence.
Credit offers. Founding and referral eligibility reviews require separate permission to read the company profile and selected context. Review decisions and recorded awards are retained. Referral links use a first-party cookie for up to 30 days to carry the referral into signup. When a referral qualifies, the referring business sees its own award amount and date, not the invited business’s identity, context or review notes.
Support chat. The chat window on our home page, sign-in page and app is run by Chatwoot. Messages you send there are stored by Chatwoot and read by Room staff. Before a chat starts we ask for your email so we can reply. When you are signed in, the chat carries your name, email and company instead. Chatwoot stores a cookie in your browser to keep your conversation; signing out clears it.
Email. We send sign-in links and short notices about requests, reviews, and answers waiting for you. Notices contain links, not content. Contact messages you submit, including your account email or the email address you enter and any organization you enter, are delivered by our email service to the Room team so we can reply.
We use hosting, email delivery, support chat, product analytics, and model providers as processors. Each receives only what its function needs. We disclose data when the law requires it. We do not share it with advertisers.
Account data is kept while your account is active. Disconnecting a source removes its saved credential and stops future acquisition and pending claims work that depends on it. It does not delete imported snapshots, established chats or recorded disclosures. Pausing processing stops new brief processing and discovery. Changes within an admitted source scope can be processed under its current agreement. Later source additions are recorded separately and wait behind an active processing pass. Provider-side access withdrawal is detected on a subsequent API call, rather than immediately. To close your account or request deletion of saved content, contact us; we confirm what was removed and what records remain.
You can access, correct, export, or ask us to delete your personal data. Write to us through the contact form. Depending on where you live you may have additional rights under local law; we honor them.
Changes to this notice are posted here with a new date.