Privacy Policy

This Privacy Policy explains how Publisheds processes information when you use our website, web application, and the prepared Publisheds browser extension release candidate 0.6.2. It describes the product's current data flows; it does not replace any rights you may have under applicable law.

1. Who this policy covers and how to contact us

“Publisheds”, “we”, “us”, and “our” mean the operator of the services offered under the Publisheds brand. For a privacy question, request, or concern, email [email protected]. Please do not send passwords, access tokens, recovery codes, or other secrets by email.

2. Information we process

Depending on which Publisheds features you use, we process the following categories:

• Account and workspace information: account identifiers, email address, display or profile information, authentication state, membership, role, and plan or entitlement information.
• Content you provide to the service: catalog, publishing, project, document, and operational information that you enter, import, or choose to synchronize.
• Service and security information: requests made to our services, authentication and session events, feature configuration, error information, and information needed to prevent abuse, secure accounts, and operate the service.
• Public market observations: when the extension's market-contribution setting is on, observations from Amazon or Audible pages that you have opened, such as search terms, ASINs, titles, authors, formats, prices, ratings, review counts, ranking, page counts, language, publisher, ISBN, and category or listing facts. The extension does not send descriptions, cover images, or review text through that contribution flow.

3. Browser extension data and permissions

The extension needs access to the Amazon, Audible, KDP, and KDP Reports pages declared in its manifest so it can show its interface and perform the features you request on those pages. It does not request the Chrome cookies, history, or webRequest permissions. It does not read a browser-wide history or collect data from websites outside its declared host permissions.

The extension reads page content only on the declared pages. It can keep local book and keyword caches, watched-item history, settings, sync status, and a local KDP publication draft so that features continue to work in the same Chrome profile. A KDP publication draft is used locally to fill fields after you initiate that workflow; the extension does not send that local draft to Publisheds merely because it is stored.

The extension also creates a random installation identifier, sent as the authorization client_id, and stores it in Chrome local extension storage. It binds an extension authorization grant to the Chrome profile that started it. It is not derived from device hardware, browsing history, or account credentials, but it persists until extension data is cleared or the extension is removed.

Market contribution is off by default in version 0.6.2. It starts only after you opt in through the extension controls. When enabled, observations are queued and sent to Publisheds after a delay to help build market data. Although the observation payload is limited to market facts, the request is made through your signed-in Publisheds session; do not treat it as an anonymous browsing mode. Turning the setting off stops new contribution payloads from being queued or sent.

Earlier extension versions could treat market contribution as active when the setting had never been defined. Version 0.6.2 migrates an undefined setting to off and does not send queued market observations while the setting is off. After updating, review the Market contribution setting before choosing whether to opt in.

4. KDP, reports, and Amazon Ads

After you connect Publisheds and open a supported KDP catalog page, catalog synchronization can start automatically when the signed-in tab is visible and the safety interval permits it. A full scan is limited to once every 24 hours after a successful scan. While the catalog page remains open, the extension schedules a one-page observation at a randomized interval of approximately 11–16 minutes. Work due while the tab is hidden is deferred until it becomes visible; retries and manual runs are subject to backoff and safety cooldowns. A manual sync control is also available.

The KDP catalog snapshot sent to Publisheds can include title and edition identifiers, title, subtitle, author, format, publishing status, ASIN or ISBN, marketplace, price, currency, and publication metadata. The Premium KDP financial-report flow, when available to your account and initiated by you, sends the selected report data to Publisheds for import into your workspace.

The prepared 0.6.2 release candidate does not include an Amazon Ads integration. It does not request Amazon Ads host permissions, does not bundle or run Amazon Ads content scripts, does not expose Amazon Ads web-accessible resources, and does not transmit Amazon Ads report rows to Publisheds. If a future release adds that integration, this policy and the relevant in-product disclosure will be updated before the change.

Publisheds is independent from Amazon, KDP, Audible, and Amazon Ads. Your use of those services remains subject to their own terms and privacy notices.

5. Authentication and tokens

You may authenticate in Publisheds using the available account sign-in methods. If you choose an external identity provider, that provider handles its own sign-in page and privacy practices; Publisheds receives the information needed to establish and manage your account.

When you choose Google OAuth, Publisheds requests the openid, email, and profile scopes. Google can return its stable subject identifier (sub), your email address (email) and verification flag (email_verified), and profile claims available for your account, such as name, given_name, family_name, picture, and locale. Publisheds does not receive your Google password.

For the extension, an access token is kept in Chrome session storage and a refresh token may be kept in Chrome local extension storage so the session can be renewed. The PKCE verifier, nonce, state, and expiry used during authorization are kept only in session storage. They expire after 180 seconds. A retryable network or server failure keeps them available until that expiry so the exchange can be retried. Retrying authorization reuses the pending transaction until it expires; successful exchange, terminal validation failure, or the end of the browser session clears it earlier. The extension does not use the website's cookies as its extension session and does not request permission to read cookies. Signing out clears the local extension session and asks the service to revoke the refresh token.

6. How we use information

• to provide, secure, troubleshoot, and improve Publisheds and the features you choose to use;
• to authenticate users, maintain sessions, enforce roles and entitlements, and prevent fraud or misuse;
• to store and present your workspace, catalog, and selected provider imports;
• to produce the market-data features from permitted public market observations; and
• to comply with applicable legal obligations and respond to valid requests.

We do not sell personal information or use the extension to serve third-party advertising.

Where data-protection law requires a legal basis, we use performance of the service agreement or steps you request to provide account and publishing features; consent for processing presented as optional or consent-based; legitimate interests in security, fraud prevention, service reliability, and improvement that does not override user rights; and compliance with legal obligations. Consent can be withdrawn for future processing without affecting earlier lawful use.

7. Chrome Web Store Limited Use

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. These commitments apply to raw data and to aggregated, anonymized, de-identified, or derived data handled by the extension:

• we request, collect, use, and transfer only extension user data and permissions strictly necessary to provide or improve the extension's disclosed single purpose: supporting the user's Amazon-first publishing, catalog, reporting, and book-market research workflows;
• we transfer it only when necessary to provide or improve that purpose, to comply with applicable law, to protect against fraud or abuse, or as part of a merger, acquisition, or asset sale after obtaining explicit prior user consent;
• we do not permit humans to read it unless the user expressly consents to access specific data, the data is aggregated and anonymized for permitted internal operations, access is necessary for security, or access is required by law; and
• we do not use, transfer, or sell it for personalized advertising, to advertising platforms or data brokers, or to determine creditworthiness or for lending.

Before a 2026 extension release collects or transmits a category of user data, that collection, its strictly necessary use, and any server transfer must be prominently disclosed in the Chrome Web Store listing and in the relevant installation, connection, or feature control. A materially different purpose requires an updated prominent disclosure and any consent required before use.

8. Sharing, processors, and independent platforms

We use these named providers where the corresponding service or feature is active:

• Cloudflare: delivery and edge security for the public website.
• Hetzner: hosting for the Publisheds application and API.
• Supabase: managed PostgreSQL database hosted on AWS in the eu-west-1 region.
• AWS S3 or configured S3-compatible storage: backups and object or private-file storage.
• Stripe: checkout, subscriptions, invoices, and payment processing when you use paid billing.
• Google: identity information when you choose Google sign-in; the public site also requests Google Fonts from the visitor's browser.
• Sentry: error and reliability monitoring when configured; application text is masked in browser replay and default PII transmission is disabled in server monitoring.
• OpenAI and DeepSeek: processing for configured AI features; only information needed for the requested feature is sent to the selected provider.

Amazon, KDP, Audible, and Amazon Ads are independent platforms, not Publisheds processors. The extension operates on their declared pages and uses the session already present in the browser for the user-facing workflow. Those platforms apply their own terms and privacy notices. We may also disclose information where required by law or necessary to protect the security, rights, and integrity of Publisheds, our users, or others. We do not sell personal information.

The managed PostgreSQL database is located in AWS eu-west-1, while other named providers may process information in other regions according to the service used and their own infrastructure. Publisheds has not yet completed or published a provider-by-provider record of contractual safeguards for international transfers. Finalizing that record and the corresponding contractual safeguards is pending; this policy therefore does not claim that Standard Contractual Clauses, an adequacy decision, or EU-only processing applies to every transfer.

9. Storage, retention, and deletion

On your device, extension data remains in the Chrome profile until the relevant feature clears it, you sign out where applicable, you clear extension data, or you remove the extension. Access tokens are session-scoped; refresh tokens remain only for the lifetime accepted by the service or until they are cleared or revoked. Local tracking history and caches are bounded by the extension's feature limits.

On our systems, we retain account, workspace, and imported data for as long as needed to provide the service, maintain security and records, resolve disputes, or meet legal obligations. Retention can therefore vary by data type and account state. You can request deletion or information about a specific data category by contacting us at the address above.

10. Security

We use access controls, authenticated service requests, token rotation and revocation flows, validation of extension message origins, and other reasonable technical and organizational measures designed to protect information. No service or transmission can be guaranteed fully secure; keep your device and account credentials secure and contact us promptly if you suspect misuse.

11. Your choices and rights

You can turn off market contribution in the extension, sign out, remove the extension, and manage data available in your Publisheds account. Depending on where you live, you may have rights to request access, correction, deletion, restriction, objection, portability, or to complain to a data-protection authority. To exercise a right, contact us at [email protected]. We may need to verify your request and will apply the rights available under the law that applies to you.

12. Changes to this policy

We may update this policy when the service or applicable requirements change. We will post the revised version here and change the effective date. For a material change to extension data use, we will provide an appropriate in-product or release disclosure before that change takes effect.