Privacy Policy

Scope

This policy applies to the AgentShot website, the AgentShot desktop application, and infrastructure operated by Hormuz Labs for AgentShot. It also applies to AgentShot accounts, which are shared with Pitch (trypitch.co), a Hormuz Labs product that is becoming part of AgentShot. Services run by others—including GitHub, your AI model provider, and sites opened in a browser—have their own privacy policies.

The website

The agentshot.si website has no sign-in, contact forms, advertising, or first-party analytics. We do not set cookies on the website. Accounts are created and used in the desktop app, as described below.

The site is hosted on Cloudflare Pages. Like other web hosts, Cloudflare may process standard request and security data when it serves a page, such as your IP address, request time, requested URL, browser or user-agent information, referring page, and signals used to detect abuse. Cloudflare processes that data under its own privacy commitments and may make limited operational logs available to us.

Links and downloads may take you to GitHub, Homebrew, the AgentShot apt repository, or another site. Those services receive the information ordinarily sent when your browser connects to them.

The desktop app

Your projects stay local

AgentShot stores and processes your projects, footage, audio, transcripts, edits, settings, and exports on your computer. Hormuz Labs does not receive those files merely because you use the app.

AI providers you choose

With your own key, AgentShot connects directly to the AI provider or compatible endpoint you select, and Hormuz Labs is not in between. That provider may receive your instructions, relevant transcript text, and a limited number of still frames when the model needs visual context. It does not receive your full video through AgentShot. Your provider’s terms and privacy policy govern its processing. API keys are stored in your operating system’s keychain.

Browser and external tools

When AgentShot searches the web, downloads a tool, or connects to a service at your direction, that service receives ordinary network request data and any information needed for the requested action. AgentShot uses its own browser by default; it accesses your browser only if you enable that option.

Mobile companion and remote workers

In Settings → Mobile, you can pair the AgentShot iOS or Android companion app with your computer using a 6-digit verification code over local Wi-Fi or Tailscale. Paired connections are encrypted and pinned to your computer’s certificate so footage, notes and exports move directly between your phone and your computer.

You can also connect AgentShot to a home worker you run yourself (manul --worker) or lease an AgentShot cloud worker. When you connect a worker, AgentShot coordinates the encrypted peer mesh (manul-mesh) and syncs the active project’s files to that worker so it can run edits and renders for you.

AgentShot accounts

You can sign in to AgentShot to use the AgentShot key, which covers models, voice and music without keys of your own, and to subscribe to a plan. Accounts are shared with Pitch: one email, one account, one plan and credit balance.

Sign-in

Sign-in is provided by Clerk. When you create an account or sign in, Clerk processes your email address, your name and profile picture if you sign in with Google or another identity provider, an account ID, sign-in times, and the device and network data needed to keep sessions secure. AgentShot keeps a session token for your account on your computer.

The AgentShot gateway and usage records

Requests made with the AgentShot key go through the AgentShot gateway, operated by Hormuz Labs, which forwards them to the model, voice and music providers we work with and returns the result. The same limits apply as with your own key: your instructions, relevant transcript text and a limited number of still frames, never your full video. The gateway logs usage per account so we can bill for it and prevent abuse: the time, the model tier and model, the amount used (such as tokens or seconds of audio), and the credits charged. Those usage logs do not store the text of your prompts or the replies.

Billing

Plans, top-ups and invoices are processed by Dodo Payments, which acts as merchant of record and handles your payment details, billing address and tax information under its own privacy policy. We do not receive or store full card numbers. We receive what we need to run your plan: the plan and billing period, payment and subscription IDs, amounts, currency, country, and status.

Optional diagnostics

On first run, release builds ask separately whether you want to send crash reports and usage statistics. Both choices start off, closing the prompt means no, and either choice can be changed at any time in Settings → About. Builds made from source send neither.

Usage statistics

If enabled, AgentShot sends a fixed set of product events through a Hormuz Labs Cloudflare Worker to PostHog. These events describe actions such as opening the app, creating a project, active time, the selected model and tool names used in an agent run, accepting an edit, completing an export, and installing a tool. Events also include app version, operating system, architecture, and a random installation ID that is not tied to your AgentShot account or identity, even when you are signed in.

Crash reports

If enabled, AgentShot sends uncaught errors and crash information to PostHog’s error tracking, through our proxy: the error’s type, message and stack trace. Local variables, console output, network requests, screenshots and crash dumps are excluded. File paths, computer names, and user details are removed.

What diagnostics never include

Diagnostics do not include your footage, file or folder names, paths, project titles, prompts, agent replies, transcripts, API keys, or visited URLs. We do not pass your IP address to PostHog. The complete, current event list is published in AgentShot’s telemetry documentation.

How we use information

We use the limited information described above to deliver and secure the website, distribute AgentShot, run accounts, the AgentShot key and billing, diagnose crashes, understand whether features work, improve the product, prevent abuse, and meet legal obligations. We do not sell personal information or use it for targeted advertising.

Where data-protection law requires a legal basis, we process data as necessary to provide the services you request (including accounts, plans and billing), for our legitimate interests in operating and improving AgentShot without overriding your rights, with your consent for optional diagnostics, or to comply with law.

Sharing and retention

We share information only with service providers needed for the purposes above, such as Cloudflare, Clerk, Dodo Payments, the model, voice and music providers behind the AgentShot key, and PostHog; when you direct us to connect to a third party; or when required to protect rights, safety, and the integrity of the service or to comply with law. These providers may process information in countries other than yours.

We retain information only as long as reasonably needed for those purposes, security, and legal obligations. Account data is kept while your account exists; usage and billing records are kept as long as needed for billing, disputes and tax law. Optional usage events may wait on your computer while offline, up to 500 events. Turning usage statistics off deletes unsent events and the random installation ID. A later opt-in creates a new ID.

Your choices and rights

• Leave crash reports and usage statistics off, or change either setting at any time.
• Choose which AI provider AgentShot uses and manage data with that provider, or use AgentShot without an account at all.
• Cancel a plan in the app under Settings → Keys → AgentShot key, and ask us to delete your account by writing to [email protected].
• Delete local AgentShot projects and application data from your computer.
• Depending on where you live, request access, correction, deletion, restriction, objection, or portability for personal information we control, and complain to your local data-protection authority.

Diagnostic installation IDs are intentionally not linked to an account or identity, so we may be unable to identify a particular event as yours.

Changes and contact

We may update this policy as AgentShot changes. We will post the revised policy here and change the effective date.

For privacy questions or requests, including about your account, email [email protected]. General questions can also go in the AgentShot repository; do not include personal information in a public issue.