Privacy Policy

Effective date: October 11, 2026

Girderly LLC (“Girderly,” “we,” “us”) respects your privacy. This Privacy Policy explains how we handle information across these contexts: Part A — the Girderly Gmail™ add-on, which surfaces the data from your connected field-service or accounting platform inside Gmail; Part B — the Girderly Outlook add-in, which surfaces that data inside Outlook (Microsoft 365); Part C — the Girderly website at girderly.com and your Girderly account; and Part D — the connected platforms Girderly works with (currently JobTread™, QuickBooks® Online (Intuit), CompanyCam®, and Contractor+®), including how each is authorized and how its credential is stored. By using a Girderly add-in or the Girderly website, you consent to the practices described in this Policy. Girderly is provided by Girderly LLC, a Texas limited liability company.

Girderly connects to one platform at a time — the one you choose and authorize. Throughout Part A and Part B, “your connected platform” means whichever platform you have connected (for example, JobTread, QuickBooks Online, CompanyCam, or Contractor+); the details specific to each platform are in Part D.

Part A — The Girderly Gmail add-on

Girderly is designed to keep your data inside your own Google and connected-platform accounts. The add-on runs on Google’s infrastructure and reaches your connected platform to display your information; except for the actions you explicitly trigger (described next), it does not route your Gmail messages, or the connected-platform records it displays (your contacts, jobs, status, and financials), through a Girderly server. Those exceptions only happen when you ask for them: when you explicitly choose to upload a file attachment from an email to your connected platform; when you explicitly ask Girderly to read a file attachment to capture its figures or identify the related job, contact, or vendor in your connected platform; when you explicitly ask Girderly to summarize an email you have open or a file attachment on it, or use another AI feature; and when you explicitly log an email, or save a note, to a record in your connected platform. In each case the content passes through Girderly’s servers only momentarily to perform the action you requested and is not retained afterward — for an AI feature, the content is sent transiently to Girderly’s AI provider to generate the result (see “Summarizing an email or an attachment, and other AI features” below). Two limited items are also sent to Girderly’s licensing and support service — your Google account email address, and, when you first connect your platform, a minimal connection signal — each described below. Connecting to your platform uses that platform’s own authorization screen (OAuth) or, for a platform that issues an API key, a key you paste in Settings; the resulting credential is held only to call that platform on your behalf. How each platform’s credential is stored, and what Girderly reads and writes there, is described in Part D.

Google user data Girderly accesses

Girderly requests the narrowest Google account permissions it needs to work. The Google user data it accesses is limited to the following:

• The email message you currently have open. Girderly uses the gmail.addons.current.message.readonly permission, which lets the add-on read the single message you are viewing while you interact with it. Girderly uses that message only for actions you explicitly take on it: (1) the sender’s email address, read the moment you open the email, so it can identify which contact, vendor, job, customer, or project the message relates to in your connected platform; (2) a file attachment that you explicitly choose to upload to your connected platform, or that you explicitly ask Girderly to read to capture its figures, or to identify the related job, contact, or vendor, in your connected platform (see “Attaching email files” and “Reading an attachment” below); (3) the message content, when you explicitly ask Girderly to summarize the open email (or a file attachment on it) or use another AI feature on it (see “Summarizing an email or an attachment, and other AI features” below); and (4) the message content — its subject and body — when you explicitly log the email, or save a note, to a record in your connected platform (see “Logging an email” below). Girderly reads the message body only to produce the AI result you request, or to log the email or save a note when you ask; it does not read subject lines or labels for any other purpose, does not read attachments except one you explicitly choose to upload, to capture figures or the related record from, or to summarize, and never reads, searches, or lists your mailbox as a whole.
• Your Google account email address. When you use the add-on, Girderly reads your Google account email address through Google’s OpenID Connect sign-in (the openid and userinfo.email permissions), so it can identify your account for subscription and licensing. This method is required because a published add-on must reliably identify signed-in users by email. Girderly does not read your name, photo, or any other profile information.

That is the complete set of Google user data Girderly can access. Girderly requests no Google “restricted” scopes and accesses no other Google service data.

How Girderly uses Google user data

• The sender’s email address is used solely to look up the matching record in your connected platform and display it in the Gmail sidebar. It is used only at the moment you open the message and is not retained afterward, except that for some platforms Girderly keeps a limited index of your records’ contact email addresses and identifiers so it can match a sender quickly — see Part D.
• A file attachment you choose to upload is read only at the moment you click to attach it, and is used solely to deliver it to your own connected-platform account. It passes through Girderly’s servers momentarily and is deleted immediately after the upload completes — see “Attaching email files” below.
• An attachment you ask Girderly to read is read only at the moment you ask, and is used solely to extract the amounts, or identify the related record, for you to review and save. It is processed only transiently, on Girderly’s own servers, and is not retained; it is not sent to any third party or any AI provider except where you additionally ask Girderly to summarize it — see “Reading an attachment” below.
• The message content is read when you explicitly use an AI feature (for example, to summarize the open email or a file attachment on it), and is used solely to generate the result you requested. It is sent transiently to Girderly’s AI provider to produce that output and is not retained by Girderly afterward — see “Summarizing an email or an attachment, and other AI features” below.
• The message content — its subject and body is also read when you explicitly log the email, or save a note, to a record in your connected platform, and is used solely to post it there. It passes through Girderly’s servers only momentarily to reach your platform, is not sent to any AI provider, and is not retained by Girderly afterward — see “Logging an email” below.
• Your Google account email address is used to identify your account and to establish and manage your free trial and subscription. For this purpose it is sent to Girderly’s licensing service and stored on our servers (see Part C). It is not used to read your mail.
• Girderly does not use Google user data for advertising, does not sell or rent it, does not transfer it to anyone except as needed to provide the feature you request, and does not use it to develop, improve, or train generalized artificial-intelligence or machine-learning models. This use complies with the Google API Services User Data Policy, including the Limited Use requirements.

Attaching email files

When you choose to attach a file from an email to a record in your connected platform — an explicit action you take, one file at a time — Girderly reads that email attachment and uploads it to your connected-platform account. To complete the transfer, the file passes through Girderly’s servers only momentarily and is deleted immediately after it is delivered. Girderly does not retain the attachment and uses it only to perform the upload you requested. Girderly never uses it for advertising, does not sell it, does not review it manually, and does not use it to train artificial-intelligence or machine-learning models. Girderly’s use of information received from Google APIs for this feature adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Reading an attachment

When you explicitly ask Girderly to read a file attachment to capture its figures, or to identify the related record, in your connected platform — an action you take, one file at a time — Girderly extracts the text from that file to produce the amounts or the related record, which you review before saving. The file is processed only transiently, on Girderly’s own servers, and is not written to any lasting Girderly database, cache, or log. For this figure-capture and record-resolution, the file and the text extracted from it are not sent to any third party and are not sent to any AI provider. If you additionally ask Girderly to summarize the attachment, the extracted text is sent to Girderly’s AI provider as described under “Summarizing an email or an attachment, and other AI features” below — that is the only case in which an attachment’s content leaves Girderly’s own servers. Girderly does not retain the attachment or the text extracted from it, does not sell it, does not review it manually, and does not use it to train or improve artificial-intelligence or machine-learning models. Girderly’s use of information received from Google APIs for this feature adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Summarizing an email or an attachment, and other AI features

When you explicitly use one of Girderly’s AI features — to summarize an open email or a file attachment on it, to catch you up on a customer or job, to answer a question, to draft a reply, to draft a payment follow-up, or to turn an email into suggested action items — Girderly generates the result you asked for, which you can save to your connected platform. To generate it, the content is sent over an encrypted (TLS) connection to Girderly’s AI provider, OpenAI. That content is the email’s text and, when you choose to summarize an attachment, the text Girderly extracts from that attachment on its own servers (never the raw file); and, for features that draw on your connected platform (such as catching you up, answering, or drafting a payment follow-up), a snapshot of the related record from your connected platform — for example its contact details, invoices, balances, and recent transactions — is included in what is sent to OpenAI. The content is processed only transiently, in memory, to create the output; it is never written to any Girderly database, cache, or log. OpenAI receives text only, does not use it to train or improve any artificial-intelligence or machine-learning models, and may retain it for a short period (up to 30 days) solely to detect and prevent abuse of its service, with no human review except where its automated systems flag content for review to investigate abuse, or where the law requires it. Girderly itself does not retain the content, sell it, use it for advertising, or review it manually. Nothing is written to your connected platform unless you click to save the result. Where your connected platform’s provider requires it (for example, QuickBooks Online), Girderly asks for your consent, and shows you what will be shared, before any AI feature uses that platform’s data. Girderly’s use of information received from Google APIs for these features adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Logging an email

When you explicitly choose to log an open email, or save a note, to a record in your connected platform — a job, customer, project, or vendor — Girderly saves the email or note (and, where supported, a text attachment of it) to that record in your own connected-platform account, so you have a record of the correspondence there. To do so, the content passes through Girderly’s servers only momentarily; it is not written to any lasting Girderly database, is not sent to any AI provider, and is not retained by Girderly after it is posted. It is used only to create the entry you asked for. Girderly never uses it for advertising, does not sell it, does not review it manually, and does not use it to train artificial-intelligence or machine-learning models. Girderly’s use of information received from Google APIs for this feature adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Other information the add-on handles

• Your connected-platform authorization. You connect Girderly to your platform through that platform’s own authorization screen (OAuth), or by pasting an API key the platform issues you. The resulting access credential is used only to call your connected platform on your behalf. It is not Google user data. How and where it is stored is described in Part D; where Girderly stores it on its own servers, it is encrypted at rest, kept in a record isolated to your account, and is not readable by Girderly’s application users or by other customers. Girderly does not use it for any purpose other than making the connected-platform requests you ask the add-on to make.
• Connected-platform data. Using your authorization, Girderly retrieves contact, job, status, and financial information from your connected platform and displays it in the Gmail sidebar. It fetches this data on demand to render the card; it does not store this data durably, though for some platforms it holds it briefly in a short-lived cache and keeps a limited sender-to-record index, as described in Part D.
• Connection signal. When you first connect your platform, the add-on sends Girderly a one-time connection signal about your own account: your Google account email address, which email platform you use, your connected platform’s organization identifier and role, and your own name from your connected-platform profile, together with the date you connected. We store this with your account record (see Part C) so we can confirm your setup is complete, address you by name in your account and in the messages we send you, help you if you contact support, and understand how many installs complete setup. Only your own profile is used this way. Your access credential is never included in this signal, and none of your connected-platform contacts, jobs, or financial data — and no other person’s information — is sent or stored. This information is used only to run and support the product; it is never used for advertising. You can ask us to delete your name and connection details at any time by emailing legal@girderly.com.

How Girderly protects your information

• Encryption in transit. All data Girderly handles travels over encrypted HTTPS/TLS connections — between Gmail, Girderly’s add-on code, Girderly’s servers, and your connected platform’s API.
• No lasting server-side copies of your Gmail message data. Girderly does not store your Gmail message data. The sender’s email address is processed transiently to render the card. A file attachment you choose to upload, an attachment you ask Girderly to read, the content of an email or attachment you ask Girderly to summarize or use another AI feature on, and an email or note you log are each processed only transiently to perform the action you requested and are not written to any lasting Girderly database, cache, or log — with the AI exception that content you submit to an AI feature is sent to Girderly’s AI provider as described above. (Your Google account email address is handled separately — for licensing and trial/subscription management — as described above and in Part C.)
• Your connected-platform credential is encrypted and isolated to you. Where Girderly stores your connected-platform credential on its servers, it is stored in encrypted form (AES-GCM at rest), in a record keyed to your account, accessible only to the Girderly service that calls your platform on your behalf, with the decryption key held separately. Girderly does not use the credential for any purpose other than the connected-platform requests the add-on makes for you. Storage differs by platform — see Part D.
• Least privilege. Girderly requests read access only to the single message you currently have open (gmail.addons.current.message.readonly) — enough to resolve the sender, upload or read an attachment you choose, use an AI feature when you ask, and log an email or save a note when you ask — and no other Gmail access. It requests no “restricted” scopes and cannot read, search, or list the rest of your mailbox.
• Revocable at any time. Selecting Disconnect in the add-on erases the connected-platform credential and settings Girderly holds for you and, where the platform supports it, revokes Girderly’s access with that platform; you can also revoke Girderly from within your connected platform. Uninstalling the add-on stops Girderly from running. Where Girderly stores a credential on its servers, it additionally deletes any stored credential automatically once it has gone unused for 90 days, along with any incomplete connection records. To delete the name and connection details Girderly keeps with your account record, email legal@girderly.com.

Google API Limited Use

Girderly’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Girderly uses the Gmail message data it accesses — the sender’s address; any attachment you choose to upload, or to read so Girderly can capture its figures or identify the related record (which Girderly performs on its own servers); and, when you request it, the content of an email or attachment used by an AI feature, and the content used to log an email or save a note — solely to provide the in-product features you request. Girderly does not sell this data or use it for advertising, and neither Girderly nor its AI provider uses it to train or improve generalized artificial-intelligence or machine-learning models. Girderly transfers this data only as necessary to provide a feature you request — for AI features, to its AI provider (OpenAI), which receives text only (never the raw attachment file), processes it to return the result, does not use it for model training, and permits human review only to investigate abuse of its service or where required by law; and for the attach-file, record-resolution, and log/note features, to your own connected platform (not to any AI provider). Girderly does not manually review this data.

Part B — The Girderly Outlook add-in

This part describes the Girderly add-in for Outlook (Microsoft 365). The Outlook add-in surfaces your connected-platform data on the email you have open, the same way the Gmail add-on does, but it uses a different technical model — described here on its own, not by reference to Part A. The Outlook add-in requests only the Office ReadItem permission. It uses no Microsoft Graph permissions, and it does not use a Microsoft sign-in — you are not asked for your Microsoft credentials.

What the Outlook add-in reads

Using the Office ReadItem permission, the add-in reads the message you currently have open, and uses it only for the actions you explicitly take: (1) the sender’s email address, to look up the matching record in your connected platform and display it to you; (2) the message content, when you explicitly use one of Girderly’s AI features on the open message — to summarize it, to catch you up, to answer a question, to draft a reply, to draft a payment follow-up, or to turn it into to-dos (see “Girderly AI features” below); (3) the message content — its subject and body — when you explicitly log the email or save a note to a record in your connected platform (see “Logging an email” below); (4) a file attachment that you explicitly choose to upload to your connected platform (see “Attaching a file” below); and (5) a file attachment that you explicitly ask Girderly to read to capture its figures, or to identify the related record, in your connected platform (see “Reading an attachment” below). It reads the message body only to produce the AI output you request or to log an email or save a note when you ask, and it reads an attachment only to upload it, to capture its figures or the related record, or to summarize it when you ask. It does not read your contacts, does not read attachments except one you explicitly choose to upload, to capture figures or the related record from, or to summarize, and never reads, searches, or lists your mailbox as a whole. The sender’s address is used only at the moment you open the message and is not retained by Girderly.

Girderly AI features

When you explicitly use one of Girderly’s AI features on an open email — to summarize the email or a file attachment on it, to catch you up on a customer or job, to answer a question, to draft a reply, to draft a payment follow-up, or to turn it into suggested action items — Girderly generates the output you asked for, which you can save to your connected platform. To generate it, the content is sent over an encrypted (TLS) connection: it passes transiently through Girderly’s own service — where it is held only in memory to complete your request and is never written to any Girderly database, cache, or log — and on to Girderly’s AI provider, OpenAI. That content is the email’s text and, when you choose to summarize an attachment, the text Girderly extracts from that attachment on its own servers (never the raw file); and, for features that draw on your connected platform, a snapshot of the related record from your connected platform — for example its contact details, invoices, balances, and recent transactions — is included in what is sent to OpenAI. OpenAI receives text only, does not use it to train or improve any artificial-intelligence or machine-learning models, and may retain it for a short period (up to 30 days) solely to detect and prevent abuse of its service, with no human review except where its automated systems flag content for review to investigate abuse, or where the law requires it. Girderly itself does not retain the content, sell it, use it for advertising, or review it manually; nothing is written to your connected platform unless you save the result. Where your connected platform’s provider requires it (for example, QuickBooks Online), Girderly asks for your consent, and shows you what will be shared, before any AI feature uses that platform’s data.

Logging an email

When you explicitly choose to log an open email or save a note to a record in your connected platform, Girderly saves the email or note (and, where supported, a text attachment of it) to that record in your own connected-platform account. The content is processed only transiently to do so; it is not written to any lasting Girderly database, cache, or log, is not sent to any AI provider, and is not retained by Girderly afterward. It is used only to create the entry you asked for.

Attaching a file

When you explicitly choose to attach a file from an email to a record in your connected platform — one file at a time — Girderly reads that attachment and uploads it to your connected-platform account using your authorization. To complete the transfer, the file passes briefly through Girderly’s own file service and is deleted immediately after delivery. Girderly does not retain the attachment, does not send it to any AI provider, does not sell it, does not review it manually, and does not use it to train artificial-intelligence or machine-learning models.

Reading an attachment

When you explicitly ask Girderly to read a file attachment to capture its figures, or to identify the related record, in your connected platform, the attachment is sent over an encrypted (TLS) connection to Girderly’s own extraction service, hosted on Girderly’s own infrastructure (not a third party and not an AI provider), which extracts the text in memory to produce the amounts or the related record you review before saving, and does not retain the file or the extracted text. Nothing is written to any lasting Girderly database, cache, or log. If you additionally ask Girderly to summarize the attachment, the extracted text is sent to Girderly’s AI provider as described under “Girderly AI features” above — that is the only case in which an attachment’s content leaves Girderly’s own infrastructure. Girderly does not sell it, review it manually, or use it to train artificial-intelligence or machine-learning models.

Connecting your platform

You connect Girderly to your platform through that platform’s own authorization screen (OAuth), which opens in an Office dialog, or by pasting an API key the platform issues you. You do not enter your Microsoft credentials. Where the credential is stored differs by platform and is described in Part D. For some platforms the Outlook add-in stores the credential in your own Outlook mailbox (Office roaming settings); for others, Girderly holds the credential on its servers, encrypted at rest. Part D states which applies to each platform.

After you connect

Once connected, the add-in reaches your connected platform, using your authorization, to fetch and display the information related to the open message, and to make the changes you request. Other than the actions you explicitly trigger — the AI features described above (where the content, and for some features a snapshot of the related connected-platform record, passes transiently to Girderly’s AI provider and is not retained); logging an email or saving a note; uploading a file attachment you choose; and reading an attachment you ask Girderly to read (each processed only transiently and not retained) — Girderly does not receive, store, or retain your connected-platform data or your message content, except for the short-lived cache and limited sender-to-record index described in Part D. Your connected-platform information stays in your account and is shown only to you.

Account, billing, and licensing

Your Girderly subscription, free trial, and account records are handled as described in Part C, and billing is processed by our merchant of record, Polar. For an Outlook user, the email address that identifies your seat and subscription is your Microsoft (Microsoft 365) account email rather than a Google account email. Girderly does not use any Outlook add-in data for advertising or marketing, does not sell it, and does not use it to train artificial-intelligence or machine-learning models.

Part C — The Girderly website and your account

This part covers information handled through the Girderly website at girderly.com — including our contact, trial-request, and support forms, our website chat assistant, analytics, advertising, your interactions with us on social media, and your billing and marketing relationship with us. It does not expand what the Girderly add-ins can access; their data handling is described in Part A, Part B, and Part D above. We never use the Girderly add-in data described in Part A, Part B, and Part D for analytics, advertising, or marketing.

Information you provide to us

Depending on how you interact with the website, you may provide:

• Contact and sales inquiries. When you use our contact form or request a demo or trial, we collect your name, email address, and the contents of your message, and — where the form asks for it — your company name and phone number.
• Support requests. When you submit our “Report an Issue” form, we collect your name, email address, the Google or Microsoft account you use with Girderly, the issue type, and your description of the problem.
• Feature requests. If you send us a feature request, we collect your name, email, company (if provided), and the request itself.
• Website chat assistant. If you use the chat assistant on our site, we store the messages you send and our responses, together with basic technical details of the session (see below). Please do not enter passwords, API keys, or other sensitive information into the chat.
• Account and billing details. If you subscribe, we maintain your subscription record — the email address associated with your subscription and each seat, your plan, and its status.

Information collected automatically

When you visit the website, we and our service providers may automatically collect your IP address, browser type and user agent, the page you visited, the referring URL, and date/time stamps; standard visitor statistics collected by our website host and its built-in analytics; analytics data via Google Analytics; and, unless you opt out, online identifiers used for analytics and advertising (see “Analytics and advertising” below).

Social media and community interactions

We maintain a presence on social media and community platforms — for example, Instagram, LinkedIn, Facebook, and groups for the contractor community. When you interact with us there, we may collect and store your public profile information (such as your username or handle and your profile link), the content of your comment, message, or review, and related details such as the platform and the date. We use a social-media management provider (Metricool) to gather and organize these interactions. We use this information to respond to you and provide support, to understand feedback and sentiment about Girderly, to engage with and grow our community, and to identify people who may be interested in Girderly. This information reflects your public activity on those platforms, and your use of each platform remains governed by that platform’s own terms and privacy policy. If you would like us to remove information about you that we obtained from social media, please contact legal@girderly.com.

Combining information about you

To recognize you across the different ways you interact with us, we may link and combine this information into a single profile. We tag each piece of information with how we are permitted to use it, and we honor those limits. In particular, information from the Girderly add-ins (Part A, Part B, and Part D) is never combined into marketing profiles or used for advertising. You can ask us to access or delete the profile we hold about you at any time by emailing legal@girderly.com.

Cookies

Our website uses cookies and similar technologies to operate the site, remember your preferences, measure usage (including through Google Analytics and our website platform’s built-in statistics), and support advertising. Cookies fall into essential, analytics, and advertising categories; you can accept or decline non-essential cookies through our cookie controls, and most browsers let you refuse or delete cookies. If you decline, some parts of the site may not work as intended. The Girderly add-ins themselves do not use cookies.

Analytics and advertising

We use Google Analytics and advertising partners (including Google) to understand how our site is used, measure our marketing, and show you relevant ads on other sites and services, including retargeting. These partners may set cookies and receive online identifiers associated with your device or browser. Some U.S. state privacy laws treat this kind of sharing for cross-context behavioral advertising as a “sale” or “share” of personal information; we do not receive money for it. You can opt out at any time — see “Your privacy rights and choices” below. We never use data from the Girderly add-ins (Part A, Part B, and Part D) for analytics or advertising.

How we use website and account information

We use the information above to respond to your inquiries and provide customer support; provide, administer, and secure your Girderly subscription and account; operate, maintain, and improve the website and the product; detect and prevent spam, fraud, and abuse; engage with our community and understand feedback about Girderly; send you service-related messages and, where permitted, newsletters, announcements, and marketing email; and to advertise and market our products, including through analytics and advertising partners. We do not use this information to make automated decisions that produce legal effects about you, and we never use Girderly add-in data (Part A, Part B, and Part D) for marketing or advertising.

Billing

Subscription payments are processed by our third-party merchant of record, which handles the transaction and payment-card details on our behalf. Girderly does not receive or store your full payment-card number. We retain the subscription and seat information needed to provide and account for your subscription.

Free trial and account lifecycle

When you start Girderly’s free trial or subscribe, we record the email address of the Google or Microsoft account you use with Girderly and related dates in our systems so we can provide and manage your trial and subscription, confirm your access, send you trial- and account-related messages, and understand conversion. This information is stored with our database provider (Supabase) and, where you have not opted out, may be used to send you the trial and onboarding emails described under “Email and marketing communications.” You can opt out of marketing at any time.

When you connect a platform, we also record that you have connected, your connected platform’s organization identifier and role, your own name from your connected-platform profile, and the date of connection, so we can confirm your setup, address you by name, provide support, and measure how many installs complete setup. We do not store your connected-platform contacts, jobs, or financial data durably, except the short-lived cache and limited sender-to-record index described in Part D; we do not store any other person’s information. Your access credential is stored as described in Part D. These records are stored with our database provider (Supabase). You can ask us to delete your name and connection details at any time by emailing legal@girderly.com.

Email and marketing communications

We send service messages (such as confirmations, security notices, and account or subscription updates) that are necessary for your account. We also send newsletters and marketing email — for example, to people who start a trial or ask to hear from us — using our email provider (Resend). Every marketing message includes an unsubscribe link, and you can opt out of marketing at any time; opting out will not affect service messages related to your account. Our email provider may record whether you open a message or click a link so we can gauge interest and improve our communications.

Service providers we use

We share information with a limited set of service providers who process it only to provide services to us and are required to protect it:

• WordPress.com (Automattic) — hosts girderly.com, provides visitor statistics, and provides Akismet spam filtering for our web forms.
• Google Analytics (Google) — website usage analytics and measurement.
• Advertising partners (including Google and Meta Platforms) — measurement and advertising, including retargeting on other sites and services.
• Supabase — the database that stores your form submissions, support tickets, feature requests, chat-assistant logs, account and subscription lifecycle records, your connection records, your encrypted connected-platform credentials (including, for QuickBooks Online, your Intuit company ID and user ID and encrypted Intuit access and refresh tokens, and a monthly per-company read count), a limited sender-to-record index used to match email senders to your customers or projects, your combined profile and social-interaction records, and the short-lived record used to complete a connected-platform authorization.
• Render — hosts our customer-management application and the backend services that connect to your platforms and run the AI features, including the short-lived cache used to render cards.
• Polar (our merchant of record) — processes subscription payments; card processing is handled by Stripe.
• Resend (Plus Five Five, Inc.) — our email delivery provider.
• Metricool — gathers and manages our social-media and community interactions.
• Google Workspace / Gmail — our support and business mailboxes receive and store correspondence you send us.
• OpenAI — our AI provider; generates responses in the website chat assistant, and generates the summaries, answers, catch-ups, drafted replies and payment follow-ups, and suggested action items you request in the Girderly add-ins, from the content you submit. For add-in AI features it receives the email’s text and, for features that draw on your connected platform, a snapshot of the related record from that platform (for example, QuickBooks customer, invoice, balance, and transaction details). It receives text only (never a raw attachment file), is sent the request with retention turned off, and does not use that content to train its models.

On the product side, the Girderly add-ins communicate with your connected platform (currently JobTread, QuickBooks Online, CompanyCam, or Contractor+) using your own authorization, as described in Part A, Part B, and Part D.

How we share information

We do not sell your personal information for money. We share it only: (a) with the service providers listed above; (b) with analytics and advertising partners for measurement and advertising as described in “Analytics and advertising,” which some U.S. state laws treat as a “sale” or “share” of personal information (you can opt out — see below); (c) when required to do so by law, legal process, or a lawful government request, or to protect the rights, property, or safety of Girderly, our users, or the public; and (d) in connection with a merger, acquisition, financing, or sale of assets, in which case we will require the recipient to honor this Policy or notify you of any material change. We never share Girderly add-in data (Part A, Part B, and Part D).

Data retention and deletion

We keep website and account information for as long as needed to provide the service, maintain your account, meet our legal and accounting obligations, and resolve disputes, after which we delete or anonymize it. You may ask us to access, correct, or delete the information we hold about you, including your connected-platform connection details, by contacting legal@girderly.com; we will respond consistent with applicable law. Data handled by the Girderly add-ins is governed by Part A, Part B, and Part D. Your access credential is held as described in Part D; you can erase it immediately using Disconnect.

Your privacy rights and choices

Depending on where you live (including California), you may have the right to: access or know the personal information we hold about you; delete it; correct it; opt out of the “sale” or “sharing” of your personal information and of targeted advertising; limit the use of sensitive personal information; port your information; and not be treated differently for exercising these rights. To exercise a request, email legal@girderly.com or use the choices below. We will take reasonable steps to verify your identity and will respond within 45 days (we may extend once by another 45 days and will tell you if we do). You may use an authorized agent with your written permission.

Your privacy choices — opting out

• Marketing email. Use the unsubscribe link in any marketing message, or email legal@girderly.com.
• Analytics and advertising. Decline non-essential cookies through our cookie controls or your browser settings to opt out of analytics and advertising.
• Global Privacy Control (GPC). We treat a GPC browser signal as a request to opt out of the “sale” or “sharing” of your personal information for the browser that sends it, where required by law.

Do Not Track

Some browsers offer a “Do Not Track” (DNT) signal. Because there is no common industry standard for DNT, our website does not currently respond to DNT signals; however, we honor Global Privacy Control (GPC) signals as described above.

Sensitive personal information

We do not seek to collect or process “sensitive personal information” as defined under applicable privacy laws (such as government identifiers, precise geolocation, health, or biometric data). Please do not submit such information to us through the website, the chat, or a social-media message.

International users and data transfers

Girderly is based in the United States, and the information handled under this Part C is stored and processed in the United States and in other countries where we or our service providers operate. If you access the website or provide information to us from outside the United States, you understand that your information will be transferred to, stored, and processed in the United States, which may have data-protection laws different from those in your country. Where required for transfers of personal information from the European Economic Area, the United Kingdom, or Switzerland, we rely on appropriate safeguards, such as the European Commission’s Standard Contractual Clauses (together with the UK International Data Transfer Addendum), with the service providers that process the information.

Legal bases for processing (EEA and UK)

If you are in the European Economic Area (EEA), the United Kingdom, or Switzerland, we process your personal information on one or more of the following legal bases: to perform a contract with you or take steps at your request before entering into one; our legitimate interests in operating, securing, marketing, and improving our business and the website, weighed against your rights and interests; your consent, which you may withdraw at any time; and compliance with our legal obligations.

Your rights in the EEA, UK, and Switzerland

If you are in the EEA, the UK, or Switzerland, in addition to the choices described above you may have the right to request access to, and rectification or erasure of, your personal information; to restrict or object to our processing of it; to data portability; and to withdraw any consent you have given. To exercise these rights, email legal@girderly.com. For this personal information, the data controller is Girderly LLC. You also have the right to lodge a complaint with your local data-protection supervisory authority — in the UK, the Information Commissioner’s Office (ICO); in the EEA, your national supervisory authority. We will not treat you differently for exercising these rights.

Security

We take reasonable measures to protect your information, including encryption in transit (HTTPS/TLS), encryption at rest for any stored connected-platform credential, access controls, and reputable service providers. However, no method of transmission over the Internet or method of electronic storage is 100% secure, and we cannot guarantee absolute security.

Links to other sites

The website may link to sites we do not operate, including JobTread, QuickBooks Online (Intuit), CompanyCam, Contractor+, Google, and Microsoft. We are not responsible for the content or privacy practices of those sites, and we encourage you to review their privacy policies.

Children

Girderly is a business tool intended for adults. The Service is not directed to, and we do not knowingly collect personal information from, anyone under 18. If you are under 18, please do not use the Service or provide us with personal information. If we learn that we have collected personal information from someone under 18, we will delete it.

Changes to this Policy

We may update this Policy from time to time. Material changes will be reflected by updating the effective date above and, where appropriate, by a more prominent notice on the site.

Contact

Girderly LLC, Austin, Texas, USA. Questions about this Policy: legal@girderly.com.

Part D — Connected platforms

Girderly connects to one platform at a time, using an authorization you grant through that platform’s own authorization screen (OAuth) or an API key the platform issues you. This part describes, for each supported platform, how Girderly connects, what credential it holds and where, the access it uses, and how you disconnect. What the add-in reads from your email, and how the AI, attach-file, read-attachment, and log/note features work, is the same regardless of platform and is described in Part A (Gmail) and Part B (Outlook) above.

JobTread

You authorize Girderly through JobTread’s own authorization screen (OAuth), and Girderly receives a JobTread access credential (a grant key). For the Gmail add-on, Girderly stores that credential on its servers, encrypted at rest (AES-256-GCM), in a record keyed to your Google account identifier. For the Outlook add-in, the credential is stored in your own Outlook mailbox (Office roaming settings) rather than on Girderly’s servers, with a single-use hand-off that passes through Girderly’s connection service (connect.girderly.com) exactly once and is deleted the moment the add-in claims it. Using that authorization, Girderly calls the JobTread API directly to display your contacts, jobs, status, and financial information and to make the changes you request. You can revoke access at any time with Disconnect in the add-in, or from your JobTread profile under Grants. JobTread is your separate service, governed by your own agreement with JobTread; Girderly claims no ownership of your JobTread data.

QuickBooks Online (Intuit)

You authorize Girderly through Intuit’s own authorization screen (OAuth 2.0; scopes: QuickBooks accounting data, plus openid, profile, and email to identify you). Only a QuickBooks company admin can connect. Girderly stores your QuickBooks connection — your Intuit company ID, your Intuit user ID, and your access and refresh tokens — on its servers, encrypted at rest (AES-GCM); the add-ons themselves hold only a rotating link token. All QuickBooks calls are made by Girderly’s server, which reads your QuickBooks data live — customers, vendors and contractors, jobs and projects, invoices, bills, balances, and payments — to show the card to you only. Girderly does not store your QuickBooks business data durably. It holds it briefly in a short-lived cache (up to 24 hours to match an email sender to a customer, and 15 minutes or less for card details), and keeps only a monthly count of reads per company. Girderly writes to QuickBooks only when you click to do so — for example, “Log email” and “Add note” save a text attachment of the email or note, plus a dated line in the record’s Notes field, into your own QuickBooks company (on a project, to the parent customer, labeled with the project). The AI features send the open email, and a snapshot of the related customer’s or job’s QuickBooks data, to Girderly’s AI provider as described in Part A and Part B, and only when you ask; before any AI feature uses your QuickBooks data, Girderly asks for your consent and shows you what will be shared. You can disconnect at any time in Girderly’s Settings, or from the Apps page in QuickBooks; disconnecting revokes Girderly’s Intuit token and deletes the connection. Girderly is not affiliated with Intuit, is not listed in the Intuit App Store, and does not process your QuickBooks data on Intuit’s behalf. QuickBooks Online is your separate service, governed by your agreement with Intuit (including Intuit’s Global Privacy Statement); Girderly claims no ownership of your QuickBooks data.

CompanyCam

You authorize Girderly through CompanyCam’s own authorization screen (OAuth). Girderly stores your CompanyCam connection — your access and refresh tokens — on its servers, encrypted at rest (AES-GCM); the add-ons hold only a rotating link token and exchange it for a short-lived access token to call CompanyCam. Using that authorization, Girderly resolves the email sender to a CompanyCam project and displays project details (such as contact, address, status, labels, and photos), and, at your direction, makes the changes you request (for example, adding a note or label). To match a sender to a project quickly, Girderly keeps a limited index of your projects’ contact email addresses and identifiers; it does not otherwise store your CompanyCam business data durably. You can disconnect at any time, which revokes Girderly’s access and deletes the connection. CompanyCam is your separate service, governed by your agreement with CompanyCam; Girderly claims no ownership of your CompanyCam data.

Contractor+

You connect Girderly to Contractor+ by pasting, in Girderly’s Settings, an API key that Contractor+ issues for your workspace. Girderly stores that key on its servers, encrypted at rest (AES-GCM), in a record keyed to your account; the add-ons hold only a rotating link token. Because the key authorizes your Contractor+ workspace, it lets Girderly act for that workspace; revoking or regenerating it in Contractor+ ends Girderly’s access for everyone who shares it. Using that key, Girderly reads your Contractor+ clients, projects, and jobs to show the card, and, at your direction, makes the changes you request (for example, saving a note or attaching a file to a job). To match a sender to a client quickly, Girderly keeps a limited index of your clients’ contact email addresses and identifiers; it does not otherwise store your Contractor+ business data durably. You can disconnect at any time in Girderly’s Settings, which deletes the stored key and the connection. Contractor+ is your separate service, governed by your agreement with Contractor+; Girderly claims no ownership of your Contractor+ data.