Privacy Policy
Effective October 6, 2026
TechBridge Digital LLC ("TechBridge," "we," "us") respects your privacy. This policy explains what information we collect, how we use it, and the choices you have. It applies to techbridge.dev, the TechBridge Platform, and any other site or service that links to this policy.
Information we collect
Information you give us
- Contact form data. Your name, email, business name, website (optional), monthly revenue range (optional), and the message you write us.
- Cohort and waitlist data. Email, company size, role, and use case submitted when you ask to join the next Platform onboarding cohort, plus the same fields from earlier product waitlists we ran.
- Newsletter data. Email address only.
- Ask TechBridge questions. The questions you type into the Ask TechBridge assistant on this site. They are sent to our AI model provider, through Vercel AI Gateway, to generate the answer, and stored in our analytics (PostHog) with email addresses and phone numbers removed.
- Account data. If you sign up for the Platform, name and email plus any data you import or generate inside the app.
- Data from accounts you connect. If a business connects Instagram, Facebook, YouTube, Google Business Profile or Search Console to the Platform, we receive the data described under Accounts you connect to the Platform.
Information collected automatically
- Usage data. Pages viewed, referrer, device and browser metadata, approximate location from IP, timestamps.
- Cookies and similar technologies. See our Cookie Policy for the full list and purpose of each cookie.
- UTM parameters and referring site. source, medium, campaign, content and term attached to inbound links, plus the website that referred you and the first page of your visit, stored against the lead record (or booking) for attribution.
Accounts you connect to the Platform
A business can connect its own Instagram, Facebook, YouTube, Google Business Profile and Search Console accounts to the TechBridge Platform so its agent can work with them. It can also connect CompanyCam and GitHub, described after Google below. Connecting is optional. For Instagram, Facebook, YouTube and Google Business Profile, a member of the business's organization starts the connection and approves it on Meta's or Google's own consent screen, and we receive only what is granted there. Search Console works differently, as described below. This section says exactly what we receive from Meta and Google, why, how we store it, and how to end it. "The business" means the TechBridge customer that connected the account.
Instagram and Facebook (Meta)
What we receive:
- Through Instagram login (an Instagram professional account). The account's ID, username and basic profile details; its own posts and videos; comments on them, including the commenter's username and the comment text; direct messages sent to the account, including the sender's username and the message text; and reach, views, profile views and follower statistics.
- Through Facebook login (Facebook Pages, and the Instagram account linked to a Page). The list of Pages the person who connects manages, so they can choose one; the Meta user ID of that person, which we keep so that a removal request from Meta can be matched to the connection; for the Page chosen, its ID, name and Page access token, its posts, the comments on them and messages sent to the Page; and statistics for the Page and its linked Instagram account. We do not request access to anyone's personal timeline or friends list.
What we use it for:
- Publishing videos and posts to the business's Instagram account and Facebook Page. By default a person at the business approves each one first. A business can switch a type of content to automatic approval, and can switch it back.
- An inbox that shows the comments and direct messages the business receives, with replies drafted for the business to review. A reply is sent only after a person at the business approves it, or under an automatic-reply rule the business set up itself and can switch off. Direct-message replies follow Meta's messaging-window rules.
- Showing the business how its content is performing, in its dashboard and reports.
We use this data only to provide those features to the business that connected the account. We do not sell it, we do not use it for advertising, and we do not use it to train AI models.
YouTube, Google Business Profile and Search Console (Google)
TechBridge uses YouTube API Services. By using the Platform's YouTube features you agree to be bound by the YouTube Terms of Service, and the Google Privacy Policy applies to what you give Google.
What we receive, and what we use it for:
- YouTube. The business's channel ID and name, its videos and their statistics, analytics reports for the channel, and comments on its videos, including the commenter's channel name and the comment text. We use it to upload the videos the business approves, to show how they perform, and to draft replies to comments for the business to review.
- Google Business Profile. The business's listings and their details, its reviews (star rating, review text, the reviewer's display name and any existing reply) and listing performance statistics. We use it to show the reviews in one inbox, to draft replies for the business to review and, once the business approves one, to post it to Google.
- Google Search Console. The business gives us access by adding a TechBridge Google account as a user on its Search Console property, so it does not sign in to TechBridge with Google for this. For that property only, we read daily clicks, impressions and average position, and the top pages and search queries. We use it for the business's SEO reports and recommendations. Access is read-only: we change nothing in Search Console.
TechBridge'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. In plain terms: we use Google user data only to provide the features the business connected it for, as described above. We do not sell it, use it for advertising, or use it to train AI models. We do not transfer it to others except to the service providers listed below to provide those features, where the law requires it, or as part of a merger or sale of our business. Our staff do not read it unless the business asks us for support, we need to for security or to investigate abuse, or the law requires it; otherwise it is used only in aggregated, anonymized form for internal operations.
CompanyCam and GitHub
Two more connections are optional and are used only for the business that made them. We do not sell what they bring in or use it to train AI models.
- CompanyCam. A member of the business pastes a CompanyCam API token. We read the business's CompanyCam projects, job photos and photo tags, and copy the photos into the business's own storage so the agent can use them in videos and posts. We only read from CompanyCam; we change nothing there.
- GitHub. The business gives TechBridge access to the repository that holds its website. We read the site's files to prepare changes and, when the business approves one, put it on a separate branch and open a pull request in that repository. The business can remove TechBridge's access in its GitHub settings at any time.
Who else handles this data
- Hosting and storage. The Platform runs on servers we operate in the United States, behind Cloudflare's network, and stores data in a PostgreSQL database we operate. Photos, videos and other files a business uploads, syncs from CompanyCam or has generated are stored in Cloudflare R2 object storage.
- AI model providers. To draft replies and captions, the text of a comment, message or review, and the draft itself, can be sent to an AI model. Those requests go through OpenRouter, and the Platform asks OpenRouter to route them only to providers with zero-data-retention terms. Photos a business uploads or syncs can also be sent through OpenRouter to AI models that read images, so the agent can choose and describe photos for videos and posts. A reply that a business has set to send automatically is also sent to an AI screening service (TypeSafe, directly or through Vercel AI Gateway) for a safety check. That service receives only the outgoing reply text.
- Voiceovers. To make the audio for a video, the words it will say are sent to ElevenLabs, which returns the recording.
- Search research. For a business's SEO reports, we send its website address, the search terms we are checking and its competitors' websites to DataForSEO, which returns ranking and keyword data.
- Notifications and email. When something is waiting for approval, we tell the business through the channels it turned on: email (sent through Resend), text message (Twilio) and Discord. The Platform's other email, such as sign-in and invitation messages, is sent through Resend too. A notification can include a one-line preview of what is waiting, such as the reply we drafted.
How we store it
- In our database, the access and refresh tokens that Meta and Google give us are encrypted with a key held in AWS Key Management Service, and each is bound to the organization and connection it belongs to. Each time a token is stored, used, refreshed or revoked, we log the action. The log holds no message content.
- A token is decrypted only when it is needed to call Meta or Google. That includes work done by the business's own agent, which runs on a separate instance that we operate and receives the token from our servers over a signed request.
- The comments, messages, reviews and statistics described above are stored in our database, kept separate from other organizations' data.
- The TechBridge Google account we use to read Search Console has its credential encrypted the same way.
Cookies and device storage
Connecting an account happens on our servers and on Meta's and Google's own pages. We do not embed Instagram, Facebook or YouTube players or widgets, so connecting or using these accounts stores nothing on your device beyond the sign-in session and the other items listed in our Cookie Policy. Meta and Google may use their own cookies on their own pages, under their own policies.
How long we keep it
- Tokens. Until an owner or admin disconnects the account in TechBridge, the organization is deleted, or you ask us to delete them.
- Comments, messages, reviews and statistics. For as long as the organization has an account, unless the business deletes them. Disconnecting an account does not delete them unless the owner or admin ticks the option to delete them as well. Copies can remain in backups until the backups are overwritten.
What deleting removes, and what it keeps
Deleting an account's stored data removes, for that connected account:
- Facebook and Instagram. Comments, our replies to them, direct messages and conversations, contacts (the people who commented or messaged: their platform user ID, username and display name), inbox items, saved post details (thumbnail, caption and link), cached Page and account insights, and the connection with its token. A Page connection covers both Facebook and Instagram; Instagram login covers Instagram only.
- YouTube. Comments, our replies, comment-check records, inbox items, saved video details (title and thumbnail), cached channel analytics, and the connection with its token.
- Google Business Profile. Reviews, our replies, inbox items, cached insights, and the connection with its token.
What it keeps:
- Approval records and the activity log keep the fact that something was approved, and when. The comment, message or review text, our reply text and the names or usernames in them are replaced with "[deleted]", and approvals still pending are expired. Queued and in-app notifications lose their text too.
- Content the business published through TechBridge and its statistics, the business's Business Profile listing data, and its reply rules stay in its account until the organization is deleted.
- A record that the connection was revoked and that a deletion happened. It holds counts and a confirmation code, no message text and no Meta IDs. The security log of when a connection's credentials were stored, used or revoked is also kept, and holds no message content.
Notification emails, chat and text messages we already sent to a business's team are outside our systems and cannot be recalled. Copies of deleted data can remain in backups until the backups are overwritten. Search Console data we have already collected for a business stays until the organization is deleted.
How to disconnect, revoke access and delete your data
- In the Platform. An organization owner or admin can choose Integrations, then Disconnect, on the account's card. We delete the stored token and stop Meta's webhooks for the account. Where we can, we also ask Meta or Google to revoke TechBridge's access. Those steps are best effort and never block the disconnect. Instagram login has no revoke call, and we skip the revoke when another active TechBridge connection uses the same login. The card offers a checkbox to delete the stored comments, messages and reviews too. Without it they stay. For CompanyCam and GitHub, Disconnect stops us using the connection and deletes the credential we stored; to end the access on their side, remove TechBridge's token in CompanyCam or the app in your GitHub settings.
- On Instagram or Facebook. On Instagram: Settings and activity, then Website permissions, then Apps and websites, and remove "Techbridge Digital - IG". On Facebook: Settings, then Business integrations, and remove "Techbridge Digital". Meta then tells us. For a connection we can match to your Meta account, we revoke it and delete the stored token, and if you ask Meta to delete your data we also delete the stored data listed above. Older Facebook connections may need us to match them by hand: if Meta's confirmation page says nothing was found, email us with the confirmation code.
- On Google. Open Google's app permissions page, choose TechBridge, then Remove access. That ends our access immediately. For Search Console, remove TechBridge's Google account under Settings, then Users and permissions. Google does not tell us when you do this, so delete the stored YouTube and Business Profile data with Disconnect and its checkbox, or email us.
- Delete the data. Use Disconnect with the checkbox, or have an organization owner delete the organization in the organization settings, which permanently deletes everything described in this section. Or email john@techbridge.dev and we will delete the stored data for your connected accounts and confirm within 30 days. Deletion works for a whole connected account, not for one person's comment, message or review on its own. If yours is stored because you wrote to a business that uses TechBridge, email us and we will follow up with that business. More on our data deletion page.
Text messages
A business can link a mobile number to get text messages from the Platform, such as an alert when a lead arrives or a post is waiting for approval. We text only numbers that have opted in by replying YES to our confirmation message. Reply STOP at any time to opt out, or HELP for help. Message and data rates may apply. Mobile numbers and SMS consent are never shared with third parties or affiliates for marketing or promotional purposes. Twilio delivers the messages for us. See our Messaging Policy.
Analytics stack
We run two analytics tools, each with a specific job:
- Google Search Console (GSC). Crawl status, query impressions, click-through, and indexing diagnostics for our pages in Google Search. GSC reads server-side data from Google's index; it does not place cookies on your device.
- PostHog. Product analytics on this website, run on PostHog Cloud (US). It records pages viewed, clicks, form and booking steps, and performance metrics such as page load speed, builds heatmaps, and keeps session replays: recordings of how a page was used, with every form input masked. Used to understand how visitors use the site, find friction, and improve it. You can opt out at any time on our privacy preferences page.
We do not use Google Analytics on this website.
We do not run third-party advertising trackers, retargeting pixels, or session-replay tools other than PostHog (with input masking). If we add any, we will disclose them here and update the cookie banner before they go live.
How we use information
- To respond to your inquiries and deliver the services you sign up for, including the features a business connects Meta and Google accounts for.
- To send transactional messages (account notifications, invoices, lead-form confirmations).
- To send the newsletter and product updates if you opted in. You can unsubscribe at any time: reply to any email we send, or write john@techbridge.dev, and we remove you promptly.
- To improve the site and product based on aggregate usage data.
- To meet legal, tax, and accounting obligations.
Sharing
We do not sell personal data. We share it only with vendors who help us run the business, under contract:
- Hosting and storage. Vercel hosts this website. The Platform runs on servers we operate, behind Cloudflare, which also provides R2 file storage. AWS holds the encryption key for stored tokens (Key Management Service).
- Email. Resend delivers the Platform's email. Google Workspace hosts our mailboxes, so messages you send us, and our replies, pass through it, as do the email campaigns a business sends from the Platform.
- Analytics. Google Search Console and PostHog Cloud (US). Both configured to anonymize IP where supported and to disable demographic profiling.
- AI assistant. Vercel AI Gateway and the AI model provider it routes to receive the questions you type into Ask TechBridge, to generate the answers.
- Platform services. OpenRouter and the AI model providers it routes to (for text and for photos), ElevenLabs (voiceovers) and DataForSEO (search research), each as described under Accounts you connect to the Platform.
- Payments. Stripe.
- Authentication. Google, if you choose Sign in with Google on the Platform. It gives us your name, email address and profile picture, and asks for nothing else.
- Connected accounts. Meta, Google, CompanyCam and GitHub, for the accounts a business connects, and the hosting, AI model, notification and messaging providers named under Accounts you connect to the Platform.
We may also disclose information when required by law, to enforce our Terms of Use, or to protect the rights, safety, and property of TechBridge or others.
Retention
We retain personal data only as long as needed:
- Lead records: 36 months from last contact.
- Newsletter records: until you unsubscribe.
- Account data: life of the account, then 90 days after deletion.
- Data from connected Meta and Google accounts: as set out under Accounts you connect to the Platform.
- Logs (server, application, security): up to 12 months.
- Analytics data: PostHog retains event data per our PostHog Cloud project settings (currently 12 months).
Your rights
Depending on where you live, you may have the right to access, correct, delete, port, or restrict processing of your personal data. To make a request, email john@techbridge.dev. We verify identity before fulfilling requests.
California residents have specific rights under CCPA. We do not sell personal information; we share it only with the categories of vendors listed above. Use the contact email above to exercise CCPA rights.
EU/UK residents have rights under GDPR. We process your data on the basis of legitimate interest (analytics, security), contract (delivering services), and consent (marketing emails, non-essential cookies). You can withdraw consent at any time.
Children
Our services are not directed at children under 16, and we do not knowingly collect personal information from anyone under 16. If you believe a child has provided us information, contact us and we will delete it.
International transfers
Our infrastructure is hosted in the United States. If you access our services from outside the US, your data is transferred to and processed in the US under the safeguards of our vendor agreements.
Security
We use industry-standard practices: TLS in transit, encrypted storage at rest, access controls, and routine vendor reviews. No system is 100% secure; we recommend strong, unique passwords and enabling two-factor authentication on Platform accounts.
Changes
We will update this page when our practices change and revise the effective date above. Material changes will be communicated via email or in-app notification.
Contact
Questions or requests: john@techbridge.dev. Mail: TechBridge Digital LLC, Virginia, USA.

