Legal
Privacy Policy
Last updated 15 October 2026
This describes what the product does, not what a template says. The short version: your CRM data is read in your browser and is not uploaded, and the only customer data we keep on a server is what an advertising platform needs to match a conversion - hashed identifiers, a timestamp and an amount.
Who we are
ValueBasedBidding is operated by BetterSignals. For questions or requests about your data, write to alon@bettersignals.co.
Where our customer is a business using the product on its own data, that business is the controller of the personal data in its CRM and we are its processor. For our own website and marketing contacts, we are the controller.
What we store on our servers
This is the complete list. There is nothing else.
| What | Why |
|---|---|
| Hashed email addresses (SHA-256) and ad click IDs | The only way an advertising platform can match a conversion to the click that produced it. The hash is one-way; we cannot read the address back out of it. |
| A conversion timestamp, a value and a currency | What is sent to the ad platform, and nothing more. |
| Your answers about your business, beside a summary of your analysis | Who you sell to, the sales cycle and customer sizes you gave, each short claim taken from your description with whether your data bore it out, and counts from the analysis (rows read, deals it learned from, factors kept, the measured sales cycle). Used by us to understand who the product works best for. Never your description itself, a CRM row or an amount. |
| A model identifier, and the rules a saved model contains | So any figure can be traced back to the rule that produced it. The rules are segment-level statistics - a close rate, an average deal size, and the category each applies to, such as an industry - never an individual record. |
| Encrypted access tokens for a CRM or ad account you connect | Encrypted at rest. Needed to read your leads on a schedule and to send values on your behalf. |
| Workspace and run records - a workspace name, when a sync ran, how many rows it handled, and hashed IP addresses for rate limiting | Operating the service and stopping abuse. |
| Your name and work email, given at signup or through Sign in with Google | To let you back into your workspace and to reach you about it. |
| Your phone number, only if you chose to give one at signup | To call you about your results, when you asked for that. Never shared. |
| Billing records - your plan, its status and dates, and the last 30 days of ad spend on campaigns that bid with your values | Your plan is priced on that spend. Card details are held by our payment provider, never by us. |
| The link to a Google Sheet you connect, which tab to read, and the column names and status words you confirmed | So we know which sheet to read and how to read it. Its rows are read to price new leads but never stored, and removing our access from the sheet’s sharing settings ends it at once. |
| For Meta: a hashed phone number, Meta’s own browser tokens, the browser’s user agent and the form page address (never its query string) | What Meta needs to match a lead to the ad that produced it. |
What we never store
We do not keep CRM records. Specifically, we never write to our servers:
- Names, postal addresses or phone numbers
- Email addresses in readable form, anywhere in the conversion feed
- Individual deal amounts, company names or job titles
- Notes, free text or anything a salesperson typed
This is enforced by the database rather than by policy. The conversion table carries constraints that reject a row whose email field is not a 64-character hash, so a plaintext address cannot be written even by mistake.
One exception, stated plainly: if you give us your email address on our website - to receive a report or to be contacted - we store that address in readable form, because an address we cannot read is an address we cannot write to. That is a marketing contact, kept separate from any customer’s CRM data, and you can ask us to delete it at any time.
Where your CRM data is actually processed
A file you upload never leaves your browser. It is read, mapped and analysed on your own machine. The model is fitted there. Only the finished conversion rows - hashed identifier, time, value, currency - are sent to our server, and only when you choose to publish them.
A connected CRM is read through our server but not written down. When you connect HubSpot or share a Google Sheet with us, deals pass through our service to your browser, which does the analysis. Once you send values, our server also reads new leads as they arrive and prices them on the model you saved. Those records are held in memory while that happens and are not saved; only the conversion rows described above are.
The one AI call, and what it is not allowed to see
When you load your leads, we make a single call to Anthropic, the AI company, which does not train its models on what is sent through its API. Its only job is to suggest which column in your file is which, and to note the claims you made about your buyers so the product can test them against your data.
It never receives your rows. It is sent a description of each column: the header name, what kind of value it holds, how often it is filled in, how many distinct values there are, and - only for short category columns like an industry list - a few example labels. It is never sent an email address, a name, a phone number, an address, a click ID, a deal amount, or free text.
The one exception is yours to switch on: sorting a free-text column into a few groups. Only then is that column's text sent, with email addresses, phone numbers, street addresses and links removed first, and it is not kept.
It never produces a number. Every value, multiplier and rate in the product comes from arithmetic on your own rows. If the AI call fails, the product carries on without it.
Who else touches the data
We use these providers, and no others, to run the service:
- A hosting provider - runs the site and the service.
- A database provider - holds the tables described above.
- Anthropic - the AI provider, for the column-mapping call, on the column descriptions above, and the free-text sorting only when you switch it on.
- An email provider - the alerts you ask for, and messages you send us from the contact page or the help panel, which reach our inbox and are not stored.
- A payment provider - payments, when a paid plan applies. It holds your card details; we never see them.
- Google and HubSpot - when you connect them, to send values and read deals respectively, under the permissions you grant. Google also, when you share a Google Sheet with us, to read that one sheet. Meta, when you connect it, to send values to the Dataset you choose.
- Analytics providers - to see which pages get visited and how they are used, never with your CRM data. Described on their own below.
We do not sell data, and we do not share it for advertising of our own.
Analytics on this website
This site uses analytics services to see which pages get visited and how. They set cookies in your browser and report page views and clicks. One of them also records how a page is used (scrolling, clicks and pointer movement) so we can see where a page is confusing, as heatmaps and as replays of a visit. Anything typed into a field is hidden from it.
On the product screens, where you load leads, see values, connect accounts or read results, that recording only sees the shape of a visit: which step you are on, and where you click and scroll. Everything on those screens that comes from your data (your leads, deals, column names, values and figures) is masked before anything is recorded, so it is never captured. Only our own buttons and menus stay readable.
Neither has a route to your CRM data. A file you upload is read and priced in your browser and is never sent anywhere, which is a promise the product keeps regardless of whether this cookie exists - analytics could not see that file even if it tried. They see which pages you visited, not what you typed into them.
For visitors from the EU, Iceland, Liechtenstein, Norway and Switzerland, none of it loads at all, unless they accepted it on an earlier visit. “Cookie settings” at the foot of the page withdraws that.
You can also opt out at any time by blocking third-party cookies in your browser or with a tracker-blocking extension.
What we send to Google, and why it is hashed
When you publish, we send Google a conversion for each lead: the click ID if there is one, the hashed email if there is one, the time, the value and the currency. Both identifiers travel together where a lead has both, because Google matches on the click ID and falls back to the email.
The email is hashed (SHA-256) in the format Google requires: in your browser before it leaves, when you publish from a file, or on our server in memory, when the leads come from a connected CRM. Only the hash is ever stored or sent. Google matches the hash against its own hashed records. Neither we nor anyone reading our database can reverse it.
What we access in your Google account
We ask Google only for what the product needs, and only when you choose to connect:
- Sign in with Google (your name, email address and profile picture): to create your account and let you back in. We keep your name and email address.
- Google Ads (the
adwordspermission): to list the ad accounts you can use and their currency, create one conversion action for your lead values, and read which bid strategy each campaign uses so we can tell you whether it will use the values. We never change a campaign, budget, bid or keyword. We keep the account ID you choose. - Google Data Manager (the
datamanagerpermission): to send each lead’s conversion value to that conversion action, as described below.
The access Google gives us is stored encrypted and deleted when you disconnect. We do not sell Google user data, do not use it for advertising, do not use it to train AI models, and do not share it with anyone except as needed to run the product for you. You can remove our access at any time at myaccount.google.com/permissions.
ValueBasedBidding.com’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
How long we keep it
- Conversion rows: kept while your feed is active, so a platform can collect them and so a republish does not send the same conversion twice. Deleted when you delete the feed, and on request.
- Access tokens: deleted when you disconnect the account.
- Run records: kept for operational history.
- Your account and billing records: while your workspace is open, and billing records as long as tax law requires.
- Marketing contacts: until you ask us to remove yours.
Your rights
You can ask us for a copy of what we hold about you, ask us to correct it, or ask us to delete it. Write to alon@bettersignals.co and we will respond within 30 days.
If you are an individual whose details sat in a customer’s CRM, that customer controls the data and is the right first point of contact. Tell us anyway and we will help them act on it.
Depending on where you live you may also have the right to complain to a data protection authority.
Security
Traffic is encrypted in transit. Access tokens are encrypted at rest. Feed URLs are authorised by a token we store only as a hash, so a copy of our database does not hand anyone a working feed.
No system is perfect. If we discover a breach affecting your data we will tell you promptly and say what happened.
Changes
If we change how the product handles data, this page changes with it and the date at the top moves. Material changes will be told to active customers directly rather than left here to be noticed.
Questions about anything on this page: alon@bettersignals.co