Privacy Policy
Effective: 10 May 2026 · Updated: 19 November 2026 · Version 1.12
This Privacy Policy describes how SOFTSURE LLC, the operator of SelfPub Go (“we”, “us”, “the platform”), collects, uses, shares, and protects personal data of users in the European Economic Area, the United Kingdom, the United States, and other regions we serve. We comply with the EU General Data Protection Regulation (GDPR), the UK GDPR, the California Consumer Privacy Act (CCPA / CPRA), and applicable state privacy laws.
1. Who we are (data controller)
The data controller is SOFTSURE LLC, a limited liability company registered in Georgia (ID 445788915), Angisa Street N 20-22, Building N 33, Batumi, Georgia, operating SelfPub Go at selfpubgo.com. We act as a data controller for account information and as a data processor for the Amazon Ads data we retrieve on your behalf and the book details and files you add. Your KDP royalty reports are not uploaded to us — see section 2. Contact: privacy@selfpubgo.com; the company directly: contact@softsureco.com.
2. What we collect, and the legal basis for each
- Account data — email, full name, hashed password or OAuth provider id, and how you signed up (on the website, with Google, or in the desktop app). Legal basis: contract performance (Article 6(1)(b)).
- Workspace metadata — workspace name, primary marketplace, default currency, locale. Legal basis: contract performance.
- Amazon Ads credentials — encrypted refresh tokens obtained via Amazon’s OAuth flow. We never see your Amazon password. Legal basis: contract performance + your explicit consent at OAuth grant time.
- Amazon Ads data — campaigns, keywords, search terms and performance figures (including Kindle pages read from ads) that we retrieve from Amazon through your authorisation. Stored on your behalf, processed only for your workspace. Legal basis: contract performance.
- KDP royalty reports — not collected. The desktop app reads them on your own computer and keeps the result in a local database there; the reports themselves are never uploaded to us. AI features you use, such as the weekly summary, send the royalty and profit totals they need through our server to Anthropic for that one request, and we don't store them. To set up your books, the app sends us only the book identifiers it finds in a report — ASIN, marketplace, format, title and author name. Legal basis for those identifiers: contract performance. The app also tells us whether you have loaded reports, how long ago and how often, and whether they came through our Chrome extension or by hand — never the figures, titles or file names in them. Legal basis: legitimate interest (Article 6(1)(f)).
- Approximate location — the country (and, for a few regions, the region) worked out from the IP address of your requests, so that AI features stay off where our AI provider does not offer them. We keep only the country code with your account, not the IP address. IP Geolocation by DB-IP. Legal basis: legitimate interest (Article 6(1)(f)).
- AI app connections — if you connect an AI app such as Claude or ChatGPT: which app, its access level, the changes you approved through it, and a log of its requests without their content. Section 5 has the details and the legal basis.
- Manuscripts and book metadata— files and text you add. If you write or lay out a book in the app (Manuscript), we keep a copy of its text, its recent saved versions and its images on our servers, so you can open the book on another computer or get it back. Treated as your intellectual property and processed only for your account. The text goes to our AI provider (Anthropic) only when you press an AI button in Manuscript — such as checking the text or writing texts for Amazon from the book — for that one request, and we don't store what was sent. Legal basis: contract performance.
- Comments on a book you share — if you give readers a link to your book (selfpubgo.com/read/…), we keep the shared copy while the link works, and the comments readers leave there: the name they type, the comment, the quoted passage and its place in the book. A reader’s browser is told apart by a random key it makes itself; we keep only a hash of that key, not the reader’s IP address. You see all comments on your book; a reader sees only their own. Legal basis: contract performance for you; for readers, legitimate interest in passing their comments to the author they wrote them for (Article 6(1)(f)).
- Usage analytics — page views, referring site, device and browser, and a small set of product events (sign-up, installer downloads), reported to Google Analytics 4. Opting in is what lets the tag store anything on your device and recognise you across visits: Google then assigns a random client ID kept in the
_gacookie. That is pseudonymous rather than anonymous. Either way your IP address reaches Google’s servers as part of the request — section 6 explains what is and is not sent if you decline. We attach no name, email, or account ID to these events. Legal basis: consent (Article 6(1)(a)). - Referral source of your registration — the campaign tags a link carried (
utm_sourceand friends, or agclid/msclkidfrom an ad click), the site that referred you (host and path, never its query string), and the first page you opened, plus the country of your connection (our hosting provider works it out from your IP address; we keep only the country). Recorded by us, not by a third party, and sent to our own server only when you actually register. It carries no name, e-mail, account ID or device identifier. Where it is kept depends on your banner answer: accepting analytics stores it in our ownspg_attrcookie for 90 days, otherwise it lives in your browser’s session storage and is gone when you close the tab. Legal basis: legitimate interest in knowing which channels bring authors to us (Article 6(1)(f)) — and, for the 90-day cookie, your consent to analytics storage. - Desktop app install records — when you run the desktop app it reports a random installation ID it generated itself, the app version, the operating system name, and the time it last started. Once you sign in, that record is linked to your account. No device identifier, serial number, MAC address or advertising ID is collected, and the ID means nothing outside our database. Purpose: knowing which builds are actually in use, so support and updates work. Legal basis: legitimate interest (Article 6(1)(f)).
- Public demo sign-ins — when someone signs in to the shared demo account, we record the time, the country and IP address the sign-in came from, and the type of app or browser used. We use this to count demo visits and to stop abuse of a password that anyone can see. IP addresses are deleted after 30 days. Legal basis: legitimate interest (Article 6(1)(f)).
- Diagnostic logs — error reports, request traces. Personal data is redacted before logging. Retention: 30 days. Legal basis: legitimate interest in operating a reliable service.
- Billing data — when you buy a plan, Paddle.com, our Merchant of Record, collects your payment details, billing address and tax details on its own checkout and processes them as a controller under its own Privacy Notice. We never see or store your full card number. From Paddle we receive and keep the record of your purchases: your Paddle customer and subscription IDs, the plan and billing period, amounts, tax and currency, payment status and dates, and the type of payment method (for a card, its brand and last four digits). Legal basis: performance of our contract with you (Article 6(1)(b)) and our legal obligations for tax and accounting records (Article 6(1)(c)).
We do not collect special-category data (race, religion, health), and we do not knowingly collect data from children under 16. If you believe a child has provided personal data, contact us immediately.
3. How we use your data
We process personal data to:
- Provide the platform and the modules you have enabled.
- Send transactional email (account verification, password reset, billing receipts, security alerts) — these cannot be opted out of while you have an active account.
- Send emails that help you get started (for example, connecting Amazon or installing the app) and an email when a new version of the app comes out, telling you what is new in it. Every such email has an unsubscribe link. In these emails we count which links are pressed: we record which email, which link and when — nothing about your device or location. Legal basis: legitimate interest (Article 6(1)(f)).
- Send other news and educational content — only if you opt in, with opt-out anytime via the email footer.
- Improve the platform — aggregated usage analytics (see section 2), A/B tests on UI improvements.
- Detect fraud, abuse, and policy violations.
- Comply with legal obligations (tax, audit, lawful subpoena).
We do not sell personal data. We do not use your data, your ad campaigns, or your manuscripts to train AI models — ours or any third party’s.
4. Sub-processors
We use the following sub-processors, each bound by Data Processing Agreements aligned with GDPR Article 28:
- Supabase (United States) — authentication, database, file storage for your selfpubgo.com account.
- Vercel (United States) — website hosting.
- Anthropic (US / EU) — the AI features, including the weekly summary and the AI buttons in Manuscript. Anthropic does not train on our API data.
- Resend (US) — transactional email delivery.
- Railway (United States) — the servers and database behind the app: your account, Amazon Ads data and book list.
- Amazon Web Services — receives the Amazon Marketing Stream data Amazon sends for your campaigns.
- Google LLC (United States) — Google Analytics, for the usage analytics described in section 2. It loads on every page, but until you accept analytics it stores nothing on your device and sends only anonymous pings. Processing takes place in the United States.
- Cloudflare (global) — domain services, protection against attacks, and file storage.
- Amazon Advertising API — read/write to your Amazon Ads account. We act on your behalf via your OAuth grant and submit data only to Amazon.
Material additions are notified by email at least 30 days in advance with a right to object.
AI apps you connect to your account yourself, such as Claude or ChatGPT, are not on this list: they are recipients you choose, not our sub-processors. Section 5 explains what they receive.
Payments are handled by Paddle.com, our Merchant of Record: you buy your plan from Paddle, which processes your payment details as a controller under its own Privacy Notice, so it is not one of our sub-processors.
5. AI apps you connect (Claude, ChatGPT)
You can connect an AI assistant, such as Claude by Anthropic or ChatGPT by OpenAI, to your SelfPub Go account through our MCP server at mcp.selfpubgo.com. Nothing is shared until you sign in on selfpubgo.com and press Allow on our consent screen. How to connect and disconnect: Claude & ChatGPT.
- What the AI app receives — the answers to the requests it makes for you: your books (titles, ASINs, formats, marketplaces, list prices and the royalty-per-sale and break-even figures SelfPub Go works out), your book ideas and book projects (niche, format, price, paper, costs, links, notes, keywords, competing books, the title, description and keyword fields you prepared for Amazon, checklist marks and release-plan dates), your Amazon Ads campaigns, ad groups, keywords, targets, bids and budgets, ad results, the search terms shoppers typed before clicking your ads (including the ones SelfPub Go’s nightly AI check marked as not about your book, and why), negative keywords, Best Sellers Rank, ratings and keyword positions, tracking links for ads outside Amazon and their results, your Amazon Ads billing status and notices, your change history in SelfPub Go and in Amazon Ads, your notes and tasks in SelfPub Go, keyword and niche research estimates, and the results of the KDP calculators it runs for you. The sign-in also gives it your account’s name and email address. It does not receive your KDP royalty reports, your password or your Amazon Ads sign-in tokens.
- Who receives it — the provider of the AI app you chose (for example Anthropic or OpenAI), which handles it under its own terms and privacy policy and your settings with it. We send nothing to an AI app you have not connected, and we do not control what its provider keeps.
- Changes — if you leave Allow changes ticked, the app can also propose changes to your campaigns, to your book records, book ideas and book projects in SelfPub Go, and an ads launch for a new book, whose campaigns start spending once created. Each change is applied only after you confirm it in the chat. We keep each proposal and its result, with the values before and after, so it can be shown in your change history, marked as made by AI, and undone.
- What we log — for every request: the time, which tool was called, the size of the request and of the answer, the number of rows returned, how long it took and whether it worked. We also keep which apps you connected (the name the app gave itself and the web address it returns you to), their access level, and when each was connected, last used and disconnected. We do not log your conversation, your questions or the answers. Purpose: running the connection, its request limits, security and support. Legal basis: contract performance and legitimate interest (Article 6(1)(f)).
- Retention — while your account exists; all of it is deleted with your account.
- Your controls — disconnect any app in the SelfPub Go app (Settings → Connect AI) or on selfpubgo.com (Connected AI); its access stops at its next request. You can switch changes on or off for each app in the same place, and remove SelfPub Go from the AI app itself. To delete what the provider already received, use that provider’s own settings.
- Royalties in Claude Desktop — separately, when you switch it on, the SelfPub Go app lets Claude Desktop read your royalty and profit numbers from the app on your own computer, read-only. They go from your computer to your Claude chat and do not pass through our servers.
6. International transfers
The servers and database behind the app run in the United States (Railway), and so do the website’s account database (Supabase) and server functions (Vercel), so account and Amazon Ads data is processed there under the safeguards below. Analytics is opt-in: Google Analytics 4 is operated by Google LLC in the United States, so accepting analytics cookies sends your page views, device information, and IP address to servers in the US. If you decline, the tag stores nothing on your device and sends only cookieless pings with no identifier that can single you out — though the request itself still reaches Google.
For other third-country transfers we rely on Standard Contractual Clauses (Commission Decision 2021/914) with supplementary measures including encryption at rest and in transit.
7. Retention
- Active account data — for the lifetime of your account.
- Account deletion — from the app (Settings → Account → Delete account) sign-in closes at once and your data is erased within minutes; a request by email is completed within 30 days. Backups roll off within 90 days.
- Record of a deletion — your email address, account number and the dates of sign-up and deletion, kept for 2 years to show the request was honoured. Used for nothing else and not shared.
- Billing records — 7 years (legal obligation in most jurisdictions).
- Diagnostic logs — 30 days.
- Referral source — 90 days in your browser (or one visit without the cookie); the copy stored with your registration is deleted with your account.
- AI app connections and their request log — while your account exists; deleted with it (section 5).
- Manuscripts — the copy, its versions and images until you delete them in the app or delete your account. A shared copy — until you revoke its link or the link expires; readers’ comments — until you delete them, or with your account.
- Install records — deleted with your account. A record never linked to any account holds no personal data (a random ID, version, OS) and is kept as long-term product statistics.
- Demo sign-ins — IP addresses 30 days; the time, country and type of app or browser are kept as statistics.
- Audit logs — 12 months minimum, longer if required by law.
8. Your rights
Under GDPR / UK GDPR, you have the right to:
- Access — request a copy of all personal data we hold.
- Rectify — correct inaccurate data.
- Erase — delete your account in the app, or request deletion (subject to legal retention obligations).
- Port — receive data in machine-readable format.
- Restrict / object to specific processing.
- Withdraw consent at any time.
Exercise any of these by emailing privacy@selfpubgo.com. We respond within 30 days. If you are unsatisfied, you have the right to lodge a complaint with your supervisory authority.
California residents have equivalent rights under CCPA / CPRA, including the right to know what we collect, the right to delete, and the right to opt out of any sale (we do not sell). Submit requests to the same address; we verify identity before processing.
9. Security
We protect your data with technical and organisational measures suited to the risk. More on the Security page.
10. Cookies
See Cookie Policy for the full list. In short: strictly necessary cookies for auth, opt-in cookies for Google Analytics 4 plus our own 90-day spg_attr cookie that remembers which channel brought you (set only if you accept analytics), and no advertising cookies at present.
11. Changes to this policy
We update this policy when we add sub-processors, change retention windows, or expand processing purposes. Material changes are notified by email at least 30 days before they take effect. Minor clarifications are versioned in the version history at the end of this page.
12. Contact
privacy@selfpubgo.com — all privacy requests, including DSARs, breach notifications, and DPO inquiries.
13. Version history
- 1.12 — 19 November 2026: we now email you when a new version of the app comes out and count which links in our emails are pressed; every such email has an unsubscribe link.
- 1.11 — 17 November 2026: the desktop app now tells us whether, how and how recently KDP reports were loaded — never what is in them.
- 1.10 — 29 October 2026: removed technical detail from sections 4, 7 and 9. What we collect and why has not changed.
- 1.9 — 23 October 2026: added billing data — payments through Paddle.com, our Merchant of Record.
- 1.8 — 23 October 2026: added manuscripts kept for Manuscript, readers’ comments on books you share by link, and when manuscript text goes to AI.
- 1.7 — 19 October 2026: added public demo sign-ins; the referral source now names the country; account data now names how you signed up.
- 1.6 — 15 October 2026: added section 5, AI apps you connect (Claude, ChatGPT).
Earlier versions are available on request at privacy@selfpubgo.com.