Privacy Policy
Last updated November 15, 2026.
This policy explains how CodepushGo, LLC ("Capve", "we") handles personal data when you use the hosted Capve service at capve.app. CodepushGo, LLC is a US limited liability company at 131 Continental Dr, Suite 305, Newark, DE 19713, United States.
Capve is a campaign and affiliate analytics service. It records clicks and conversions, attributes them to campaigns, and shows reports. If you run your own copy of the Capve software, you are the operator of that copy. This policy applies only to the service we host.
1. Two roles
We play two different parts, and the difference matters.
- Account data. When you create an account, pay us, or write to support, we decide why and how that data is used. Under the GDPR we are the controller.
- Tracking data. Clicks, conversions, and the identifiers that come with them are collected for your campaigns. You decide the purposes and the means. You are the controller. We process that data on your instructions to provide the service. The Terms of Service are those instructions.
You need your own legal basis, and your own notice, for the people who click your tracking links or whose conversions you send us.
2. Account data we collect
When you use the dashboard, API, or MCP server, we collect:
- Name, email address, and a password, stored only as a hash.
- Account, team, and invite records, including each member's role.
- Session cookies that keep you signed in, and a cookie that remembers which account you are viewing.
- API and MCP tokens. We store a hash of the token. The token itself is shown once.
- Billing records: the plan you chose, trial dates, subscription status, and a Stripe customer id. Stripe collects and stores payment card numbers. We do not.
- Campaigns, offers, landers, routing rules, postback URLs, traffic-source settings, and other configuration you save.
- Security and audit logs, such as sign-in events, team changes, and actions taken with an API token.
- Messages you send us, and the transactional email we send you.
3. Tracking data we process for you
When someone opens a Capve tracking link, or when your server reports a conversion, the service stores the data needed to redirect, attribute, and report. That can include:
- IP address and user agent.
- Device type, operating system, and browser, read from the user agent, and a flag when the request looks like a bot.
- Approximate location and network data the edge network provides, such as country, region, city, and ISP.
- Referring domain, click time, and the campaign, path, lander, and offer that was served.
- Click identifiers and parameters on the link, including values you map into sub parameters, an external click id, and a cost if the link includes one.
- A random visitor id in a first-party cookie, and a hash of the IP address and user agent, used to count unique clicks on a campaign.
- Conversion details you or a network send, such as an order id, amount, currency, status, and the click they belong to.
The optional browser snippet stores click_id and velo_ref in localStorage on your site. It does not send a request to Capve from the browser.
We do not sell tracking data. We do not use it to advertise to those visitors, and we do not combine it across Capve customers to build advertising profiles.
4. Cookies
capve_sessionkeeps you signed in. It is HttpOnly, lasts 30 days, and is renewed when you sign in.capve_account_contextremembers the account you are working in. It is also HttpOnly._capve_vidis a random visitor id set on a tracking request. It lasts one year. It is not an advertising id._velo_refstores the affiliate code from a tracking link for 30 days so a later conversion on that browser can be tied back to the click.
Our website analytics provider, DataFast, may set first-party cookies on capve.app to count unique visitors and sessions. They are not used on your tracking links.
Session cookies are required to use the dashboard. Tracking cookies are part of attribution. If a browser blocks them, some clicks will not be tied to a later visit.
5. Why we use account data
- To create and run your account, team, campaigns, and reports.
- To take payment, apply the trial, and enforce the plan's click allowance.
- To send service email: verification, password reset, invites, and billing notices.
- To secure the service, investigate abuse, and keep audit logs.
- To answer support requests.
- To meet tax, accounting, and other legal duties.
The legal bases are performance of our contract with you, our legitimate interest in keeping the service secure and reliable, and legal obligation where a law requires us to keep a record. We do not send marketing mail as part of the service.
6. How long we keep it
- Account data is kept while the account is open, and then for as long as we need it to finish deletion, resolve a dispute, or meet a legal hold.
- Billing records are kept for as long as applicable tax and accounting laws require.
- Click and conversion records are kept for the life of the account. If we set a shorter retention window for raw clicks, clicks older than that window that have no conversion are deleted. Converted clicks stay with the conversion.
- The log of outgoing postback deliveries is deleted after 30 days.
- When you email us to close an account, we delete or anonymize the account and its tracking data within 30 days, except records we must keep and residual copies in backups, which age out on their normal cycle.
7. Who else receives data
We use these processors to run the hosted service:
- Cloudflare, Inc., for hosting, the database, the edge network, and email delivery.
- Stripe, Inc., for subscriptions and payment methods. Stripe does not receive click logs.
- Bento (Bentonow), when enabled, for transactional email to you. Bento does not receive click logs.
- DataFast, for website analytics on capve.app: pages viewed, referrer, browser, device and approximate location. DataFast does not receive click logs.
We also send data when you tell us to. An outgoing postback sends the fields you put in that URL, such as a click id or payout, to the host you named. Team members see the account data their role allows.
We disclose data if the law, a court, or a competent authority requires it, or if disclosure is needed to investigate abuse or to protect the rights, safety, and security of Capve, our customers, or the public.
If we sell or reorganize the business, account data may transfer to the buyer. We will post notice before a different privacy policy applies. Tracking data transfers only as part of providing the service, or as you instruct.
8. International transfers
We are a US company. Cloudflare processes requests on a global edge network, so personal data may be processed outside the European Economic Area. Where the law requires a transfer tool, we use one the European Commission has approved, such as its standard contractual clauses, or we rely on an adequacy decision that covers the recipient.
9. Your rights
If you are in the EEA, the United Kingdom, or Switzerland, you can ask us to access, correct, delete, or restrict your account data, to object to processing based on legitimate interest, and to receive a portable copy. You can also complain to the competent data protection authority where you live or work, or where an alleged infringement occurred.
For tracking data, the controller is the Capve customer who ran the campaign. Direct requests about a click or conversion to that customer. If you ask us, and we can identify the customer, we will pass the request on.
California residents can ask us to know, correct, or delete the personal information we hold as a business, and to opt out of sale or sharing. We do not sell personal information, and we do not share it for cross-context behavioral advertising. We do not discriminate against you for exercising these rights. You may use an authorized agent if you can show the agent has permission to act for you.
Email support@capgo.app to use any of these rights. We may need to confirm that you control the account. We reply within the time the applicable law allows.
10. Children
Capve is a business service. You must be at least 18 to open an account. We do not knowingly collect account data from anyone under 18. If you believe we have, email support@capgo.app and we will delete it.
11. Security
We protect the service with HTTPS, hashed passwords, hashed API tokens, signed HttpOnly session cookies, and access controls between accounts. No hosting method is perfectly secure. If we learn of a breach that the law requires us to announce, we will notify the affected customers and, where required, the supervisory authority.
12. Changes
We will post changes on this page and update the date above. If a change materially reduces your rights, we will also email the account owner before it takes effect.
13. Contact
CodepushGo, LLC, 131 Continental Dr, Suite 305, Newark, DE 19713, United States. Email support@capgo.app.