Homunculus Studio for Chrome
Privacy policy
Effective: 2 November 2026. Last updated:
Homunculus is operated by Tru Path LLC. This policy explains how we handle information when you use the Homunculus Studio Chrome extension and its connected recording, sharing, generation and marketing features at homunculus.com.ai. It also covers people who open a Studio share link. You can read this page without signing in.
Captures start on your device. The recorder and open side panel automatically upload finished recordings to Homunculus to create public share links when your account is connected. Saving a screenshot for sharing also uploads it. Other processing, generation and repurpose features send content when you use them. Some requested features use the providers described below. Anyone with an active public share link can access its content.
1. Information we handle
- Account connection: your Homunculus API key is saved in Chrome extension storage and sent to Homunculus over HTTPS to authenticate requests, including connection checks. Requests and saved content are associated with your account. Never share your key.
- Browser context: tab URLs, titles and favicons show the current page, name captures and support actions you select. A displayed favicon may load from its source website. The extension does not use Chrome's history database to collect past browsing history.
- Captures: the screen, window or tab you select, screenshots, GIFs and optional sound. Tab or system sound depends on your capture settings and Chrome's controls. Microphone and camera are used when you enable them and grant access. Captures can include faces, voices, messages and other personal information visible or audible during capture.
- Recording activity: quick tab recording captures timestamps, page URLs, clicks and coordinates, scroll positions, viewport size and clicked-element descriptions (tag, role, ID and accessibility label). It does not collect keystrokes or form-field values as an event stream; those values can still appear in screen pixels or page URLs.
- Content you provide: titles, annotations, recordings, reference videos, reaction takes, source URLs, instructions, captions and template choices. Content requests also include topics, keywords, scripts, voice or tone preferences and generated podcast, blog or social-post material.
- Tasks and files: task titles, descriptions, status, creator details, the named assignee's verified login email, attachment filenames and uploaded file contents. Sharing uses the connected HighLevel location and verified member identity. Task files are available to the creator and named assignee in that same location; they are not public Studio recording shares.
- Account tools: your postcard order status, QR statistics and search reports. Reports use the site URL and dates you supply. The GoHighLevel action uses the contact email and share URL you enter to update an existing contact.
- Technical and share activity: service logs may include IP address, request time, URL, browser information and errors. Share pages record opening or playback activity and timestamps. Owners can see engagement counts and may receive a viewing notification; counts do not establish who watched.
2. How we use information
We use information to authenticate you; capture, process, store and deliver requested content; generate or edit walkthroughs; run selected tools; create and revoke share links; display status and engagement; provide support; and protect the service.
We do not sell extension user data, use it for targeted advertising, or use it for creditworthiness or lending decisions. We do not use or transfer it for purposes unrelated to user-facing features, except as needed for security or legal compliance. The extension contains no third-party advertising or analytics trackers. Our use of information received from Google APIs follows the Chrome Web Store User Data Policy, including its Limited Use requirements. Service logs and share engagement described here are separate from advertising tracking.
3. Local storage, uploads and sharing
Recordings and reaction takes initially use your browser's IndexedDB. Settings, device preferences, API keys and metadata use extension storage; the appearance preference also uses local storage. Stopping a recording in the recorder page, or stopping a quick-tab recording while the side panel is open, automatically attempts to upload it to Homunculus and create a public share link. A quick-tab recording stopped by keyboard shortcut with the side panel closed stays local until you choose Upload & create share link. Saving a screenshot for sharing also uploads it. Uploads require a valid Homunculus API key; if an upload fails, a local copy may still be available to download or retry.
Choosing an upload, processing, generation or repurpose action sends the necessary content to Homunculus. Generate can use your instruction, URL, reference frames and event track; server-side walkthrough generation also processes page text, screenshots and action history. Account tools make requests when you open or use them.
A public share link makes the processed video, GIF or screenshot, title and preview accessible without an account to anyone with the link. Recipients can forward or download it. Messaging services may fetch and cache previews. Copying or sharing a media file creates a separate copy outside Homunculus. Revocation cannot remove copies already downloaded or cached by others.
4. Providers and other recipients
We use the following providers as needed for the feature you request:
- Amazon Web Services and Google Firebase / Google Cloud: application infrastructure, authentication, account and job records, and storage. Task attachments use private Amazon S3 storage and authenticated application downloads.
- OpenRouter and AI providers: generation and editing send instructions and relevant page text, URLs, screenshots or reference frames to OpenRouter for model processing. The generation configuration uses DeepSeek, and action checks use TypeSafe Jev through OpenRouter. The model service receives content included in those requests. Content topics, keywords, source material and scripts are also processed for the selected Content feature. Model selections depend on the feature and configuration; a configured Anthropic service may also be used for text generation.
- fal.ai: Repurpose's cut-out feature sends reaction video to the VEED background-removal service through fal.ai. Podcast speech generation sends the requested script and voice settings to fal.ai's Kokoro text-to-speech service. Homunculus receives and stores the resulting media.
- Browserbase, when configured: site cloning uses a hosted browser to visit the submitted URL and process page content. Otherwise a browser on Homunculus infrastructure performs it. Websites visited for cloning, generation or video retrieval receive normal web requests.
- Google Search Console: search reports query the Google connection already authorized for your Homunculus account.
- DataForSEO, when used by search reports or rank tracking: the requested website/domain, keywords and search-location settings are sent to obtain search metrics. This is separate from your Google Search Console connection.
- GoHighLevel, when selected: your submitted contact email finds an existing contact in your connected account, and the share URL is saved in its Outreach URL field. This Outreach URL action does not itself email the contact. Content delivery can upload generated audio to the selected location's Media Library and create Content order records containing the generated material. Video-view notices, when enabled, use HighLevel email to notify the verified recording owner; share activity and the owner's matching contact details are used for that notice. Access to delivered records and media links follows the connected HighLevel account's settings.
- Recipients and apps you choose: sharing, clipboard copies and downloads disclose content to your selected people or services. Their handling of those copies follows their own policies.
Authorized support or operations personnel may access relevant information to handle your request, maintain the service, investigate abuse or comply with legal obligations. We may disclose information when required by law or necessary to protect users and the service. Processing may occur in the United States and other countries where providers operate.
Other Homunculus tools opened from the extension, such as website creation, agents or placing a mailing order, involve additional data flows for the actions you take there. Viewing postcard status in the extension does not submit a new mailing order.
5. Retention and deletion
Local captures remain until you delete them, clear extension data or uninstall. Downloaded files remain wherever you saved them. Deleting locally or uninstalling does not delete an uploaded copy.
Uploaded Studio recording media and share links become inaccessible through the recording service seven days after upload; revoking a link disables that link sooner. Expiry does not guarantee erasure of underlying server files or account records. Automatic physical deletion of expired recording files is not currently implemented. Contact us to request deletion.
Repurpose working files are cleaned up after processing. Its temporary uploads and results are eligible for best-effort cleanup after six hours, rather than guaranteed deletion at an exact time. Task files, task metadata and Content orders are not subject to the seven-day Studio recording expiry. The creator can delete task files or tasks through Homunculus; copies delivered to HighLevel or downloaded by a recipient must also be managed there. Other account records and operational logs may remain for service operation, support, security and applicable legal requirements. We review deletion requests against those requirements and explain any information that must be retained.
6. Your choices and rights
- Choose what to capture and stop at any time. The recorder and open side panel start uploading when recording stops, without a separate review-before-upload step. Keyboard-only quick-tab recordings made with the panel closed stay local until you upload them. Avoid capturing passwords, payment details or other people's private information.
- Manage microphone, camera and website permissions in Chrome and your operating system. Restricting access may disable the corresponding feature.
- Delete local captures, clear the stored API key or uninstall. Disable a credential at Homunculus API Keys.
- Revoke public links through the extension or Homunculus Video Library.
- Request access, correction or deletion using the contact details below. Include your account email and relevant recording or job ID, never your password or API key. We may verify account ownership before acting.
Depending on your location, you may also have rights to receive a copy, restrict or object to processing, withdraw consent, or complain to your data protection authority. Contact us to exercise applicable rights.
7. Contact and updates
For privacy questions, access requests or deletion requests, contact Tru Path LLC, the operator of Homunculus, at amir@trupathmarketing.com.
We publish revisions here and update the date above. If materially different data handling requires notice or consent, we will provide that notice or request consent before it begins.