Legal
Privacy Policy
Effective date: August 19, 2026
Plain-English summary
1. Who this policy covers
This policy is published by Brightmotion (“we”, “us”) and covers the AgentHog service at agenthog.io (and its former address, hog.brightmotion.io), its SDKs, CLI, and APIs. It addresses two audiences:
- End Users — people who use the websites, apps, and games of our customers. We process data about End Users only on our customers' behalf (§2–4).
- Customers — people who create AgentHog accounts. For their account data, we are the controller (§5).
2. Our role: a processor, not a marketer
When a customer installs AgentHog in their product, the data their integration sends us (“Customer Data”) belongs to that customer. We act as a data processor (a “service provider” under the CCPA/CPRA): we store, secure, and query Customer Data on the customer's instructions, and nothing more. Specifically, we do not:
- Sell Customer Data or share it with third parties for their own purposes.
- Use Customer Data for advertising or ad targeting of any kind.
- Combine data across customers, or build profiles of End Users that span more than one customer's products.
- Track End Users across unrelated websites. The tracker's identifier is first-party and scoped to the customer's own site.
The customer — not Brightmotion — decides what to collect and is responsible for telling End Users about it and obtaining any consent the law requires.
3. What the Service collects for customers
When a customer's integration is active, the Service receives:
- Events — pageviews, screen views, clicks, form submissions, and custom events the customer defines (for example a signup or a purchase), with properties the customer chooses to attach. Autocapture records element metadata (such as a button's label), never the contents of what anyone types.
- A random identifier — the browser tracker stores a randomly generated ID in a first-party cookie and localStorage so that visits by the same browser can be connected. It is not derived from anything about the person or device, and it is not shared across unrelated sites.
- Technical context — user agent, and the IP address of each request. The raw IP address is used transiently to derive coarse, country-level geolocation, network (ASN) classification, and bot scoring, and is then discarded: we store only a salted, one-way hash of the IP whose salt rotates daily, which prevents long-term tracking by address. We never store raw IP addresses or precise location.
- Identity the customer supplies — a customer may associate events with their own user identifiers or traits (for example an account email in their product). Whether to do that, and disclosing it, is the customer's choice and responsibility.
The Service deliberately does not include:
- Session replay, screenshots, or screen recording.
- Keystroke logging — keyboard activity contributes a single yes/no signal used for bot detection; nothing typed ever leaves the device.
- Device fingerprinting, third-party cookies, or cross-site advertising identifiers.
4. End User rights: contact the site or app you used
If you're an End User
Because we have no direct relationship with End Users, requests to access, correct, export, or delete End User data must be made to the relevant customer — the operator of the website, app, or game you used, whose privacy policy governs that data. When a customer instructs us (by email to [email protected]) to delete or export an End User's data, we complete the request within 30 days. If an End User contacts us directly, we will refer them to the relevant customer and notify that customer where we reasonably can.
5. Data we collect from account holders
For people who sign up for AgentHog, we collect and control:
- Account data — name, email address, and authentication data, handled through our sign-in provider (Clerk).
- Billing data — plan, invoices, and payment status, handled through our payment provider (Stripe). Card numbers go to Stripe directly; we never see or store them.
- Service usage — event volumes, feature usage, and logs, used to operate, meter, and secure the service.
- Correspondence — support and privacy request emails you send us.
We use this data to provide and bill the Service, communicate with you about it, and meet legal obligations. We do not sell account data, and we do not use it for third-party advertising. Account holders can access or delete their account data by emailing [email protected].
6. Subprocessors and service providers
We use a small set of vendors to run the Service, each bound by contracts limiting their use of data to providing their service to us:
- Railway — application and database hosting.
- Cloudflare — network, DNS, and DDoS protection in front of the Service.
- Clerk — customer authentication (account holders only; End User data does not pass through Clerk).
- Stripe — payment processing (account holders only).
7. Retention
- Customer Data (events and sessions) ages out automatically at the end of the customer's plan retention window — 30 days on the free plan, 12 months on Pro. Aggregate daily rollups, which contain no per-user records, persist beyond the window.
- When a customer closes their account, we delete their Customer Data within 60 days.
- Deleted data may persist in backups for up to 90 additional days — the retention of our longest backup cycle — before those backups age out.
- Account and billing records are kept as long as the account is active and thereafter as required for tax and accounting law.
8. Security
All data is encrypted in transit. Access to production systems is limited to personnel who need it to operate the Service. Identifier design is part of our security posture: raw IP addresses are never written to storage, and the stored IP hash rotates daily, so even a full copy of the database cannot be used to follow an address over time.
9. Data Storage
The Service is hosted in the United States, and data you send it is processed and stored there.
10. Children
AgentHog accounts are for adults and businesses; we do not knowingly collect account data from children under 13 (or the higher age a jurisdiction sets). Customers are prohibited from using the Service to collect data from children where they lack the required parental consent — see the Terms of Service.
11. Changes and contact
We will post changes to this policy here, and for material changes give account holders at least 30 days' notice by email or in-product notice. Questions or requests: [email protected].