Privacy Policy

Who we are and how Lightbulb works

The Lightbulb entities are Lightbulb Partners Pty Ltd (Australia, ABN 93 656 255 784; ACN 656 255 784) and Lightbulb Partners Artificial Intelligence Inc. (Canada). The entity providing your account or contracted service is responsible for the personal information it handles. Contact support@lightbulbpartners.com to identify the responsible entity or make a request. For workspace data, the organization operating the installation generally decides the purposes of processing and who may access it; this policy does not replace that organization's own privacy notice.

The Lightbulb workspace runs in an installation that you or your organization operate, on your own computer or on your organization's server. The installation keeps its data in its own database and file storage: its user accounts, company and project records, documents, conversations with Lightbulb agents, approvals, activity records and the data Lightbulb obtains from connected accounts. The organization that operates an installation decides who can use it, what it keeps and which outside services it may contact. An installation can reach only the internet hosts its administrator allows.

Lightbulb also runs a small number of hosted services on Amazon Web Services (AWS) in the United States:

• our websites, agents.lightbulbpartners.com and accounts.lightbulbpartners.com, which deliver the Lightbulb web interface and these pages;
• Lightbulb accounts at accounts.lightbulbpartners.com, for sign-in, multi-factor authentication, billing and linking installations to an account;
• the connection service, which an installation can use to sign in to providers such as Google, Meta, LinkedIn, X and TikTok with Lightbulb's registered apps, and which keeps the long-lived credential for each such connection in encrypted custody (see How connected accounts work); and
• optional services that an installation administrator can turn on: Managed AI credits and the video export used for posting to TikTok (see AI processing and service providers and TikTok data).

When you use the web interface at agents.lightbulbpartners.com, your browser loads Lightbulb's program code from our website and then exchanges workspace data directly with your installation through a connection window that you approve. That workspace traffic is not routed through our servers. The website code runs in your browser and can read what it displays, so it is part of the software you trust.

Information we process

Lightbulb account information (hosted)

• Your name, email address and password. Passwords are stored only as bcrypt hashes.
• Multi-factor authentication settings, password-recovery requests, and security records such as failed sign-in attempts and ended sessions.
• Billing records, such as your plan, subscription status and purchases of Managed AI credits. Payments are made through Stripe Checkout; we do not receive full card numbers.
• Installations linked to your account, such as device identifiers, public keys and license or seat records.

Workspace data (in your installation)

Profiles of the installation's users, company and project records, documents you upload or create, conversations with Lightbulb agents, approvals, activity and audit records, and data from connected accounts. This data stays in the installation unless the installation sends it to a service described in this policy, such as an AI provider.

Data from connected accounts

When you connect an account, Lightbulb receives OAuth tokens and the account details and content described in the provider sections below.

Our websites

Lightbulb accounts use essential cookies to keep you signed in and protect account requests. AWS CloudFront processes the technical information needed to deliver our hosted product and account pages, such as your IP address, the page requested and your browser type. Our websites remember your selected region and measurement preference in your browser.

Our public marketing website, www.lightbulbpartners.com, uses optional Google Analytics and Google Ads measurement only after your affirmative choice. Use the available Cookie preferences or Measurement preferences controls to change or withdraw that choice. Public acquisition and account links may carry campaign fields and advertising click or linker identifiers with the corresponding consent.

Optional advertising measurement on the dedicated account payment-confirmation page is a separately enabled feature. Where enabled, it requires affirmative advertising consent and a server-verified qualifying new paid subscription. Conversion data is limited to the purchase outcome, an opaque transaction identifier, the actual amount paid and its currency. Enhanced conversions are a separately enabled option that also requires affirmative advertising and user-data consent; where enabled, they use a SHA-256 hash derived from the current customer's verified email address. We do not send raw customer details, credentials or workspace or connected-account content to advertising measurement.

The private workspace and appliance interface do not load optional advertising scripts. Their essential sign-in and security storage is separate from optional public website measurement.

Messages and support

If you contact us, we keep your message and contact details so we can respond. Account emails, such as password-recovery messages, are sent from noreply@lightbulbpartners.com through Amazon Simple Email Service.

How we use information

• to provide the features you use, including connecting accounts and doing the work you or your organization ask Lightbulb to do;
• to authenticate users, keep accounts and installations secure and prevent abuse;
• to process payments and manage subscriptions, licenses and credits;
• to provide support and send service messages; and
• to comply with the law and enforce our terms.

We do not sell personal information, and we do not use data from connected accounts for advertising.

How connected accounts work

You connect an account in the Connector Hub in Lightbulb. The provider shows its own consent screen, where you see and approve the permissions Lightbulb asks for. Depending on the provider and your role, a connection belongs to you alone or is shared with a company, tenant or project.

An installation connects an account in one of two ways:

• Through our connection service. The provider returns you to agents.lightbulbpartners.com, which passes the one-time authorization code to accounts.lightbulbpartners.com. The connection service exchanges the code with the provider and keeps the long-lived credential (a refresh token or, where the provider issues none, a long-lived access token) encrypted with AES-256-GCM, together with the permissions granted and identifiers of the connected account, such as a TikTok account ID. It delivers an access token, sealed so that only your installation can decrypt it, with a local authorization lease limited to 24 hours. The provider token can have a longer lifetime; the local lease does not revoke it at the provider. The service renews authorized access when needed. The temporary records used while you sign in expire after 10 minutes and are then deleted. Apart from the TikTok video export, the connection service does not store the content of your connected accounts.
• Directly from the installation. An installation administrator can instead configure the installation's own provider credentials. The installation obtains and stores the tokens, and they do not pass through our connection service. Available connection methods vary by provider. Google Analytics and Google Ads also support the hosted connection service; Meta Ads uses installation-configured credentials.

Installations store provider tokens encrypted with AES-256-GCM. Lightbulb uses a connection when you or another authorized user of your workspace asks it to do something, such as running a workflow, answering a question or publishing an approved post, and for the automatic copying described in the provider sections. Publishing to a social account waits for approval by a person in your workspace, and posting to TikTok also needs approval from a second person.

Google user data

This section applies when you connect a Google account for Gmail, Google Calendar, Google Drive, Google Docs, Google Sheets, Google Slides, Google Meet or Google Workspace administration, or connect YouTube, Google Analytics or Google Ads. Google's consent screen lists the exact permissions you grant.

What we access and why

• Gmail. Lightbulb reads, lists and searches your messages and threads so it can answer questions about your email, summarize conversations and bring relevant messages into your work. For a mailbox connected for you alone, Lightbulb checks for new messages about once a minute and records each new message's sender, recipients, subject, date, labels and a short snippet. When you link an email to a legal matter, its attachments are added to that matter's documents. Lightbulb also asks for permission to send email, but sending through Gmail is currently turned off.
• Google Calendar. Lightbulb reads your calendars and availability, and creates, changes and deletes events when you ask; Google then emails invitations and updates to attendees. If you use Lightbulb scheduling, your Lightbulb appointments are added to your Google Calendar. For a calendar connected for you alone, Lightbulb copies the events on your primary calendar, from 30 days ago to a year ahead, about every 15 minutes.
• Google Drive. Lightbulb lists, reads and downloads your files so it can find and use your documents, creates or updates files when you ask, and, when you use it to deliver a file to a customer, can give that customer view access. About every 15 minutes it copies file details (names, types, sizes, links, folders and the email addresses files are shared with) and adds the text of supported files of up to about 25 MB to your installation's search index. For connections shared with a company or tenant, this covers shared drives only.
• Google Docs, Sheets and Slides. Lightbulb reads the documents, spreadsheets and presentations you point it to, and creates or edits them when you ask.
• Google Meet. Lightbulb asks for permission to create meeting spaces and read their details, and currently uses it only to check that the connection works. It does not access meeting recordings, transcripts or audio.
• Google Workspace administration. When an administrator connects Google for a company or tenant, Lightbulb also asks for permission to manage your organization's users and their security settings. It uses this to look up a user, and to suspend a user or sign a user out of all sessions in access-removal workflows; these two actions need approval before they run.
• YouTube. Lightbulb reads your channel and video details and statistics, and uploads videos after they are approved. Uploads are private unless you choose otherwise. Lightbulb also asks for read-only YouTube Analytics access, which it does not currently use.
• Google Analytics. Lightbulb reads account, property and web stream information and runs aggregate reports, such as sessions, add-to-cart, checkout and purchase counts, to measure marketing. It has read-only access. An authorized user selects the property used by the workspace.
• Google Ads. Lightbulb reads account, campaign and performance data. With approval it can create budgets and campaigns, which are created paused, change budgets and pause campaigns. It cannot turn campaigns on.

How Google data is stored

Google data that Lightbulb copies or creates is stored in your installation: email details, calendar events, file details and indexed file text, documents you work on, report results, and records of Lightbulb's requests to Google. Some of those request records include what Google returned, such as email headers and snippets, calendar events, file details, spreadsheet values and directory user records. Tokens are stored encrypted. Our hosted services keep only the encrypted credential described in How connected accounts work, not the content of your Google account.

How Google data is shared

Lightbulb sends Google data to an AI model when a feature needs it: to do something you ask, such as summarizing an email thread or drafting from a document; to build the search index for files your installation indexes; and, if your organization turns on email triage, to sort incoming email. These requests go only to the AI provider your installation uses (see AI processing and service providers). Otherwise we transfer Google data only as described under Limited Use below.

Retention and deletion

Google data stays in your installation until it is deleted in Lightbulb or by the organization that operates the installation. Disconnecting Google stops Lightbulb from using the connection but does not delete data already copied. You can also remove Lightbulb's access at any time in your Google Account. See Data Deletion Instructions.

Limited Use

Lightbulb's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

• We use Google user data only to provide or improve the user-facing features described in this section.
• We transfer it only as needed to provide or improve those features (for example, to the AI provider your installation uses), for security purposes, to comply with applicable law, or as part of a merger, acquisition or sale of assets after obtaining your explicit prior consent.
• We do not use or transfer it to serve advertisements, including retargeting, personalized or interest-based advertising.
• We do not sell it, and we do not use it to determine creditworthiness or for lending.
• We do not use it, including data obtained through Google Workspace APIs, to develop, improve or train generalized or non-personalized AI or machine-learning models.
• Lightbulb personnel do not read it unless you give us permission for specific data, it is necessary for security purposes such as investigating abuse, it is required to comply with the law, or it has been aggregated and anonymized for internal operations.

Meta data (Facebook, Instagram and Meta Ads)

This section applies when you connect Facebook Pages and Instagram professional accounts through Facebook Login, or connect Meta Ads.

What we access and why

• Your Facebook profile basics: your Facebook user ID and name, to identify the connection.
• Pages and Instagram accounts: the IDs and names of the Facebook Pages you manage, including Pages owned through a business portfolio, and the ID and username of the Instagram professional account linked to each Page, so you can choose where to post.
• Publishing: after a person in your workspace approves it, Lightbulb publishes or schedules posts, photos and videos on your Facebook Page, and publishes images and Reels to your Instagram professional account from a publicly accessible web address.
• Performance: Lightbulb reads Page details such as follower counts, your recent Page posts, and reach and engagement figures for your Page, posts and Instagram account where Meta makes them available, to report on your content.
• Lightbulb also asks for permission to manage Page settings and Instagram comments, which it does not currently use.
• Meta Ads (installation-configured connections only): Lightbulb reads ad account, campaign and performance information. With approval it can create campaigns and ad sets, which are always created paused and target only by location, age, gender and platform, change budgets and pause campaigns. It cannot turn campaigns on.

How Meta data is stored and shared

Your profile, Page and Instagram identifiers, the posts you publish through Lightbulb, their results and any performance figures your workspace saves are stored in your installation. Page access tokens are requested from Meta when needed and are not stored. For a connection made through our connection service, the service keeps your encrypted Facebook user access token. Meta does not issue a refresh token, so the connection lasts until that token expires (about 60 days) and you then reconnect.

We do not sell this data or use it for advertising. Lightbulb sends it to an AI model only when a task needs it, and only to the AI provider your installation uses (see AI processing and service providers).

To remove Lightbulb's access to Facebook and Instagram and ask us to delete data, see Data Deletion Instructions.

LinkedIn data

• Sign-in details: your LinkedIn member ID, name, email address and whether it is verified, and your profile picture, from LinkedIn's sign-in, to identify the connection.
• Publishing: after a person in your workspace approves it, Lightbulb publishes posts with text, images or video to your LinkedIn profile, or to a LinkedIn Page you administer if your connection includes Page permissions.
• Performance: Lightbulb reads engagement figures for posts and, where your connection allows it, follower and Page statistics and the Pages you administer.
• Lightbulb does not read or send LinkedIn messages.

These details, the posts you publish through Lightbulb and their results are stored in your installation. LinkedIn does not issue Lightbulb's app a refresh token, so for a connection made through our connection service, the service keeps your encrypted access token until it expires (about 60 days) and you then reconnect.

We do not sell this data or use it for advertising. Lightbulb sends it to an AI model only when a task needs it, and only to the AI provider your installation uses (see AI processing and service providers).

X data

• Account details: Lightbulb may store your X user ID, name, username and profile image to identify the connection.
• Publishing: after a person in your workspace approves it, Lightbulb publishes text posts to your X account. It also asks for permission to upload media, which it does not currently use.
• Performance: Lightbulb reads the public metrics of your posts and profile.

For a connection made through our connection service, the service keeps your encrypted X refresh token and renews access when needed. Posts and metrics your workspace saves are stored in your installation.

We do not sell this data or use it for advertising. Lightbulb sends it to an AI model only when a task needs it, and only to the AI provider your installation uses (see AI processing and service providers).

TikTok data

• Account details: your TikTok account identifier (open ID) and, when you or a workflow asks for them, your display name and profile information, follower, following, like and video counts, and a list of up to 20 of your recent videos.
• Posting with Direct Post (when your installation turns it on): Lightbulb reads your posting options from TikTok, such as which audiences, comments, duets and stitches are available and the maximum video length. It posts only after you review the exact video, caption and settings and give your express consent, and after a second person in your workspace approves the post. You choose the audience, and comments, duets and stitches are off unless you turn them on.
• Video export: to post, your installation uploads the approved video to our hosted service. TikTok can fetch it through an unguessable link that expires after 2 hours. Anyone with that link can access the video while it is valid. Link expiry stops downloads but does not automatically erase the stored video. The hosted copy remains until it is removed manually; ask us to delete it using the Data Deletion Instructions. Do not treat the 2-hour access window as a storage-deletion deadline.
• For each post, Lightbulb records the result TikTok reports, such as its status, its visibility and the resulting post ID.

For a connection made through our connection service, the service keeps your encrypted TikTok refresh token. Posting with Direct Post requires such a connection. Other TikTok data is stored in your installation.

We do not sell this data or use it for advertising. Lightbulb sends it to an AI model only when a task needs it, and only to the AI provider your installation uses (see AI processing and service providers).

ChatGPT app, OpenAI connector and MCP tool data

When you connect the Lightbulb ChatGPT app or OpenAI MCP connector, ChatGPT may send your prompt and selected tool arguments to Lightbulb. Lightbulb may return only the data needed to answer the request or continue the workflow. The returned data categories for the ChatGPT app and MCP connector may include:

• Lightbulb profile summary, role, scope type and selected company context.
• Company names, company refs or slugs, and non-sensitive company metadata.
• Project refs, project names, safe project summaries and project status.
• Workflow refs, workflow type, workflow state and recent workflow run summaries.
• Approval refs, approval status and concise human-in-the-loop approval summaries.
• Agent, capability, connector category and orchestration surface summaries.
• AutoCompany loop refs, loop goals, run status and run summaries.
• Recommended next steps, current-work summaries and helper context.

Lightbulb does not intentionally return OAuth tokens, passwords, API keys, client secrets, authorization headers, backend trace IDs, workflow instance IDs, tenant IDs, user IDs, raw company UUIDs, pending approval IDs, project IDs, workflow definition IDs, AutoCompany loop or run IDs, event IDs, correlation IDs, idempotency keys, debug logs or other internal diagnostics in ChatGPT-visible tool responses.

ChatGPT receives Lightbulb tool results only when you have connected the app and invoke or approve the relevant workflow. OpenAI handles that data under its own terms and privacy policy.

AI processing and service providers

Lightbulb uses AI models to answer questions, draft content, search your documents and run agent workflows. A request to an AI model can include personal information and content from connected accounts when the task needs it.

• AI providers your installation uses. Your installation can send prompts, tool results, documents and search-indexing requests to providers connected with your organization's API keys, such as OpenAI, Anthropic, Google or xAI, or a compatible service approved by your administrator. Document and file-processing features can send file contents as well as text. Processing locations, model-training settings and retention depend on the provider, product and agreement your organization selects. The organization must choose settings and agreements suitable for the data it sends; configuring an API key does not itself establish a no-training or zero-retention arrangement.
• Managed AI credits (optional). If your installation administrator turns on Managed AI and you approve its use, text requests are relayed through our hosted service to OpenAI's Responses API with OpenAI's response storage turned off. Our hosted service keeps usage and billing records (provider, model, token counts, charges and SHA-256 fingerprints of each request and response) but not the text of prompts or responses.
• Model training. We do not use connected-account data to train general-purpose or cross-customer models. This policy also prohibits using Google API data for generalized or non-personalized model training. Organization-specific AutoML features may process datasets supplied by an authorized user for that organization's own permitted purpose; users must have the necessary rights and comply with the source provider's restrictions. These commitments do not mean that the software automatically detects and removes every provider's data from every user-selected dataset or AI request.
• Speech (optional). If your organization turns on Lightbulb voice features, audio is transcribed by the speech provider it chooses (Deepgram, OpenAI or xAI) and spoken replies are generated by ElevenLabs, OpenAI or xAI. Voice features are not part of a standard installation.
• Hosting. The hosted deployment is configured for AWS in the United States (us-east-1). Website files may be delivered from CloudFront edge locations outside your country. Workspace storage remains at the location chosen by the installation operator.
• Email. Amazon Simple Email Service sends our account emails.
• Payments. Stripe processes payments for subscriptions and Managed AI credits.

Lightbulb does not filter content from connected accounts out of AI requests: when a task needs that content, it goes to the AI provider your installation uses. Your organization controls which AI providers the installation can use.

AI and automation can summarize, classify, rank or recommend actions using information supplied to the workspace, including financial records, correspondence and work-related information. These outputs may inform decisions made by your organization. The organization must provide any notices and human review required for its use case, and must not treat model output as an independent professional judgment. To question a decision affecting you, contact the organization making it; contact us about personal information handled in our hosted services.

Retention

• Installation data is kept until it is deleted in Lightbulb or by the organization that operates the installation. Some features have their own retention settings; for example, team messages are kept for 365 days unless an administrator changes this. Records of Lightbulb's requests to connected providers are kept until deleted, unless the installation is configured to delete them after 90 days.
• Connection credentials in our connection service are kept while the connection is in use. When you disconnect, the installation requests erasure of the hosted credential and retries while it is running until the request succeeds. Connection identifiers, provider details and dates remain after credential erasure; they do not currently have an automatic deletion schedule. Credentials for failed connections can remain encrypted until replaced or manually removed. Expired Meta and LinkedIn credentials are erased when the service next attempts to use them. To request removal of retained records, follow the Data Deletion Instructions.
• Sign-in records used to complete a connection expire after 10 minutes and are deleted within minutes after that.
• Lightbulb account data is kept while the account is open. Account closure and removal of account, billing and Managed AI usage records currently require manual handling; closure does not trigger a universal automatic deletion deadline. We assess what must be retained for tax and accounting duties, payment disputes, security or legal claims, and remove or de-identify personal information that is no longer needed. In response to a deletion request, we explain any retained categories, reason and applicable period instead of promising immediate erasure of every record.
• TikTok video exports are described in TikTok data.
• Logs and backups. The hosted infrastructure configuration specifies 30 days for operational logs and 14 days for automatic database backups. Deletion from active storage does not immediately remove backup copies; they expire through the backup lifecycle. Installation operators control their own logs, archives and backups, which may have different retention settings. A legal preservation obligation can require particular records to be kept longer.

Your choices and rights

You can disconnect a connected account at any time in the Connector Hub, remove Lightbulb's access in your account with the provider, and ask us to delete your data. Step-by-step instructions are on our Data Deletion Instructions page.

Depending on where you live, you may have the right to access, correct, delete or export your personal information, and to object to or restrict some processing. To make a request, contact us at support@lightbulbpartners.com. For data stored in an installation, we may refer your request to the organization that operates it, because that organization controls the data.

If you are not satisfied with our response, you can complain to a privacy regulator, such as the Office of the Australian Information Commissioner or the Office of the Privacy Commissioner of Canada.

Security

Our hosted services use HTTPS. The connection service encrypts provider credentials with AES-256-GCM, Lightbulb account passwords are stored only as bcrypt hashes, and our website's security policy blocks third-party scripts and connections. Installations encrypt stored provider tokens with AES-256-GCM and can reach only the internet hosts their administrator allows. No system is completely secure; if you believe your account or data has been compromised, contact us right away.

Where data is processed

Installation data is stored wherever the installation runs. Our hosted deployment is configured in the United States; AI, payment, email and other providers can process information in additional countries under their own arrangements. Overseas law-enforcement or other authorities may have lawful access. For processing we arrange, we remain responsible to the extent required by applicable privacy law. Relevant safeguards include encrypted transport, encryption of stored connection credentials, access restrictions and the contractual or other protections required for the particular transfer. This policy does not claim that every country offers identical protection, that an unverified special transfer certification applies, or that accepting this policy waives your privacy rights. Your organization is responsible for assessing providers it independently configures. Contact us for information about a particular transfer.

Children

Lightbulb is a business service and is not directed to children. We do not knowingly collect personal information from anyone under 18. If you believe a child has given us personal information, contact us and we will delete it.

Changes to this policy

We may update this policy. We will post the new version on this page with a new "Last updated" date and, if the changes are material, take reasonable steps to tell you, such as a notice in Lightbulb or an email.

Contact us

For privacy questions, access or correction requests, deletion requests and complaints, email support@lightbulbpartners.com, addressed to the Privacy Contact. Include your account or organization and enough information to locate the records, but do not send passwords, API keys or access tokens. We may reasonably verify your identity. We respond without undue delay, normally within 30 days, and meet any shorter deadline required by law. If a lawful extension is needed, we explain the reason and expected response date. Ask this contact for a postal contact or an accessible copy of this policy.