Privacy, in plain words.
Kamply collects little, and this page names all of it. No marketing cookies, no trackers, no selling data.
On this website
Measurement is Cloudflare Web Analytics: cookieless, aggregate page counts, no cross-site tracking, no advertising pixels, no session recording. The site sets no marketing cookies and runs no product telemetry. When you click a download or checkout link, the site records that a click happened, the page it was on, and the first page of your visit. The record holds no email, IP address, cookie or identifier. The first page is kept in your browser tab’s session storage and is gone when the tab closes. The Download page asks GitHub’s public Releases API for the current version, and GitHub serves the DMG; GitHub receives the ordinary network request needed to do that under its own privacy policy.
The walkthrough form
Submitting the form stores your email address, and the role and use-case answers if you give them, in a Cloudflare D1 database. It is used for one thing: replying to you about the walkthrough. It is never sold, shared, or added to a mailing list you did not ask for.
Buying and your account
Checkout and the account page sit on api.kamplyapp.com behind Google sign-in (Cloudflare Access). We store your Google account email, your brand’s name, and your subscription record (plan, status, billing period) in Cloudflare D1. Payment happens at Polar, the merchant of record: your card details go to Polar and never touch our servers. Polar’s own privacy policy covers the payment data it holds. Once you are signed in there, this site asks api.kamplyapp.com whether your browser has a session, so the header can show your account instead of the walkthrough button. That request returns your email, your plan line, and your profile picture if your Google account has one, none of which is stored here; a signed-out visitor is simply told no. The picture is fetched by our own Worker, so your browser never asks Google for it while you read this site.
Competitor Intel
Running a report needs the same Google sign-in. We store the Google account email on the job row, use it to email you the finished report, and count the run against your 20 a day. The job and that email address are deleted after 14 days, along with the report itself. The report page is unlisted rather than private: anyone you send the link to can read it for those 14 days without signing in. The report also holds ad copy and review text quoted from the public pages it read, which belong to the sources it names.
In the Mac app
Your brand assets and everything the app makes stay on your Mac as ordinary files. The app signs in with the same Google identity and fetches the tool keys it works with; those are stored in your macOS Keychain. The app sends us no analytics, and crash reports are kept on your Mac and never uploaded.
When the app uses outside services
Creating a deliverable can send your prompt and the minimum context needed for that step to the service doing the work. Those services can include Anthropic or OpenAI for your own Claude Code or Codex CLI agent running inside the app, OpenAI for opted in image work, ElevenLabs for generated audio, and the stock libraries you ask Kamply to search. Their terms cover the content they process. The app keeps downloaded assets and finished files on your Mac.
Getting your data removed
Email akash@team.kamplyapp.com with the subject “Kamply privacy request”. That route does not create another walkthrough record. We delete your walkthrough entry, account row, or both; Polar handles deletion of the payment records it holds.
Changes
This page changes only when the practices change, in the same commit. Last updated 11 October 2026.