Last updated: October 4, 2026
This policy describes how Paul Katic, publisher of Should I Bid, collects, uses and protects your personal data in connection with the use of Should I Bid, in accordance with the General Data Protection Regulation (GDPR).
The data controller is Paul Katic, who publishes Should I Bid as an individual. For any question regarding your data: contact@shouldibid.app. If the business is taken over by a company, this policy will be updated to say so.
We collect the data you provide (name, email address, account and company information), the data required for billing (processed via Stripe), as well as Service usage data (keywords submitted, analyses performed, technical logs). If you connect your Google Ads account, the data described in section 5 is added.
Your data is processed to: provide and improve the Service (performance of the contract), manage billing (legal obligation and contract), ensure security (legitimate interest) and, with your consent, send you marketing communications.
We use providers to operate the Service, notably Supabase (hosting and database), Vercel (website hosting and audience measurement), Stripe (payments) and third-party data analysis providers. These providers only access data to the extent necessary for their task.
You can choose to connect your Google Ads account to Should I Bid. This connection is optional: all analyses remain available without it. It goes through Google's authorization screen, where you give your consent. Google offers a single permission for Google Ads (see, edit, create and delete): Should I Bid only uses it as described below.
Data we access:
• the list of Google Ads accounts you have access to (ID, name, currency, time zone), so you can choose which account to use;
• the structure of your campaigns (campaigns, ad groups, keywords, negative keywords), to avoid duplicates and let you choose where to add items;
• the status, daily budget and presence of ads of a campaign created by Should I Bid, when you enable or pause it;
• your search terms reports and their statistics (clicks, cost, conversions), only when you ask for them to be analyzed.
How we use it: this data is used only to provide the features you trigger in Should I Bid: showing your accounts, creating campaigns, ad groups, keywords, negative keywords and draft ads at your request, and analyzing your search terms. We only change your account when you explicitly ask us to (a button in Should I Bid, or a request you confirm in Claude). Campaigns we create are paused: nothing runs, so nothing is spent, until you enable them, in Google Ads or in Should I Bid after a confirmation that shows the daily budget. When you choose an existing campaign, Should I Bid only adds the ad groups, keywords and negatives you selected: paused, unless you ask for them to be enabled right away; negatives apply as soon as they are added. Should I Bid can only enable or pause campaigns it created itself; it never changes the budget or bids, nor the status of your other campaigns.
Sharing: we never sell your Google Ads data. We do not use it for advertising (targeting, retargeting, personalized ads) or to assess creditworthiness, and we do not transfer it to advertising platforms or data resellers. It is only shared with the providers strictly needed for the features you use: Supabase (hosting) and, when you ask for your search terms to be analyzed, our artificial intelligence provider (OpenRouter), configured so that this data is not used to train models. If you use Should I Bid from Claude or through our API, the result of the action you requested (for example the list of your accounts or a summary of what was created) is returned to your conversation or application, at your request. Finally, data may be disclosed to comply with the law, for security purposes (investigating abuse), or as part of a merger or sale, with your explicit prior consent.
Human access: no one at Should I Bid reads your Google Ads data, unless you ask us to (for example for a support request), it is necessary for security (investigating a bug or abuse), it is required by law, or it is aggregated and anonymized for the internal operation of the Service.
Retention and security: your Google authorization is stored encrypted on our servers. It is never displayed, nor passed to Claude, Anthropic or any other tool. The list of your accounts and the structure of your campaigns are read when you need them and are not stored. Along with your Should I Bid account, we keep the history of what Should I Bid created in your Google Ads account (what and when) and the results of the analyses you run. They are deleted with your Should I Bid account.
Disconnection and deletion: you can disconnect your Google Ads account at any time from Should I Bid; your authorization is then deleted from our servers. You can also revoke it directly with Google at https://myaccount.google.com/permissions. To request the deletion of data obtained from your Google Ads account, write to contact@shouldibid.app.
Should I Bid's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.
Your data is retained for the duration of your contractual relationship, then archived or deleted in accordance with applicable legal obligations.
You have the right to access, rectify, erase, restrict, port and object to your data. You can exercise these rights by writing to contact@shouldibid.app. You may also file a complaint with the competent supervisory authority.
The Service uses cookies strictly necessary for its operation (authentication, session). Any analytics cookies are only set with your consent.
We measure website traffic with Vercel Web Analytics, provided by our hosting provider Vercel. It sets no cookies: it counts visits in an aggregated, anonymous way (page viewed, referring site, country, device and browser type). Before anything is sent, the page address is stripped of its parameters, except campaign parameters (utm).
We implement reasonable technical and organizational measures to protect your data against unauthorized access, loss or alteration.