Privacy
Privacy Policy
Last updated 20 July 2026
This policy covers the SafeBets investor relations landing pages operated by Effective Visibility Marketing on behalf of Foresight Collective, Inc. It describes what these pages actually collect, why, and what you can do about it. It does not cover safebets.world, which is a separate site with its own policy. See When you are sent to safebets.world.
We advertise a securities offering. These pages exist so we can tell which ads work and so we can send the offering materials to people who ask for them. In the EEA, the UK and Quebec nothing at all is stored on your device until you accept the banner, and in practice we ask everyone, everywhere. If you do not accept, we still count that a visit happened, with no identifier attached to it. If you fill in the form, your name and email go to the SafeBets investor relations team, because that is the whole point of the form.
Who is responsible for your data
The controller for these landing pages is Foresight Collective, Inc., 1 World Trade Center, 85th Floor, New York, NY 10007, United States. Foresight Collective is the advertiser of record for the offering.
Effective Visibility Marketing (EVM LLC) builds and runs these pages and the measurement system behind them as a service provider to Foresight Collective, and processes the data described here on its instructions.
For any question about this policy, or to exercise any of the rights below, write to sbleads@evmllcapps.com.
What we collect, and when
Before you make a privacy choice
On the investor landing pages the measurement script is not loaded at all until you answer the banner. Until then nothing is written to or read from your device: no cookie, no localStorage, no sessionStorage, no fingerprint. We record only that a page was viewed, along with the consent state, the region rule that applied, the country and the page path. That record carries no identifier of any kind and cannot be linked back to you or to any later visit.
After you accept
Once you accept, the first-party measurement described below runs. If you decline, we stay in the state above permanently for you, and we record the refusal itself so that you are not asked again on every page.
| What | Detail |
|---|---|
| First-party click id | A value we mint called evmcid. It identifies one click, not one
person, and it is the key that ties a click to the campaign that produced it. It is
ours and is not shared with advertising platforms. |
| Visitor id and session id | Pseudonymous values that let us tell a returning visit from a new one and group pageviews into a single session. They carry no name, email or account. |
| Campaign parameters | The UTM values on the link you arrived from: source, medium, campaign, content,
term and id. Plus our own campaign markers evmtk and
evmtrk. |
| Advertising platform click ids | When an ad platform puts its own click id in the link, we keep it so the click
can be reconciled with what that platform billed us. These include
li_fat_id, gclid, wbraid, gbraid,
dclid, msclkid, twclid, fbclid,
ttclid, sclid, epik, irclid and
rdt_cid. |
| Landing page and page variant | The page you landed on, the page path and title, and a snapshot reference for which version of the page you were shown, so we can compare one version against another. Query strings and fragments are stripped from stored URLs before they are written. |
| Referrer | The address you came from, also with the query string stripped. |
| Device type | A coarse bucket only: mobile, tablet, desktop or bot. Not a device fingerprint. |
| Country | Country only, derived by our hosting provider from your connection. We do not store city, region or any finer location. |
| Consent state | What you chose, the version of the notice you were shown, the exact time in UTC, and which regional rule applied. We keep this so we can prove the choice was yours and so we can honour it. |
| IP address | Stored only as a salted SHA-256 hash. The raw IP address is never written to our database. It is used to derive your country and to detect automated traffic. |
| Browser user agent | Stored both as a hash and, in our pageview and visitor records, as the raw user agent string your browser sends. We use it to bucket device type and to identify bots. See the honesty note below. |
| Event records | Which pages were viewed and which steps were reached, each with a precise UTC timestamp, and a flag for whether the traffic looked automated. |
Our IP handling is strict: the raw address never lands in the database. The user agent is not held to the same standard. We store the hash and we also store the raw user agent string on pageview and visitor records. A user agent is not a name or an address, but it is more identifying than a hash and we would rather say so here than let this policy imply a protection we have not built yet. Reducing this to the hash and the coarse device bucket is on our list.
The request form
If you ask for the offering materials, we collect what you type: your name, email address, phone number if you give one, your self-certification that you are an accredited investor, and whether you opted in to marketing. Alongside that we store the campaign parameters above, the page variant you saw, your browser timezone, language, screen and window size, your country, and hashes of your IP address and user agent. For the form specifically, both the IP address and the user agent are stored only as hashes.
Your self-certification is exactly that: your own statement. It is not verification. Accredited investor status is verified separately by SafeBets before any investment, as Rule 506(c) requires.
Why we collect it
- To measure advertising performance. To know which ad, which campaign and which version of a page led to someone asking for the materials, so we stop paying for the ones that do not work.
- To prevent fraud and keep billing accurate. To spot automated traffic, detect click ids that were not issued by us, and check what platforms invoice us against clicks that actually arrived.
- To contact you about the offering you asked about. If you submit the form, so the SafeBets investor relations team can send you the materials you requested.
We do not use this data to build advertising profiles about you, we do not sell it, and we do not currently send it to advertising platforms.
Legal basis
| Where you are | Basis we rely on |
|---|---|
| EEA, United Kingdom, Quebec | Your consent, collected before anything is stored on or read from your device, for all non-essential storage and for the measurement built on it. You can withdraw it at any time and it is as easy to refuse as to accept. |
| Everywhere, for the essentials | The strictly necessary basis covers the record of your privacy choice itself and basic security. Without storing your decision we would have to ask you again on every page, which is worse for you, not better. |
| Everywhere, for the form | You gave us your details in order to be sent the offering materials, so we process them to do the thing you asked for, and to meet the record-keeping obligations that attach to a securities offering. |
| United States and elsewhere | Measurement runs with notice and a working opt-out. We honour the Global Privacy Control and Do Not Track browser signals when your browser sends them. |
We apply the strictest treatment by default rather than deciding from your IP address whether you are entitled to be asked. Location lookups fail on travellers, VPNs and corporate networks, so we ask everyone and use region rules only to relax that where a jurisdiction genuinely allows it.
How long we keep it
- Identifiers on your device: 395 days (13 months). The cookie carrying the click id and visitor id expires then, and is refreshed while you keep visiting.
- Attribution window: 90 days. A click id older than 90 days is not honoured for attribution even if it is still on your device.
- Consent records are kept as long as we need them to prove your choice was properly obtained and to keep honouring it.
- Form submissions are kept for as long as the investor relations relationship and the record-keeping obligations of the offering require, and are deleted when you ask us to, subject to those obligations.
Who else sees it
We use a small number of service providers. They process data for us and are not permitted to use it for their own purposes.
- Supabase. The database where the records described above are stored.
- Vercel. Hosting and the edge network that serves these pages. It also supplies the country associated with your connection.
- Resend. Delivers the notification email when someone submits the form.
- Pipedrive. The customer relationship system. This route is built but switched off. It sends nothing at all unless and until it is enabled, at which point form submissions would also be created as records there.
Separately, and this is a disclosure rather than a processor relationship: when you submit the request form, your details are sent to the SafeBets investor relations team so they can respond to you. That is what you are asking for when you submit it.
Our providers are United States based, so if you are outside the United States your data is transferred there.
When you are sent to safebets.world
After you submit the request form, and from several links on these pages, you are sent to safebets.world. That is a different website run by a different company. This policy stops at that boundary.
Once you are there, their own cookies, their own analytics and their own privacy policy apply, and the choice you made on our banner does not carry across. If you want to know what they collect, read their policy at safebets.world before you continue.
Your rights and how to use them
Depending on where you live you have some or all of the following rights. We will honour all of them for anyone who asks, wherever you are, rather than checking whether your jurisdiction compels us to.
- Access. Ask what we hold about you and get a copy.
- Deletion. Ask us to erase it.
- Correction. Ask us to fix something that is wrong.
- Objection. Object to our processing, including for measurement.
- Withdraw consent. At any time, and as easily as you gave it. Withdrawing does not undo processing that already happened lawfully.
- Complain. To your local data protection authority. In the UK that is the Information Commissioner's Office.
To exercise any of these, email sbleads@evmllcapps.com. To make a request about measurement data specifically, it helps a great deal if you include the click id from your browser, since that is how those records are indexed. If you cannot find it, tell us roughly when you visited and which ad you clicked and we will look.
To withdraw consent for measurement you can also clear this site's cookies and site data in your browser, which removes the stored decision and the identifiers, and you will be asked again on your next visit.
Children
These pages advertise a securities offering to accredited investors. They are not intended for anyone under 18 and we do not knowingly collect data from children.
Changes to this policy
If we change what we collect or why, we will update this page and change the date at the top. Where the change affects something you consented to, we will ask you again rather than quietly relying on the old answer.
Contact
For privacy-related inquiries:
SafeBets
legal@safebets.world
611 S Dupont Highway, Suite 102
Dover, DE 19901, United States
For anything relating specifically to a request submitted through these landing pages, you can also write to sbleads@evmllcapps.com, which reaches the team that operates them.
Data Protection Officer
SafeBets has not appointed a Data Protection Officer, as it is not required to do so under applicable data protection laws. For any question relating to privacy or data protection, use the contact details above.