Privacy policy
Last updated 18 November 2026
Trakbolt ("we") is attribution software for online businesses ("clients"). It joins each order to the ad click that started it and sends conversion signals back to the ad platforms the client chooses. This policy covers the people who use the Trakbolt app and the visitors and customers of our clients' websites.
Our role
For the visitors and customers of a client's website we act as a processor (or service provider): the client decides what is collected and where it is sent, and its own privacy policy applies. For the people who sign in to Trakbolt we are the controller of their account data.
What we collect
- App users: name, work email, a password hash, two-factor settings, the workspaces they can open, and an audit log of changes they make.
- Website visits (through the client's tracking script): page, referrer, campaign and click ids from the link, country, region, device and browser. One first-party cookie (
wp_vid) holds a random visitor id. The IP address is used to send an event and to find the country; it is not stored with the visit. - Visits to this website (Trakbolt's own pages, not the app): Trakbolt runs its own tracking script here, with the same visit data and
wp_vidcookie as above. A message sent through the contact form is joined to the visit that sent it, so we know which page or campaign brought it. If you use the free tracking check on these pages, we read your site's public homepage once and keep your answers, name, work email and the visit details (pages seen, referrer, campaign, device, browser, screen, language, time zone, country) with your request. Never sent to an ad platform. - Leads and orders (sent by the client's systems): order id, value, currency, time and the ids that join the order to a visit. Email and phone are stored as one-way SHA-256 hashes. Names and plain contact details are stored only when the client turns on contact details, always encrypted, and never for a healthcare client without a signed business associate agreement (BAA).
- Ad-account connections: when a client connects an ad account (for example by signing in with Google), we keep the access token, encrypted, to import ad spend and upload conversions for that client only.
How we use it
- To show the client which ads and channels led to its leads and sales.
- To send conversion events, and audiences the client has approved, to the ad platforms the client has connected.
- To run, secure and support the service (sign-in, abuse and bot filtering, error tracking by id and code).
We do not sell personal data, use it for our own advertising, or combine one client's data with another's.
Who receives it
- Ad platforms the client connects (Google, Meta, Microsoft, Pinterest, Reddit, Snapchat, TikTok and others): hashed email and phone, click ids, IP address and user agent, generic event names, value and order id. Never a name, a plain contact detail, or, for healthcare clients, a product or condition.
- Our hosting and infrastructure providers (Vercel for the app, a managed Postgres provider for the database), under their data processing terms.
- Authorities, when the law requires it.
Google user data
When a client signs in with Google to connect a Google Ads account, Trakbolt asks for access to Google Ads (adwords) and Google's Data Manager (datamanager). We use that access only to read the client's campaign costs and to upload the client's own conversions and approved audiences to that account. Trakbolt's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google user data for advertising, sell it, or let people read it except where the client asks for support, for security, or where the law requires. A client can disconnect at any time in Settings → Ad accounts, which revokes the token at Google and deletes our copy.
How long we keep it
- Raw visits: the client's retention period (395 days by default), then deleted automatically.
- People, leads and orders: until the client deletes them or closes its account.
- Ad-account tokens: until the account is disconnected.
- App user accounts: until the user is removed; audit records are kept for security.
Security
Data is encrypted in transit and at rest; secrets and any stored contact details are also encrypted in the application. Every record belongs to one client workspace and no query crosses workspaces. Staff access is limited and logged.
Your choices and rights
Visitors can block or clear the wp_vid cookie, and clients can respect consent choices through the consent settings of their workspace. If you are a visitor or customer of one of our clients, contact that business first: it decides what is collected and can delete your data in Trakbolt. You can also write to us and we will pass your request on. App users can ask us for a copy of their data, a correction, or deletion. Depending on where you live you may have further rights (for example under the GDPR or US state privacy laws), including the right to complain to a data protection authority.
Children
Trakbolt is a business service and is not directed at children under 16.
Changes
We will post changes here and update the date at the top. Significant changes are announced to app users by email or in the app.
Contact
Questions or requests: hello@trakbolt.com.