Privacy policy

What PPC Manager is

PPC Manager is an invite-only web workspace for managing Amazon Sponsored Products advertising, offered to brand owners as software. Access is limited to accounts the operator provisions; there is no self-service signup. This policy explains what data the service processes, where, for how long, and how to ask for a copy or deletion. Advertising data is processed on behalf of the organization that invited you.

How the software handles your work

• The web app stores your records and shows them to you for review.
• The optimization work runs on your own computer, inside your own Claude subscription (from Anthropic), through skills and a small program you install there (the “runner”). We never receive, store or use your Claude credentials, and we never run Claude on your behalf. What Claude processes on your computer is governed by your agreement with Anthropic.
• Bulksheets (Amazon upload files) are built on your computer. You download them and upload them to Amazon yourself; the service never changes anything in your Amazon account.

More detail is on About the software.

Data we process

• Account data: the name, email address and role of each invited user, for sign-in, permissions and service emails.
• Advertising and sales reports: the campaign, keyword, search-term, budget and sales reports you upload (or, if Amazon Ads API access is granted and you authorize it, that the service retrieves read-only, as described below).
• Workspace mirror: a copy of the PPC workspace files on your computer (product settings, campaign structure, weekly results, decisions and bulksheets), sent by your runner and stored in our database and in a private file store. For some files, such as original reports that stay on your computer, only a fingerprint (file path, size and checksum) is recorded.
• Runner details: for each runner you pair, its label, computer name, operating system and Python version, runner version, IP address, when it last connected, and the results of the checks you ask it to run.
• Operational logs: the IP address, country and browser user agent seen at sign-in and on API calls, and an audit trail of actions taken in your workspace (who did what, and when), kept for security and troubleshooting.

Data from the Amazon Ads API

We are applying for access to the Amazon Ads API as a software provider. If access is granted, the service would retrieve your advertising reports only after you authorize it with Login with Amazon, and only with read-only access. Data obtained from Amazon would be:

• used only to provide the service to the user who authorized it;
• never used to create, change or delete campaigns or anything else in your Amazon account;
• never sold, never used to train AI models and never shared with third parties other than the processors listed below, which host the service for us;
• stored, kept and deleted like the rest of your data, as set out below.

Where data is stored: our processors

• Vercel hosts the web app, which runs in the European Union (Dublin, Ireland).
• Supabase provides sign-in, the database and the private file storage, in the European Union (Ireland).
• Resend sends transactional email, such as service notifications.
• GitHub holds the daily database backup, a private GitHub Actions artifact kept for 7 days.

Resend and GitHub may process data outside the European Union. Where they do, the transfer relies on the safeguards those providers offer under the GDPR (Standard Contractual Clauses or the EU-US Data Privacy Framework).

Why we may process it

• Account data, your reports and your workspace mirror: to provide the service you asked for (performance of a contract).
• Operational logs and the audit trail: to keep the service and your workspace secure (legitimate interests).

How long we keep data

• Raw report files you upload stay in private storage until your runner has processed them. Processed files are deleted about 90 days after upload by an automatic clean-up; that clean-up is paused during early access, and until it runs again processed files may be kept longer. A small record of each upload (file name, size, date and checksum) stays with your account history.
• Your workspace mirror and records are kept while your account is active.
• Daily database backups are kept for 7 days and then expire automatically.
• Before a database upgrade, the operator also takes a one-off full copy of the database, kept offline and deleted within 30 days.
• When an account is closed, we delete its data within 30 days. Copies inside daily backups expire within 7 days after that deletion, and inside a one-off upgrade copy within 30 days.

Security

• All traffic between your browser or runner and the service is encrypted in transit.
• Every database query is scoped to your organization, and the database's row-level security blocks every other access path to your data.
• Access tokens, including runner tokens, are stored only as hashes. The runner never holds a database password or a service key.
• Uploaded reports and workspace files move over encrypted connections and sit in private storage; bulk files go directly to private storage over short-lived signed links.

Cookies

We use only the cookies needed to keep you signed in. There are no advertising, analytics or tracking cookies. Your light or dark theme choice is kept in your own browser.

What we do not do

• We do not sell your data or share it beyond the processors above.
• We do not use your data for advertising or to train AI models.
• We run no AI and no optimization logic on our servers.
• We do not mix data between organizations.

Your rights and contact

You can ask for a copy (export) of your data, or for its correction or deletion, at any time: contact the operator at cristian.furcila@gmail.com. Deletion requests are honored within 30 days. You can also complain to a data protection authority.

We announce changes to this policy by email and update the date at the top of this page. Use of the service is governed by the terms of service.